adammerkley Posted December 10, 2011 Share Posted December 10, 2011 Noticed yesterday that the Pending Sector count on my parity disk (2TB Seagate LP drive that I bought on Black Friday) was 24. This surprised me because the drive successfully passed 3 preclear cycles only 2 weeks ago... To troubleshoot, I did this (nevermind the risk of running without a parity disk temporarily...): Stopped the array Unassigned the parity disk Restarted the array without parity disk Stopped the array Reassigned parity disk Restarted the array, selecting that I wanted to rebuild parity. When the parity sync was done, I noted that the drive showed 0 pending sectors. Wanting to now read all the sectors on the drive, I ran a nocorrect parity check. The parity check is complete and the drive still shows 0 pending sectors. Thoughts? Link to comment
WeeboTech Posted December 10, 2011 Share Posted December 10, 2011 on read they become "pending sectors" Sectors pending reallocation at the next write. So when you recreated parity, the sectors were written to and thus reallocated somewhere else. I would do a periodic smart test -t long during an idle period. (disable spin down). I would make sure I had monthly parity checks enabled. If pending sectors grows, then consider RMA'ing the drive you'll need the SEATOOLS boot cd. Link to comment
lionelhutz Posted December 10, 2011 Share Posted December 10, 2011 Do you now have 24 reallocated sectors? Link to comment
adammerkley Posted December 10, 2011 Author Share Posted December 10, 2011 Do you now have 24 reallocated sectors? I guess I should have mentioned in the original post, no, there are no reallocated sectors... 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 118 099 006 Pre-fail Always - 181165264 3 Spin_Up_Time 0x0003 093 092 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 75 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 061 060 030 Pre-fail Always - 1477444 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 664 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 22 183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0 184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 188 Command_Timeout 0x0032 100 100 000 Old_age Always - 0 189 High_Fly_Writes 0x003a 092 092 000 Old_age Always - 8 190 Airflow_Temperature_Cel 0x0022 074 064 045 Old_age Always - 26 (Lifetime Min/Max 21/35) 191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 13 193 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 75 194 Temperature_Celsius 0x0022 026 040 000 Old_age Always - 26 (0 21 0 0) 195 Hardware_ECC_Recovered 0x001a 031 017 000 Old_age Always - 181165264 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 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 19091129630976 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 2913237044 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 3694510915 Link to comment
lionelhutz Posted December 10, 2011 Share Posted December 10, 2011 Other people have had that happen. There's no real explanation for it. Peter Link to comment
WeeboTech Posted December 10, 2011 Share Posted December 10, 2011 I suppose that since you wrote and refreshed them, the were not weak sectors any longer (by the firmware's standards). I would still suggest periodic smart tests. Definitely a monthly parity check. I might even institute monthly a badblocks readonly test. The only problem with that is /dev/md0 does not exist without doing a manual mknod. Link to comment
Joe L. Posted December 10, 2011 Share Posted December 10, 2011 Other people have had that happen. There's no real explanation for it. Peter Actually, there is. Before re-allocating a sector, the SMART firmware will attempt to write to the original sector and verify it can them be read from there. If successful the original "write" was faulty and there is no need to re-allocate the sector. If there are lots of sectors that are un-readable, but can be successfully re-written, keep an eye on the drive. It might indicate a bad drive, or bad voltage regulation from the power supply. Good that it now works. Was this a drive that had been pre-cleared??? It would help if I read what you wrote. I'd suspect it wrote the sectors improperly when it write the initial parity. What power supply (specific make/model) and what number of green/non-green drives are you running?? Joe L. Link to comment
adammerkley Posted December 11, 2011 Author Share Posted December 11, 2011 What power supply (specific make/model) and what number of green/non-green drives are you running?? I'll have to look next time I pop the server open, but it's a 650W Antec. Not single 12V rail 4 green, 5 non-green. Those numbers will flip once the drive I'm preclearing is done. Link to comment
dlandon Posted December 11, 2011 Share Posted December 11, 2011 Thats very curious. I just replaced an Antec 650w PSU several months ago with a new OCZ 850w modular PSU. I had a lot of drive issues and ended up RMA'ing drives and bought a new one to replace drives with a lot of errors including Pending Sectors. Two of my new drives were ticking up re-allocated sectors - several every few days. Once I changed out the Antec PSU for the new OCZ 850w PSU, all errors immediately stopped. Haven't had a single issue with any of the eight drives in my server since. Wonder if the Antec PSU has an issue? Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.