I upgraded my RN10200 tfrom 6.1.4 to 6.2.5 last night, or should i say i tried to. it seemed to go okay and siad it would install after a reboot which i did and left it to it. This morning it was unresponsive I can't connect via file explorer or a web browser to the control pages. The blue power and ACT LEDs are on but thats about it (oh fan is running).
Any ideas?
Model: RN10200|ReadyNAS 100 Series 2- Bay (Diskless)
May I know the status of the NAS when you check it on RAIDar? If you do not have RAIDar installed on one of your PCs, you may download the installer here.
You can try booting the NAS without the drives in it (Note: Please label the drives with its corresponding bay) and see if RAIDar can detect the NAS with a status of 'No disks detected'.
If it detects the NAS, it will be best to contact the NETGEAR support team so they can check what caused the issue. If it is not detected even without the drives in it, you can try doing a USB boot recovery and see if that helps. You may check this article for the steps on how to do the USB boot recovery.
I've rebooted without the drives and still nothing.
I will now try the USB boot recovery method. After reading the link you (@JohnCM_S ) provided I beleive i will need to use version 6.2.5 of the firmware on the USB (which is what i was trying to install) rather than try a newer version?
Also I use an IMac, the USB recovery guide implies a windows machine is needed, or have i miss read?
Cheers
Model: RN10200|ReadyNAS 100 Series 2- Bay (Diskless)
I will now try the USB boot recovery method. After reading the link you (@JohnCM_S ) provided I beleive i will need to use version 6.2.5 of the firmware on the USB (which is what i was trying to install) rather than try a newer version?
Yes, you will use the 6.2.5 firmware on the USB.
Also I use an IMac, the USB recovery guide implies a windows machine is needed, or have i miss read
If you are going to use the USB recovery tool, you can only do that on a Windows PC.
There is a step on the last part of the article on how to manually create a USB recovery drive for ARM-based units. You may try doing that using your iMac.
We’d greatly appreciate hearing your feedback letting us know if the information we provided has helped resolve your issue or if you need further assistance.
If your issue is now resolved, we encourage you to mark the appropriate reply as the “Accept as Solution” or post what resolved it and mark it as a solution so others can be confident in benefiting from the solution.
The NETGEAR community looks forward to hearing from you and being a helpful resource in the future!
Thank you for you assistance @JohnCM_S . I followed the insructions for creating the USB drive as follows but its just sitting there with blue lights on!
I formated an 8Gb USB drive for MS-DOS
Copied the following files to the root of the USB:
initrd-recovery.gz (From the downloaded and expanded "usbrecovery.v2.0.R17" \\Arm)
NTGR_USBBOOT_INFO.txt (From the downloaded and expanded "usbrecovery.v2.0.R17" \\Arm)
uImage-recovery (From the downloaded and expanded "usbrecovery.v2.0.R17" \\Arm\rn10x)
Powered down the NAS
Inserted teh USB drive in the front port
Powered up whilst holding the "backup" buton for 30 seconds
The instructions did not mention where the firmware file "ReadyNASOS-6.2.5-arm.img" should go on the USB if at all?!
Cheers
Model: RN10200|ReadyNAS 100 Series 2- Bay (Diskless)
You may just put the firmware image file in the same location in the USB where you put the initrd-recovery.gz, NTGR_USBBOOT_INFO.txt, and the uImage-recovery.
In case it still did not work, you can try using another flash drive and see if that helps.
RAIDar has detected the NAS and shows no disks in the unit but its using a diffrent IP address which isodd as it was set to use a static address. Is this reset when the firmware is updated? Also I can log into the NAS, is this because there are no disks in the unit? I dint think this would be the case, but its a while since i initialy set the unit up.
As an aside the instructions to create a USB recovery disk could do with updating to include copying the firmware file onto the drive.
Cheers
Model: RN10200|ReadyNAS 100 Series 2- Bay (Diskless)
My problem similar to the others in this thread but with a big difference, as far as I can see my New (old stock) ReadyNAS Duo v2 will not fully boot up.
As you can see from the attached Raidar picture, the device model number and firmware are not displayed but the Name, Status, IP and Mac addresses are. Plus, I cannot access that ReadyNAS's Dashboard, in fact none of my three browsers (Firefox, Opera & Chrome) can and so I cannot make any adjustments.
I would appreciate a diagnosis, if possible, and a way to either initiate or access the NAS's Dashboard.
No disks in the unit at the moment, but as i mentioned i cnat remeber if this stops teh admin page being accessable, i would have thought i could still access it.
After this adventure i'm a bit nervous about putting the drives back in before updating the firmware further. Currently up to 6.2.5 (whaich caused this issue) i beleive that the lastet version is 6.10!
My problem similar to the others in this thread but with a big difference, as far as I can see my New (old stock) ReadyNAS Duo v2 will not fully boot up.
As you can see from the attached Raidar picture, the device model number and firmware are not displayed but the Name, Status, IP and Mac addresses are. Plus, I cannot access that ReadyNAS's Dashboard, in fact none of my three browsers (Firefox, Opera & Chrome) can and so I cannot make any adjustments.
I would appreciate a diagnosis, if possible, and a way to either initiate or access the NAS's Dashboard.
UK Bob
@DiveNige has an OS-6 NAS, yours is a Duo, which is very different. It'd be best if you can start a new thread for your issue. Loss of model information usually means that the eeprom that holds the model information is corrupted. That can only be fixed by Netgear; the mods ( @JohnCM_S or @Marc_V ) might be willing to help.
Just to let you know, I have taken Stephen's advice and started another thread, entitled "Loss of Model Information", which I hope will result in the advice and help I need.
However, before reaching out for help in this thread, I did conduct a few preliminary test of my own:
1) I connected this new (old stock) ReadyNAS Duo v2 to my network and switched it on, I got an initial response showing that the device was electronically sound and I was able to get an IP address from my modem-router but I could not access the device using any of my three browsers.
2) I installed a WD Green 2TB HD in bay one, this was left over from my first ReadyNAS Duo v2, and I felt the drive spin up so I thought it was being formatted.
3) Some 8 to 9 hours later, I felt the drive still spinning in the NAS but I was getting no other response from the NAS itself, i.e. it's Dashboard could not be accessed and it would not switch off by pressing the off/on button on the front.
4) I ran Raidar v6 and was shown that neither the installed HD or the NAS model name were displayed, that's when I decided to reach out to this forum and send a copy of Raidar's screen capture.
5) Finally, I removed the WD Green from bay one, did another run of Raidar and noted that either with or without the disk in bay one the information displayed was still the same, no model info and "No disks detected"
Please bear in mind that I am not a complete ReadyNAS Duo v2 novice, I am using two Duo v2's at the moment and this troublesome one will be my third, so I understand how they are suppose to work and how to switch them on but, like most users, not the intricate technicalities of when they go wrong.
RAIDar has detected the NAS and shows no disks in the unit but its using a diffrent IP address which isodd as it was set to use a static address. Is this reset when the firmware is updated? Also I can log into the NAS, is this because there are no disks in the unit? I dint think this would be the case, but its a while since i initialy set the unit up.
An OS re-install does set the NAS back to using DHCP. That is intentional, as it is a method that users who set a static address (which is a bad idea for most) and then changed to a router using a different sub-net can use to re-gain access.
It is a much better idea to reserve an IP address in your router instead of using the static IP option. Since an IP reservation is based on MAC address, that means a re-install won't affect it. And if you change sub-nets, there are no hoops to jump through.
