NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

stylus's avatar
stylus
Aspirant
Apr 19, 2012

ReadyNAS 2100 won't boot.

I just purchased a 2100, I was trying to convert it to FlexRaid and was having no luck. I upgraded to v 4.2.19 and could not get it to convert to flexraid so I upgraded to v4.2.20 (T42). After upgrading I did a factory defualt intending on using RAIDar to "setup" within the first 10 minutes so that I could change raid modes. But it has been dead since.

Right now when I power it on runs for a few seconds then goes to solid lights for HDD's & USB, solid blue light, no activity. Doesn't respond to ping at last known IP, doesn't show up in raidar.

I have tried getting to the boot menu but that doesn't seem to be working, I press and hold the sys/reset button until solid lights then release the sys/reset button and hit the backup button but it dosn't toggle between modes.

I let it run for a little while but nothing has changed, do I just need to wait longer?

3 Replies

Replies have been turned off for this discussion
  • stylus, First I want to clarify that in order to change from Xraid to Flex raid or vice versa, it will require a factory default of the unit, which will result in data loss. As you are using a brand new unit, the data loss may be a non-issue.

    That being said, after the factory default, you will enter the setup using RAIDar and configure the unit for Flex-raid there.

    Here is a link to all of the boot menu instructions: http://www.readynas.com/kb/faq/boot/how ... on32004200

    If you do not have data on the unit, please perform a factory default, and see if the unit boots correctly and allows you to configure Flex-raid.

    If you have data on the unit and it is refusing to boot, please open a case with Netgear technical support.
  • I started a case with Netgear tech support, I am in the process of running western digital diagnostics of each of the 4 drives one at a time.

    In the mean time I installed Drive #1 only (or more likely Drive 0) and was able to boot up with that. At the admin website it says that drives 2,3,4 are dead (because they are currently not installed). I ran a factory reset from the website it appears to be working somewhat. I would of preferred to delete the volume and then recreate it but that was not an option.

    If it follows through and works with the 1 drive installed, should I then take the other ones to a spare workstation delete the partitions or zero them out. The goal being to install them as "blank/new" drives and all the raid to expand?

    Thanks
  • I was able to get my 2100 fixed.

    I found that the 2100, and 1500 both default to the IP 192.168.168.168 if they cannot pull a DHCP address. For whatever reason when I was doing factory default the devices were going to the 192.168.168.168 address. In my enviornment that created an IP conflict (Sonicwall default IP is 192.168.168.168).

    The IP conflict cause the raidar setup program to not work correctly. I clicked factory default from the web GUI, once it rebooted I clicked setup within in raidar and chose the raid configuration options I wanted (flexraid instead of xraid). It seems my setup options were not getting submitted to the readyNAS because of the IP conflict so it just kept rebuilding to the default Xraid configuration.

    To get around this problem I plugged the readynas into a different subnet (172.16.0.x) and it worked exactly as intended when following the convert from XRaid to Flexraid, no I can just swap the cables around and put it back where I want it.

NETGEAR Academy

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

Join Us!

ProSupport for Business

Comprehensive support plans for maximum network uptime and business peace of mind.

 

Learn More