FreeNAS 0.7.2 to NAS4Free 9.2: CAM status: Command timeout

[stoiss]

Hi all

My first post here.

I'll admit I have been out of the "loop" for the last couple of years. I started out with the old FreeNAS 0.7.1, which I understand NAS4Free is a direct continuation of.

Lately my old fileserver running FreeNAS embedded 0.7.1-something-beta on a CF, started acting up and refused to connect to the LAN.

I got hold of a FreeNAS 0.7.2.8191 which I understand is the last release before the shift to NAS4Free, wrote it to the CF and restored the config from file.

Now the thing runs like a champ again. Of course - this is an old unsupported release and I would really like to upgrade to the latest version of NAS4Free.

So I wrote NAS4Free embedded 9.2.0.1.972 on another CF (yes I tested the CF with FreeNAS 0.7.2 first and it works), but now I get these errors when booting up:

NOP. ACB: 00 00 00 00 00 00 00 00 00 00 00 00
CAM status: Command timeout
Error 5, Retries exhausted

The bootup continues after this and I can configure IP and login to the WebUI normally.

Other posts about FreeNAS 0.7.2 --> NAS4Free upgrades don't seem to deal with these errors.
Also, a google search on these errors didn't turn up anything helpful.

What does the error mean and is it an error I should worry about?

Right now I'm still trying to figure out the best way to restore my old 0.7.2 config in 9.2. The WebUI doesn't understand the old format.
An alternative would be some sort of zpool import (I have already exported the old 0.7.2 pool), but I'm a bit worried about the data stored on the disks.
As a last alternative I may have to go through all the settings in the WebUI and do the setup manually based of screenshots from FreeNAS 0.7.2.

What do you suggest?

Cheers

[raulfg3]

I'll admit I have been out of the "loop" for the last couple of years. I started out with the old FreeNAS 0.7.1, which I understand NAS4Free is a direct continuation of.

yes , correct.

So I wrote NAS4Free embedded 9.2.0.1.972 on another CF (yes I tested the CF with FreeNAS 0.7.2 first and it works), but now I get these errors when booting up:

NOP. ACB: 00 00 00 00 00 00 00 00 00 00 00 00
CAM status: Command timeout
Error 5, Retries exhausted

CF are not recomended because premature burn-ing writes, if you use a CF2IDE, try to use an old 2,5 IDE Disk instead (cheap or free if you have an old laptop or know someone that have one.
PD: Your actual error is no communication with/to your CF (So I suspect some premature burn-ing of your CF, but perhaps is other case).

As a last alternative I may have to go through all the settings in the WebUI and do the setup manually based of screenshots from FreeNAS 0.7.2.

reconfigure all by hand is easy and secure.

print your 7.1.xml file to see your config.

1 - first you need a stable and IP configured system ( you need to reboot and see that your IP is good and enable SSH service, and that you can log-in by shell).
2 - Import your disk, to do this go to Disk page and use "Claer config & import disk" http://wiki.nas4free.org/doku.php?id=do ... management
3 - import your pool ( In ZFS section Disks|ZFS|Configuration ) use import button http://wiki.nas4free.org/doku.php?id=do ... n_detected
4 - once imported and working ZFS, you need to sync curren and detected config
5 - Enable and configure others services ( SAMBA, FTP, etc...)

[stoiss]

Hi Raul,

Thank you for your response. It pretty much got me back on track on NAS4Free in almost no time.

The CPU temperature still shows as -49C. This shows up correctly in FreeNAS 0.7.2 - even on clean installs before the config is restored. The CPU I'm using is a AMD Athlon(tm) Processor LE-1620 (64bit).

I understand CF is not recommended since constant writes and reads tend to degraded the CF. However there are also benefits of running an embedded install off a CF and similar types of memory disks.

I would expect the majority of the degradation to come from writes in the form of logging. Wouldn't it be possible to simple prevent the system from logging or simply log to /tmp instead?

Again thanks for the instructions.

[b0ssman]

if you have the embedded install with no swap and no data partition on the cf card there is no significant degradation.