× NETGEAR will be terminating ReadyCLOUD service by July 1st, 2023. For more details click here.
Orbi WiFi 7 RBE973
Reply

Ready Nas - Lost Volume after forced reboot

voidness
Guide

Ready Nas - Lost Volume after forced reboot

Hi Support,

 

My 104 crashed and not responding so I unplugged and restarted, now the existing volume is gone, the error on is "remove inactive volumes to use the disk, 1,2,3,4"

 

are you able to help me restore the lost volumes ?

 

Thanks,

Dinh

Message 1 of 13
mdgm-ntgr
NETGEAR Employee Retired

Re: Ready Nas - Lost Volume after forced reboot

This is the community, support is at netgear.com/support.

You can send in your logs if you like (see the Sending Logs link in my sig) but you'll likely need to contact support (there would be some costs involved).

Message 2 of 13
voidness
Guide

Re: Ready Nas - Lost Volume after forced reboot

Thanks, do you know if there is anything I could try ?

Message 3 of 13
Sandshark
Sensei

Re: Ready Nas - Lost Volume after forced reboot

I have noted a marked increase in posts about this type of problem since the release of OS 6.6.0.  I think somebody at Netgear needs to look into why that is.  The system should be more robust than this.

Message 4 of 13
F_L_
Tutor

Re: Ready Nas - Lost Volume after forced reboot

I got this myself tonight. Ultra 4 running 6.6.1.

 

Did you ever find a solution how to retreive the volume?

Message 5 of 13
jak0lantash
Mentor

Re: Ready Nas - Lost Volume after forced reboot

Telling you how to re-assemble a RAID array without knowing the current status of the members would be way too dangerous.

If you're able to retrieve the logs, you could look at systemd-journal.log. There should be lines containing "kernel: md" which would bring some light to the status of the members of your RAID. Look at sda3, sdb3, sdc3, sdd3 and md127.

(I wish there was a log file containing the result of mdadm --examine of all the partitions, but it's not the case, so it doesn't make it easy to explain where to look.)

Message 6 of 13
voidness
Guide

Re: Ready Nas - Lost Volume after forced reboot

I have never got a solution for this, I did a search on this forums and apparently the paid support can help you to get it back, but that will cost you money, the unit has some hidden boot menu that allows you inspect deeper, of course this is reserved for support staff. 

 

I have also sent the logs to the MOD on this forums but never received a reply, I have not had time to contact support but I will soon, currently I just turn the unit off. and try not to think about it, I lost about 8TB worth of data

 

Man Sad

 

Message 7 of 13
mdgm-ntgr
NETGEAR Employee Retired

Re: Ready Nas - Lost Volume after forced reboot

voidness your situation doesn't look good.

Mar 01 04:12:27 voidness-nas kernel: md/raid:md127: Disk failure on sdd3, disabling device.
                                     md/raid:md127: Operation continuing on 3 devices.
Mar 01 04:12:27 voidness-nas kernel: md/raid:md127: Disk failure on sdc3, disabling device.
                                     md/raid:md127: Operation continuing on 2 devices.
Mar 01 04:12:27 voidness-nas kernel: md/raid:md127: Disk failure on sdb3, disabling device.
                                     md/raid:md127: Operation continuing on 1 devices.
Mar 01 04:12:27 voidness-nas kernel: md/raid:md127: read error not correctable (sector 1027231616 on sdd3).
Mar 01 04:12:27 voidness-nas kernel: md/raid:md127: read error not correctable (sector 1027231624 on sdd3).
Mar 01 04:12:27 voidness-nas kernel: BTRFS: bdev /dev/md127 errs: wr 0, rd 1, flush 0, corrupt 0, gen 0
Mar 01 04:12:27 voidness-nas kernel: BTRFS: bdev /dev/md127 errs: wr 0, rd 2, flush 0, corrupt 0, gen 0

Mar 01 04:12:27 voidness-nas kernel: BTRFS: bdev /dev/md127 errs: wr 0, rd 30229, flush 0, corrupt 0, gen 0
Mar 01 04:12:27 voidness-nas kernel: BTRFS: bdev /dev/md127 errs: wr 0, rd 30230, flush 0, corrupt 0, gen 0
Mar 01 04:12:27 voidness-nas kernel: BTRFS: bdev /dev/md127 errs: wr 0, rd 30231, flush 0, corrupt 0, gen 0
Mar 01 04:10:34 voidness-nas mdadm[2224]: Fail event detected on md device /dev/md127, component device /dev/sdb3
Mar 01 04:12:25 voidness-nas mdadm[2224]: Fail event detected on md device /dev/md127, component device /dev/sdc3
Mar 01 04:12:26 voidness-nas mdadm[2224]: Fail event detected on md device /dev/md127, component device /dev/sdd3
Mar 04 23:15:27 voidness-nas kernel: md: md127 stopped.
Mar 04 23:15:27 voidness-nas kernel: md/raid:md127: device sda3 operational as raid disk 0
Mar 04 23:15:27 voidness-nas kernel: md/raid:md127: allocated 4280kB
Mar 04 23:15:27 voidness-nas kernel: md/raid:md127: not enough operational devices (3/4 failed)
Mar 04 23:15:27 voidness-nas kernel: md/raid:md127: failed to run raid set.
Mar 04 23:15:27 voidness-nas kernel: md: md127 stopped.
Mar 04 23:29:46 voidness-nas kernel: md: md127 stopped.
Mar 04 23:29:46 voidness-nas kernel: md/raid:md127: device sda3 operational as raid disk 0
Mar 04 23:29:46 voidness-nas kernel: md/raid:md127: allocated 4280kB
Mar 04 23:29:46 voidness-nas kernel: md/raid:md127: not enough operational devices (3/4 failed)
Mar 04 23:29:46 voidness-nas kernel: md/raid:md127: failed to run raid set.
Mar 04 23:29:46 voidness-nas kernel: md: md127 stopped.

All of your disks have ATA errors.

Message 8 of 13
voidness
Guide

Re: Ready Nas - Lost Volume after forced reboot

Does the ATA error means the disks are completely unsuable ? 

Message 9 of 13
jak0lantash
Mentor

Re: Ready Nas - Lost Volume after forced reboot

The Boot Menu is certainly not hidden, there is even KB articles about it. And if you do some research, you'll find info about Tech Support Mode. BJT this is for people who are proficient in Linux and know about mdadm and BTRFS.
Message 10 of 13
voidness
Guide

Re: Ready Nas - Lost Volume after forced reboot

Just to update everyone who might run across this thread with the same issue. 

 

So I didn't want to pay support and was willing to lose all my data, because my HDDs has lots of ATA errors so I chucked them into the freezer (in airtight bags of course), I left it there for a few weeks, (because I had to buy a backup disk big enough to backup my data, hence the few weeks wait)

 

once I got my backup disk I put the drives back into the NAS and proceed to remove inactive volume and create new volume, and to my surprise the old volume came back intact with everything on it (I think all I did was click remove inactive then click new volume and the old one just came back, it didnt even asked me to put in a new volume name just restored itself). I am not sure if the fridge help or this error is merely a bug on the front end. 

 

I also did try to run these commands, but it didnt seems to help

 

mdadm --examine --scan
mdadm --assemble --scan (with really force )

 

 

so yea I didnt lose my data and I now have a backup 

Message 11 of 13
jak0lantash
Mentor

Re: Ready Nas - Lost Volume after forced reboot

Message 12 of 13
StephenB
Guru

Re: Ready Nas - Lost Volume after forced reboot

I'm glad it all worked out, and thx for updating the thread with the outcome.

Message 13 of 13
Top Contributors
Discussion stats
  • 12 replies
  • 4302 views
  • 0 kudos
  • 6 in conversation
Announcements