NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
ReadyNAS Ultra 2 - corrupt root
I have an old ReadyNAS Ultra 2 (RNDU2000) which I can no longer access. I'm unable to reach the shares on it or access https://<IP-adress>/admin
It's been years since I configured the system or last used Raidar. Everything has just been working. As far as I can remember I configured it for mirrored storage, using two identical 2TB Seagate Barracuda XT disks.
Message in Raidar after a normal boot with disks: "Corrupt root". The same message, "Corrupt root", also appear if I try a "OS Reinstall"-boot or a "Skip volume check"-boot.
If I do a normal boot without disks, the Raidar message is: "No disks were found"
The client I'm using is the latest Win 10 version with SMB/CIFS activated.
What else can I try?
- Would a boot in "Tech support"-mode make any sense?
- If so, what would be the next step once the system is booted?
- Or perhaps trying to get the NAS to boot from a recovery USB?
Any input is much appreciated!
StevOls wrote:
Any more ideas on things I can try?
I think the next thing to try is testing the disks.
Ideally you'd do this in a Windows PC using vendor tools (lifeguard for Western Digital; seatools for Seagate). Run the long generic test. Disks can be connected to the PC with SATA, or with a USB adapter/dock.
You can also try R-linux (with either one of your disks), and see if it can find your C volume. If it does, then you can try offloading the data on the NAS. https://www.r-studio.com/free-linux-recovery/
9 Replies
Replies have been turned off for this discussion
The operating system (and the ReadyNAS application) are stored in a 4 GB RAID-1 partition on the disks. A "corrupt root" error means that the NAS boot loader is unable to boot from that partition. An USB recovery isn't indicated - there is no evidence here that the flash has failed.
Do you have a backup of the data on the NAS?
You can try powering down, removing disk 1, and then power up. If that boots and you don't have a current backup, then back up up your data before doing anything else.
If the system was set up as XRAID/RAID1, you can also try booting with just Drive 2 installed.
A NAS is not a "set and forget" device. While email alerts are certainly helpful, it is best if you check in on it occasionally. Your problem may not have given any advanced warnings, but it also may have and you missed it. Do you even know if your email alerts (assuming you have them configured) are working? Changes in some email clients such as GMAIL for two-factor authentication have caused changes to have to be made in your GMAIL or other account and they may be failing if you didn't make those changes.
Thank you for your input Sandshark
Guess I just have to admit that I haven't fully understood how the NAS works, and that it's been years since I've given it much thought or love. It's rather embarrassing, but I don't even know if I once configured any email alerts. If so, the mails must be sent to a now dead mailbox.
I fully agree that I should have payed the NAS more attention, but as always it's easy to be wise in hindsight.
Thank you for your answer StephenB
I don't have a formal backup of the entire NAS. What I have is a "backup" of most of my personal files, created in Windows by copy/paste from the NAS to an External USB drive.
I've now tried to remove disk 1 and powered up as you suggested. What then happens is that the host name field in Raidar changes to some kind of default value, not the one I have set. (The default value seems to be created partly from the NAS mac-adress). The raidar information message, translated from Swedish, first says "Click on installation". If I wait for a while and then click the Rescan-button the message is changed to "Corrupt Root".
Any more ideas on things I can try?
StevOls wrote:
Any more ideas on things I can try?
I think the next thing to try is testing the disks.
Ideally you'd do this in a Windows PC using vendor tools (lifeguard for Western Digital; seatools for Seagate). Run the long generic test. Disks can be connected to the PC with SATA, or with a USB adapter/dock.
You can also try R-linux (with either one of your disks), and see if it can find your C volume. If it does, then you can try offloading the data on the NAS. https://www.r-studio.com/free-linux-recovery/
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
