NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
RN31400: data DEAD, All drive showing NEW healthy on reboot
NAS was showing 'data Dead' on LCD on inspection after noticing that it wasn't working. Turned it off and restarted the box. Rebooted, admin suite has the notification 'Remove inactive volumes to u...
I don't think the NAS retains any state on this, other than what btrfs itself retains.
What you need to do is forcibly mount the array, and perhaps also attempt to repair the file system. This isn't something I've ever needed to do, so I can't really offer much advice.
If you boot up in tech support mode, you could try
# rnutil chroot # btrfs device scan # btrfs fi show # mount -t btrfs -o ro,recovery /dev/md127 /data
If you just go into ssh with the NAS running, then you'd skip the rnutil command.
One user here successfully used that mount command to mount a missing volume. If it works then it will mount the volume read-only so you'd need to offload the data.
Hi dougal1983,
I checked the logs and saw that the volume cannot be mounted because there are not enough operational disks.
Sep 16 09:00:46 NAS kernel: md/raid:md127: device sda3 operational as raid disk 1
Sep 16 09:00:46 NAS kernel: md/raid:md127: device sdb3 operational as raid disk 3
Sep 16 09:00:46 NAS kernel: md/raid:md127: allocated 4362kB
Sep 16 09:00:46 NAS kernel: md/raid:md127: not enough operational devices (2/4 failed)
I saw errors in bay 1 and bay 3.
Sep 16 09:00:47 NAS kernel: ata1: exception Emask 0x10 SAct 0x0 SErr 0x4040000 action 0xe frozen
Sep 16 09:00:47 NAS kernel: ata1: irq_stat 0x00000040, connection status changed
Sep 16 09:00:47 NAS kernel: ata1: SError: { CommWake DevExch }
Sep 16 09:00:47 NAS kernel: ata1: limiting SATA link speed to 1.5 Gbps
Sep 16 09:00:47 NAS kernel: ata1: hard resetting link
Sep 16 09:00:47 NAS kernel: ata3: exception Emask 0x10 SAct 0x0 SErr 0x4040000 action 0xe frozen
Sep 16 09:00:47 NAS kernel: ata3: irq_stat 0x00000040, connection status changed
Sep 16 09:00:47 NAS kernel: ata3: SError: { CommWake DevExch }
Sep 16 09:00:47 NAS kernel: ata3: limiting SATA link speed to 1.5 Gbps
Sep 16 09:00:47 NAS kernel: ata3: hard resetting link
It will be best to check the health of those disks using the disk manufacturer's tool.
Regards,
Righto. All disks checked.
- Failed SMART/Extended Tests. Bad Sector repaired. (This'll be going in the bin, will get new drive).
- Passed SMART/Extended Tests.
- Passed SMART/Extended Tests.
- Passed SMART/Extended Tests.
I did get disk 3 with unknown status, after plugging back in but have given connectors a little puff of air and replugged in and it's OK for now (hopefully).
Is there a way to attempt to rebuild volume from 2,3 & 4? Will add new disc in 1 with same capacity. If I get that I'll perform a full backup in penitance!
Thank you for any and all advice!
You can try booting up the NAS again with slot 1 empty. Perhaps try read-only mode, for safety - see pages 74-75 here: https://www.downloads.netgear.com/files/GDC/READYNAS-100/ReadyNAS_%20OS6_Desktop_HM_EN.pdf
Though if there were lost writes due to the errors, the volume still might not mount. You could try Netgear support (though if you need data recovery, it will be expensive) - https://kb.netgear.com/69/ReadyNAS-Data-Recovery-Diagnostics-Scope-of-Service
StephenB No, didn't work booting in safemode and removing #1. The box decided at one point that 2 discs had failed and now will sit on it's hands. Disc 2,3,4 are fine although bay three might have an issue with the port. #1 had a bad sector and the box picked an terrible time to get it's knickers in a twist on port 3.
All I want to know is... can I ssh onto the box and tell it proceed with rebuild from 2,3,4. At this point, I don't care if I lose the data in the attempt. All I want is one attempt then I'll move on. If anyone can offer instruction (with absolute disclaimer, I won't blame anyone but myself).. I'd love to just attempt to recover data.
Alternatively if that is impossible on x-raid could you point me at DIY data recovery guides that may be relevant to x-raid devices.
I don't think the NAS retains any state on this, other than what btrfs itself retains.
What you need to do is forcibly mount the array, and perhaps also attempt to repair the file system. This isn't something I've ever needed to do, so I can't really offer much advice.
If you boot up in tech support mode, you could try
# rnutil chroot # btrfs device scan # btrfs fi show # mount -t btrfs -o ro,recovery /dev/md127 /data
If you just go into ssh with the NAS running, then you'd skip the rnutil command.
One user here successfully used that mount command to mount a missing volume. If it works then it will mount the volume read-only so you'd need to offload the data.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
