Locked up after updating, Now won't boot

[Tazap55]

After doing today's update from inside of freenas 9.10 stable, the reboot locked up and won't boot up freenas even from a shutdown. Do I need to need to download the latest (9.10.1) and reinstall to my usb stick to get it working without losing my storage files? Am desperate and appreciate any help.

Thanks in advance.
Tazap55

 

[m0nkey_]

If it's not booting, likely a bad boot device. To recover, perform a fresh install of 9.10.1, import your pool and config.

 

[philhu]

Seeing same here on my test system.

Boot device is mirrored ssd, not usb stick

 

[dlavigne]

Hard to tell without knowing your full hardware specs, please post them.

 

[dlavigne]

Seeing same here on my test system.

Boot device is mirrored ssd, not usb stick

There's been a couple of people mentioning issues with SSD after upgrade. Please create a bug report at bugs.freenas.org that includes your debug (created from System -> Advanced -> Save Debug) as well as any error messages (or an indication if it is just freezing), and post the issue number here.

 

[Tazap55]

Thanks for the replies !
I noticed in my bios that it didn't show my boot device, so I shut down the puter, unplugged my boot stick and reseated it and turned back on. Then went back into bios and my boot stick was there again. Rebooted and freenas 9.10.1 booted up OK now !

Thanks Again,
Tazap55

 

[philhu]

After hearing this, I went in and moved my SSD to another acpi port and changed the boot device in my bios.

Booted fine too.

 

[Lazulitone]

Tazap55, Philhu,

I am experiencing this exact problem on USB. It's exactly the way Taz describes it. I am disappointed to learn that it's also happening on your SSDs. I was able to change the USB port and get the system to boot, however, just a week later my USB drive has failed again. It feels like there is some kind of underlying problem with the Freenas boot device drive behavior and it is not isolated to either SSD or USB. **Something is killing these drives**.

Are you guys still experiencing e-mail reports relating to your boot devices? Taz - I am very curious to learn if you successfully imported your data pool? I am about to try the same thing and I'm afraid I'll lose all my data.

Thanks,

Laz

 

[Tazap55]

Tazap55, Philhu,

I am experiencing this exact problem on USB. It's exactly the way Taz describes it. I am disappointed to learn that it's also happening on your SSDs. I was able to change the USB port and get the system to boot, however, just a week later my USB drive has failed again. It feels like there is some kind of underlying problem with the Freenas boot device drive behavior and it is not isolated to either SSD or USB. **Something is killing these drives**.

Are you guys still experiencing e-mail reports relating to your boot devices? Taz - I am very curious to learn if you successfully imported your data pool? I am about to try the same thing and I'm afraid I'll lose all my data.

Thanks,

Laz

By unplugging and re-pluging the usb boot drive, then the bios was able to find that usb drive and able to set it as the boot drive. I have had absolutely no problems since with any data on that usb drive. I almost believe that the problem was caused by freenas trying to activate the watchdog timer in my motherboard's bios, in which I always keep disabled in bios for I am the only user of my nas. This seemed to have stopped knocking off my usb drive from being detected, once I fixed the watchdog timer issues from freenas trying to load it's ipmi module. The workaround for me was - unload the ipmi module by putting "kldunload ipmi" in postinit (and reboot).
Hope this help ya,
Taz