From owner-freebsd-current@FreeBSD.ORG Sun Aug 24 12:26:15 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D4C1416A4BF for ; Sun, 24 Aug 2003 12:26:15 -0700 (PDT) Received: from mailhost.rz.uni-karlsruhe.de (mailhost.rz.uni-karlsruhe.de [129.13.64.98]) by mx1.FreeBSD.org (Postfix) with ESMTP id CC3F243FE9 for ; Sun, 24 Aug 2003 12:26:14 -0700 (PDT) (envelope-from giggel@brain.hadiko.de) Received: from nce2.hadiko.de (hadince2.hadiko.uni-karlsruhe.de [172.20.32.2]) by mailhost.rz.uni-karlsruhe.de with esmtp (Exim 3.36 #1) id 19r0VB-0000CY-00 for freebsd-current@freebsd.org; Sun, 24 Aug 2003 21:26:13 +0200 Received: from brain.hadiko.de (root@hadil611.hadiko.uni-karlsruhe.de [172.20.44.176])h7OJQCvu001029 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sun, 24 Aug 2003 21:26:12 +0200 Received: from brain.hadiko.de (giggel@localhost.hadiko.de [127.0.0.1]) by brain.hadiko.de (8.12.9/8.12.9) with ESMTP id h7OJQC2c015591 for ; Sun, 24 Aug 2003 21:26:12 +0200 (CEST) (envelope-from giggel@brain.hadiko.de) Received: (from giggel@localhost) by brain.hadiko.de (8.12.9/8.12.9/Submit) id h7OJQCBh015590 for freebsd-current@freebsd.org; Sun, 24 Aug 2003 21:26:12 +0200 (CEST) Date: Sun, 24 Aug 2003 21:26:11 +0200 From: Thomas Gutzler To: FreeBSD Current Message-ID: <20030824192611.GA14668@brain.hadiko.de> Mail-Followup-To: Thomas Gutzler , FreeBSD Current Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.4i Subject: recover superblock X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Thomas Gutzler List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Aug 2003 19:26:16 -0000 Hi, I just lost all of my filesystems on my 5.1 box. I was running mnogosearch's indexer on my website while several errors occured. I guess there were 320 of these errors, cause the last message was "last message repeated 320 times". Unfortunately /var is lost as well, so I don't have more error messages. kernel: swap_pager: indefinite wait buffer: device: ad0s1b, blkno: 23536, size: 4096 kernel: ad0: WRITE command timeout tag=0 serv=0 - resetting kernel: ata0: resetting devices .. kernel: done kernel: bad block 4190320178290426368, ino 402986 kernel: pid 42 (syncer), uid 0 inumber 402986 on /usr: bad block I decided to reboot into singleuser and run fsck. I noticed, that the buffers couldn't be flushed before restarting and the system couldn't boot. It said: "not ufs" I plugged the harddisk into another computer and tried to run fsck. It couldn't find a superblock, used an alternative one and coredumped while trying to repair the first error. Before dumping, it said something like "Couldnt allocate 3900000000 bytes for inoinfo". I can only remember the value of around 3.9G. This happened on all filesystems of ad0. I could mount the filesystem but not access it, but df said: Used: -2.8T (on a 40G disk). I surrendered on that and ran newfs. I don't know why, but fsck works on ad1. fsck said something like "softupdate inconsistency" while trying to repair the filesystem which obviously didn't completely work. # fsck /dev/ad1s1e ** /dev/ad1s1e Cannot find file system superblock LOOK FOR ALTERNATE SUPERBLOCKS? [yn] y USING ALTERNATE SUPERBLOCK AT 32 ** Last Mounted on ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups 19093 files, 42115174 used, 33631703 free (6471 frags, 4203154 blocks, 0.0% fragmentation) # mount /dev/ad1s1e /mnt/ mount: /dev/ad1s1e on /mnt: incorrect super block same thing using fsck -b 32 or any other alternative Google somewhere advised to use tunefs, but: # tunefs -A /dev/ad1s1e tunefs: /dev/ad1s1e: could not read superblock to fill out disk Even trying to copy an alternate superblock using dd faied. Do you have any ideas, how I could recover the data on this disk ? Cheers, Tom