UPDATE: filesystem corruption with bad super block

From: barry deevey (barry.deevey_at_enmo.co.uk)
Date: 02/27/04

  • Next message: Shouben Zhou: "summary: how to uninstall the particular patch" 
    To: <sunmanagers@sunmanagers.org>
Date: Fri, 27 Feb 2004 20:35:59 -0000

    Thanks all for the responses so far...

    most are pointing me to run newfs -N

    I should have mentioned that I've already done this and it only returned an
    alternate super block of 32 - which I've already tried.....

    I don't think theres anything else I can do....

    Thanks again,
    Barry

    -----Original Message-----
    From: sunmanagers-bounces@sunmanagers.org
    [mailto:sunmanagers-bounces@sunmanagers.org]On Behalf Of barry deevey
    Sent: 27 February 2004 18:10
    To: sunmanagers@sunmanagers.org
    Subject: filesystem corruption with bad super block....

    All,

    When I try fsck on a filesystem I get the below:

    # fsck /dev/rdsk/c1t1d0s7
    ** /dev/rdsk/c1t1d0s7
    BAD SUPER BLOCK: MAGIC NUMBER WRONG
    USE AN ALTERNATE SUPER-BLOCK TO SUPPLY NEEDED INFORMATION;
    eg. fsck [-F ufs] -o b=# [special ...]
    where # is the alternate super block. SEE fsck_ufs(1M).

    I then tried to use the alternate super block:

    # fsck -F ufs -o b=32,f /dev/rdsk/c1t1d0s7
    Alternate super block location: 32.
    ** /dev/rdsk/c1t1d0s7
    BAD SUPER BLOCK: MAGIC NUMBER WRONG
    USE AN ALTERNATE SUPER-BLOCK TO SUPPLY NEEDED INFORMATION;
    eg. fsck [-F ufs] -o b=# [special ...]
    where # is the alternate super block. SEE fsck_ufs(1M).
    #

    ANY ideas at all to get fsck to recognise this filesystem would be greatly
    appreciated.

    Cheers
    Barry.
    _______________________________________________
    sunmanagers mailing list
    sunmanagers@sunmanagers.org
    http://www.sunmanagers.org/mailman/listinfo/sunmanagers
    _______________________________________________
    sunmanagers mailing list
    sunmanagers@sunmanagers.org
    http://www.sunmanagers.org/mailman/listinfo/sunmanagers

  • Next message: Shouben Zhou: "summary: how to uninstall the particular patch"

    Relevant Pages

    • Re: Recovery from disk+fs crash
      ... Robin Elfrink said: ... The filesystem was mounted read-only just then, ... Alternate super block location: 160 ... UPDATE STANDART SUPERBLOCK? ...
      (freebsd-isp)
    • Re: Really no one knows ?!
      ... situation as you, fsck was not working. ... running newfs with the -N flag on the slice. ... Booted from the Fixit disk. ... Alternate super block location: 160 ...
      (freebsd-current)
    • Strange fsck behaviour with alternated superblock
      ... I have a strange behaviour with using fsck with a alternated supperblock: ... ** Phase 5 - Check Cyl groups ... Do fsck with alternated superblock: ... Alternate super block location: 109504. ...
      (comp.unix.solaris)
    • (no subject)
      ... situation as you, fsck was not working. ... running newfs with the -N flag on the slice. ... Booted from the Fixit disk. ... Alternate super block location: 160 ...
      (freebsd-current)
    • filesystem corruption with bad super block....
      ... When I try fsck on a filesystem I get the below: ... BAD SUPER BLOCK: MAGIC NUMBER WRONG ... USE AN ALTERNATE SUPER-BLOCK TO SUPPLY NEEDED INFORMATION; ... I then tried to use the alternate super block: ...
      (SunManagers)