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 l...
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/
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.
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/
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.
Both disks fail. Doesn't matter if I try long or short generic tests in SeaTools. The long generic test fails almost instantly for both disks without any usable error information:
For the first disk I'm able to see valid Drive information in SeaTools, i.e. model number, Lifetime Bytes Read, Power-on Hours etc. For the second disk that information looks like rubbish.
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/
Is it still worth trying R-linux, or is that meaningless when the disk tests fail?
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
