Date: Sun, 7 Jul 1996 10:15:34 +0200 (MET DST) From: J Wunsch <j@uriah.heep.sax.de> To: freebsd-current@FreeBSD.org (FreeBSD-current users) Cc: scrappy@ki.net (Marc G. Fournier) Subject: Re: New install using 2.2-SNAP ... Message-ID: <199607070815.KAA24721@uriah.heep.sax.de> In-Reply-To: <Pine.NEB.3.94.960706225721.8294A-100000@ki.net> from "Marc G. Fournier" at "Jul 6, 96 10:58:25 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
As Marc G. Fournier wrote: > The reason I never noticed this before is that when I normally > install, I allocate the whole drive to FreeBSD, since I'm never going > to co-locate Linux/DOS on the same box... > > For some reason, this time, I failed to do that :( I you know how to read an fdisk table, and you can re-compute the required entries, you don't need to reinstall. What you are suffering is basically that your start values for the FreeBSD slice don't agree in terms of C/H/S from a BIOS point of view. Anyway, the LBA offset for the partition start is right, and if you pick the BIOS' geometry idea, you can recalculate the required C/H/S values to enter there. (Don't forget that sectors are numbered base 1, while cylinders and heads are numbered base 0 -- historical baggage.) This will usually end up in ``odd'' numbers, i.e. not starting on what the BIOS believes were a track boundary, but don't care, it will work nevertheless. The reason why you don't see it in ``dangerously dedicated'' mode is that the starting offset LBA is 0 there, and you can hardly miscompute a 0 into the wrong C/H/S values. :-) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199607070815.KAA24721>