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)This disk needed replacing back when you last did a factory reset (wipes all data, settings, everything).
Your smart_history.log shows:
time model serial realloc_sect realloc_evnt spin_retry_cnt ioedc cmd_timeouts pending_sect uncorrectable_err ata_errors ------------------- -------------------- -------------------- ------------ ------------ -------------- ---------- ------------ ------------ ----------------- ---------- 2016-09-18 23:50:58 ST3000DM001-1CH166 XXXXXXXX 216 216 0 0 0 0 0 6 2016-09-24 03:59:12 ST3000DM001-1CH166 XXXXXXXX 232 232 0 0 0 0 0 6 2016-09-25 03:46:26 ST3000DM001-1CH166 XXXXXXXX 240 240 0 0 0 0 0 6 2016-09-25 03:48:32 ST3000DM001-1CH166 XXXXXXXX 896 896 0 0 0 0 0 6 2016-09-25 03:50:39 ST3000DM001-1CH166 XXXXXXXX 1320 1320 0 0 0 0 0 6 2016-09-26 03:46:34 ST3000DM001-1CH166 XXXXXXXX 1472 1472 0 0 0 0 0 6 2016-09-26 03:48:41 ST3000DM001-1CH166 XXXXXXXX 2224 2224 0 0 0 0 0 6 2016-09-26 03:54:50 ST3000DM001-1CH166 XXXXXXXX 2824 2824 0 0 0 8 8 6 2016-09-27 03:43:40 ST3000DM001-1CH166 XXXXXXXX 3048 3048 0 0 0 8 8 6 2016-09-27 03:49:50 ST3000DM001-1CH166 XXXXXXXX 5216 5216 0 0 0 8 8 6 2016-09-27 03:56:00 ST3000DM001-1CH166 XXXXXXXX 7520 7520 0 0 0 8 8 6 2016-09-27 04:02:10 ST3000DM001-1CH166 XXXXXXXX 8208 8208 0 0 0 8 8 6 2016-10-03 07:23:15 ST3000DM001-1CH166 XXXXXXXX 8216 8216 0 0 0 8 8 6 2016-10-05 01:17:38 ST3000DM001-1CH166 XXXXXXXX 8304 8304 0 0 0 8 8 6 2016-10-05 01:19:49 ST3000DM001-1CH166 XXXXXXXX 8496 8496 0 0 0 8 8 6 2016-10-05 01:22:00 ST3000DM001-1CH166 XXXXXXXX 8656 8656 0 0 0 8 8 6 2016-10-05 01:24:10 ST3000DM001-1CH166 XXXXXXXX 8888 8888 0 0 0 8 8 6 2016-10-05 01:26:20 ST3000DM001-1CH166 XXXXXXXX 9136 9136 0 0 0 8 8 6 2016-10-05 01:28:31 ST3000DM001-1CH166 XXXXXXXX 9512 9512 0 0 0 8 8 6 2016-10-05 01:30:42 ST3000DM001-1CH166 XXXXXXXX 9864 9864 0 0 0 8 8 6 2016-10-05 01:32:54 ST3000DM001-1CH166 XXXXXXXX 10000 10000 0 0 0 8 8 6 2016-10-05 01:35:05 ST3000DM001-1CH166 XXXXXXXX 10416 10416 0 0 0 8 8 6 2016-10-05 01:37:17 ST3000DM001-1CH166 XXXXXXXX 10576 10576 0 0 0 8 8 6 2016-11-27 19:34:19 ST3000DM001-1CH166 XXXXXXXX 10584 10584 0 0 0 0 0 6 2016-12-02 19:16:51 ST3000DM001-1CH166 XXXXXXXX 16472 16472 0 0 0 2592 2592 6 2016-12-02 19:25:54 ST3000DM001-1CH166 XXXXXXXX 16696 16696 0 0 0 2608 2608 6 2016-12-02 19:30:27 ST3000DM001-1CH166 XXXXXXXX 16760 16760 0 0 0 2640 2640 6 2016-12-02 19:42:12 ST3000DM001-1CH166 XXXXXXXX 16832 16832 0 0 6 2816 2816 6 2016-12-02 19:47:16 ST3000DM001-1CH166 XXXXXXXX 16832 16832 0 0 8 2816 2816 6 2016-12-02 19:54:38 ST3000DM001-1CH166 XXXXXXXX 16832 16832 0 0 10 2816 2816 6 2016-12-02 20:02:03 ST3000DM001-1CH166 XXXXXXXX 16832 16832 0 0 12 2816 2816 6 2016-12-02 20:16:38 ST3000DM001-1CH166 XXXXXXXX 16856 16856 0 0 18 2848 2848 6 2016-12-02 20:22:04 ST3000DM001-1CH166 XXXXXXXX 16856 16856 0 0 20 2896 2896 6 2016-12-02 20:29:30 ST3000DM001-1CH166 XXXXXXXX 16864 16864 0 0 23 2896 2896 6 2016-12-02 20:34:15 ST3000DM001-1CH166 XXXXXXXX 16864 16864 0 0 25 2896 2896 6 2016-12-02 20:49:08 ST3000DM001-1CH166 XXXXXXXX 16904 16904 0 0 30 2912 2912 6 2016-12-02 20:56:36 ST3000DM001-1CH166 XXXXXXXX 16904 16904 0 0 32 2936 2936 6 2016-12-02 20:59:14 ST3000DM001-1CH166 XXXXXXXX 16904 16904 0 0 32 2944 2944 6 2016-12-02 23:14:35 ST3000DM001-1CH166 XXXXXXXX -1 -1 -1 -1 -1 -1 -1 34 2016-12-02 23:17:48 ST3000DM001-1CH166 XXXXXXXX -1 -1 -1 -1 -1 -1 -1 61
Can you remove the bad disk and try and boot up again and see if it comes up fine. I think it should.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
