This topic has been marked solved and closed to new posts due to inactivity. We hope you'll join the conversation by posting to an open topic or starting a new one.
After updating the firmware from web gui (6.1.8 to 6.8.0) my RN104 has "Booting ..." on the display. Attempt: OS Reinstall (with or without disks) Factory Default (with or without disks) Device still "Booting..." Please help.
Unfortunately, the following warning, whihc applies to you, is in the announcment in the forum but not in the release notes:
RN102, RN104 & RN2120: - ReadyNAS 102, 104, and 2120 must not be updated directly to 6.8.x from 6.3.x or older firmware. They must first be updated to either 6.2.5 or 6.3.5 then to 6.5.2 and then onto 6.8.x.
And the GUI does not enforce this, either. This is an unacceptible condition for which Netgear should take full responsibility. One of the Netgear mods will have to let you know how it can be fixed.
I would agree, as a novice if I were to go i nto the GUI and the device tells me there is an update I would expect it to update to something that worked wihtout having to trawl through release notes to realise I must manually go and download an intermediate firmware.
Personally I update regularly and do these checks but a novice would not I am sure!
I believe that a factory default should fix the problem. It wipes out everything, but you say you have a backup (good!). You can confirm that by putting in a spare drive and seeing if it comes up that way. If that doesn't work, a USB OS recovery should work.
Updating from a very very old firmware must have caused the problem. Like Sandshark said, it may be best to factory reset since you have backup of the data.
As i wrote in the 1 st post i already tried to do (from boot menu): 1)Factory Default (with or without disks) 2)OS Reinstall (with or without disks) with different flash drives. The device does not respond to these operations. On the device screen as before "Booting ..."
Can you try factory reset with just one disk? If you get the same problem, try another disk from the 4 existing ones. The idea is to find which disk would work and which would not.
If you put in a blank drive, it will normally "factory default" without having to go to the boot menu. If that works, then you can wipe the contents of the original drives and do the same with them. If even that doesn't work, then a USB recovery would be the only hope.
Unfortunately, the above options do not work. Device still "Booting...", no reaction, no IP address. My last chance is RS232 cable. Maybe someone have expirience with Netgear and RS232?
usb start
fatload usb 0 0x1200000 uimage-recovery
fatload usb 0 0x2000000 initrd-recovery.gz
set bootargs console=ttyS0,115200
bootm 0x1200000 0x2000000
then
Marvell>> set bootargs console=ttyS0,115200
Marvell>> bootm 0x1200000 0x2000000
## Booting kernel from Legacy Image at 01200000 ...
Image Name: Linux-3.0.101.RN_ARM.4
Created: 2015-04-01 23:06:44 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 3158996 Bytes = 3 MB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 02000000 ...
Image Name: initramfs
Created: 2016-12-21 6:08:04 UTC
Image Type: ARM Linux RAMDisk Image (lzma compressed)
Data Size: 2733934 Bytes = 2.6 MB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK
Starting kernel ...
Uncompressing Linux... done, booting the kernel.
Then nothing happens. Maybe I'm doing something wrong? Does anyone have ideas on this?
If the NAS boot menu is no longer responding with or without the hard drives inserted then there is a possibility we are looking at a hardware fault. The upgrade from very very old firmware to the latest version might have brick the NAS. There is a high chance that you might consider getting a new NAS chassis. We can still wait for any recommendations and assistance from community member that have gone to the same process.
It looks like you have done things right. That sequence looks like what happened when I tried to boot ReadyNASOS on a non-Netgear motherboard (same model as in the RN4200, but not Netgear bios) when I was looking for repair options. So maybe your flash is corrupt in a way that the recovery doesn't recognize it's a Netgear system. Perhaps @mdgm-ntgr can help on this one.
I would certaily hope that Netgear has a fix for this issue, since their update is nearly rammed down your throat each time you boot and does not warn about nor protect you from this issue.
