Return to BSD News archive
Newsgroups: comp.unix.bsd.freebsd.misc Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.mel.connect.com.au!munnari.OZ.AU!news.ecn.uoknor.edu!qns3.qns.com!imci4!newsfeed.internetmci.com!howland.reston.ans.net!EU.net!sun4nl!Utrecht.NL.net!news.iaf.nl!news.es.iaf.nl!yedi!wilko From: wilko@yedi.iaf.nl (Wilko Bulte) Subject: Re: Bad Super Block Wrong magic number Organization: Private FreeBSD site - Arnhem, The Netherlands Message-ID: <DrGKBp.92A@yedi.iaf.nl> References: <3198CC8C.1CC3@shockwave.blast.net> Date: Wed, 15 May 1996 17:52:37 GMT Lines: 17 Pat McPartland <mcp@shockwave.blast.net> writes: >My system crashed while trying to do a dump to the tape drive. I get >a "bad super block magic number wrong" message that fsck can't fix. >Is there a way to fix this without killing all my files? Probably. The FFS keeps multiple copies of the superblock. To find out where the additional copies of the superblock are use newfs -N /dev/whatever (DON'T FORGET the -N, and check the man page to see what it does). The superblock# are now printed. You can subsequently run fsck -b # where # is one of the block# printed by newfs -N Hope this helps Wilko