Date: Fri, 30 May 1997 16:50:54 -0400 From: Randall Hopper <rhh@ct.picker.com> To: Michael Kerr <mkerr@cs.ubc.ca> Cc: fs@FreeBSD.ORG Subject: Re: Install of second FreeBSD has corrupted existing install Message-ID: <19970530165054.07783@ct.picker.com> In-Reply-To: <9705301236.ZM24880@cascade.cs.ubc.ca>; from Michael Kerr on Fri, May 30, 1997 at 12:36:28PM -0700 References: <9705301124.ZM16221@cascade.cs.ubc.ca> <9705301236.ZM24880@cascade.cs.ubc.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
|> sd0s3a / 32 |> sd0s3b swap 138 |> sd0s3e /var 30 |> sd0s3f /usr 1761 |> |> I booted to another existing freebsd on the second partiton and ran |> fsck but it can only check /dev/sd0s2 which according to fdisk as shown |> below shouldn't exist. btw it checks out fine. |> now when I mount /dev/sd0a it gives me the / for the new install I was |> performing. which is the same as mounting /dev/sd0s2 (which shouldn't |> exist) |Well ,I now know you can only have one / per disk with FreeBSD. |It used my original root partion of 196 meg even though I gave it a new |partition to use. | |Arrg. Yeah, I dislike this bug too. FreeBSD should always boot off the root in the slice whose boot record invoked it. So much for having multiple versions of FreeBSD installed on the same disk. Randall
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19970530165054.07783>