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 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.5-x86.bin, PREP4TOR6_0.1-x86.bin, R4toR6_6.9.5.bin), and all seemed good. 6x4TB disks took about 12 hours to reset/resync. After a few tests all seemed OK, I then did the auto-update to the 6.10.2 firmware, the unit did a restart (soft restart, no power down), and that seemed fine too.
I started backing up files to it (just robocopy via some scripts, it's the backup unit to files on another NAS), all was working fine. That process halted after some hours due to an apparent network issue, which I eventually narrowed to the powerline adaptor connected to the Ultra 6 NAS (this NAS and my router are located together, and network to the rest of the house via a PL2000 powerline adaptor that I installed yesterday also, replacing an older AV500 unit at the same location). Other powerline adaptors on the network were still talking fine to this one, but the other PL2000 powerline adaptor stopped talking to the router one, and resetting that remote adaptor didn't fix the issue - resetting the adaptor on the router/NAS did fix that issue.
To reset the powerline located with the router/NAS, I had to unplug it, which also meant powering down the NAS via the front panel first (it was powered via the pass-through on the powerline, bad idea, so I changed that around too, so further powerline resets won't require powering off anything else).
Attempted to power the NAS back on - it now just says "ReadyNAS" on the front panel, and won't do anything else. Holding down the reset switch does not bring up any boot menu. I have pulled all the disks, no change. I swapped the memory back to the original 1GB, no change.
My suspiscion is an issue with the 6.10.2 update, which didn't manifest itself until the unit got powered down. I don't know what else I can do to further diagnose or rectify that? The only other suggestion I see on the forums is a possible power supply issue - I haven't ruled that out, but it seems unlikely. But I can attempt to try that if there is nothing else I can do?
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.
18 Replies
Replies have been turned off for this discussion
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.
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.
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).
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.
I do not have another identical unit.
I will do that.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
