Date: Fri, 30 May 1997 11:24:06 -0700 From: "Michael Kerr" <mkerr@cs.ubc.ca> To: fs@FreeBSD.ORG Subject: Install of second FreeBSD has corrupted existing install Message-ID: <9705301124.ZM16221@cascade.cs.ubc.ca>
next in thread | raw e-mail | index | archive | help
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:
<UNUSED>
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9705301124.ZM16221>