NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
ReadyNAS ultra 4 stuck on booting
Hello everyone, I have since a long time my ReadyNAS ultra 4 running on 4x3TB HDD (lost my account with the death of readynas.com). My NAS, during the first years was a little bit tweaked (outsi...
In support mode, you are running firmware from the flash, so it should already be mounted. lsblk should show you where.
But I would be very careful, as you can easily make things worse instead of better.
Thanks for the reply.
this shell command didn't work but i tried all the commnands and just one worked.
it showed me that the sorting is logical :
-sda through sdd for the 4 hdd
-sde for the flash drive inside
-sdf for the usb stick with the recovery firmware
I mounted the last 2 to check. The files had the same size, the flash files are 3 weeks old, when the firmware update worked perfectly. I wasn't confident enough to try and replace the files.
I tried the memory check and disk check, no error.
i rebooted the nas to see where it is, it's still stuck, but it appears on my router's device list, and the frontview webpage loads, but is empty, just the exterior frame appears. Nothing else work...
this shell command didn't work but i tried all the commnands and just one worked.
it showed me that the sorting is logical :
-sda through sdd for the 4 hdd
-sde for the flash drive inside
-sdf for the usb stick with the recovery firmware
I mounted the last 2 to check. The files had the same size, the flash files are 3 weeks old, when the firmware update worked perfectly. I wasn't confident enough to try and replace the files.
I tried the memory check and disk check, no error.
i rebooted the nas to see where it is, it's still stuck, but it appears on my router's device list, and the frontview webpage loads, but is empty, just the exterior frame appears. Nothing else work...
I'd try the install on a blank disk next - I think it's important to sort out if the problem is really with the flash or if it's something borked on the OS partition before you go further.
Still haven't found my spare HDD to test it, but i've looked at the logs (i'm a bit stuck, many things i try in telnet are blocked, because my working directory isn't the nas OS, but the telnet busybox, and the chroot command fails (segmentation fault).
As i looked at logs, i opened the kernel log, which stops at the 7th of january (when everything went wrong), and it lists many services which failed to start because a segfault due to an error in libc-2.13, also in dpkg.
i feel like i'm well trapped. In order to have better commands, for example to fix my chroot issue, i need to chroot in the os partition...
It's hard to say where in the process above that your volume got so borked. I've never tried to recover one in that condition. Only had it happen once (may years ago) and I had a good backup and just did a factory default and restored.
I did want to comment on your "when it's working, don't touch anything" manttra, though. That's actually no way to treat a NAS. "Install and forget" can get you into a very deep mess before you realize it, and you may realize it only after there is any chance of recovery. Had you done the steps you mentioned as the updates became available/necessary, you may have avoided this.
I "check in" on my primary NAS at least once a week and boot my backup NAS for a quick peek at least monthly, or when somehting on the primary (file issue, available update, whatever) makes me think I should do it now.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
