Can't reboot after power loss

[BlazeStar]

Using FreeNAS-9.2.1.6-RELEASE-x64

This morning there was a power loss.

The UPS ran out of battery and successfully executed a clean shutdown of FreeNAS.

Now the power is back, and when trying to reboot, I get this message on console :

http://cl.ly/image/2c3z0a3G1I2S

I'm starting to panic...

You guys have any idea what's up with this and how to fix it??

 

[hugovsky]

It seems you have a corrupted installation. Try re-install in another usb stick and restore backup config.

 

[BlazeStar]

I don't have a recent backup config, is there any way to extract that from the key??

 

[BlazeStar]

However, I do a replication everyday on a different machine.

Is there any way to extract the config from that?

Please say yes!!!

I'd really like to avoid losing my config.



Finally, it was a 9.2.1.6 install.

Would it be a good idea to upgrade to 9.3 in the same time ?

 

[enemy85]

You can try to extract the old config from the old usb key (if it's still accessible and working), i read it once on the forum but can't recall where. Try to search for it.

 

[Bidule0hm]

If it wasn't a 9.3 then you can easily mount the USB drive (if it's not to much damaged of course) on an UNIX system. Just boot from a live CD of Ubuntu of whatever and mount the USB drive with it ;)

 

[Fraoch]

Would it be a good idea to upgrade to 9.3 in the same time ?

Scientific method: only change one parameter at a time.:)

Get your data and configuration file back first, then once they're both nice and safe, try upgrading.

 

[BlazeStar]

If it wasn't a 9.3 then you can easily mount the USB drive (if it's not to damaged of course) on an UNIX system. Just boot from a live CD of Ubuntu of whatever and mount the USB drive with it ;)

Should I be able to mount it straight on my MAC (OS X 10.10.2) ?

Scientific method: only change one parameter at a time.:)

Get your data and configuration file back first, then once they're both nice and safe, try upgrading.

You're absolutely right.

 

[Bidule0hm]

I don't know many things about Mac OS (beside the fact that it's a paying bloated FreeBSD...) but in theory, yes, you should be able to mount it via the CLI and the mount command ;)

 

[gpsguy]

Here's a link to attempt recovery using FreeNAS: https://forums.freenas.org/index.php?threads/recover-freenas-configuration-from-os-drive.15426/

 

[cyberjock]

Here's a link to attempt recovery using FreeNAS: https://forums.freenas.org/index.php?threads/recover-freenas-configuration-from-os-drive.15426/

Wont work on 9.3.

 

[BlazeStar]

Here's a link to attempt recovery using FreeNAS: https://forums.freenas.org/index.php?threads/recover-freenas-configuration-from-os-drive.15426/

Nice procedure!

I've been trying that.

Code:

[root@freenas] /var/tmp/cfgmount# camcontrol devlist
<Kingston DataTraveler G3 PMAP>    at scbus9 target 0 lun 0 (pass8,da5)

Then:

Code:

[root@freenas] /var/tmp/cfgmount# mount -o ro /dev/da5s4 /var/tmp/cfgmount
mount: /dev/da5s4: Invalid argument

Does this mean my USB key is dead :S

At this point I don't know what to do and, OF COURSE, I don't have a recent config file.

I guess this doesn't get backed up with replication right?

 

[enemy85]

Thank you @gpsguy , i remembered there was something. @BlazeStar if you are still on the 9.2.1.6 as you said, you could try to save the configuration file that way.

 

[BlazeStar]

Nice procedure!

I've been trying that.

Code:

[root@freenas] /var/tmp/cfgmount# camcontrol devlist
<Kingston DataTraveler G3 PMAP>    at scbus9 target 0 lun 0 (pass8,da5)

Then:

Code:

[root@freenas] /var/tmp/cfgmount# mount -o ro /dev/da5s4 /var/tmp/cfgmount
mount: /dev/da5s4: Invalid argument

Does this mean my USB key is dead :S

At this point I don't know what to do and, OF COURSE, I don't have a recent config file.

I guess this doesn't get backed up with replication right?

Some more info, to complete my post just above.

If I plug in the USB key in my OS X 10.10.2 computer, I'll see the key.

Of course I can't read it because the filesystem is not recognized.

I still can see the partitions:

Code:

diskutil list
/dev/disk7
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:     FDisk_partition_scheme                        *4.0 GB     disk7
   1:                    FreeBSD                         988.3 MB   disk7s1
   2:                    FreeBSD                         988.3 MB   disk7s2
   3:                    FreeBSD                         1.5 MB     disk7s3
   4:                    FreeBSD                         21.2 MB    disk7s4

And I do see the 4th slice.

With the disk utility app I could even make a DMG file of the 4th slice, just in case it could be useful.

I'm still hoping there is faith for my config to be restored somehow!!

 

[zambanini]

what is so special about your config that you spend so much time to recover it instead of recreating the settings?

 

[BlazeStar]

what is so special about your config that you spend so much time to recover it instead of recreating the settings?

Well the main thing is that I have several users and groups.

And so I have CIFS shares very well configured to work with those users and groups.

So it'd be a real pain in the ass to rebuild all that.


I've also done several tweaks in the GUI and I would much like to recover that.

Namely, I had to play a lot with the NFS shares to mount them for my virtualization node.

I knew how to do it from command line, but I wanted to do it from the GUI and I succeeded, but it took a while.


So of course i could do everything again but I'd really like to succeed in recovering my config.