Date: Fri, 01 Dec 2000 00:18:24 +0100 From: "Jose M. Alcaide" <jose@we.lc.ehu.es> To: stable@FreeBSD.org Cc: rnordier@FreeBSD.org Subject: The trouble with boot0 Message-ID: <3A26E040.5162159A@we.lc.ehu.es>
next in thread | raw e-mail | index | archive | help
I was succesfully using the "boot0" boot manager with an 8GB ATA disk (in LBA mode) partitioned into two slices of 4GB (ad0s1 and ad0s2). The second one starts after cylinder 1023, but this does not cause any problems thanks to the boot0's "packet mode". Then, I decided to delete ad0s1 and replace it by two slices, each one of 2GB; these partitions were automatically named "ad0s1" and "ad0s3". In summary, the 8GB disk ended up having this partition scheme: ad0s1 (2GB) ad0s3 (2GB) ad0s2 (4GB) I installed FreeBSD 4.2-RELEASE into ad0s3 and, after that, pressing F3 for booting from ad0s3 only produces the famous beep. Note, however, that I can still boot from ad0s2 (which also contains FreeBSD and begins after cylinder 1023) and ad0s1. Only ad0s3 fails and I don't know why. I think that boot0 does not like a 3rd slice physically placed before the 2nd one. Is this a bug or a "feature"? The real disk geometry is: ad0: 8223MB <ST38410A> [16708/16/63] at ata0-master UDMA33 The geometry used (from fdisk(8)) is: cylinders=3037 heads=88 sectors/track=63 (5544 blks/cyl) And "boot0cfg -v ad0" shows # flag start chs type end chs offset size 1 0x00 0: 1: 1 0x06 720: 87:63 63 3997161 2 0x80 1023:255:63 0xa5 1023: 87:63 8415792 8421336 3 0x00 721: 0: 1 0xa5 1023: 87:63 3997224 4418568 version=1.1 drive=0x80 mask=0xf ticks=182 options=packet,noupdate,nosetdrv default_selection=F2 (Slice 2) Cheers, -- JMA ****** Jose M. Alcaide // jose@we.lc.ehu.es // jmas@FreeBSD.org ****** ** "Beware of Programmers who carry screwdrivers" -- Leonard Brandwein ** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3A26E040.5162159A>