Forum Discussion

Aspirant

May 23, 2020

ReadyNas RN2120 Corrupt Root

Am looking for help to start my NAS again. I am in the stage where I already did a hard factory reset, with the pin at the front. Even that, when I boot, I get "corrupt root" message on RAIDar. Following a reset again, corrupt root message again and I then proceed wtih OSReinstall same thing. But setup does not go through. 2TB disk capacity, does not do anything. When I come back in the morning, the NAS is still ON, the disk1 LED is on, Repeating all above steps does not solve the issue and even changing disk and/or disk slot.

The IP stays at 192.168.1.188 and going to Chrome to ADMIN key give me a browser error message as page unreacheabled. Your connection refused.

Any idea ?

Thanks.

11 Replies

Sandshark
Sensei
May 23, 2020
Just to be clear, you did a "Factory Default", not just an "OS Re-install"? You need to do the factory default to get back to square zero (which does man you lose all data, but I assume you know that), and it does not sound like that's what you have done. If that iis what you did, one of the drives may be bad.

Another option is to remove the drives and zero them (just removing all partitions is usually sufficient) using a PC, then power on with the "fresh" drives. Since you've apparently not used the NAS for a bit, using the manufacturer's tools to test the drives while you have them out could save you some head scratching and/or heartburn later, too.
- icecoldbaseball
  Aspirant
  May 23, 2020
  Yes I factory Defaulted it.
  - icecoldbaseball
    Aspirant
    May 23, 2020
    I can not even get in the GUI
- icecoldbaseball
  Aspirant
  May 23, 2020
  I stuck a fresh drive in the Nas and RAIDar said installing and then corrupt root.
  - StephenB
    Guru
    May 23, 2020
    icecoldbaseball wrote:
    
    I stuck a fresh drive in the Nas and RAIDar said installing and then corrupt root.
    
    Test the drives in the PC with vendor tools (lifeguard for western digital; seatools for seagate). I recommend running both the extended non-destructive test and a full write-zeros test.
    
    If it's not the drives, then it could be a problem with the firmware image in the flash.