NV+ 4.1.10 reboot failed.. flashing LEDs

[paflyer]

I attempted to update to the 4.1.10 version for my NV+, but the reboot failed and I have the following lights flashing:
Power (blue) slow blinking
#3, followed by all 4 drive lights in an alternating pattern (3, all, 3, all)
The LED display says (of course) BOOTING....

I have tried booting with NO drives installed, same same. I tried leaving the unit off all day while at work and turned it on when I got home, same same. I'm not real keen on trying single-drive boot-ups after reading some of the stories here. I have 4 drives @ 500g each, no REAL critical data (ESXi storage drive, along with some misc files I have or can get again) This has been running for a few months (since purchase back in Feb) on 4.1.8, and I probably should've left well enough alone :cry:

ideas, suggestions, pointers... I would like to get back to studying both ESXi and Windows servers before I forget what I've already learned. As a "not a spring chicken anymore", I forget fast!

Thanks for any info.

Mike

[mdgm-ntgr]

Looking at http://www.readynas.com/kb/faq/hardware/what_does_this_light_pattern_mean

it seems to indicate that "OS image on NAND is corrupted, please perform NAND recovery through USB"

So you may wish to try a USB Boot Recovery (http://www.readynas.com/kb/faq/boot/how_can_i_perform_a_boot_recovery_using_a_usb_flash_device). Don't do a TFTP one as TFTP boot recovery is unreliable.

[paflyer]

I thought that might be it, but the power light isn't off, it's blinking... and the #3 light isn't the only light that comes on, unless the "all 4 drive lights flashing" isn't part of the pattern.

OTOH, I'll try the USB flash drive recovery after I find a USB stick around this house that doesn't have that stupid E3 booter on it .

Thanks for the links.

[mdgm-ntgr]

The pattern I was referring to is power LED pulsating (not off) throughout, disk LED 3 on, all LEDs on, disk LED 3 on, all LEDs on etc.

Notice the arrows indicating that it's a pattern that loops?

Is that what you're seeing or something else?

[paflyer]

OK.. I see it now (d'oh!)... still have to find a USB around here that doesn't have that stupid e3 boot crap on it. If all else fails, I'll go buy one tonight.

I would've replied sooner, but this week has been the week from hell. Thanks for the links. Re-reading them again now.

[paflyer]

😄 That fixed it. Booted from the USB, no issue. Took a while to boot up as it checked each disk in turn, then shutdown with the word "Successful!" in the LED screen. Turned it back on, and everything was there working.

Very sweet. Still having the files was nice, but there was nothing on there I didn't have elsewhere... it just would've meant time rebuilding the ESXi images and server setup.

THANK YOU for your help. I really appreciate it!
Mike

[maxblack]

Congrats paflyer on resolving your problem! So if I understand this correctly, the "USB Boot Recovery" process you went thru paflyer reverted your firmware to 4.1.8? Izzat right?

Maybe mdgm can comment: is there/will there be a USB Boot Recovery image made available for 4.1.10? It seems the lack of same would be a compelling enough reason to NOT attempt a 4.1.10 upgrade at this time?

[mdgm-ntgr]

I'll need to ask Skywalker whether there'll be a USB Boot Recovery image. It's possible there may already be one.

[paflyer]

maxblack wrote:
Congrats paflyer on resolving your problem! So if I understand this correctly, the "USB Boot Recovery" process you went thru paflyer reverted your firmware to 4.1.8? Izzat right?

Yes, I reverted back to 4.1.8, which was the firmware I was running before the attempted update to 4.1.10... Think I'll stay at 4.1.8 for a while, although I still have that USB image should something happen again!! 😄

Thanks again, mdgm, for the pointers.