From: Alexey T. <al...@fr...> - 2006-03-12 06:14:09
|
I've got a: Device Model: Maxtor 96147H8 Serial Number: M0000000 Firmware Version: BAC51B90 ...that has: 196 Reallocated_Event_Count 0x0012 253 253 000 Old_age Always - 0 197 Current_Pending_Sector 0x0010 184 183 000 Old_age Offline - 69 198 Offline_Uncorrectable 0x0012 253 252 000 Old_age Always - 0 smartd keeps warning me about the pending sectors, but they're not getting remapped. I tried to read the whole disk (with dd) a coule of times, hoping that they'd get remapped, but nothing happened. Is it normal for sectors to stay pending and not get remapped? Am I misunderstanding what pending means? Alexey |
From: Bruno W. I. <br...@wo...> - 2006-03-13 03:33:58
|
On Sun, Mar 12, 2006 at 06:13:55 +0000, Alexey Toptygin <al...@fr...> wrote: > > smartd keeps warning me about the pending sectors, but they're not getting > remapped. I tried to read the whole disk (with dd) a coule of times, > hoping that they'd get remapped, but nothing happened. Is it normal for > sectors to stay pending and not get remapped? Am I misunderstanding what > pending means? Unless it is able to get a good read of the sectors, reading the disk isn't going to help. When you are ready to give up on the bad sectors, you will want to overwrite them, which will allow the disk to remap them. |
From: Alexey T. <al...@fr...> - 2006-03-13 13:08:49
|
On Sun, 12 Mar 2006, Bruno Wolff III wrote: > Unless it is able to get a good read of the sectors, reading the disk > isn't going to help. When you are ready to give up on the bad sectors, > you will want to overwrite them, which will allow the disk to remap them. OK, thanks. How can I find out which sectors are bad? smartctl says error logging is not supported: > Error logging capability: (0x00) Error logging NOT supported. > No General Purpose Logging support. although an error log is still read out. All the errors are of the form: > Error 36507 occurred at disk power-on lifetime: 29362 hours (1223 days + 10 hours) > When the command that caused the error occurred, the device was in an unknown state. > > After command completion occurred, registers were: > ER ST SC SN CL CH DH > -- -- -- -- -- -- -- > 04 51 00 01 00 00 a0 Error: ABRT > > Commands leading to the command that caused the error were: > CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name > -- -- -- -- -- -- -- -- ---------------- -------------------- > a1 ff 00 01 00 00 a0 08 29d+12:28:07.152 IDENTIFY PACKET DEVICE > c4 ff 01 01 00 00 a0 08 29d+12:28:07.136 READ MULTIPLE > 91 ff ff 00 00 00 af 08 29d+12:28:07.136 INITIALIZE DEVICE PARAMETERS [OBS-6] > c6 ff 10 00 00 00 a0 00 29d+12:28:06.816 SET MULTIPLE MODE > 91 ff ff 00 00 00 af 00 29d+12:28:06.816 INITIALIZE DEVICE PARAMETERS [OBS-6] Even after I read the entire disk with dd, no sector read errors seem to show up - just these IDENTIFY PACKET DEVICE errors (which I assume are caused by some harware autodetection stuff at boot trying to figure out if this is an ATAPI device)? Maybe I should just do a `badblocks -n` to read and then rewrite the whole disk? Alexey |
From: Bruce A. <ba...@gr...> - 2006-03-13 16:46:30
|
Your disk may be one of those ones that does not 'reset' the raw value of Current_Pending_Sector to zero, even when the sectors have been successfullly remapped. Cheers, Bruce On Sun, 12 Mar 2006, Alexey Toptygin wrote: > > I've got a: > > Device Model: Maxtor 96147H8 > Serial Number: M0000000 > Firmware Version: BAC51B90 > > ...that has: > > 196 Reallocated_Event_Count 0x0012 253 253 000 Old_age Always > - 0 > 197 Current_Pending_Sector 0x0010 184 183 000 Old_age Offline > - 69 > 198 Offline_Uncorrectable 0x0012 253 252 000 Old_age Always > - 0 > > smartd keeps warning me about the pending sectors, but they're not getting > remapped. I tried to read the whole disk (with dd) a coule of times, hoping > that they'd get remapped, but nothing happened. Is it normal for sectors to > stay pending and not get remapped? Am I misunderstanding what pending means? > > Alexey > > > ------------------------------------------------------- > This SF.Net email is sponsored by xPML, a groundbreaking scripting language > that extends applications into web and mobile media. Attend the live webcast > and join the prime developer group breaking into this new coding territory! > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 > _______________________________________________ > Smartmontools-support mailing list > Sma...@li... > https://lists.sourceforge.net/lists/listinfo/smartmontools-support > |
From: Alexey T. <al...@fr...> - 2006-03-13 16:51:00
|
On Mon, 13 Mar 2006, Bruce Allen wrote: > Your disk may be one of those ones that does not 'reset' the raw value of > Current_Pending_Sector to zero, even when the sectors have been successfullly > remapped. I don't know - the raw value of Reallocated_Event_Count is still 0, so I think I just haven't gotten the remapping to happen yet. Alexey |
From: Bruce A. <ba...@gr...> - 2006-03-13 17:36:27
|
>> Your disk may be one of those ones that does not 'reset' the raw value of >> Current_Pending_Sector to zero, even when the sectors have been >> successfullly remapped. > > I don't know - the raw value of Reallocated_Event_Count is still 0, so I > think I just haven't gotten the remapping to happen yet. Or the sectors may have become readable again. Does your disk pass a long self-test? Bruce |
From: Alexey T. <al...@fr...> - 2006-03-16 13:40:37
|
On Mon, 13 Mar 2006, Bruce Allen wrote: >> I don't know - the raw value of Reallocated_Event_Count is still 0, so I >> think I just haven't gotten the remapping to happen yet. > > Or the sectors may have become readable again. Does your disk pass a long > self-test? Yes, it passed the extended selftest with no errors: # 1 Extended offline Completed without error 00% 29445 - so I guess the following is true: >>> Your disk may be one of those ones that does not 'reset' the raw value of >>> Current_Pending_Sector to zero, even when the sectors have been >>> successfullly remapped. It is configured like so: DEVICESCAN -m root -M exec /usr/share/smartmontools/smartd-runner and is currently spamming my logs like so: Mar 16 04:25:30 rain smartd[5492]: Device: /dev/hdc, 69 Currently unreadable (pending) sectors Mar 16 04:55:31 rain smartd[5492]: Device: /dev/hdc, 69 Currently unreadable (pending) sectors Mar 16 05:25:31 rain smartd[5492]: Device: /dev/hdc, 69 Currently unreadable (pending) sectors I want it to only report changes in the unreadable pending (and I guess the offline uncorrectable) sector count; but I want the other error reporting to remain active. Is this what I should change the config to? DEVICESCAN -a -C 0 -U 0 -m root -M exec /usr/share/smartmontools/smartd-runner Alexey |
From: Bruce A. <ba...@gr...> - 2006-03-17 03:15:40
|
> I want it to only report changes in the unreadable pending (and I guess the > offline uncorrectable) sector count; but I want the other error reporting to > remain active. Is this what I should change the config to? > > DEVICESCAN -a -C 0 -U 0 -m root -M exec > /usr/share/smartmontools/smartd-runner Exactly right! Cheers, Bruce |