Quote:
Originally Posted by J65nko
UFS journalling is a rather new feature that OpenBSD does not support.
It could be that the OpenBSD r/w mount of the FreeBSD UFS+J root partition messed up some file system data, causing the boot of this file system to fail.
|
This week I installed FreeBSD 10.0 on an amd64 box with OpenBSD and Linux all on different partitions.
There seems to be a difference between OpenBSD partitions and FreeBSD partitions.
The OpenBSD partitions seem to automatically allow room for the boot program, /usr/mdec/biosboot, but the FreeBSD partitions do
not allow room for the boot program, /boot/boot...
The FreeBSD instructions were not helpful:
Quote:
Originally Posted by J65nko
...
From that manual page (9.2 version):
Code:
... then create a 30GB-sized FreeBSD slice ...
Now create a BSD scheme (BSD label) with space for up to 20 partitions:
/sbin/gpart create -s BSD -n 20 ada0s1
Create a 1GB-sized UFS partition and a 4GB-sized swap partition:
/sbin/gpart add -t freebsd-ufs -s 1G ada0s1
/sbin/gpart add -t freebsd-swap -s 4G ada0s1
Install bootstrap code for the BSD label:
/sbin/gpart bootcode -b /boot/boot ada0s1
Make sure you use the correct FreeBSD disk device name and slice designators  |
I found that when I followed these instruction, that the "gpart bootcode" command would clobber the first 8k of the freebsd-ufs partition and then it was not longer usable.
To correct it I allowed room for the /boot/boot code and skipped 16 sectors (8k) from the beginning of the slice for the partition a.
Code:
/sbin/gpart add -t freebsd-ufs -b 16 -s 1G ada0s1
/sbin/gpart add -t freebsd-swap -s 4G ada0s1
/sbin/gpart bootcode -b /boot/boot ada0s1
(Side note: -s 1G seems too small for a whole FreeBSD installation I used -s 8G and filled it half way already.)