incorrect super block, can't mount / drive

Discussion in 'macOS' started by nick122147, May 26, 2010.

  1. nick122147 macrumors newbie

    Joined:
    May 6, 2009
    #1
    Yesterday I suddenly couldn't start any new programs, then I tried a restart. But it would not start back up. I have already verbose booting enabled, efi is saying something like "cannot get file size info".
    When booting from a Mac install disk disk utility says it cannot repair this drive. Mount command says incorrect super block. Mount_hfs command says "invalid input".
    Any other way I can try repairing the superblock?
    Could it be a hardware fault? It is a kingspec 256GB ssd drive.

    Thanks !
     
  2. nick122147 thread starter macrumors newbie

    Joined:
    May 6, 2009
    #2
    tried fsck_hfs when botted up from an usb drive. this is what I get:

    sudo fsck_hfs -d -f /dev/disk2s1
    ** /dev/rdisk2s1
    Using cacheBlockSize=32K cacheTotalBlock=16384 cacheSize=524288K.
    Executing fsck_hfs (version diskdev_cmds-491~1).
    Block 2 is not an MDB or Volume Header
    Block 503676921 is not an MDB or Volume Header
    unknown volume type
    primary MDB is at block 0 0x00
    alternate MDB is at block 0 0x00
    primary VHB is at block 0 0x00
    alternate VHB is at block 0 0x00
    sector size = 512 0x200
    VolumeObject flags = 0x01
    total sectors for volume = 503676923 0x1e057ffb
    total sectors for embedded volume = 0 0x00
    CheckForClean - unknown volume type
     
  3. satcomer macrumors 603

    satcomer

    Joined:
    Feb 19, 2008
    Location:
    The Finger Lakes Region
    #3
  4. nick122147 thread starter macrumors newbie

    Joined:
    May 6, 2009
    #4
    I managed to get some data of the drive with disk rescue 2. Together with a 3 weeks old backup I don't seem to have lost anything.
    I have now reinstalled into the same drive and everything seems to be working fine. I will keep a close eye on the ssd drive with regular backups.

    It happened after unplugging a midikeyboard and soundcard kind of at the same time as closing the screen/going to sleep mode. Not sure how that can have caused this.

    Thanks.
     

Share This Page