NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
ReadyNas NV+ Freezing Dead Drive?
I've had a ReadyNAS NV+ for a very long time and it has served me well. Lately it seems to freeze after running for about an hour and is unusable. All I can do is pull the power plug.
For the bri...
You shouldn't post public links to your logs, as there is some information in them that shouldn't be shared. I took the liberty of redacting your link. If you do want log analysis, the best way is to send a private message to one of the mods ( JohnCM_S or Marc_V ) and ask them to analyze them. You send a PM using the envelope icon on the upper right of the forum.
That said, I did take a look at your logs. You have one disk that is failing, and one that is marginal. I suggest replacing both. You can see the stats for yourself in disk_smart.log.
=== START OF INFORMATION SECTION === Model Family: Western Digital Caviar Green (Adv. Format) Device Model: WDC WD20EARS-00MVWB0 Serial Number: WD-WCAZA3720518 ... 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 184
and
Device Model: WDC WD20EARS-00MVWB0 Serial Number: WD-WCAZA3682468 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 11 198 Offline_Uncorrectable 0x0030 200 200 000 Old_age Offline - 4
WD-WCAZA3682468 has better stats (fewer pending sectors), and is the disk I think is marginal. Though the stats can be misleading.
The SATA reset actually was triggered by the first disk, even though that has no SMART errors. However, I'd still suggest replacing the other two and then see if the problem resolves. Per disk_smart.log there are no errors logged by hdc itself, so I am thinking errors in the other drives might have created issues on the SATA interface.
Oct 12 14:54:31 MERCURY kernel: :::::::::::::::::::Drive at position 1 found status 51, need retry.
Oct 12 14:54:31 MERCURY kernel: hdc: status timeout: status=0xd0 { Busy }
Oct 12 14:54:31 MERCURY kernel: ide: failed opcode was: unknown
Oct 12 14:54:31 MERCURY kernel: Drive error count too high, need reset, will wait padre_NSPIO to do the reset later.
Oct 12 14:54:31 MERCURY kernel: hdc: status timeout: status=0xd0 { Busy }
Oct 12 14:54:31 MERCURY kernel: ide: failed opcode was: unknown
Oct 12 14:54:31 MERCURY kernel: Drive error count too high, need reset, will wait padre_NSPIO to do the reset later.
Oct 12 14:54:31 MERCURY kernel: hdc: status timeout: status=0xd0 { Busy }
Oct 12 14:54:31 MERCURY kernel: ide: failed opcode was: unknown
Oct 12 14:54:31 MERCURY kernel: Failing rq 86a0dcc8 on hdc
...
Oct 12 14:55:13 MERCURY kernel: Reset sata channel 0
Oct 12 14:55:13 MERCURY kernel: ==== SATA init channel 0
Oct 12 14:55:13 MERCURY kernel: After INIT SATA channel 0, retry=105, sata=113, status=50
Oct 12 14:55:13 MERCURY kernel: Reset sata channel 1
Oct 12 14:55:13 MERCURY kernel: Need to disable irq on 1
Oct 12 14:55:13 MERCURY kernel: ==== SATA init channel 1
Oct 12 14:55:13 MERCURY kernel: After INIT SATA channel 1, retry=6, sata=113, status=50
Oct 12 14:55:13 MERCURY kernel: Need to enable irq on 1
Oct 12 14:55:13 MERCURY kernel: Reset sata channel 2
Oct 12 14:55:13 MERCURY kernel: Need to disable irq on 2
Oct 12 14:55:13 MERCURY kernel: ==== SATA init channel 2
Oct 12 14:55:13 MERCURY kernel: After INIT SATA channel 2, retry=128, sata=113, status=50
Oct 12 14:55:13 MERCURY kernel: Need to enable irq on 2
Oct 12 14:55:13 MERCURY kernel: Reset sata channel 3
Oct 12 14:55:13 MERCURY kernel: Need to disable irq on 3
Oct 12 14:55:13 MERCURY kernel: ==== SATA init channel 3
Oct 12 14:55:13 MERCURY kernel: After INIT SATA channel 3, retry=138, sata=113, status=50
Oct 12 14:55:13 MERCURY kernel: Need to enable irq on 3
Oct 12 14:55:13 MERCURY kernel: failed channel image=0
Oct 12 14:55:13 MERCURY kernel: failed_channel image=0
Oct 12 14:55:13 MERCURY kernel: Release waiting_for_dma flag 0
Oct 12 14:55:13 MERCURY kernel: Release the req pointer 86a0dcc8
You should backup all your data, since it is possible that the volume will fail when you replace the disks (since more than one are showing errors). After you backup the data, start by hot-swapping WD-WCAZA3720518 with a replacement, and wait for the resync to complete. Then hot-swap WD-WCAZA3682468. I suggest replacing them with 2 TB WDC Red drives (though Ironwolf would also be fine).
Thank you very much for your detailed reply.
I bought a new drive to replace drive 2, but after I've installed it now the NAS won't power on at all. The power button does nothing. I think maybe it's finally just died.
I might make an attempt to put the drives in a PC and see if I can access the array, but I think I might have to accept the fact the data is gone.
EquinoxBlue wrote:I might make an attempt to put the drives in a PC and see if I can access the array, but I think I might have to accept the fact the data is gone.
If you do put them into a PC, you'll need RAID recovery software that can handle the ext file system. R-Studio is one option. https://www.r-studio.com/
EquinoxBlue wrote:
I bought a new drive to replace drive 2, but after I've installed it now the NAS won't power on at all. The power button does nothing. I think maybe it's finally just died.
Does it power up with all disks removed? Label them by slot as you remove them.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
