July 6, 201312 yr Can someone tell me if this drive is dying based on the smart report attached. Thanks smart_report_disk4.txt
July 6, 201312 yr Dying is an understatement. Get a replacement NOW ... you're definitely living on borrowed time if you have any data on that drive. 37 reallocated sectors isn't all that catastrophic -- but 1293 MORE pending reallocation is a very bad sign.
July 6, 201312 yr The drive does not look good. unRAID cannot function correctly if any drive has Current_Pending_Sector RAW_VALUE greater than zero. pre-clear might reduce the Current_Pending_Sector to zero. Even if pre-clear works, the drive should be watched.
July 6, 201312 yr Author My parity check on July 1st had 0 errors so I should be able to just swap it out and be ok, right?
July 6, 201312 yr My parity check on July 1st had 0 errors so I should be able to just swap it out and be ok, right? Yes.
July 6, 201312 yr Author OK I just replaced it. Just waiting for it to rebuild the drive. Data rebuild in progress. Fingers crossed
July 6, 201312 yr Glad that it worked out for you I never experienced a drive failing on me, are you getting some kind of notice from unraid if a smart report is showing errors or for you have to check for yourself periodically?
July 6, 201312 yr Author I have a script that runs a smart report weekly. I believe this drive is failing as well. Can someone confirm? smart_report_disk2.txt
July 6, 201312 yr I have a script that runs a smart report weekly. I believe this drive is failing as well. Can someone confirm? It's got a few errors .. and 3 pending reallocations (this will be reallocated when you write to the drive). It's not at the "failed" point (yet), but I'd watch it and see if you get additional reallocations ... if so I'd replace it just to be safe. These are good drives to reformat and then use as backup drives.
July 6, 201312 yr Author So they can be reused? Not in unraid? What would I use the drive for? I assumed they were garbage because of the errors. What in the smart report tells you that the drive is hurting badly?
July 6, 201312 yr What in the smart report tells you that the drive is hurting badly? It's NOT "hurting badly" ... it simply has some sectors that need to be reallocated (the "pending sectors") ... which means they've failed and the drive's SMART system will use spare sectors to replace them. A few reallocated sectors is no big deal ... but what I suggested is that you watch to see if that gets worse => if so, then the drive is failing; if not, then it's fine.
July 6, 201312 yr The pending sectors need to resolved in order for unRAID to provide parity protection. Rebuild the drive onto itself in order to clear the pending sectors. Or replace the drive and run pre-clear on it.
July 6, 201312 yr Author Thanks guys. What in the log tells me that the drive is failed (should not be re-used) or the drive can be pre-cleared and re-used in the array I assume the log from the first drive I posted in the 1st thread should not be re-used. The 2nd one I will preclear
July 7, 201312 yr Author I assume this is the correct command to use for smart reports? smartctl -a -d ata /dev/sdc
July 7, 201312 yr Thanks guys. What in the log tells me that the drive is failed (should not be re-used) or the drive can be pre-cleared and re-used in the array I assume the log from the first drive I posted in the 1st thread should not be re-used. The 2nd one I will preclear Pre-clear them both. If the current pending sector drops to zero and the reallocated sectors count does not rise then the disk may be fine.
July 7, 201312 yr I assume this is the correct command to use for smart reports? smartctl -a -d ata /dev/sdc Or smartctl -a /dev/sdc
July 7, 201312 yr Author I precleared one of the disks and this was the output. Does not even look like it finished properly. This is with version 1.13 preclear script. Looks like an issue with the script maybe. Joe L... help ================================================================== 1.13 = unRAID server Pre-Clear disk /dev/sdh = cycle 1 of 1, partition start on sector 64 = Disk Pre-Clear-Read completed DONE = Step 1 of 10 - Copying zeros to first 2048k bytes DONE = Step 2 of 10 - Copying zeros to remainder of disk to clear it = **** This will take a while... you can follow progress below: = = = = = = = = Elapsed Time: 6:24:25 0+0 records in 0+0 records out 0 bytes (0 B) copied, 0.0125323 s, 0.0 kB/s ./preclear_disk.sh: line 642: let: percent_wrote=(0 / ): syntax error: operand expected (error token is ")") Wrote 0 bytes out of bytes (% Done) ./preclear_disk.sh: line 1849: / (1373192449 - 1373192422) / 1000000 : syntax error: operand expected (error token is "/ (1373192449 - 1373192422) / 1000000 ") ========================================================================1.13 == WDC WD20EARS-00MVWB0 WD-WMAZA3775121 == Disk /dev/sdh has been successfully precleared == with a starting sector of 64 ============================================================================ ./preclear_disk.sh: line 817: [: : integer expression expected ./preclear_disk.sh: line 817: [: : integer expression expected ./preclear_disk.sh: line 817: [: : integer expression expected ./preclear_disk.sh: line 817: [: : integer expression expected ./preclear_disk.sh: line 817: [: : integer expression expected ./preclear_disk.sh: line 817: [: : integer expression expected ./preclear_disk.sh: line 817: [: : integer expression expected ./preclear_disk.sh: line 817: [: : integer expression expected ./preclear_disk.sh: line 817: [: : integer expression expected ./preclear_disk.sh: line 817: [: : integer expression expected ./preclear_disk.sh: line 817: [: : integer expression expected ./preclear_disk.sh: line 817: [: : integer expression expected ./preclear_disk.sh: line 817: [: : integer expression expected ./preclear_disk.sh: line 817: [: : integer expression expected ./preclear_disk.sh: line 817: [: : integer expression expected ./preclear_disk.sh: line 817: [: : integer expression expected ./preclear_disk.sh: line 817: [: : integer expression expected ** Changed attributes in files: /tmp/smart_start_sdh /tmp/smart_finish_sdh ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 200 ok Spin_Up_Time = 205 ok Start_Stop_Count = 100 ok Reallocated_Sector_Ct = 200 ok Seek_Error_Rate = 200 ok Power_On_Hours = 77 ok Spin_Retry_Count = 100 ok Calibration_Retry_Count = 100 ok Power_Cycle_Count = 100 ok Power-Off_Retract_Count = 200 ok Load_Cycle_Count = 199 ok Temperature_Celsius = 123 ok Reallocated_Event_Count = 200 ok Current_Pending_Sector = 200 ok Offline_Uncorrectable = 200 ok UDMA_CRC_Error_Count = 200 ok Multi_Zone_Error_Rate = 200 ok No SMART attributes are FAILING_NOW 3 sectors were pending re-allocation before the start of the preclear. a change of -3 in the number of sectors pending re-allocation. 0 sectors had been re-allocated before the start of the preclear. a change of 0 in the number of sectors re-allocated. SMART overall-health status = root@Tower3:/boot/scripts#
July 7, 201312 yr Is this one ok to preclear and use again? Hard to say from the SMART report ... definitely has a fair number of reallocated sectors; but none are "pending", so it may have just been a bad area on the drive that's now been mapped out. I'd attach it to a PC and run Seagate's SeaTools -- run all of the tests, both long & short. If ZERO errors, then the drive is okay to use. If ANY errors I wouldn't use it.
July 8, 201312 yr Author It looks like the preclear script had a syntax error. No idea why. Maybe Joe can comment
Archived
This topic is now archived and is closed to further replies.