PfSense on Alix2d13 - Boot error

d82k

Dear all,

I have downloaded the following image: pfSense-2.2.2-RELEASE-4g-i386-nanobsd.img, and copied on my 4GB CF.

Unfortunately when I try to boot the frist time I receive this error: "Mounting from ufs:/dev/ufs/pfsense0 failed with error 19."

I think I have found the solution here: https://doc.pfsense.org/index.php/Boot_Troubleshooting#NanoBSD_on_Newer_Hardware

But I cannot get the "loader prompt".
"After the F1/F2 prompt and the kernel loads, press space to get a loader prompt." it does not work…

PC Engines ALIX.2 v0.99h
640 KB Base Memory
261120 KB Extended Memory

01F0 Master 044A CF Card
Phys C/H/S 7314/16/63 Log C/H/S 914/128/63

1  pfSense
2  pfSense

F6 PXE
Boot:  1
/boot/config: -h
Consoles: serial port
BIOS drive C: is disk0
BIOS 640kB/261120kB available memory

FreeBSD/x86 bootstrap loader, Revision 1.1
(root@pfs22-i386-builder, Mon Apr 13 20:28:31 CDT 2015)
Loading /boot/defaults/loader.conf
/boot/kernel/kernel text=0x11fb1a7 data=0x832e48+0x279e60 syms=[0x4+0xf3a10+0x4+0x16bd76]

Hit [Enter] to boot immediately, or any other key for command prompt.
Booting [/boot/kernel/kernel]...

I'm using putty… any idea/suggestions on how I can get the prompt please?
Thank you
dk

doktornotor

You do not need any prompt. This works out of the box. Try some other tools to write a working image on the CF.

d82k

Thank you for your reply…

I just did

# gzip -d pfSense-2.2.2-RELEASE-4g-i386-nanobsd.img.gz
# dd if=./pfSense-2.2.2-RELEASE-4g-i386-nanobsd.img of=/dev/sdc bs=1M

where sdc is my CF…

Anything wrong?

EDIT: I try with a smaller image

d82k

Solved using a 2GB image.

Is there a way to expand the partition? it seems pfsense believes my CF is 2GB only…

doktornotor

Expand? No, not really. (Also, there are two system slices you can switch between.)

stephenw10

Yeah. there's no practical way to expand the image. It's possibe to create another slice in the remaiing space and use it for something but I wouldn't recommend it. Are you running out of space?
I usually run the 1GB image simply because it writes to the card faster.
That's a curious error though, I thought the images were now small enough for even the most optimistic definition of 4GB! What card do you have?

Steve