On Tue, Jan 02, 2007 at 10:40:01AM -0600, Reid Priedhorsky wrote:
...
> Jan 2 07:38:13 reidster kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> Jan 2 07:38:17 reidster kernel: hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=8152823, high=0, low=8152823, sector=8152822
> Jan 2 07:38:17 reidster kernel: ide: failed opcode was: unknown
> Jan 2 07:38:17 reidster kernel: end_request: I/O error, dev hda, sector 8152822
> Jan 2 07:38:17 reidster kernel: EXT3-fs error (device hda5): ext3_get_inode_loc: unable to read inode block - inode=228624, block=458828
> Jan 2 07:38:17 reidster kernel: Remounting filesystem read-only
> Jan 2 07:38:17 reidster kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> Jan 2 07:38:17 reidster kernel: hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=8152823, high=0, low=8152823, sector=8152822
> Jan 2 07:38:17 reidster kernel: ide: failed opcode was: unknown
> Jan 2 07:38:17 reidster kernel: end_request: I/O error, dev hda, sector 8152822
> Jan 2 07:38:17 reidster kernel: EXT3-fs error (device hda5): ext3_get_inode_loc: unable to read inode block - inode=228626, block=458828
You have an error on the same sector there (8152822), this sector is
probably bad.
> And smartctl -a /dev/hda reports:
...
> SMART Attributes Data Structure revision number: 10
> Vendor Specific SMART Attributes with Thresholds:
> ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
> 1 Raw_Read_Error_Rate 0x000f 054 049 006 Pre-fail Always - 157409182
> 3 Spin_Up_Time 0x0003 096 096 000 Pre-fail Always - 0
> 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 2
> 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 15
> 7 Seek_Error_Rate 0x000f 081 060 030 Pre-fail Always - 153797081
> 9 Power_On_Hours 0x0032 083 083 000 Old_age Always - 15442
> 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0
> 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 21
> 194 Temperature_Celsius 0x0022 030 056 000 Old_age Always - 30
> 195 Hardware_ECC_Recovered 0x001a 054 049 000 Old_age Always - 157409182
> 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0
> 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0
> 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0
> 200 Multi_Zone_Error_Rate 0x0000 100 253 000 Old_age Offline - 0
> 202 TA_Increase_Count 0x0032 100 253 000 Old_age Always - 0
>
> I'm currently running a long self-test, and I'll re-post if the report
> then shows anything.
>
> Any help would be much appreciated.
My guess. You had a few bad sectors; you rebooted, fsck was not happy a
wrote on those sectors ; the controller detected them and relocated them
(you have a relocated count of 15); everything is fine.
The surface test will tell you (the long test) if there are still some
sectors unreadable. But most likely everything has been fixed. If a
sector is bad and the test failed, you can try to play with dd and force
a reloc of that sector but the chances of screw-up are pretty high.
Anyway, you drive is at least 1.5year old (uptime about that time), and
bad sectors do happen. I would not panic since you have backups (because
you _do_ have backups) :-)
jacques
Attachment:
signature.asc
Description: Digital signature