BAD SUPER BLOCK, MAGIC NUMBER WRONG

[Michael Elleby III_1]

Any attempts to run fsck on this file system result in the same error message.

Any suggestions?

Mike Elleby

[Michael Elleby III_1]

I resolved this issue. The superblock on the root disk was overwritten. More or less, the filesystem is 'toast'..

I'm reinstalling the OS on the disk as I write this...

Mike Elleby

[Robert Binkley]

Try to boot with out sysconfigtab..
booting Tru64, with options to bypass /etc/sysconfigtab (boot -fl cs)



This type of problem can be caused by a mis-configuration.
I have seen two things specifically cause it here:
- a patched source module which was a higher level then
another patch
- a residue XMI bus in the /sys/conf/HOST file which was
removed.

First, try building a brand new kernel:
cd /sys/conf
doconfig -c BOGUS # or other new name of your choice

if that works, look for differences in the config:
diff BOGUS
then:
edit ident in BOGUS to be
mv /sys/HOSTNAME /sys/HOSTNAME.old
mv /sys/BOGUS /sys/HOSTNAME
mv /sys/conf/BOGUS and BOGUS.list to HOSTNAME and HOSTNAME.list

if it doesn't work, review whatever patches you have applied (particularly
anything patching a *.c or *.h) for incompatability.

[Ralf Puchner]

8. BAD SUPER BLOCK: MAGIC NUMBER WRONG

Setup self explanatory
Action Stop processing this file system. The user should rerun fsck using the -b switch to specify an alternate superblock.

Reinstalling the OS seems a little bit dramatically ;-)