Why isn't the sector reallocating?
in [Storage]
|
Prev: Bad Sectors
Next: Recommendations for 1 TB drive?
From: Yousuf Khan on 20 Jan 2010 11:30 Here's the SMART report from Everest about this drive. It's got one Pending Sector, one Offline Uncorrectable Sector, and one Reallocated Sector already. So one sector got reallocated, while the other one is pending and/or uncorrectable. What would the explanation for this be? Yousuf Khan > [ Maxtor 6L300R0 (L61F02TH) ] > > 03 Spin Up Time 63 185 178 24932 OK: Value is normal > 04 Start/Stop Count 0 253 253 789 OK: Always passing > 05 Reallocated Sector Count 63 253 253 1 OK: Value is normal > 06 Read Channel Margin 100 253 253 0 OK: Value is normal > 07 Seek Error Rate 0 253 252 0 OK: Always passing > 08 Seek Time Performance 187 245 239 60582 OK: Value is normal > 09 Power-On Time Count 0 179 179 31859 OK: Always passing > 0A Spin Retry Count 157 253 252 0 OK: Value is normal > 0B Calibration Retry Count 223 253 252 0 OK: Value is normal > 0C Power Cycle Count 0 251 251 1165 OK: Always passing > C0 Power-Off Retract Count 0 253 253 0 OK: Always passing > C1 Load/Unload Cycle Count 0 253 253 0 OK: Always passing > C2 Temperature 0 42 253 35 OK: Always passing > C3 Hardware ECC Recovered 0 253 252 24009 OK: Always passing > C4 Reallocation Event Count 0 253 253 0 OK: Always passing > C5 Current Pending Sector Count 0 253 253 1 OK: Always passing > C6 Off-Line Uncorrectable Sector Count 0 252 252 1 OK: Always passing > C7 Ultra ATA CRC Error Rate 0 1 1 13996 OK: Always passing > C8 Write Error Rate 0 253 252 0 OK: Always passing > C9 <vendor-specific> 0 253 252 2 OK: Always passing > CA <vendor-specific> 0 253 252 0 OK: Always passing > CB <vendor-specific> 180 253 252 0 OK: Value is normal > CC <vendor-specific> 0 253 252 0 OK: Always passing > CD <vendor-specific> 0 253 252 0 OK: Always passing > CF <vendor-specific> 0 253 252 0 OK: Always passing > D0 <vendor-specific> 0 253 252 0 OK: Always passing > D1 <vendor-specific> 0 234 234 232 OK: Always passing > D2 <vendor-specific> 0 253 252 0 OK: Always passing > D3 <vendor-specific> 0 253 252 0 OK: Always passing > D4 <vendor-specific> 0 253 252 0 OK: Always passing
From: Rod Speed on 20 Jan 2010 14:41 Yousuf Khan <bbbl67(a)spammenot.yahoo.com> wrote > Here's the SMART report from Everest about this drive. It's got one Pending Sector, one Offline Uncorrectable Sector, > and one Reallocated Sector already. So one sector got reallocated, while the other one is pending and/or > uncorrectable. What would the explanation for this be? Sectors are only ever reallocated on writes to that sector, essentially so you dont lose what data is in them and can attempt to get the data by repeated reads etc. So the pending sector has not been written to since it went bad, or isnt bad reliably and sometimes is fine. The offline uncorrectable sector means that that sector cant be reallocated. Given that its a Maxtor, I'd bin the drive with that many bads. You have quite a few errors on the cable too. >> [ Maxtor 6L300R0 (L61F02TH) ] >> >> 03 Spin Up Time 63 185 178 24932 OK: Value is normal >> 04 Start/Stop Count 0 253 253 789 OK: Always passing >> 05 Reallocated Sector Count 63 253 253 1 OK: Value is normal >> 06 Read Channel Margin 100 253 253 0 OK: Value is normal >> 07 Seek Error Rate 0 253 252 0 OK: Always passing >> 08 Seek Time Performance 187 245 239 60582 OK: Value is normal >> 09 Power-On Time Count 0 179 179 31859 OK: Always passing >> 0A Spin Retry Count 157 253 252 0 OK: Value is normal >> 0B Calibration Retry Count 223 253 252 0 OK: Value is normal >> 0C Power Cycle Count 0 251 251 1165 OK: Always passing >> C0 Power-Off Retract Count 0 253 253 0 OK: Always passing >> C1 Load/Unload Cycle Count 0 253 253 0 OK: Always passing >> C2 Temperature 0 42 253 35 OK: Always passing >> C3 Hardware ECC Recovered 0 253 252 24009 OK: Always passing >> C4 Reallocation Event Count 0 253 253 0 OK: Always passing >> C5 Current Pending Sector Count 0 253 253 1 OK: Always passing >> C6 Off-Line Uncorrectable Sector Count 0 252 252 1 OK: Always passing >> C7 Ultra ATA CRC Error Rate 0 1 1 13996 OK: Always passing >> C8 Write Error Rate 0 253 252 0 OK: Always passing >> C9 <vendor-specific> 0 253 252 2 OK: Always passing >> CA <vendor-specific> 0 253 252 0 OK: Always passing >> CB <vendor-specific> 180 253 252 0 OK: Value is normal >> CC <vendor-specific> 0 253 252 0 OK: Always passing >> CD <vendor-specific> 0 253 252 0 OK: Always passing >> CF <vendor-specific> 0 253 252 0 OK: Always passing >> D0 <vendor-specific> 0 253 252 0 OK: Always passing >> D1 <vendor-specific> 0 234 234 232 OK: Always passing >> D2 <vendor-specific> 0 253 252 0 OK: Always passing >> D3 <vendor-specific> 0 253 252 0 OK: Always passing >> D4 <vendor-specific> 0 253 252 0 OK: Always passing
From: Rod Speed on 20 Jan 2010 15:52 Rod Speed <rod.speed.aaa(a)gmail.com> wrote > Yousuf Khan <bbbl67(a)spammenot.yahoo.com> wrote >> Here's the SMART report from Everest about this drive. It's got one Pending Sector, one Offline Uncorrectable Sector, >> and one Reallocated Sector already. So one sector got reallocated, while the other one is pending and/or >> uncorrectable. What would the explanation for this be? > Sectors are only ever reallocated on writes to that sector, > essentially so you dont lose what data is in them and can > attempt to get the data by repeated reads etc. > So the pending sector has not been written to since it > went bad, or isnt bad reliably and sometimes is fine. > The offline uncorrectable sector means that that sector cant be reallocated. Sorry, my brain fart there, thats actually a bad found in the offline scan. > Given that its a Maxtor, I'd bin the drive with that many bads. > You have quite a few errors on the cable too. >>> [ Maxtor 6L300R0 (L61F02TH) ] >>> >>> 03 Spin Up Time 63 185 178 24932 OK: Value is normal >>> 04 Start/Stop Count 0 253 253 789 OK: Always passing >>> 05 Reallocated Sector Count 63 253 253 1 OK: Value is normal >>> 06 Read Channel Margin 100 253 253 0 OK: Value is normal >>> 07 Seek Error Rate 0 253 252 0 OK: Always passing >>> 08 Seek Time Performance 187 245 239 60582 OK: Value is normal >>> 09 Power-On Time Count 0 179 179 31859 OK: Always passing >>> 0A Spin Retry Count 157 253 252 0 OK: Value is normal >>> 0B Calibration Retry Count 223 253 252 0 OK: Value is normal >>> 0C Power Cycle Count 0 251 251 1165 OK: Always passing >>> C0 Power-Off Retract Count 0 253 253 0 OK: Always passing >>> C1 Load/Unload Cycle Count 0 253 253 0 OK: Always passing >>> C2 Temperature 0 42 253 35 OK: Always passing >>> C3 Hardware ECC Recovered 0 253 252 24009 OK: Always passing >>> C4 Reallocation Event Count 0 253 253 0 OK: Always passing >>> C5 Current Pending Sector Count 0 253 253 1 OK: Always passing >>> C6 Off-Line Uncorrectable Sector Count 0 252 252 1 OK: Always passing >>> C7 Ultra ATA CRC Error Rate 0 1 1 13996 OK: Always passing >>> C8 Write Error Rate 0 253 252 0 OK: Always passing >>> C9 <vendor-specific> 0 253 252 2 OK: Always passing >>> CA <vendor-specific> 0 253 252 0 OK: Always passing >>> CB <vendor-specific> 180 253 252 0 OK: Value is normal >>> CC <vendor-specific> 0 253 252 0 OK: Always passing >>> CD <vendor-specific> 0 253 252 0 OK: Always passing >>> CF <vendor-specific> 0 253 252 0 OK: Always passing >>> D0 <vendor-specific> 0 253 252 0 OK: Always passing >>> D1 <vendor-specific> 0 234 234 232 OK: Always passing >>> D2 <vendor-specific> 0 253 252 0 OK: Always passing >>> D3 <vendor-specific> 0 253 252 0 OK: Always passing >>> D4 <vendor-specific> 0 253 252 0 OK: Always passing
From: Yousuf Khan on 20 Jan 2010 16:56 Rod Speed wrote: > Sectors are only ever reallocated on writes to that sector, > essentially so you dont lose what data is in them and can > attempt to get the data by repeated reads etc. Actually, this drive has just recently been reformatted, so there's really no data on it to lose. I used a quick ntfs format, rather than a full one. I ran a quick SMART test on it too, should I run the full test? > You have quite a few errors on the cable too. Yeah, this was one of my old slave IDE drives, I had been running it back on the IDE cable again for a few months. At some point, it used to drop out quite a lot if there was any sort of heavy usage of it. I had to remove the master and make this the master to get the transfers done properly. I'm now running them back through the SATA converter again. Yousuf Khan
From: Rod Speed on 20 Jan 2010 17:20
Yousuf Khan wrote > Rod Speed wrote >> Sectors are only ever reallocated on writes to that sector, >> essentially so you dont lose what data is in them and can >> attempt to get the data by repeated reads etc. > Actually, this drive has just recently been reformatted, so there's really no data on it to lose. I used a quick ntfs > format, rather than a full one. A full one should reallocate that pending sector. > I ran a quick SMART test on it too, should I run the full test? Wouldnt do any harm, it might well show up some more bads and provide more evidence to bin the drive. >> You have quite a few errors on the cable too. > Yeah, this was one of my old slave IDE drives, I had been running it > back on the IDE cable again for a few months. At some point, it used > to drop out quite a lot if there was any sort of heavy usage of it. I > had to remove the master and make this the master to get the > transfers done properly. > I'm now running them back through the SATA converter again. OK, it may just be a residual from the old PATA cable use. |