From owner-freebsd-questions@FreeBSD.ORG Tue Jun 29 06:59:25 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0CEBC16A4CE for ; Tue, 29 Jun 2004 06:59:25 +0000 (GMT) Received: from colossus.systems.pipex.net (colossus.systems.pipex.net [62.241.160.73]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1D37843D1F for ; Tue, 29 Jun 2004 06:59:24 +0000 (GMT) (envelope-from robert@irrelevant.com) Received: from albert.mosthosts.net (81-86-155-6.dsl.pipex.com [81.86.155.6]) by colossus.systems.pipex.net (Postfix) with ESMTP id 38DC91C00120; Tue, 29 Jun 2004 07:59:21 +0100 (BST) Received: from angua.irrelevant.com (dhcp88.internal.irrelevant.com [192.168.0.88]) by albert.mosthosts.net (Postfix) with ESMTP id 550B945; Tue, 29 Jun 2004 08:17:12 +0100 (BST) Message-Id: <6.1.1.1.0.20040629080008.0798b1c0@albert> X-Sender: irrelevant1@albert X-Mailer: QUALCOMM Windows Eudora Version 6.1.1.1 Date: Tue, 29 Jun 2004 08:03:37 +0100 To: ruben@bloemgarten.demon.nl From: Rob In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed cc: freebsd-questions@FreeBSD.ORG Subject: Re: FW: help please? corrupted hard disc - invalid super block. X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Jun 2004 06:59:25 -0000 hi, thanks for the help! Mounting /dev/ad5e worked (at least in read-only, it wants a fsck) so rather than try a repair, and risk blowing it up, (and I'm on 4.8, which still has disklabel nor bsdlabel) I'll copy everything off and re-initialise the disc in due course. Thanks! Rob. At 15:53 28/06/2004, Ruben Bloemgarten wrote: >It looks like you wrote the disklabel for the slice to the disk or >vice-versa. >If you check /dev there probably isn't a /dev/ad5s* there. Try mounting >/dev/ad5e instead of /dev/ad5s1e. To verify, do a bsdlabel ad5s1 to see if >you have a disklabel for the slice. Otherwise you could : >1.backup you disklabel > #bsdlabel /dev/ad5e > disklabel.BAK >2. write a correct disklabel for /dev/ad5s1 > #bsdlabel -w -B ad5s1 >3. Edit your disklabel to be correct : > a. note the size values of #bsdlabel ad5s1 > b. make another backup of your saved disklabel > c. edit one of the backups and change the size value > to the value you got from #bsdlabel ad5s1 > d. write your edited disklabel to ad5s1 > #bsdlabel -R ad5s1 disklabel.BAK > This *should* return no errors. >4. try to mount ad5s1 >Now this is all based on them hope that you don't have to erase the >bad/sliceless disklabel on da5. > >Good luck, >Ruben > >-----Original Message----- >From: owner-freebsd-questions@freebsd.org >[mailto:owner-freebsd-questions@freebsd.org] On Behalf Of Rob >Sent: Monday, June 28, 2004 11:08 AM >To: questions@freebsd.org >Subject: help please? corrupted hard disc - invalid super block. > > >Hi! > >I have a hard disc that I think must have been set up wrong initially... > >It was however working fine, but at some point filled up to capacity, >wherapon the next reboot it failed to mount. > >System is 4.8-RELEASE, Generic Kernel. > >Currently the disc shows: > >luggage# mount -r /dev/ad5s1e /mnt >mount: /dev/ad5s1e on /mnt: incorrect super block > >luggage# disklabel -r ad5 ># /dev/ad5c: >type: ESDI >disk: ad5s1 >label: >flags: >bytes/sector: 512 >sectors/track: 63 >tracks/cylinder: 255 >sectors/cylinder: 16065 >cylinders: 14593 >sectors/unit: 234441585 >rpm: 3600 >interleave: 1 >trackskew: 0 >cylinderskew: 0 >headswitch: 0 # milliseconds >track-to-track seek: 0 # milliseconds >drivedata: 0 > >8 partitions: ># size offset fstype [fsize bsize bps/cpg] > c: 234436482 0 unused 0 0 # (Cyl. 0 - >14592*) > e: 234436482 0 4.2BSD 16384 16384 300 # (Cyl. 0 - >14592*) >Warning, partition c doesn't cover the whole unit! >Warning, An incorrect partition c may cause problems for standard system >utilities > >luggage# fsck /dev/ad5s1e >Can't open /dev/ad5s1e: Invalid argument > >luggage# fsck -b 32 /dev/ad5s1e >Alternate super block location: 32 >Can't open /dev/ad5s1e: Invalid argument > >luggage# file -s /dev/ad5s1e >/dev/ad5s1e: can't read `/dev/ad5s1e' (Invalid argument). > > > >At this point I am stuck ... most of the "Invalid Super Block" messages I >can find when searching relate to cd-roms. > >If I could mount the disc even read-only, I could copy the data off. > >Can anybody give me any clues on where to go from here? > >Thanks in advance, > >Rob > > >_______________________________________________ >freebsd-questions@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-questions >To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" > >_______________________________________________ >freebsd-questions@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-questions >To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"