NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
DOLMark
Jun 28, 2017Aspirant
ReadyNAS NV+ Stuck on Booting
Hi
Got a clients NV+ that'd hung completely. It responded to pings but nothing else.
Have rebooted it and I get;
- All Drives led's green
- Can Ping device
- No HTTP access
- No SSH access
- No sign of it on raidar (under OSX)
- LCD Display says "Booting ..." followed by "Checking FS"
No %'age display and no activity light after a short while
If I reboot using the "Skip filesystem checks" option I get exactly the same apart from;
- LCD Display shows Booting ...
- Power Blue LED goes from Pulsing to Solid and then Pulsing again etc
- When it does this the ping goes;
64 bytes from 192.168.1.251: icmp_seq=861 ttl=64 time=1.049 ms
64 bytes from 192.168.1.251: icmp_seq=862 ttl=64 time=9.335 ms
64 bytes from 192.168.1.251: icmp_seq=863 ttl=64 time=1.801 ms
64 bytes from 192.168.1.251: icmp_seq=864 ttl=64 time=1.561 ms
64 bytes from 192.168.1.251: icmp_seq=865 ttl=64 time=1.534 ms
64 bytes from 192.168.1.251: icmp_seq=866 ttl=64 time=0.873 ms
64 bytes from 192.168.1.251: icmp_seq=867 ttl=64 time=2.184 ms
64 bytes from 192.168.1.251: icmp_seq=868 ttl=64 time=1.646 ms
64 bytes from 192.168.1.251: icmp_seq=869 ttl=64 time=6952.255 ms
64 bytes from 192.168.1.251: icmp_seq=870 ttl=64 time=5949.652 ms
64 bytes from 192.168.1.251: icmp_seq=871 ttl=64 time=4948.032 ms
64 bytes from 192.168.1.251: icmp_seq=872 ttl=64 time=3944.158 ms
64 bytes from 192.168.1.251: icmp_seq=873 ttl=64 time=2943.767 ms
64 bytes from 192.168.1.251: icmp_seq=874 ttl=64 time=1943.396 ms
64 bytes from 192.168.1.251: icmp_seq=875 ttl=64 time=943.577 ms
64 bytes from 192.168.1.251: icmp_seq=876 ttl=64 time=27.301 ms
64 bytes from 192.168.1.251: icmp_seq=877 ttl=64 time=4.686 ms
64 bytes from 192.168.1.251: icmp_seq=878 ttl=64 time=0.972 ms
64 bytes from 192.168.1.251: icmp_seq=879 ttl=64 time=0.898 ms
64 bytes from 192.168.1.251: icmp_seq=880 ttl=64 time=1.633 ms
Which is possibly it watchdogging?
Device has 4 drives in it.
Help? I've run out of ideas :-(
Mark
12 Replies
Replies have been turned off for this discussion
- StephenBGuru - Experienced User
Try powering down, removing the disks (labeling by slot). Then power up, and confirm that RAIDar can see the NAS (no disks status).
If you have access to a windows machine, try testing the disks with vendor tools (Lifeguard for Western Digital, Seatools for Seagate)
FWIW, the guidance in the readynas led language document says:
ReadyNAS OS is booting, this stage should not last for more than 3 minutes. Otherwise, one of disk may be bad or incompatible. SATA backplane is the next to be questioned, and then NAND or SODIMM.
So maybe try running the memory test while the disks are being tested.
- DOLMarkAspirant
Hi Stephen
Thanks for the quick reply.
With drives removed OSX Raidar does indeed see it in "No disks detected" status
Memory test is as far as "checking pat 2" without complaining yet
Guess I need to find a windows machine to borrow to test the drives. Everything here is OSX or Ubuntu.
Mark
- StephenBGuru - Experienced User
If you can't find a windows machine, you should still be able to run a SMART diag with smartctl.
Related Content
NETGEAR Academy

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