NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
RNDP600E will not boot from from USB recovery tool
I cannot seem to get the darn RNDP600E to boot from the recovery USB that i created using the USB recovery tool app. I have tried 6 different thumbdrives and nothing. I followed the instructions...
The system coming up fine using a scratch disk shows that the problem is not the firmware on the internal flash so USB Boot Recovery is a waste of time.
Why would the boot start up and then say "Retry Startup"? My thought process was to try either a USB recovery to force the loading of the OS or to just do an OS Reinstall. But as I mentioned, I can't get either to start. Clearly (hahaha), I am not an expert on this but that was my best guess.
I also tried running check disks on the drives that I have and they all seem to be fine although the NAS was sending me reports a while back regarding a small number of allocation errors. BTW, correct me if I am wrong but the way I had it understood was that if one of my drives failed, the NAS would stay up and running. Let's say one drive failed, why would the system get stuck on startup?
Is there a way for me to run a report to see where the error is manifesting itself? I don't want to waste anyboby's time here fishing around without solid data to look at.
Thanks
CB
The system and the settings are stored on the disks. So if it's stuck on "retry startup", it's because that OS volume is somehow corrupted. USB Boot recovery is to rewrite the flash (where boot menu and firmware/system archive for factory default installation are stored), so useless here. OS Reinstall is to rewrite some of the system and settings on top of the existing OS. But as it doesn't wipe it and reinstall the OS from scratch, it doesn't solve all the boot issues.
Next steps would be to manually fix the OS, or to manually share the volume on the network.
Looks like one of your disks, disks 4 is bad:
Device Model: ST3000DM001-1CH166
I'm not able to read the SMART error counts from this disk.Read SMART Data failed: scsi error badly formed scsi parameters
That disk model is known to have very high failure rates.
The data volume seems to be O.K. at the array level (though I haven't tried starting the array).
However the root volume array is very messed up:/dev/sda1 Creation Time : Sun Sep 18 21:49:06 2016 Raid Level : raid1 Raid Devices : 6 State : clean Update Time : Sun Mar 19 19:08:01 2017 Array State : A..... ('A' == active, '.' == missing, 'R' == replacing) /dev/sdb1 Creation Time : Sun Sep 18 21:49:06 2016 Raid Level : raid1 Raid Devices : 6 State : clean Update Time : Sat Dec 3 12:09:26 2016 Array State : AA.... ('A' == active, '.' == missing, 'R' == replacing) /dev/sdc1 Creation Time : Sun Sep 18 21:49:06 2016 Raid Level : raid1 Raid Devices : 6 State : clean Update Time : Sat Dec 3 11:47:43 2016 Array State : AAA.AA ('A' == active, '.' == missing, 'R' == replacing) /dev/sdd1 Creation Time : Sun Sep 18 21:49:06 2016 Raid Level : raid1 Raid Devices : 6 State : active Update Time : Fri Dec 2 21:23:06 2016 Array State : AAAAAA ('A' == active, '.' == missing, 'R' == replacing) /dev/sde1 Creation Time : Sun Sep 18 21:49:06 2016 Raid Level : raid1 Raid Devices : 6 State : clean Update Time : Sat Dec 3 12:00:45 2016 Array State : AA..AA ('A' == active, '.' == missing, 'R' == replacing) /dev/sdf1 Creation Time : Sun Sep 18 21:49:06 2016 Raid Level : raid1 Raid Devices : 6 State : clean Update Time : Sat Dec 3 12:07:03 2016 Array State : AA...A ('A' == active, '.' == missing, 'R' == replacing)
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
