From owner-freebsd-questions Wed Oct 29 17:49:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA03637 for questions-outgoing; Wed, 29 Oct 1997 17:49:32 -0800 (PST) (envelope-from owner-freebsd-questions) Received: from dusya.osd.com (dusya.osd.com [199.181.168.1]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id RAA03630 for ; Wed, 29 Oct 1997 17:49:30 -0800 (PST) (envelope-from jray@dusya.osd.com) Received: from borscht by dusya.osd.com (NX5.67g/NX3.0M) id AA00520; Wed, 29 Oct 97 17:48:52 -0800 From: James Ray Message-Id: <9710300148.AA00520@dusya.osd.com> Received: by borscht.osd.com (NX5.67g/NX3.0X) id AA01179; Wed, 29 Oct 97 17:48:59 -0800 Date: Wed, 29 Oct 97 17:48:59 -0800 To: freebsd-questions@freebsd.org Subject: need help recovering from bad 2.2.5 install Cc: jray@seanet.com Sender: owner-freebsd-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I tried to install 2.2.5 on a drive that had an existing 2.1.7 installation on another partition. I now understand that this is not a good thing to do. Please assist me in getting my 2.1.7 system working again. Here's my partition scheme: 295megs DOS 305megs (was linux, tried installing 2.2.5 here via modem) 1.1gig FreeBSD 2.1.7 (The drive is a 1.7gig, the SCSI adapter is an Adaptec 1542) I tried installing 2.2.5 on the 305meg partition. I did the minimal install, and added the Boot Manager. During the install, everything appeared to be going in the right place (the 305 meg partition). When I was done, the Boot Manager gave me three choices, DOS, BSD, and BSD. However, both BSD choices booted as 2.2.5, so I gave up, and used DOS's fdisk /mbr to nuke the boot manager, and made the 1.1gig partition active. While I was at it, I used DOS's fdisk to delete the 305meg partition and formatted it as FAT, for dos backup reasons that we won't get into here. The 1.1 gig partition then booted as 2.2.5 in single-user mode, and gave me these messages: /dev/rsd0s3f: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY /dev/rsd0s3e: /dev/rsd0s3e: BAD SUPER BLOCK: MAGIC NUMBER WRONG /dev/rsd0s3e: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY THE FOLLOWING FILE SYSTEMS HAD AN UNEXPECTED INCONSISTENCY /dev/rsd0s3f (/usr), /dev/rsd0s3e (/var) Automatic file system check failed ... help! # So I ran fsck: # fsck ** /dev/rsd0a ** Last mounted on / ** Root file system ** Phase 1 blah blah until Phase 5 865 files, 13417 used, 383478 free (238 frags, 47905 blocks, 0.1% fragmentation)** /dev/rsd0s3f BAD SUPER BLOCK: MAGIC NUMBER WRONG pid 15 (fsck), uid 0: exited on signal 8 Floating point exception # I would like to recover my 1.1 gig partition and make it bootable as a 2.1.7 system again. What can I do ? I must admit that I have no backups from which to restore -- now a tape drive is first on the list ... Thanks, James Ray.