Can't boot with NanoBSD. Two or one slice?

bellera

I want to migrate from 1.2.3 to 2.0…

Does anybody know if I have to do the same? Or not needed?

1. Modify the CF on a running box:

sysctl kern.geom.debugflags=16
boot0cfg -v -B ad0

2. Go with the modified CF to NO RUNNING box:

Booting … serial ...

Limitation: No possible to boot from the second slice, as you said.

http://forum.pfsense.org/index.php/topic,21194.msg109995.html#msg109995

jimp

What kind of hardware is this running?

bellera

FabiaTech FX5622 as explained at:

http://forum.pfsense.org/index.php/topic,21194.msg109995.html#msg109995

Thanks in advance!

jimp

It's likely still required. The other hardware that change was needed for still requires it as well (Netgate Hamakua and FW7535)

bellera

Ok, thanks!

I read other similar posts using no packet option for boot0cfg

http://www.freebsd.org/cgi/man.cgi?query=boot0cfg

packet  Use the disk packet (BIOS INT 0x13 extensions) interface,
		     as opposed to the legacy (CHS) interface, when doing disk
		     I/O. This allows booting above cylinder 1023, but
		     requires specific BIOS support. The default is `packet'.

Is the same reason? Is my system not allowing to boot above cylinder 1023?

Regards,

Josep Pujadas

jimp

Usually the nopacket mode was for really old hardware/BIOS setups like the WRAP.