From owner-freebsd-current Sun Mar 26 06:39:52 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id GAA17391 for current-outgoing; Sun, 26 Mar 1995 06:39:52 -0800 Received: from inet-gw-3.pa.dec.com (inet-gw-3.pa.dec.com [16.1.0.33]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id GAA17385; Sun, 26 Mar 1995 06:39:51 -0800 Received: from dude.pcs.dec.com by inet-gw-3.pa.dec.com (5.65/24Feb95) id AA13272; Sun, 26 Mar 95 06:39:22 -0800 Received: by dude.pcs.dec.com (/\=-/\ Smail3.1.16.1 #16.37) id ; Sun, 26 Mar 95 16:36 MSZ Message-Id: From: me@dude.pcs.dec.com ( Michael Elbel ) Subject: Re: cvs commit: src/sys/scsi sd.c To: phk@ref.tfs.com (Poul-Henning Kamp) Date: Sun, 26 Mar 1995 16:36:37 +0200 (MSZ) Cc: me@FreeBSD.org, bde@zeta.org.au, current@FreeBSD.org Reply-To: me@FreeBSD.org (Michael Elbel) In-Reply-To: <199503252208.OAA19222@ref.tfs.com> from "Poul-Henning Kamp" at Mar 25, 95 02:08:10 pm X-Mailer: ELM [version 2.4 PL21] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 1387 Sender: current-owner@FreeBSD.org Precedence: bulk > > Hrrm, both of my FreeBSD disks use the whole drive starting at sector 0, > > there aren't any slices on them. The slice changes don't allow me to mount > > them any more. Is this on purpose, I.e. do I *have* to fdisk my disks > > or is the code supposed to work with FreeBSD covering the whole disk? > > Yes, you have to slice them, the good news is that you don't loose any > disk-space doing so :-) Erm, how's that? Originally the while disk was used for partitions, now there's 32 sectors less (standard 64/32 translation). Or am I missing something obvious besides the possibility that there were 32 spare sectors in the last cylinder. Nevertheless, I can't get my 2 Gig Quantum Empire to be accepted by the new kernel. The new code seems to insist on checking the sector start and size information against the C/H/S begin and end information. I finally managed to fdisk it in a way that the slice code accepts the start after remembering that track sectors are starting at 1 instead of 0. However, I haven't found a way to make it happy about the end yet. I simply can't have the slice end beyond cylinder 1023 - I guess this is the usual bios limit, right? So, how am I supposed to get my disk to be recognized fully? I don't want to lose that Gig ;-) Michael -- Michael Elbel, Digital-PCS GmbH, Muenchen, Germany - me@FreeBSD.org Fermentation fault (coors dumped)