I cannot get the SS4200 to boot FreeNAS 0_70. I can get the serial connection to work. Bot hangs after:
* Welcome to FreeNAS! *
* *
* 1. Boot [default] *
* 2. Boot with ACPI disabled *
* 3. Boot in Safe Mode *
* 4. Boot with verbose logging *
* 5. Escape to loader prompt *
* 6. Reboot

I have selected all the options but it just hangs after a line of text on the screen. Please help.

That's in connection to 115200/9600 baud discussion. I was told that FreeBSD's terminal supports only 9600, so you need to set baud rate to 9600 in SS4200 BIOS, then switch your terminal to 9600 as well, and then everything will work.

That did not work. Set the BIOS and putty session to 9600,8,n,1 but the same hang after the boot. I have disabled ACPI in the BIOS. Not sure what I am missing?

FreeBSD's boot loader only supports up to 9600bps unless compiled with BOOT_COMCONSOLE_SPEED set. The default is not. I have not tested FreeBSD with anything higher.

The kernel will not send klog messages to the serial device unless you set the following options in /boot/loader.conf:

console="comconsole"
comconsole_speed="9600"

Also make sure that at least the following is provided in /boot/device.hints, to tell the kernel that the first serial port (sio0) is willing to be a kernel log device:

hint.sio.0.flags="0x10"

I believe that's all I did.

Thanks. That worked. Now I am stuck at another screen.

Here is what I did. At the menu, I typed "5" and went to the "ok" prompt. At the "ok" prompt, I modified console by: console="comconsole"
and then "boot" from the ok prompt.

Now, it boots and you can see messages on the screen:
...
...
...
Generating .htpasswd.
Starting lighttpd.
Starting background file system checks in 60 seconds.

Sat Sep 19 04:43:25 UTC 2009

Jamba, I am stuck at the exact same spot. I believe it's because we have not setup our /etc/ttys properly to change ttyd0 to on and from dialup to vt100. However, without being able to get a shell to login, I don't see how to do that. Can anyone shed some light on this please?

Tim & Jamba: what's the problem? Just SSH right in...

I had to login to the web interface to enable SSH. However, I did edit the /etc/ttys file and made the changes that I mentioned in my prior post and it still doesn't produce a login prompt over my serial cable connection to HyperTerminal. No big deal as long as I have SSH I suppose, though I'd still like to know a solution for getting shell access via serial.

Tim:
1) did you try pressing Enter? IIRC, getty only shows login prompt on serial devices upon transition of CTS to high and I'm not sure the SS4200 cable routes that signal properly.
2) check running processes (from SSH) to ensure that getty is indeed running and attached to the serial port
3) use "kill -1 1" to reread your /etc/ttys, not reboot. (remember, /etc is on md0 RAM disk; on each reboot, it's re-populated from the flash card/whatever boot device you have)

I got the serial console fully working.
Here's what I did:

edited /cf/boot/loader.conf and added these lines:
boot_multicons="YES"
boot_serial="YES"
comconsole_speed="9600"
console="comconsole,vidconsole"

then in the FreeNAS web interface went to System -> Advanced, then Command Scripts
added the following scripts to execute PostInit in top to bottom order:
cat /etc/ttys | sed '/ttyd0/s/dialup/vt100/g' >/tmp/ttys1
cat /tmp/ttys1 | sed '/ttyd0/s/off/on/g' >/tmp/ttys2
rm -rf /etc/ttys
mv /tmp/ttys2 /etc/ttys
kill -1 1

Yes, I did the same. I realized that the login prompt was not showing up because no "getty" was running on the Serial port. I connected to the FreeNAS web interface and went to System -> Advanced -> File Editor and loaded the /etc/ttys file and modified the ttyd0 line to "on". I then saved the file on the web interface.

Then I went to System -> Advanced -> Command and typed in "kill -HUP 1" and clicked on Execute and got the login prompt on the Serial port.

I have documented all the steps in installing and running FreeNAS 0.70 with ZFS on my blog at: http://bitsforbytes.blogspot.com

Hello everyone,

As stated above on this page under PATA port issues:

"amd64 version of FreeNAS 0.70 cannot see the PATA port whatsoever. The solution is to use the i386 version, or add the following to /boot/device.hints:
hint.ata.0.at="isa"
hint.ata.0.port="0x1F0"
hint.ata.0.irq="14"
"

How do I modify a LiveCD installation of FreeNAS 0.70 and then boot from that CD and install it on the DOM?

Thanks

There was a recent thread on the FreeBSD-Questions mailing list about adding a feature to an installation CD:

http://lists.freebsd.org/pipermail/freebsd-questions/2010-January/210962.html

Basically, you must extract the existing CD contents, make your modifications, then re-squish everything back into an iso9660 image, taking care to specify the proper boot emulation and code.

As for the actual installation, you will need either a VGA card hack or a serial hack to actually interact with the installer.

Personally, I just burn the DOM with an image prepared on another system entirely, and forego all preinstallation interaction entirely.

I probably can do that too on another system, but since FreeBSD/FreeNAS 64-bit do not include the IDE/PATA drivers, it will still not work on SS4200 once brought in.

I don't know if 64bit version will make any difference since SS4200 can only have 2GB memory so the argument that if you have a 64-bit CPU you should always install a 64-bit OS is moot because there won't be any significant benefit on SS4200.

I install freenass by booting it into emergency mode with usb flash. Then dd embedded image to dom /dev/ad0. Mount /dev/ad0a to somewhere. Modify device.hints to includes those ata lines.

I successfully install Full version FreeNas amd64 from usb-flash without using CD-ROM at all.

1. Create bootable usb flash. I use Grub4Dos. HowTO (http://clsv.livejournal.com/7278.html).
a) format flash to FAT32 with HPUSBFW (http://narod.ru/disk/6621841000/HPUSBFW.rar.html)
b) Install GRUB4DOS_GUI on your flash (http://narod.ru/disk/6621849000/GRUB4DOS_GUI.rar.html)
c) Edit MENU.LST. You must delete two first lines which loading graphic wallpaper. And add lines to boot freenas iso image:

title FreeNAS install
map /freebsd/bootonly.iso (hd32)
map --hook
chainloader (hd32)
boot

2. Boot from flash in emergency mode ss4200 or set option in BIOS to boot from USB.
3. in FreeBSD boot screen press option 5 and in command prompt enter: set console=comconsole. Reconnect to serial port on 9600 speed. Press 'Enter' and enter command 'boot' to boot freenas kernel.
4. in Freenas command prompt you should create freenas-iso device:

mdconfig -a -t vnode -f /cf/freebsd/bootonly.iso -u 2

Check that you device mount properly:

mkdir /mnt/cdrom
mount -t cd9660 /dev/md2 /mnt/cdrom

and unmount it: umount /mnt/cdrom

5. Through freenas web-interface modify function get_cdrom_list() in file: /etc/inc/util.inc.

I modified this function like this:

function get_cdrom_list()
{
$disklist = array();

$disklist[md2] = array();
$disklist[md2]['name'] = "md2";
$disklist[md2]['devicespecialfile'] = "/dev/md2";
$disklist[md2]['type'] = "IDE";
$disklist[md2]['size'] = "NA";

$disklist[$diskname]['desc'] = "md2";

return $disklist;
}

6. Save file and install freenas to your DOM. Press 9 in freenas start menu. Next press '3'... etc.
7. After installation, if you install amd64, don't forget mount /dev/ad0s1 and edit /boot/device.hints as described above and loader.conf. And delete unneeded bootonly.iso from directory /cf on DOM after reboot.

I using FreeNAS custom image from this site: http://shell.peach.ne.jp/aoyama/
because it included ZFS pool version 13 and use FreeBSD 7.3-RC2 :)
I created mirroring ZFS tank from 2 WD20EARS (WD 2TB green with AFD). And it work great!

FreeNAS 0.71 is now released. Did anyone here test the shutdown problem was solved?

Nope. It's solved in FreeBSD 8 - FreeNas is based on 7.

i'm constantly running into the:

run_interrupt_drive_hooks: still waiting after 60 seconds for xpt_config
run_interrupt_drive_hooks: still waiting after 120 seconds for xpt_config
run_interrupt_drive_hooks: still waiting after 180 seconds for xpt_config
...

can anyone help?

xyyz: sounds like the USB issue as described above. Try disabling USB in the bios

hmmm, that's a problem because the CDROM drive's USB. there's no other work around? i've tried both the x86 and amd64 versions.