stuck on reboot - HELP !!!

[Doug Benet]

I was accessing my FreeNas using SSH - I ran the command REBOOT from the SBIN or BIN folder don't remember which folder. I just ran the command. The system rebooted but then it got stuck with the following message:

Loading /boot/defaults/loader.conf
|

I did some manual reboot. I also pressed the ESC key to choose the USB boot drive. Tried several options, but I keep getting stuck with the same message.
I was on the way to make a backup of all my configuration.

Don't know what to do. HELP.
I cant afford to lose the files on the FreeNas server.

Thanks

 

[gcooper]

I was accessing my FreeNas using SSH - I ran the command REBOOT from the SBIN or BIN folder don't remember which folder. I just ran the command. The system rebooted but then it got stuck with the following message:

Loading /boot/defaults/loader.conf
|

I did some manual reboot. I also pressed the ESC key to choose the USB boot drive. Tried several options, but I keep getting stuck with the same message.
I was on the way to make a backup of all my configuration.

Don't know what to do. HELP.
I cant afford to lose the files on the FreeNas server.

Try upgrading via the CD. Hopefully *crosses fingers* it was just a corrupt/wonky install (it would help to know what you did prior to that point -- did you setup serial console access perhaps?).

Worst comes to worst, you'll need to reinstall from scratch, but your data is still available on the volumes [assuming you don't accidentally toast them]. Thus, if you do autoimport and set everything up again you'll have access to it. Best of luck!

 

[Doug Benet]

Everything was fine prior the error. The server was up for seven days without a glitch. I log in to the server using the Terminal program (OSX Lion) inside my own network.

Step 1
#ssh root@ip
#password
# Everything fine

Step 2
# ls
# cd /sbin or /bin (don`t remember which folder it was - but I issued a REBOOT command)
# reboot

Step 3
The server gets stuck in the boot processes

Is there anyway to repair it? What if I mount it in a FreeBSD system and tried to do something?

 

[Doug Benet]

Try upgrading via the CD. Hopefully *crosses fingers* it was just a corrupt/wonky install (it would help to know what you did prior to that point -- did you setup serial console access perhaps?).

Worst comes to worst, you'll need to reinstall from scratch, but your data is still available on the volumes [assuming you don't accidentally toast them]. Thus, if you do autoimport and set everything up again you'll have access to it. Best of luck!

I did the upgrade via the CD and it worked no problems at all. Thanks for the help.

 

[gcooper]

I did the upgrade via the CD and it worked no problems at all. Thanks for the help.

What version was this BTW? There was a bug that I "quietly" fixed in 8.0.3/8.0.4 where it could set the wrong slice active in ix-update and it would get lost booting a blank partition. This shouldn't be an issue in 8.0.4 at least... That being said, ticket # 875 is similar to what you've described (and I'm looking into that in the background for loloish).

 

[gcooper]

Everything was fine prior the error. The server was up for seven days without a glitch. I log in to the server using the Terminal program (OSX Lion) inside my own network.

Step 1
#ssh root@ip
#password
# Everything fine

Step 2
# ls
# cd /sbin or /bin (don`t remember which folder it was - but I issued a REBOOT command)
# reboot

Step 3
The server gets stuck in the boot processes

Is there anyway to repair it? What if I mount it in a FreeBSD system and tried to do something?

Issuing

Code:

reboot

is a bad idea, potentially, because it doesn't wait for services to stop before rebooting.

Code:

shutdown -r now

is better.