Lost networking, FreeNAS now in continual reboot

[avalon60]

I lost all my network early yesterday morning, and after getting most devices back , Freenas could not be found when I tried to connect by its' IP address.
I have now connected a monitor and keyboard to the system and saw that FreeNAS looked like it was locked up. I did a hard reset using the button on the case, and now FreeNAS is just in a continual reboot.

I wanted to find its' IP address, in case it had changed, and that is why I did what I did.

Now FreeNAS has locked up after the n'th reboot, saying
stopped at vfs_busy+0x1df: addb %al,(%rax)

The boot drive is a 16Gb Sandisk ssd, but have 2 sandisk cruzer 16Gb drives , 1 inside and the other outside in the USB ports
Is there any way of getting FreeNASback up and running as it has done for the last 5 years.
Thanks

 

[dlavigne]

Sounds like the boot device failed. Do a fresh install of the same version to a new boot device. If that resolves the issue, you can restore a previously saved config.

 

[avalon60]

Could I boot from an older version which is on the Sandisk USB drive, I think 9.? something and then upload the last backup I have. or is that too big a jump.
Thanks

 

[dlavigne]

Just be careful that the config is not newer than the OS version. If in doubt, you're better off reinstalling the same version as the config.

 

[avalon60]

Yes ok, I'm going to install the same version, as I've just flashed it to a 16gb usb stick

 

[avalon60]

I've installed FreeNAS 11.2 onto a 16gb sandisk cruzer blade, and now on booting up I am getting this:
CPU 5 COR (256) OVER ICACHE L0 IRD error.
Is it serious.

Also getting : em0 no link and also em1 no link and gave up.
I have a ethernet cable plugged in to one of the rj45 ports, but there is not ip address to get to gui, and upload my backup

 

[Redcoat]

CPU 5 COR (256) OVER ICACHE L0 IRD error.

Didn't you have an encounter with this last year?

 

[avalon60]

Not as far as I can remember.

I've edited my [post above with more bad news.

 

[avalon60]

I can't edit my post, but now I found that I did have this problem last April, and I'm going to dio what I did then and see what happens