From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <9f3897940705240613g16958272s7f65eda6600889c@mail.gmail.com> Date: Thu, 24 May 2007 15:13:52 +0200 From: "=?UTF-8?Q?Pawe=C5=82_Lasek?=" To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu> Subject: Re: [9fans] MBR messed up on installation In-Reply-To: <290d7653665aee78a057e836829bb903@coraid.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20070523183556.GA2037@polynum.com> <290d7653665aee78a057e836829bb903@coraid.com> Topicbox-Message-UUID: 7175c7a8-ead2-11e9-9d60-3106f5b1d025 On 5/24/07, erik quanstrom wrote: > > Disk: /dev/rwd0d > > NetBSD disklabel disk geometry: > > cylinders: 38792, heads: 16, sectors/track: 63 (1008 sectors/cylinder) > > total sectors: 39102336 > > > > BIOS disk geometry: > > cylinders: 1024, heads: 255, sectors/track: 63 (16065 sectors/cylinder) > > total sectors: 39102336 > why is netbsd making up chs numbers? it would seem to me that that is > the problem. i'm not sure where the fdisk partition table standard is, > so i can't say definatively this is wrong. but it seems like trouble, making > up one's on chs numbers. BIOS geometry seems a little off to me, although It is voodoo magick after all... Especially with a ~20 GB drive. It looks like NetBSD placed LBA-like values into it's disklabel, propably received by it's own drivers, while MBR partition table is made up in ... weird way? Maybe it has that weird geometry to allow booting from every partition without using LBA, as BIOS had 1024 cylinders set. Anyway I'd recommend staying away from Plan9 fdisk if you use other OS, especially other than those from MS (And NT might take it badly too). I'd recommend setting Plan 9 partition from BSD or GNU fdisk and then use plan 9 to make it's own partition table in it. -- Paul Lasek