help! bad filesystem summary trashes system

Peter Jeremy PeterJeremy at optushome.com.au
Mon Nov 29 23:00:15 PST 2004


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


More information about the freebsd-stable mailing list