Mailing List Archive
tlug.jp Mailing List tlug archive tlug Mailing List Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]Re: [tlug] Mac OS X: bad super block has become Unsupported sector size (0)
- Date: Sat, 21 May 2011 13:12:35 +0900
- From: Jean-Christian Imbeault <jc.imbeault@example.com>
- Subject: Re: [tlug] Mac OS X: bad super block has become Unsupported sector size (0)
- References: <BANLkTi=TkqhnrjOvQmepK_RfLHRO2s60HA@example.com> <4DD7305B.4050005@example.com>
Oh no, this isn't lookin too good for me. I'm hopin that all I've done is trash the FAT or somesuch and that I can still recover the data? Unfortunate I can't make an image as the disk is 1TB and I don't have anything that could accept an image that size (not that I even know how to make an image). Can anyone recommend a file recovery tool or some way of getting files of he drive? Or has beefs really gone and erased everything? Jc On Saturday, May 21, 2011, Simon Cozens <simon@example.com> wrote: > On 21/05/2011 11:22, Jean-Christian Imbeault wrote: >> First I tried to fsck the HDD and it complained about a bad >> superblock. It tried to use alternate superblocks but couldn't find >> any suitable ones. I manually forced it to use the first alternat >> using fsck -b 32 but it still complained, same for trying to use the >> last one. > > Oh dear. OS X's fsck is not particularly filesystem-aware. It is what linux > would call fsck.ufs - i.e. it assumes that everything checks is a UFS > filesystem. Since you're later trying to mount it as MSDOS, I suspect this > will have trashed your data. > >> I then did a newfs on the HDD thinking this would regenerate the >> superblocks. > > If the fsck didn't trash your data, the newfs most certainly will have done. > >> macmini:~ jci$ sudo /sbin/mount_msdos /dev/disk1s1 /Volumes/ELEMENTS/ >> mount_msdos: Unsupported sector size (0) > > It's not MSDOS any more. Who knows what it is. > >> I'd be happy at this point if I could just mount the drive so I can >> move my files off it to a new HDD. > > It's probable that there aren't any files left to move. Sorry. :( > > My advice would be: get it into a Linux box. Image the filesystem *now* before > doing anything else with it. Try fsck.vfat and hope for the best, although > probably the FATs have already gone. :( > > > -- > To unsubscribe from this mailing list, > please see the instructions at http://lists.tlug.jp/list.html > > The TLUG mailing list is hosted by the award-winning Internet provider > ASAHI Net. > Visit ASAHI Net's English-language Web page: http://asahi-net.jp/en/ >
- Follow-Ups:
- Re: [tlug] Mac OS X: bad super block has become Unsupported sector size (0)
- From: Simon Cozens
- Re: [tlug] Mac OS X: bad super block has become Unsupported sector size (0)
- From: Peter Brandt
- [tlug] Handling Raw Hard Drive Images (was Re: Mac OS X: bad super block has become Unsupported sector size (0))
- From: jep200404
- References:
- [tlug] Mac OS X: bad super block has become Unsupported sector size (0)
- From: Jean-Christian Imbeault
- Re: [tlug] Mac OS X: bad super block has become Unsupported sector size (0)
- From: Simon Cozens
Home | Main Index | Thread Index
- Prev by Date: Re: [tlug] Mac OS X: bad super block has become Unsupported sector size (0)
- Next by Date: Re: [tlug] Mac OS X: bad super block has become Unsupported sector size (0)
- Previous by thread: Re: [tlug] Mac OS X: bad super block has become Unsupported sector size (0)
- Next by thread: Re: [tlug] Mac OS X: bad super block has become Unsupported sector size (0)
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links