NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
hokieguy
Dec 12, 2012Aspirant
Identifying a failing drive
Hi all,
I'm running an original NV with 3x1TB drives. In the last day or so, one of the drives has gotten pretty noisy - it sounds almost like a drive is constantly running and the normal noise that a running drive makes is much louder than usual. Problem is, I don't know which drive it is. RAIDAR shows no issues, the health checks in Frontview are OK. I rebooted and did a volume scan which had no errors. I'm thinking I'll go ahead and order a replacement drive since something weird is definitely going on.
Any suggestions on best way to ID the drive with the issue? If I power the NAS off, pop out drive 1, and power up.... everything will be OK, right? Then I can repeat this process with each drive to see which one is the culprit?
Any bets on which drive is the bad/failing/noisy one based on these SMART checks?
Disk 1
Model: ST31000340NS
Serial: 9QJ4DVVQ
Firmware: SN06
SMART Attribute
Spin Up Time 0
Start Stop Count 35
Reallocated Sector Count 0
Power On Hours 18067
Spin Retry Count 0
Power Cycle Count 35
End-to-End Error 0
Reported Uncorrect 0
Command Timeout 0
High Fly Writes 0
Airflow Temperature Cel 32
Temperature Celsius 32
Current Pending Sector 0
Offline Uncorrectable 0
UDMA CRC Error Count 0
ATA Error Count 0
Extended Attribute
Hot-add events 0
Hot-remove events 0
Lp stat events 11
Power glitches 0
Hard disk resets 0
Retries 0
Repaired sectors 0
Disk 2
Model: ST31000340NS
Serial: 5QJ0210S
Firmware: SN03
SMART Attribute
Spin Up Time 0
Start Stop Count 108
Reallocated Sector Count 11
Power On Hours 40855
Spin Retry Count 3
Power Cycle Count 108
End-to-End Error 0
Reported Uncorrect 0
Command Timeout 2
High Fly Writes 0
Airflow Temperature Cel 34
Temperature Celsius 34
Current Pending Sector 286
Offline Uncorrectable 286
UDMA CRC Error Count 0
ATA Error Count 0
Extended Attribute
Hot-add events 0
Hot-remove events 0
Lp stat events 0
Power glitches 0
Hard disk resets 0
Retries 0
Repaired sectors 0
Disk 3
Model: WDC WD1001FALS-00J7B0
Serial: WD-WMATV6875260
Firmware: 05.00K05
SMART Attribute
Raw Read Error Rate 0
Spin Up Time 8441
Start Stop Count 54
Reallocated Sector Count 0
Seek Error Rate 0
Power On Hours 19825
Spin Retry Count 0
Calibration Retry Count 0
Power Cycle Count 52
Power-Off Retract Count 51
Load Cycle Count 54
Temperature Celsius 33
Reallocated Event Count 0
Current Pending Sector 0
Offline Uncorrectable 0
UDMA CRC Error Count 0
Multi Zone Error Rate 0
ATA Error Count 30
Extended Attribute
Hot-add events 0
Hot-remove events 0
Lp stat events 0
Power glitches 0
Hard disk resets 0
Retries 0
Repaired sectors 0
Thanks!
I'm running an original NV with 3x1TB drives. In the last day or so, one of the drives has gotten pretty noisy - it sounds almost like a drive is constantly running and the normal noise that a running drive makes is much louder than usual. Problem is, I don't know which drive it is. RAIDAR shows no issues, the health checks in Frontview are OK. I rebooted and did a volume scan which had no errors. I'm thinking I'll go ahead and order a replacement drive since something weird is definitely going on.
Any suggestions on best way to ID the drive with the issue? If I power the NAS off, pop out drive 1, and power up.... everything will be OK, right? Then I can repeat this process with each drive to see which one is the culprit?
Any bets on which drive is the bad/failing/noisy one based on these SMART checks?
Disk 1
Model: ST31000340NS
Serial: 9QJ4DVVQ
Firmware: SN06
SMART Attribute
Spin Up Time 0
Start Stop Count 35
Reallocated Sector Count 0
Power On Hours 18067
Spin Retry Count 0
Power Cycle Count 35
End-to-End Error 0
Reported Uncorrect 0
Command Timeout 0
High Fly Writes 0
Airflow Temperature Cel 32
Temperature Celsius 32
Current Pending Sector 0
Offline Uncorrectable 0
UDMA CRC Error Count 0
ATA Error Count 0
Extended Attribute
Hot-add events 0
Hot-remove events 0
Lp stat events 11
Power glitches 0
Hard disk resets 0
Retries 0
Repaired sectors 0
Disk 2
Model: ST31000340NS
Serial: 5QJ0210S
Firmware: SN03
SMART Attribute
Spin Up Time 0
Start Stop Count 108
Reallocated Sector Count 11
Power On Hours 40855
Spin Retry Count 3
Power Cycle Count 108
End-to-End Error 0
Reported Uncorrect 0
Command Timeout 2
High Fly Writes 0
Airflow Temperature Cel 34
Temperature Celsius 34
Current Pending Sector 286
Offline Uncorrectable 286
UDMA CRC Error Count 0
ATA Error Count 0
Extended Attribute
Hot-add events 0
Hot-remove events 0
Lp stat events 0
Power glitches 0
Hard disk resets 0
Retries 0
Repaired sectors 0
Disk 3
Model: WDC WD1001FALS-00J7B0
Serial: WD-WMATV6875260
Firmware: 05.00K05
SMART Attribute
Raw Read Error Rate 0
Spin Up Time 8441
Start Stop Count 54
Reallocated Sector Count 0
Seek Error Rate 0
Power On Hours 19825
Spin Retry Count 0
Calibration Retry Count 0
Power Cycle Count 52
Power-Off Retract Count 51
Load Cycle Count 54
Temperature Celsius 33
Reallocated Event Count 0
Current Pending Sector 0
Offline Uncorrectable 0
UDMA CRC Error Count 0
Multi Zone Error Rate 0
ATA Error Count 30
Extended Attribute
Hot-add events 0
Hot-remove events 0
Lp stat events 0
Power glitches 0
Hard disk resets 0
Retries 0
Repaired sectors 0
Thanks!
16 Replies
Replies have been turned off for this discussion
- de_niroGuideremove this one which is in very bad condition
Disk 2
Model: ST31000340NS
Serial: 5QJ0210S
Firmware: SN03
Current Pending Sector 286 - hokieguyAspirantThanks, I suspected Drive 2 was the bad one, as well - based on what you pointed out, also it's the oldest drive by far. I suppose I can't complain when the drive has over 4.5 years of nearly 24x7 use on it! A new WD Red is on the way as a replacement.
- gibxxiGuideThis is also a SMART value you should note with concern:
Reallocated Sector Count 11
That value indicates sectors that have ALREADY gone bad and have been reallocated with spare sectors by the drive itself. As soon as you see this value go above 0, you need to keep an eye on it and budget for a replacement ASAP. - StephenBGuru - Experienced User
Netgear suggests replacement when the count reaches 50. Sometimes a drive will have a few of these, and then stabilize - other times the count just climbs like crazy.gibxxi wrote: This is also a SMART value you should note with concern:
Reallocated Sector Count 11
That value indicates sectors that have ALREADY gone bad and have been reallocated with spare sectors by the drive itself. As soon as you see this value go above 0, you need to keep an eye on it and budget for a replacement ASAP.
Pending sector count is related to reallocated sector count, for replacement purposes you should sum them! So definitely replace this drive, since the combined count is way over the 50 limit.
Sectors are reallocated when a write fails, pending sector count is incremented when read fails. - hokieguyAspirantThanks for the additional info. The drive has actually quieted back down, but I'll be replacing it as soon as the new drive gets here anyway. Should be within the next 1-2 days.
Just curious - if this drive is in such bad shape, why didn't I get any kind of alerts from the NAS? I have had one other drive fail in the past and got warnings from the NAS that it was failing and instructing me to replace it ASAP. I guess there are certain conditions that must be met to trigger an alert, and this time, despite the drive being unhealthy, those conditions weren't met? - StephenBGuru - Experienced UserAlthough the NAS ought to give alerts on pending sector counts, it doesn't. You should have log entries on the reallocated sectors, and if you have email alerts configured you should have gotten them as the count increased.
- hokieguyAspirantLogs show the increase in reallocated sectors happened back in May and June 2012, no changes since then. I do have email alerts enabled - I honestly don't remember if I got alerts about the reallocated sectors increasing back then or not. I may have, and then not worried about it once they stopped at 11.
- gibxxiGuideYou may be lucky. I've always treated HDD's that exhibit bad sectors like I used to do with floppy disks. If it's a surface error, don't trust it. And be ready to replace it. But, that's me. Your data, only you can judge how much risk your prepared to live with.
:) - hokieguyAspirantHi again all, just a month or so later, and I appear to have another failing drive. The NAS is again really noisy but the SMART info doesn't show anything that's concerning to me - no retries pending counts or anything. I shut the NAS down and pulled drive #1 as I suspected it might be the bad one (oldest drive) and restarted. NAS was still noisy so as it was booting, I plugged #1 back in. It is now doing a full resync of drive #1 - is that normal? I thought it would just realize it was the same drive and be on its way.
Is there a better way to ID the noisy drive than just repeating the above process with #2 and #3?
Thanks! - mdgm-ntgrNETGEAR Employee RetiredWhen you hot-add a drive the ReadyNAS wipes it and adds it to the array.
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!