kern/130698: [boot] FreeBSD 8-CURRENT does not start any more
since Dec. 10th [regression]
Thomas Schweikle
tps at vr-web.de
Sat May 9 16:10:04 UTC 2009
The following reply was made to PR kern/130698; it has been noted by GNATS.
From: "Thomas Schweikle" <tps at vr-web.de>
To: bug-followup at freebsd.org, tps at vr-web.de
Cc:
Subject: Re: kern/130698: [boot] FreeBSD 8-CURRENT does not start any more
since Dec. 10th [regression]
Date: Sat, 09 May 2009 18:03:42 +0200
I had some time today and tested sysinstall:
6.4-Stable:
Installing a first disk allows to create DD disks and "normal" disks.
Creating slices works as expected. Comitting changes works.
Creating labels works as expected. Commiting changes works.
Installing a second disk allows to create DD disks and "normal" disks.
Creating slices works as expected. Committing changes works.
Creating labels works as expected. Committing changes works only for DD disks.
7.1-Release-p5:
Installing a first disk allows to create DD disks and "normal" disks.
Creating slices works as expected. Committing changes works.
Creating labels works as expected. Committing changes works.
Installing a second disk allows to create DD disks and "normal" disks.
Creating slices works as expected. Committing changes works.
Creating labels works as expected. Committing changes works only for DD disks.
7.2-Stable:
Installing a first disk allows to create DD disks and "normal" disks.
Creating slices works as expected. Committing changes works.
Creating labels works as expected. Committing changes works.
Installing a second disk allows to create DD disks and "normal" disks.
Creating slices works as expected. Committing changes works.
Creating labels works as expected. Committing changes works only for DD disks.
8.0-Head:
Installing a first disk allows to create DD disks and "normal" disks.
Creating slices works as expected. Committing changes works.
Creating labels works as expected. Committing changes works.
Installing a second disk allows to create DD disks and "normal" disks.
Creating slices works as expected. Committing changes works.
Creating labels works as expected. Committing changes works only for DD disks.
It is impossible to install a second disk with sysinstall. Partitioning the second disk works, but labeling it doesn't. As soon as you are committing changes only the error message "There where errors comitting labels to /dev/ad1" is displayed. I can not tell what exactly sysinstall confused.
Trying the same with fdisk/disklabel works. But the boot-label has to start at offset 0 if you'd like the bootloader find the label to boot from. At the moment: there is something seriously broken within FreeBSD-8.0-HEAD!
yum# fdisk /dev/ad0
******* Working on device /dev/ad0 *******
parameters extracted from in-core disklabel are:
cylinders=17753 heads=15 sectors/track=63 (945 blks/cyl)
Figures below won't work with BIOS for partitions not in cyl 1
parameters to be used for BIOS calculations are:
cylinders=17753 heads=15 sectors/track=63 (945 blks/cyl)
Media sector size is 512
Warning: BIOS sector numbering starts with sector 1
Information from DOS bootblock is:
The data for partition 1 is:
sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD)
start 0, size 16777216 (8192 Meg), flag 80 (active)
beg: cyl 0/ head 0/ sector 1;
end: cyl 1023/ head 85/ sector 1
The data for partition 2 is:
<UNUSED>
The data for partition 3 is:
<UNUSED>
The data for partition 4 is:
<UNUSED>
yum# fdisk /dev/ad1
******* Working on device /dev/ad1 *******
parameters extracted from in-core disklabel are:
cylinders=17753 heads=15 sectors/track=63 (945 blks/cyl)
Figures below won't work with BIOS for partitions not in cyl 1
parameters to be used for BIOS calculations are:
cylinders=17753 heads=15 sectors/track=63 (945 blks/cyl)
Media sector size is 512
Warning: BIOS sector numbering starts with sector 1
Information from DOS bootblock is:
The data for partition 1 is:
sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD)
start 63, size 16771797 (8189 Meg), flag 80 (active)
beg: cyl 0/ head 1/ sector 1;
end: cyl 1023/ head 254/ sector 63
The data for partition 2 is:
<UNUSED>
The data for partition 3 is:
<UNUSED>
The data for partition 4 is:
<UNUSED>
yum#
yum# disklabel /dev/ad0
# /dev/ad0:
8 partitions:
# size offset fstype [fsize bsize bps/cpg]
a: 1048576 0 4.2BSD 2048 16384 8
b: 472720 1048576 swap
c: 16777216 0 unused 0 0 # "raw" part, don't edit
d: 2332672 1521296 4.2BSD 2048 16384 28552
e: 1048576 3853968 4.2BSD 2048 16384 8
f: 11874672 4902544 4.2BSD 2048 16384 28552
yum# disklabel /dev/ad1
disklabel: /dev/ad1: no valid label found
yum#
geom itself seems to be broken (at least the docs). It isn't helpful to just print out "geom list help" for command "geom list" if something isn't what geom expected. geom just prints nothing for any disk in the system regardless of being DD or not:
yum# geom part list
yum# geom label list
yum#
--
Thomas
More information about the freebsd-bugs
mailing list