From owner-freebsd-fs Fri May 30 11:24:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA00554 for fs-outgoing; Fri, 30 May 1997 11:24:25 -0700 (PDT) Received: from grolsch.cs.ubc.ca (grolsch.cs.ubc.ca [142.103.6.9]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA00549 for ; Fri, 30 May 1997 11:24:23 -0700 (PDT) Received: from cascade.cs.ubc.ca (cascade.cs.ubc.ca [142.103.7.7]) by grolsch.cs.ubc.ca (8.8.5/8.6.9) with ESMTP id LAA04827 for ; Fri, 30 May 1997 11:24:10 -0700 (PDT) Received: (mkerr@localhost) by cascade.cs.ubc.ca (8.8.5/8.6.12) id LAA16223 for fs@FreeBSD.ORG; Fri, 30 May 1997 11:24:07 -0700 (PDT) From: "Michael Kerr" Message-Id: <9705301124.ZM16221@cascade.cs.ubc.ca> Date: Fri, 30 May 1997 11:24:06 -0700 X-Mailer: Z-Mail (3.2.1 10apr95) To: fs@FreeBSD.ORG Subject: Install of second FreeBSD has corrupted existing install Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-fs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I had a free partition(slice) 2 as seen below for /dev/rsd0. I started an install of freebsd to that partition but the network link was too slow and after waiting a while I canceled. Under dos I deleted the partition so that it was again free. The only unusual thing I noticed is that when I was going through the install I chose A for automatic when in disklabel(I think that was the program) It created the following sd0s3a / 32 sd0s3b swap 138 sd0s3e /var 30 sd0s3f /usr 1761 Now I wanted / to be bigger but everytime I deleted it and the swap and tried to make the / bigger and the swap smaller it would give me an error when I tried to give it the name /. So in the end I went with automatic. After a slow ftp wait I gave up and canceled the install. I went to dos and deleted the partiton for the new free bsd. I found on reboot that where my original bsd boot was is now the aborted install which has no bootable kernel and therefore cannot boot. 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. The / that stopped working is located on /dev/sd0a and its /usr is on /dev/sd1s3e. 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) running fsck on /dev/sd0a checks out fine same with /dev/sd0s2. fsck on any other /dev/sd0s? gives an error. example: fsck /dev/sd0s1 ** /dev/rsd0s1 BAD SUPER BLOCK: MAGIC NUMBER WRONG ioctl (GCINFO): Invalid argument /dev/rsd0s1: can't read disk label Any hints on how to fix this mess would be really appreciated. Sincerely, Michael Kerr Here are the partitions ******* Working on device /dev/rsd0 ******* parameters extracted from in-core disklabel are: cylinders=553 heads=255 sectors/track=63 (16065 blks/cyl) parameters to be used for BIOS calculations are: cylinders=553 heads=255 sectors/track=63 (16065 blks/cyl) Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 0 is: sysid 6,(Primary 'big' DOS (> 32MB)) start 63, size 4192902 (2047 Meg), flag 0 beg: cyl 0/ sector 1/ head 1; end: cyl 260/ sector 63/ head 254 The data for partition 1 is: sysid 165,(FreeBSD/NetBSD/386BSD) start 4192965, size 401625 (196 Meg), flag 0 beg: cyl 261/ sector 1/ head 0; end: cyl 285/ sector 63/ head 254 The data for partition 2 is: The data for partition 3 is: sysid 5,(Extended DOS) start 8610840, size 273105 (133 Meg), flag 0 beg: cyl 536/ sector 1/ head 0; end: cyl 552/ sector 63/ head 254 ******* Working on device /dev/sd1 ******* parameters extracted from in-core disklabel are: cylinders=553 heads=255 sectors/track=63 (16065 blks/cyl) parameters to be used for BIOS calculations are: cylinders=553 heads=255 sectors/track=63 (16065 blks/cyl) Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 0 is: sysid 165,(FreeBSD/NetBSD/386BSD) start 63, size 1124487 (549 Meg), flag 80 beg: cyl 0/ sector 1/ head 1; end: cyl 69/ sector 63/ head 254 The data for partition 1 is: sysid 165,(FreeBSD/NetBSD/386BSD) start 4192965, size 128520 (62 Meg), flag 0 beg: cyl 261/ sector 1/ head 0; end: cyl 268/ sector 63/ head 254 The data for partition 2 is: sysid 165,(FreeBSD/NetBSD/386BSD) start 4321485, size 1220940 (596 Meg), flag 0 beg: cyl 269/ sector 1/ head 0; end: cyl 344/ sector 63/ head 254 The data for partition 3 is: sysid 6,(Primary 'big' DOS (> 32MB)) start 5542425, size 3341520 (1631 Meg), flag 0 beg: cyl 345/ sector 1/ head 0; end: cyl 552/ sector 63/ head 254 From owner-freebsd-fs Fri May 30 12:37:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA03444 for fs-outgoing; Fri, 30 May 1997 12:37:55 -0700 (PDT) Received: from grolsch.cs.ubc.ca (grolsch.cs.ubc.ca [142.103.6.9]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA03439 for ; Fri, 30 May 1997 12:37:52 -0700 (PDT) Received: from cascade.cs.ubc.ca (cascade.cs.ubc.ca [142.103.7.7]) by grolsch.cs.ubc.ca (8.8.5/8.6.9) with ESMTP id MAA07538 for ; Fri, 30 May 1997 12:36:30 -0700 (PDT) Received: (mkerr@localhost) by cascade.cs.ubc.ca (8.8.5/8.6.12) id MAA24882 for fs@FreeBSD.ORG; Fri, 30 May 1997 12:36:29 -0700 (PDT) From: "Michael Kerr" Message-Id: <9705301236.ZM24880@cascade.cs.ubc.ca> Date: Fri, 30 May 1997 12:36:28 -0700 In-Reply-To: "Michael Kerr" "Install of second FreeBSD has corrupted existing install" (May 30, 11:24am) References: <9705301124.ZM16221@cascade.cs.ubc.ca> X-Mailer: Z-Mail (3.2.1 10apr95) To: fs@FreeBSD.ORG Subject: Re: Install of second FreeBSD has corrupted existing install Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-fs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On May 30, 11:24am, Michael Kerr wrote: > Subject: Install of second FreeBSD has corrupted existing install > I had a free partition(slice) 2 as seen below for /dev/rsd0. I started an > install of freebsd to that partition but the network link was too slow and > after waiting a while I canceled. Under dos I deleted the partition so that > it was again free. > > The only unusual thing I noticed is that when I was going through the install > I chose A for automatic when in disklabel(I think that was the program) > It created the following > > sd0s3a / 32 > sd0s3b swap 138 > sd0s3e /var 30 > sd0s3f /usr 1761 > > Now I wanted / to be bigger but everytime I deleted it and the swap and tried > to make the / bigger and the swap smaller it would give me an error when I > tried to give it the name /. So in the end I went with automatic. > > After a slow ftp wait I gave up and canceled the install. > I went to dos and deleted the partiton for the new free bsd. > I found on reboot that where my original bsd boot was is now the aborted > install > which has no bootable kernel and therefore cannot boot. > > 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. > > The / that stopped working is located on /dev/sd0a and its /usr is on > /dev/sd1s3e. > > 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. Mike From owner-freebsd-fs Fri May 30 13:53:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA07933 for fs-outgoing; Fri, 30 May 1997 13:53:13 -0700 (PDT) Received: from whqvax.picker.com (whqvax.picker.com [144.54.1.1]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id NAA07928 for ; Fri, 30 May 1997 13:53:09 -0700 (PDT) Received: from ct.picker.com by whqvax.picker.com with SMTP; Fri, 30 May 1997 16:52:01 -0400 (EDT) Received: from elmer.ct.picker.com ([144.54.57.34]) by ct.picker.com (4.1/SMI-4.1) id AA28009; Fri, 30 May 97 16:51:59 EDT Received: by elmer.ct.picker.com (SMI-8.6/SMI-SVR4) id QAA17090; Fri, 30 May 1997 16:50:55 -0400 Message-Id: <19970530165054.07783@ct.picker.com> Date: Fri, 30 May 1997 16:50:54 -0400 From: Randall Hopper To: Michael Kerr Cc: fs@FreeBSD.ORG Subject: Re: Install of second FreeBSD has corrupted existing install References: <9705301124.ZM16221@cascade.cs.ubc.ca> <9705301236.ZM24880@cascade.cs.ubc.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.74 In-Reply-To: <9705301236.ZM24880@cascade.cs.ubc.ca>; from Michael Kerr on Fri, May 30, 1997 at 12:36:28PM -0700 Sender: owner-fs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk |> 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