NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

hokieguy's avatar
hokieguy
Aspirant
Dec 12, 2012

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!

16 Replies

Replies have been turned off for this discussion
  • mdgm wrote:
    When you hot-add a drive the ReadyNAS wipes it and adds it to the array.


    OK so the resync is normal then.

    Is there a better way? Let it boot fully on 2 drives, shut down, re-add the 3rd drive while off?
  • mdgm-ntgr's avatar
    mdgm-ntgr
    NETGEAR Employee Retired
    If the drives become out of sync, a resync would be needed anyway. So not sure that would help here. Obviously too late for the first drive.
  • I never followed up on this - I pulled each drive independently and none was the source of the noise, it must have been the fan? In any event, the unit quieted back down on its own and seems to be running normally again.

    Side question - I still have the failed drive I pulled a couple months ago. Is there anything I should do in terms of data security before I trash it? Is it even possible for someone to extract useful data from 1 drive of a 3 drive NAS? Should I take a hammer to it just to be safe?

    Thanks!
  • mdgm-ntgr's avatar
    mdgm-ntgr
    NETGEAR Employee Retired
    Your data wouldn't be able to be recovered just off that disk. Anyway, if you want and if the drive still kind of works (not completely dead) you could write zeroes to the start of the disk. That would be wipe the partition table off the disk. You could then format it with say NTFS and someone looking at the disk may think it was taken from a Windows machine rather than from a NAS.
  • StephenB's avatar
    StephenB
    Guru - Experienced User
    mdgm wrote:
    Your data wouldn't be able to be recovered just off that disk. Anyway, if you want and if the drive still kind of works (not completely dead) you could write zeroes to the start of the disk. That would be wipe the partition table off the disk. You could then format it with say NTFS and someone looking at the disk may think it was taken from a Windows machine rather than from a NAS.
    Or zero the entire drive. WD lifeguard will do that (and that function is not limited to WDC disks).

NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology! 

Join Us!

ProSupport for Business

Comprehensive support plans for maximum network uptime and business peace of mind.

 

Learn More