Date: Tue, 30 Nov 2004 18:00:11 +1100 From: Peter Jeremy <PeterJeremy@optushome.com.au> To: Michael Nottebrock <michaelnottebrock@gmx.net> Cc: freebsd-stable@freebsd.org Subject: Re: help! bad filesystem summary trashes system Message-ID: <20041130070010.GX79646@cirb503493.alcatel.com.au> In-Reply-To: <200411282225.36617.michaelnottebrock@gmx.net> References: <200411282144.56438.michaelnottebrock@gmx.net> <20041128210746.GN32181@gsmx07.alcatel.com.au> <200411282225.36617.michaelnottebrock@gmx.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 2004-Nov-28 22:25:29 +0100, Michael Nottebrock wrote: >> Have you tried telling fsck to use an alternate super block (-b option)? > >I found an alternate superblock at 128, but using it gives the same error. That's not promising but you could try one of the other alternates. Assuming you didn't specify any non-standard options when you (or sysinstall) created that partition, running "newfs -N <device>" will report all the alternate superblocks. >> If it's just a glitch that's affected the primary super block, this >> should work. If the in-core data got corrupted and has been written to >> all the superblocks, you might need to play with a filesystem editor. > >Can you suggest such an editor (and possibly give some hints what exactly to >do with it)? Unfortunately, no. I thought there was something in ports but I can't find it now. You might need to write something yourself :-(. -- Peter Jeremy
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041130070010.GX79646>