freeNAS wont boot after update

Status
Not open for further replies.

macdog

Cadet
Joined
Nov 16, 2015
Messages
4
Hi just wondering if anyone can tell me how screwed I am! Just did an update from my freeNAS web interface. The system rebooted but I get "isolinux.bin missing or corrupt" on the console. I guess that means my boot device is screwed (USB stick).

Any advice on recovering it (gonna be a right pain building the whole thing again from scratch!). I can see the partitions in windows, but that's about it.

Thanks.
 
D

dlavigne

Guest
Do you get the same error if you reboot into an earlier boot environment?
 

danb35

Hall of Famer
Joined
Aug 16, 2011
Messages
15,504
Do you have a backup of your config file? If so, easy: install a clean copy of FreeNAS to a new USB stick, boot from that stick, and upload your saved config file.

If not, harder. You'll still need to install a clean copy of FreeNAS to a new USB stick, but then you'll need to recover your config file from the old stick. And then you'll need to set up your system to make backups of your config file, so you don't have this problem again in the future.
 

macdog

Cadet
Joined
Nov 16, 2015
Messages
4
Do you get the same error if you reboot into an earlier boot environment?

I wanted to try that, but I don't even see the grub loader. Goes from POST to "failed to boot. isolinux.bin missing or corrupt".
 

macdog

Cadet
Joined
Nov 16, 2015
Messages
4
Do you have a backup of your config file? If so, easy: install a clean copy of FreeNAS to a new USB stick, boot from that stick, and upload your saved config file.

If not, harder. You'll still need to install a clean copy of FreeNAS to a new USB stick, but then you'll need to recover your config file from the old stick. And then you'll need to set up your system to make backups of your config file, so you don't have this problem again in the future.

I don't, but obviously after this episode that's something I will be doing. The plan was always to get another USB stick and run both of them, but slipped my mind! Learning the hard way!

Thanks, this looks like a decent plan B if I can't recover the existing device as-is.
 
Status
Not open for further replies.
Top