NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
ItsPeter
Jan 18, 2020Star
ReadyNAS Ultra 6 doesn't boot - Stuck on "ReadyNAS" prompt screen
Yesterday I upgraded my old ReadyNAS Ultra 6 to OS6, previously running 4.2.31. I replaced the 1GB RAM in the unit with 2x2GB sticks (new), and followed the upgrade process (BIOS_Update_Package_0...
- Jan 21, 2020
Thanks everyone for your feedback and assistance. As identified, my VPD file was corrupt, and without the Model and Serial info, that seemed to be stopping Frontview, etc from working correctly.
Only someone with the correct Netgear tools can re-create that VPD file, luckily I've been given the help privately to restore my Serial, etc back info the unit, and we are back up and running again. Sounds like I may not have specifically done anything wrong with what I did with the unit, it is just unfortunately a scenario that can happen on these older units. Fortunately fixable, I guess just a possible scenario to be aware of for anyone else thinking of the OS4 to OS6 upgrade.
ItsPeter
Jan 18, 2020Star
OK, so I used the USB recovery tool:
https://kb.netgear.com/30267/RAIDiator-4-2-USB-Recovery-Tool
And that appears to have un-bricked the unit, and I can access the Boot Menu now. I've currently got it running a memory test, and from there it seems the options are either Factory Reset or Reinstall OS - I'm sure one of those gets me where I want to go, just not sure which to try first. Open to any suggestions, otherwise I'll post another update on whatever I try next.
If anyone else stumbles across this thread btw, the USB recovery is completely non-intuitive. The front panel just displayed "ReadyNAS" the whole time, the same as when the unit was hung, so I had no idea if it was doing anything (it did NOT indicate "Recovery Mode" as suggested on the Netgear page). I shut down the process on the first attempt in case the USB was not compatible with the unit, found a second USB, which happened to have an LED activity indicator, and that's what told me the unit actually appeared to be doing something - I could see the USB was being accessed on this attempt. After about a minute or so the unit shut itself down, but never once did the unit itself indicate what was going on.
ItsPeter
Jan 18, 2020Star
Memory test came back with no errors, so I restarted the unit, it attempted to boot, and then came up "ERR: Could not mount root RAID d". To be expected I guess - the volume was created on a newer firmware, so obviously the old firmware that's back on there doesn't understand the current volume.
It looks like Factory Reset is the only way forward from here, so I've kicked that off. I'd prefer to upgrade the unit to 6.9.5 first, to avoid creating/syncing disks multiple times, but it doesn't look like there's any way to do that that I can see, so we'll create the volume under 4.2.31, and then see if I can update to OS6 before having to resync the whole volume under 4.2.31 first.
- ItsPeterJan 18, 2020Star
So the factory reset went through the initial stages OK (checking disks, creating volume), and then sat there with disk 6 flashing on the front panel. I thought it might be syncing, but usually it indicates progress for that on the front panel too. I tried to access it via RAIDar, but ReadyNAS Frontview is coming up as an empty screen (the borders and frame are on the page, but no info or controls). Also in RAIDar, the "Model" string looks completely corrupt (looks like UTF-8 or Unicode or something, being converted incorrectly as ASCII).
I wondered if maybe disk 6 was actually failing (shouldn't be, it's one of the newer disks in the unit), so I shut it all down, swapped disks 4 & 6, and kicked off factory reset again. It eventually reached the same state, the disk 6 icon is flashing on the front panel, no other info (just the IP address), and Frontview is still blank.
I am assuming it is therefore syncing, and will leave it overnight, fingers crossed. If anyone has any suggestions let me know - it seems like either files/info are missing that I need to restore to get the old Frontview working again, or perhaps the OS6 bios changes mean the old firmware will no longer work correctly. In which case I guess I either need to find a way to revert to the previous BIOS, or I can try USB recovery again, but with the 6.9.5 firmware on the USB (in hindsight that's probably what I should have done to start with).
- ItsPeter2May 27, 2025Guide
If you have an identical unit, you could try placing the disks in there (in the same bays in the same order), and see if that gets you access to the data.
Otherwise, it sounds at least like your hardware isn't dead, but you might be best starting a new thread to get suggestions - this original thread was more about issues I had upgrading from OS4 to OS6, but sounds like you have a different issue.
- StephenBJan 18, 2020Guru - Experienced User
ItsPeter wrote:
so we'll create the volume under 4.2.31, and then see if I can update to OS6 before having to resync the whole volume under 4.2.31 first.
A factory reset will re-install OS6, because you now have the OS-6 image in the flash memory.
I'm not sure what happened to create your main issue, but I am thinking you didn't shutdown the NAS cleanly, and instead just pulled the plug. The preferred way to shut down from the front panel is:
- If the status display screen is not lit, press the Power button three times initiate a
graceful shutdown. - If the status display screen is lit, press the Power button two times to initiate a
graceful shutdown.
You might consider getting a UPS for your NAS - power loss generally does no harm, but as you found out there is some risk that it will result in data loss. The NAS can monitor the UPS, and shutdown cleanly when it's battery drains.
- ItsPeterJan 18, 2020Star
The NAS was shut down cleanly, two consecutive presses of the off switch on the front panel - I heard the heads on the drives park as it powered down, it generated the "The system is shutting down." email and everything.
I would have thought the USB recovery has put the 4.2.31 OS back into the flash memory? But something hasn't 100% worked with that. I was wondering if the BIOS update (BIOS_Update_Package_0.5-x86.bin) isn't compatible with 4.2.31, but after much browsing, it seems that shouldn't be an issue. I'm still wondering about downgrading the BIOS, but I haven't been able to find any older BIOS images, or instructions on installing them.
At this stage drive 6 is still flashing as if syncing, I will leave it a little while longer, and if nothing comes of that will try USB recovery to 6.9.5 and see what happens there.
- SandsharkJan 18, 2020Sensei - Experienced User
USB recovery would have put in whatever OS you used to create the recovery drive. If you followed the onlione instructions verbatim, then you are likely back to 4.2.x. If you used the modified OS6 image to create the recovery drive, then it should be running that. From your description and symptoms, I think you did recover to OS 4.2.31.
You didn't need to create an entire RAID to do the OS6 update again. A single drive JBOD would have worked just fine, and much faster.
- If the status display screen is not lit, press the Power button three times initiate a
Related Content
NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!