NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
RNDU600 stuck at "Booting... checking root FS"
Running OS6.4.2 on RNDU600 on 6 2TB drives set up as RAID-5.
When either hard or soft shutdown, upon powering up the LCD gets to "Booting...checking root FS" and stays there. It's been there for 16 or more hours at a time.
What troubleshooting steps can I take?
- raidar cannot detect the unit
- I've tried restarting, and tried leaving it for a while
- While off, I pulled the one disk that was previously hinting at failing, but it tests ok in WD diagnostics, so I re-inserted it
- I tried to use the boot menu to reinstall the OS from flash, but it just goes to the same 'booting...checking root fs" screen.
- my next move will be to pull all disks and test them to make sure none have individually failed.
- while I have them out, I will try to do an off-line backup of any content I can see, if I can see any.
what else can I try to get back up and running, sort of a factory reset?
Update:
in private message, mgdm got me to send him a image of my corrupted file system for analysis through tech mode, then was able to reset the os remotely.
System booted without issue, but needs to be reconfigured.
The data volumes and all of the addons were present.
I was able to restore my config from a recent backup and restart the system, getting my configuration back.
Some add-ons worked (plex) while others did not (transmission, sickbeard).
But at least the NAS is back up and I can start to fix things.
Thanks so much mdgm-ntgr.
11 Replies
Replies have been turned off for this discussion
attempted the boot menu 'os reinstall', but still locked up at 'checking boot FS'. Not sure if the OS reinstall was successful (i.e happened before the 'check boot FS' failure) or didn't happen (i.e. check boot FS failure prevented reinstall of OS)
- RAIDAR from my PC, nor ReadyNAS cloud, can detect the unit while in the booting state.
Scouring the forum for similar posts...
I read through this troubleshooting, and nothing here seems to match. However, i am currently doing the built in disk test from the boot menu to see if I can detect failed disks. I normally get email SMART alerts before a failure, and I've tested the only one that has ever given a hint, so I'm not expecting a failed disk, but one never knows.
http://kb.netgear.com/app/answers/detail/a_id/29772
- YAY, RAIDAR CAN detect the array during DISK TEST. First time I've seen the NAS communicate in a few days.
Depending on the outcome of the disk test, is it possible it's my flashed firmware? Should I attempt USB recovery?
http://kb.netgear.com/app/answers/detail/a_id/29952/~/readynas-os-6%3A-usb-recovery-tool
Based on this post:
Hi jetheroheller,
If you don't have a backup of your files, boot the device in Volume Read Only mode and see if they'll be available. If this works, start backing them up then we'll work on your main issue afterwards.
Kind regards,
BrianL
NETGEAR Community TeamIt's ReadyNAS Ultra 6 + (RNDU600) running R4toR6_6.4.2.bin (OS 6.4.2).
The disk that was hinting at failing looked fine w.r.t. SMART and tested fine with WD Diagnostics, but had 9 pending sector counts. That was the only hint I caught, and only showed up as a caution in CrystalDiskInfo, showed up as test passed WD Diagnostics. There were no emails from the NAS or other errors.
I haven't tried booting without that drive because I wanted to exhaust the diagnostics before triggering something that might result in a resync event, if possible.
So what's next? I'll try to figure out how to trigger volume read only mode, but otherwise, what do we do?
What errors was the disk that was hinting at possibly failing giving? It sounds like there may be a problem with the root filesystem on the disks in which case it might not be possible to boot into volume read-only mode. If you can't boot into volume read-only mode we can discuss what the next appropriate step is.
No, this problem doesn't suggest that there is anything wrong with the firmware on the internal flash so doing USB Boot Recovery would be a waste of time and if anything may introduce a new problem.
Also as you have an RAIDiator-x86 4.2.x unit if you were going to do USB Boot Recovery you would use the USB Recovery tool for RAIDiator 4.2.x (but you could use OS6 firmware renaming it to RAIDiator-x86-something).
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
