Incorrect super block on a disk

[Greg 'groggy' Lehey]

On Saturday,  3 May 2003 at 16:57:57 -0700, Paul English wrote:
>
> Hi,
> 	I have a disk that I sent out for data recovery. The recovery
> place returned my data on another hard drive. I'm trying to mount the
> relevant partition of said hard drive. When I do I get:
>
> mount: /dev/ad1s2e on /mnt: incorrect super block
>
> When I try to fsck, I get:
>
> INCORRECT SUPER BLOCK: MAGIC NUMBER WRONG
>
> it tries for an alternate superblock, fails and then I try doing
> fsck -b 32 (as recommended in the manpages) and I get the same error.
>
> Is there anything I'm doing wrong or something else to try?

It seems pretty certain that whatever they sent back from the data
recovery house is not a UFS file system.  You should try to find out
how they got the data there.  I can't imagine them creating a new file
system.  Until you know that, there's not much point trying
alternatives, though some of them exist.

> Can I somehow regenerate the super block?

Regenerating super blocks is simple: that's what newfs(8) does.  The
trick is keeping your data.

Greg
--
When replying to this message, please copy the original recipients.
If you don't, I may ignore the reply or reply to the original recipients.
For more information, see http://www.lemis.com/questions.html
See complete headers for address and phone numbers
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-questions/attachments/20030504/33d52b29/attachment.bin