From owner-freebsd-bugs@FreeBSD.ORG Fri May 1 17:30:04 2009 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 377431065689 for ; Fri, 1 May 2009 17:30:04 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 249D88FC1B for ; Fri, 1 May 2009 17:30:04 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n41HU3NB004216 for ; Fri, 1 May 2009 17:30:03 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n41HU3k2004213; Fri, 1 May 2009 17:30:03 GMT (envelope-from gnats) Date: Fri, 1 May 2009 17:30:03 GMT Message-Id: <200905011730.n41HU3k2004213@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Thomas Schweikle Cc: Subject: Re: kern/130698: [boot] FreeBSD 8-CURRENT does not start any more since Dec. 10th [regression] X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Thomas Schweikle List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 May 2009 17:30:04 -0000 The following reply was made to PR kern/130698; it has been noted by GNATS. From: Thomas Schweikle 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: The data for partition 3 is: The data for partition 4 is: 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--