NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
ReadyNas 3200 Unresponsive after disk sync
I have a ReadyNas 3200, and I did a factory reset. I then upgraded the firmware to the 4.2.28 on the website, performed setup, and transferred a number of files. I then powered the unit down, an...
I found the problem, it was a bad RAM stick. Once I removed the bad stick, it worked just fine.
I have tried about 30 times, and I cant get into the boot menu. I have checked the reset switch with a multimeter, and it appears to be making proper contact.
I tried with one PSU at a time, with all the disks in and all the disks out.
I also tried hooking up a VGA monitor to the port on the back and I did not get anything on the monitor.
I saw this thread too: https://community.netgear.com/t5/Using-your-ReadyNAS/ReadyNAS-3200-boot-Could-not-find-external-flash-device/td-p/955257/page/3
I am able to take the thumb drive out (the warranty void sticker was already broken....I got this second hand, hrmmmmm), and put in a PC and it reads ok, but I guess that does not mean the image is corrupted. Can I put a new image on the USB drive somehow?
It's unlikely the problem would be with the flash, but you could try USB Boot Recovery if you really want to.
Have you checked to make sure the RAM is properly seated?
I did try re-seating the ram, same result.
I did not do the USB recovery yet, since I am guessing if I cant get to the boot menu, I cant do that anyway.....
I did take a look at the files on the thumb drive that is in the ReadyNas already, it says I have radiator ver 4.2.27. I am not sure if it didnt update to 4.2.28 or maybe it didnt update the .txt file (Version.txt)
I also remembered that while it was syncing, I tried to install the Plex add-on (PlexMediaServer-0.9.12.19.1537-f38ac80-i686.bin)
If the firmware update completed the version.txt would have been overwritten with the one in 4.2.28.
USB Boot Recovery is not done via the boot menu.I found the problem, it was a bad RAM stick. Once I removed the bad stick, it worked just fine.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
