Orbi WiFi 7 RBE973
Reply

NV+ (4.1.12) - Stuck at "Booting - found bad disk"

mccasle
Follower

NV+ (4.1.12) - Stuck at "Booting - found bad disk"

I am running four Seagate Barracuda 1.5 TB drives. After my UPS died, I had to reboot all three NV+ boxes. The first two came back perfectly.

On the third one, the power button flashes 3 times and then the activity button flashes 1 time. The pattern then repeats itself.

Is this an indication that drive 3 is bad? How best to remedy since I cannot get this to show on Raidar?

Thanks!
Message 1 of 5
mdgm-ntgr
NETGEAR Employee Retired

Re: NV+ (4.1.12) - Stuck at "Booting - found bad disk"

No. This does not indicate which disk is bad.
Message 2 of 5
2Nutz
Aspirant

Re: NV+ (4.1.12) - Stuck at "Booting - found bad disk"

Your best starting reference point for the light pattern would be at the below link.

http://www.readynas.com/kb/faq/hardware ... ttern_mean

Since you have 2 other units which are the same, why not take out the drives of the failing box and install them in one of the units that you know is functioning. Should tell you real quick if its a drive problem or NAS problem.
Message 3 of 5
mdgm-ntgr
NETGEAR Employee Retired

Re: NV+ (4.1.12) - Stuck at "Booting - found bad disk"

If the LCD says a disk is bad I wouldn't start by moving the drives to another chassis. You should only migrate redundant arrays.

If you can put the NAS in tech support mode and PM me your I.P. etc. I can do a quick check to see which disk is probably the one the NAS has identified as being bad.
Message 4 of 5
mdgm-ntgr
NETGEAR Employee Retired

Re: NV+ (4.1.12) - Stuck at "Booting - found bad disk"

The problem disk is disk 1:


# get_ata_errors /dev/hdc
49996
# get_ata_errors /dev/hde
0
# get_ata_errors /dev/hdg
0
# get_ata_errors /dev/hdi
0


That ATA error count is huge. Power off the NAS, remove disk 1 and try booting again. What happens?
Message 5 of 5
Top Contributors
Discussion stats
  • 4 replies
  • 1913 views
  • 0 kudos
  • 3 in conversation
Announcements