From nobody@FreeBSD.org  Sun Jan 18 15:44:43 2009
Return-Path: <nobody@FreeBSD.org>
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 9ABFC1065672
	for <freebsd-gnats-submit@FreeBSD.org>; Sun, 18 Jan 2009 15:44:43 +0000 (UTC)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (www.freebsd.org [IPv6:2001:4f8:fff6::21])
	by mx1.freebsd.org (Postfix) with ESMTP id 886D08FC0C
	for <freebsd-gnats-submit@FreeBSD.org>; Sun, 18 Jan 2009 15:44:43 +0000 (UTC)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (localhost [127.0.0.1])
	by www.freebsd.org (8.14.3/8.14.3) with ESMTP id n0IFihFB069729
	for <freebsd-gnats-submit@FreeBSD.org>; Sun, 18 Jan 2009 15:44:43 GMT
	(envelope-from nobody@www.freebsd.org)
Received: (from nobody@localhost)
	by www.freebsd.org (8.14.3/8.14.3/Submit) id n0IFihRu069728;
	Sun, 18 Jan 2009 15:44:43 GMT
	(envelope-from nobody)
Message-Id: <200901181544.n0IFihRu069728@www.freebsd.org>
Date: Sun, 18 Jan 2009 15:44:43 GMT
From: Thomas Schweikle <tps@vr-web.de>
To: freebsd-gnats-submit@FreeBSD.org
Subject: FreeBSD 8-CURRENT does not start any more since Dec. 10th.
X-Send-Pr-Version: www-3.1
X-GNATS-Notify:

>Number:         130698
>Category:       kern
>Synopsis:       [boot] FreeBSD 8-CURRENT does not start any more since Dec. 10th [regression]
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sun Jan 18 15:50:00 UTC 2009
>Closed-Date:    Fri Sep 23 20:42:06 UTC 2011
>Last-Modified:  Fri Sep 23 20:42:06 UTC 2011
>Originator:     Thomas Schweikle
>Release:        FreeBSD 8-CURRENT
>Organization:
>Environment:
FreeBSD yum.tps 8.0-CURRENT FreeBSD 8.0-CURRENT #37: Wed Dec 10 14:18:10 CET 2008     root@yum.tps:/usr/obj/usr/src/sys/YUM  i386
>Description:
yum# dmesg
Copyright (c) 1992-2008 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
	The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 8.0-CURRENT #37: Wed Dec 10 14:18:10 CET 2008
    root@yum.tps:/usr/obj/usr/src/sys/YUM
WARNING: WITNESS option enabled, expect reduced performance.
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: Intel(R) Core(TM)2 Duo CPU     T7500  @ 2.20GHz (989.12-MHz 686-class CPU)
  Origin = "GenuineIntel"  Id = 0x6fb  Stepping = 11
  Features=0xfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS>
  Features2=0x2201<SSE3,SSSE3,CX16>
  AMD Features=0x20100000<NX,LM>
  AMD Features2=0x1<LAHF>
  TSC: P-state invariant
real memory  = 201326592 (192 MB)
avail memory = 178044928 (169 MB)
ACPI APIC Table: <PTLTD  	 APIC  >
MADT: Forcing active-low polarity and level trigger for SCI
ioapic0 <Version 1.1> irqs 0-23 on motherboard
kbd1 at kbdmux0
acpi0: <INTEL 440BX> on motherboard
acpi0: [ITHREAD]
acpi0: Power Button (fixed)
Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0
pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
pci0: <ACPI PCI bus> on pcib0
pcib1: <ACPI PCI-PCI bridge> at device 1.0 on pci0
pci1: <ACPI PCI bus> on pcib1
isab0: <PCI-ISA bridge> at device 7.0 on pci0
isa0: <ISA bus> on isab0
atapci0: <Intel PIIX4 UDMA33 controller> port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x1400-0x140f at device 7.1 on pci0
ata0: <ATA channel 0> on atapci0
ata0: [ITHREAD]
ata1: <ATA channel 1> on atapci0
ata1: [ITHREAD]
pci0: <bridge> at device 7.3 (no driver attached)
vgapci0: <VGA-compatible display> port 0x1410-0x141f mem 0xf0000000-0xf7ffffff,0xe8000000-0xe87fffff at device 15.0 on pci0
bt1: <Buslogic Multi-Master SCSI Host Adapter> port 0x1060-0x107f mem 0xe8800000-0xe880001f irq 17 at device 16.0 on pci0
bt1: BT-958 FW Rev. 5.07B Ultra Wide SCSI Host Adapter, SCSI ID 7, 192 CCBs
bt1: [GIANT-LOCKED]
bt1: [ITHREAD]
le1: <AMD PCnet-PCI> port 0x1080-0x10ff irq 18 at device 17.0 on pci0
le1: 16 receive buffers, 4 transmit buffers
le1: Ethernet address: 00:0c:29:bf:26:f2
le1: [ITHREAD]
acpi_acad0: <AC Adapter> on acpi0
atrtc0: <AT realtime clock> port 0x70-0x71 irq 8 on acpi0
atkbdc0: <Keyboard controller (i8042)> port 0x60,0x64 irq 1 on acpi0
atkbd0: <AT Keyboard> irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
atkbd0: [ITHREAD]
psm0: <PS/2 Mouse> irq 12 on atkbdc0
psm0: [GIANT-LOCKED]
psm0: [ITHREAD]
psm0: model IntelliMouse, device ID 3
ppc0: <Parallel port> port 0x378-0x37f irq 7 on acpi0
ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode
ppc0: [GIANT-LOCKED]
ppc0: [ITHREAD]
ppbus0: <Parallel port bus> on ppc0
plip0: <PLIP network interface> on ppbus0
plip0: WARNING: using obsoleted IFF_NEEDSGIANT flag
lpt0: <Printer> on ppbus0
lpt0: Interrupt-driven port
ppi0: <Parallel I/O> on ppbus0
uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
uart0: [FILTER]
uart1: <16550 or compatible> port 0x2f8-0x2ff irq 3 on acpi0
uart1: [FILTER]
fdc0: <floppy drive controller> port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0
fdc0: [FILTER]
fd0: <1440-KB 3.5" drive> on fdc0 drive 0
cpu0: <ACPI CPU> on acpi0
acpi_throttle0: <ACPI CPU Throttling> on cpu0
pmtimer0 on isa0
orm0: <ISA Option ROMs> at iomem 0xc0000-0xc7fff,0xc8000-0xc8fff,0xdc000-0xdffff,0xe4000-0xe7fff pnpid ORM0000 on isa0
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
Timecounter "TSC" frequency 989117558 Hz quality 800
Timecounters tick every 100.000 msec
ad0: 8192MB <VMware Virtual IDE Hard Drive 00000001> at ata0-master UDMA33
acd0: CDROM <VMware Virtual IDE CDROM Drive/00000001> at ata1-master UDMA33
Waiting 5 seconds for SCSI devices to settle
WARNING: WITNESS option enabled, expect reduced performance.
Trying to mount root from ufs:/dev/ad0s1a

The kernel boots and the system is usable.
Same with a kernel after Dec. 10th: looks mainly the same, but "root" does not mount because it is not found. The system asks for its root device:
Manual root filesystem specification:
  <fstype>:<device>  Mount <device> using filesystem <fstype>
                       eg. ufs:da0s1a
  ?                  List valid disk boot devices
  <empty line>       Abort manual input

mountroot> ?

List of GEOM managed disk devices:
  ad0f ad0e ad0d ad0b ad0a acd0 ad0 fd0

shouldn't this list look like:
  ad0s1a ad0s1b ad0s1d ad0s1e ad0s1f acd0 ad0 fd0

Looks like kernels after Dec. 10th, 2008 are having problems with the MBR
written on disk by kernels before Dec. 10th.

The system is installed on a "Dangerously dedicated disk".
>How-To-Repeat:

>Fix:


>Release-Note:
>Audit-Trail:
Responsible-Changed-From-To: freebsd-i386->freebsd-bugs 
Responsible-Changed-By: linimon 
Responsible-Changed-When: Sun Jan 18 23:15:46 UTC 2009 
Responsible-Changed-Why:  
Looks like a side-effect of the gpart changes. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=130698 

From: Thomas Schweikle <tps@vr-web.de>
To: bug-followup@FreeBSD.org
Cc:  
Subject: Re: kern/130698: [boot] FreeBSD 8-CURRENT does not start any more
 since Dec. 10th [regression]
Date: Fri, 01 May 2009 19:16:04 +0200

 This is a MIME-formatted message.  If you see this text it means that your
 E-mail software does not support MIME-formatted messages.
 
 --=_vrwf103-17367-1241198171-0001-2
 Content-Type: text/plain; charset=ISO-8859-15
 Content-Transfer-Encoding: quoted-printable
 
 Looks a lot like the kernel does not correctly test what boot block
 is given, but assumes something not really correct on a IBM
 compatible PC. Within my boot block I have:
 
 yum# dd if=3D/dev/ad0 of=3Dmbr.bin bs=3D512 count=3D1; hexdump mbr.bin
 0000000 3ceb 0000 0000 0000 0000 0000 0002 0000
 0000010 0000 0000 0000 0000 0012 0002 0000 0000
 0000020 0000 0000 1600 661f 006a 5051 5306 c031
 0000030 f088 6a50 8910 e8e5 00c0 668d cb10 31fc
 0000040 8ec9 8ec1 8ed9 bcd1 7c00 e689 00bf fe07
 0000050 f3c5 bea5 7dee fa80 7280 b62c e801 0060
 0000060 01b9 be00 8eaa 01b6 7c80 a504 0775 19e3
 0000070 04f6 7580 8314 10c6 c6fe fe80 7205 49e9
 0000080 e1e3 a2be eb7d 314b 89d2 0016 b609 e810
 0000090 002e 00bb 8b90 0a77 de01 00bf b9c0 ae00
 00000a0 f129 a4f3 49fa 1474 64e4 02a8 f775 d1b0
 00000b0 64e6 64e4 02a8 fa75 dfb0 60e6 e9fb 1350
 00000c0 ecbb 8b8c 0844 4c8b 0e0a 5ae8 73ff be2a
 00000d0 7d9d 1ce8 be00 7da7 16e8 3000 cde4 c716
 00000e0 7206 3404 ea12 0000 ffff 07bb b400 cd0e
 00000f0 ac10 c084 f475 01b4 c3f9 f62e b006 8008
 0000100 2274 fa80 7280 bb1d 55aa b452 cd41 5a13
 0000110 1272 fb81 aa55 0c75 c1f6 7401 8907 b4ee
 0000120 cd42 c313 b452 cd08 8813 5af5 cb72 e180
 0000130 743f fac3 8b66 0846 6652 b60f 66d9 d231
 0000140 f766 88f3 88eb 43d5 d230 f766 88f3 5ad7
 0000150 3d66 03ff 0000 77fb 869d c0c4 02c8 e808
 0000160 9140 fe88 e028 668a 3802 72e0 b002 bf01
 0000170 0005 5ec4 5004 02b4 13cd 735b 4f0a 1c74
 0000180 e430 13cd eb93 0feb c3b6 4601 7308 ff03
 0000190 0a46 e3d0 5e00 2805 0246 8877 52c3 6165
 00001a0 0064 6f42 746f 2000 7265 6f72 0d72 000a
 00001b0 9080 9090 9090 9090 9090 9090 9090 0080
 00001c0 0001 55a5 ffc1 0000 0000 0000 0100 0000
 00001d0 0000 0000 0000 0000 0000 0000 0000 0000
 *
 00001f0 0000 0000 0000 0000 0000 0000 0000 aa55
 
 What looks good for me. It is a standard MBR. One partition all
 allocated to FreeBSD, partition type 0xA5:
 yum# fdisk
 ******* Working on device /dev/ad0 *******
 parameters extracted from in-core disklabel are:
 cylinders=3D17753 heads=3D15 sectors/track=3D63 (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=3D17753 heads=3D15 sectors/track=3D63 (945 blks/cyl)
 
 Media sector size is 512
 Warning: BIOS sector numbering starts with sector 1
 Information from DOS boot block 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>
 
 disklabel gives back:
 yum# disklabel 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
 
 It is further impossible to boot a disk on this system. I have tried
  with a partition entry and with DD disks. No way. In both cases the
 actual kernel fails to find the root device, while FreeBSD
 7.1-STABLE kernel does not have any problem.
 
 Even if you boot from a CD it is not possible to create a partition,
 then slice it up for install. You might do so, but right after you
 have done it, the no slice is found. Even rebooting doesn't help.
 Seems there is some really nasty going on!
 
 --=20
 Thomas
 
 
 --=_vrwf103-17367-1241198171-0001-2
 Content-Type: application/pgp-signature; name="signature.asc"
 Content-Transfer-Encoding: 7bit
 Content-Description: OpenPGP digital signature
 Content-Disposition: attachment; filename="signature.asc"
 
 -----BEGIN PGP SIGNATURE-----
 Version: GnuPG v2.0.12-svn4966 (MingW32)
 Comment: GnuPT 2.9.2
 
 iEYEARECAAYFAkn7LlkACgkQJuPdOes4UCS8oACgoJbo+37xaoISaymaETF9ZAsO
 rIgAnApPLKDvz8QY6l1NzMSlqLML8dIS
 =5/CP
 -----END PGP SIGNATURE-----
 
 --=_vrwf103-17367-1241198171-0001-2--

From: Thomas Schweikle <tps@vr-web.de>
To: bug-followup@FreeBSD.org, tps@vr-web.de
Cc:  
Subject: Re: kern/130698: [boot] FreeBSD 8-CURRENT does not start any more
 since Dec. 10th [regression]
Date: Fri, 01 May 2009 20:11:20 +0200

 This is a MIME-formatted message.  If you see this text it means that your
 E-mail software does not support MIME-formatted messages.
 
 --=_vrwf103-23107-1241201482-0001-2
 Content-Type: text/plain; charset=ISO-8859-15
 Content-Transfer-Encoding: quoted-printable
 
 Not sure if gpart is to exaust anything, but:
 
 yum# gpart show
 yum#
 
 does not produce any output.
 
 
 --=20
 Thomas
 
 
 --=_vrwf103-23107-1241201482-0001-2
 Content-Type: application/pgp-signature; name="signature.asc"
 Content-Transfer-Encoding: 7bit
 Content-Description: OpenPGP digital signature
 Content-Disposition: attachment; filename="signature.asc"
 
 -----BEGIN PGP SIGNATURE-----
 Version: GnuPG v2.0.12-svn4966 (MingW32)
 Comment: GnuPT 2.9.2
 
 iEYEARECAAYFAkn7O0gACgkQJuPdOes4UCR57gCeNUglN0QHjZqvDeVbPLjudxU7
 RQoAn10O98pixQCVWHX5p2wjhuoskwwE
 =GCIj
 -----END PGP SIGNATURE-----
 
 --=_vrwf103-23107-1241201482-0001-2--

From: John Baldwin <jhb@FreeBSD.org>
To: bug-followup@FreeBSD.org, tps@vr-web.de
Cc:  
Subject: Re: kern/130698: [boot] FreeBSD 8-CURRENT does not start any more
 since Dec. 10th [regression]
Date: Wed, 06 May 2009 14:39:26 -0400

 gpart does not support "dangerously dedicated" disks and they have been 
 deprecated in FreeBSD for a long time now.  The reason gpart rejects it 
 is the partition does not start on a cylinder boundary (instead it 
 starts one sector into the disk).  You can ask marcel@ if he wants to 
 make an exception, but DD disks have been deprecated for quite a while 
 and I believe sysinstall has not let you create them for several years now.
 
 -- 
 John Baldwin

From: Thomas Schweikle <tps@vr-web.de>
To: bug-followup@FreeBSD.org
Cc:  
Subject: Re: kern/130698: [boot] FreeBSD 8-CURRENT does not start any more
 since Dec. 10th [regression]
Date: Sat, 09 May 2009 08:06:41 +0200

 This is a MIME-formatted message.  If you see this text it means that your
 E-mail software does not support MIME-formatted messages.
 
 --=_vrwf103-2109-1241849215-0001-2
 Content-Type: text/plain; charset=UTF-8
 Content-Transfer-Encoding: quoted-printable
 
 Am 06.05.2009, 20:39 Uhr, schrieb John Baldwin <jhb@freebsd.org>:
 
 > gpart does not support "dangerously dedicated" disks and they have been=
  =20
 > deprecated in FreeBSD for a long time now.  The reason gpart rejects it=
  =20
 > is the partition does not start on a cylinder boundary (instead it =20
 > starts one sector into the disk).  You can ask marcel@ if he wants to  =
 
 > make an exception, but DD disks have been deprecated for quite a while =
 =20
 > and I believe sysinstall has not let you create them for several years =
 =20
 > now.
 
 Hmmmmm. I shortly installed FreeBSD 6.4 from CD-Rom and since I
 could not boot from a real partititon I decided to create a DD disk.
 sysinstall did it for me without any warning ...
 
 Shure it is deprecated, but at now I am shure it is possible as
 before to create DD disks using sysinstall. I'll test sysinstall on
 FreeBSD 7.2 and FreeBSD Head next. Will take a while, since I do not
 have an installable PC at hand.
 
 --=20
 Thomas
 
 
 --=_vrwf103-2109-1241849215-0001-2
 Content-Type: application/pgp-signature; name="signature.asc"
 Content-Transfer-Encoding: 7bit
 Content-Description: OpenPGP digital signature
 Content-Disposition: attachment; filename="signature.asc"
 
 -----BEGIN PGP SIGNATURE-----
 Version: GnuPG v2.0.12-svn4966 (MingW32)
 Comment: GnuPT 2.9.2
 
 iEYEARECAAYFAkoFHX4ACgkQJuPdOes4UCQvuACfWmvSgMPed4uqR2ziPiqfhhcu
 yKwAnAobrSL7vlbqoGMRo715WS7+AWIj
 =QM8b
 -----END PGP SIGNATURE-----
 
 --=_vrwf103-2109-1241849215-0001-2--

From: "Thomas Schweikle" <tps@vr-web.de>
To: bug-followup@freebsd.org, tps@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

From: gazelle11 <gazelle11@gmx.de>
To: bug-followup@freebsd.org, tps@vr-web.de
Cc:  
Subject: Re: kern/130698: [boot] FreeBSD 8-CURRENT does not start any more
 since Dec. 10th [regression]
Date: Mon, 18 May 2009 09:10:19 +0200

 Had the chance to change fstab. Works again!
 
 
 -- 
 Thomas

From: Thomas Schweikle <tps@vr-web.de>
To: bug-followup@FreeBSD.org, tps@vr-web.de
Cc:  
Subject: Re: kern/130698: [boot] FreeBSD 8-CURRENT does not start any more
 since Dec. 10th [regression]
Date: Fri, 29 May 2009 17:54:43 +0200

 This is a MIME-formatted message.  If you see this text it means that your
 E-mail software does not support MIME-formatted messages.
 
 --=_vrwf103-22611-1243612495-0001-2
 Content-Type: text/plain; charset=ISO-8859-15
 Content-Transfer-Encoding: quoted-printable
 
 This problem is gone now. Would be nice we have it in the FAQ or
 Handbook. Since I searched first there but did not find anything ...
 
 Anyway: you may close this since it is fixed!
 
 --=20
 Thomas
 
 
 --=_vrwf103-22611-1243612495-0001-2
 Content-Type: application/pgp-signature; name="signature.asc"
 Content-Transfer-Encoding: 7bit
 Content-Description: OpenPGP digital signature
 Content-Disposition: attachment; filename="signature.asc"
 
 -----BEGIN PGP SIGNATURE-----
 Version: GnuPG v2.0.12-svn4966 (MingW32)
 Comment: GnuPT 2.9.2
 
 iEYEARECAAYFAkogBU4ACgkQJuPdOes4UCREnwCeMdNy21bMpjNOQ/jf+E4dsvgw
 udkAoJ65cKNH6r/Nrc5kZCxO0uYQdeRd
 =HvM6
 -----END PGP SIGNATURE-----
 
 --=_vrwf103-22611-1243612495-0001-2--

From: Andrew I Baznikin <dikiy@scn.ru>
To: bug-followup@FreeBSD.org, tps@vr-web.de
Cc:  
Subject: Re: kern/130698: [boot] FreeBSD 8-CURRENT does not start any more
 since Dec. 10th [regression]
Date: Thu, 8 Oct 2009 12:27:34 +0000

 Same for me, but I can't boot using 'new' device name!
 
 mountroot> ?
 
 List of GEOM managed disk devices:
 ad4 ad4a acd0
 
 I tried to boot using ad4a and still got same error.
 I boot up using Frenzy-1 live cd to make some tests:
 
 frenzy:~# dd if=/dev/ad4 of=mbr.bin bs=512 count=1; hexdump mbr.bin
 1+0 records in
 1+0 records out
 512 bytes transferred in 0.014784 secs (34632 bytes/sec)
 0000000 31fc 8ec0 8ec0 8ed8 bcd0 7c00 e689 00bf
 0000010 b906 0100 a5f3 fd89 08b1 abf3 45fe e9f2
 0000020 8a00 46f6 20bb 0475 d284 0378 568a 88ba
 0000030 0056 fce8 5200 c2bb 3107 88d2 fc6f a30f
 0000040 bb56 1b73 078a 83bf b107 f203 74ae b110
 0000050 f20b 75ae 8303 0bc7 0d8a cf01 c3e8 4200
 0000060 c380 7310 58d6 7f2c 063a 0475 0572 7448
 0000070 300d 04c0 88b0 b846 b2bf e807 00a4 77be
 0000080 e807 00b0 568a 4eb9 8ce8 3000 cde4 891a
 0000090 03d7 bc7e 01b4 16cd 1275 e430 1acd fa39
 00000a0 f272 468a ebb9 b01b e807 0094 e430 16cd
 00000b0 e088 1c3c ec74 3b2c 043c 0676 c72c 043c
 00000c0 e577 0f98 46a3 730c 88de b946 00be 8a08
 00000d0 8914 3cf3 9c04 0a74 e0c0 0504 07be c693
 00000e0 8007 f653 bb46 7540 bb08 0600 03b4 59e8
 00000f0 5e00 759d 8a06 b856 ea80 bb30 7c00 02b4
 0000100 47e8 7200 81a2 febf 5501 75aa 569a 81be
 0000110 e807 001a ff5e b0e3 e846 0024 31b0 d000
 0000120 17eb ab0f 0c56 74be e807 ffeb fe89 03e8
 0000130 be00 0781 a8ac 7580 e805 0004 f6eb 7f24
 0000140 bb53 0007 0eb4 10cd c35b 748a 8b01 024c
 0000150 01b0 8956 f6e7 bb46 7480 6613 006a ff66
 0000160 0874 5306 016a 106a e689 8048 40cc 13cd
 0000170 fc89 c35e 2020 0aa0 6544 6166 6c75 3a74
 0000180 0da0 008a 0f05 0401 0b06 0e0c 9f83 a6a5
 0000190 0ca9 0c0d 0a0b 0809 120a 100d 3f0f 44bf
 00001a0 d34f 694c 756e 46f8 6572 4265 c453 9090
 00001b0 bb66 7244 7669 2065 00b1 0f80 00b6 0180
 00001c0 0001 fea5 ffff 003f 0000 e482 0950 0000
 00001d0 0000 0000 0000 0000 0000 0000 0000 0000
 *
 00001f0 0000 0000 0000 0000 0000 0000 0000 aa55
 0000200
 
 
 frenzy:~# fdisk /dev/ad4
 ******* Working on device /dev/ad4 *******
 parameters extracted from in-core disklabel are:
 cylinders=155061 heads=16 sectors/track=63 (1008 blks/cyl)
 
 Figures below won't work with BIOS for partitions not in cyl 1
 parameters to be used for BIOS calculations are:
 cylinders=155061 heads=16 sectors/track=63 (1008 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 156296322 (76316 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>
 
 
 frenzy:~# disklabel ad4
 # /dev/ad4:
 8 partitions:
 #        size   offset    fstype   [fsize bsize bps/cpg]
   a: 156301472       16    unused        0     0       
   c: 156301488        0    unused        0     0         # "raw" part, don't edit
 
 
 frenzy:~# disklabel ad4s1
 # /dev/ad4s1:
 8 partitions:
 #        size   offset    fstype   [fsize bsize bps/cpg]
   a:  1048576        0    4.2BSD     2048 16384     8 
   b:  4194304  1048576      swap                    
   c: 156296322        0    unused        0     0         # "raw" part, don't edit
   d:  6291456  5242880    4.2BSD     2048 16384 28552 
   e: 144761986 11534336    4.2BSD     2048 16384 28552 

Date: Wed, 14 Oct 2009 16:24:57 +0100
Subject: Re: kern/130698: [boot] FreeBSD 8-CURRENT does not start any more
 since Dec. 10th [regression]

Hi,

This may not be the right place to report this, but I tried to install
8.0-RC1 last weekend on a disk that had opensolaris/zfs on it before.
It wouldn't allow me to install, no matter what I tried partition wise.

I'm now running RELENG_7 which works. Tried to boot a RELENG_8 kernel
which failed, and changed ad8s1a to ad8p1a in fstab but it still wouldn't
find it.

I've not used freebsd for a while so am not up to speed on recent
development. But I would have expected a fresh install of 8.0-RC1 to
work. Never had these problems in 386bsd or 2.2 versions ;)

Regards,

Frank

_____________________________________________________________

This email (including any attachments to it) is confidential, legally
privileged, subject to copyright and is sent for the personal attention
of the intended recipient only. If you have received this email in error,
please advise us immediately and delete it. You are notified that
disclosing, copying, distributing or taking any action in reliance on
the contents of this information is strictly prohibited. Although we
have taken reasonable precautions to ensure no viruses are present in
this email, we cannot accept responsibility for any loss or damage arising
from the viruses in this email or attachments. We exclude any liability
for the content of this email, or for the consequences of any actions
taken on the basis of the information provided in this email or its
attachments, unless that information is subsequently confirmed in
writing. If this email contains an offer, that should be considered as
an invitation to treat.
_____________________________________________________________
State-Changed-From-To: open->closed 
State-Changed-By: jh 
State-Changed-When: Fri Sep 23 20:42:05 UTC 2011 
State-Changed-Why:  
Closed at submitter's request. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=130698 
>Unformatted:
