Re: XFS: SB validate failed

["Spam Magnet" <spam.wax@xxxxxxxxx>]

On Sun, Jun 1, 2008 at 6:46 AM, Stefan Smietanowski <stesmi@xxxxxxxxxx> wrote:
> One way is : od -t c jaz7.img | grep X | head
>
> Look for X   F   S   B, may be split on two lines for you.
>
> This is what my disk looks like but of course, it's on a DOS
> partition:
>
> 0077000   X   F   S   B  \0  \0 020  \0  \0  \0  \0  \0  \0  \0   `  \0
>

I couldn't find any XFS by using the full dump of the disk:
$ od -t c jaz7.img | grep X | head
0040000 353   > 220   (   j   0   X   ]   I   H   C  \0 002     001  \0
0040240 003 303   H 367 363 001   F 374 021   N 376   Z   X 273  \0  \a
0040560 023   Y   Z   X   r  \t   @   u 001   B 003   ^  \v 342 314 303
1041040   5   0                           E   X   E   !  \0   K   -   H
1141360 031  \0   t  \b   P  \r 362  \t   .  \0 265   P   X  \f 026   z
1141400   # 001 353  \n   X 034 022 020   D 001   I 016   X 034   @ 023

(The healthy disk image also doesn't have any XFS but it has: 'S f x'
(capital s))
50.exe at offset 1041040 made me check the image file using a Windows
utility called : UFS Explorer.
(www.ufsexplorer.com) They claim that they can recover XFS partitions.
To my surprise that software
recognized the image as a FAT16 file system containing only one single
file called "50.exe"
I am more inclined to believe 'fdisk' rather than UFS Explorer:
Most likely the original format that Iomega had shipped the Jaz disk
with was a FAT16 and then
somebody in our lab had decided to format it to xfs.

I am beginning to feel that I will need to recover my data manually,
one file at a time :(
(It's really frustrating that I can see all my beautiful file names
through hexdump but can't access them).

So is there a preferred way of hard disk/partition recovery for XFS
file system ?
And if I end up doing that, where can I get more info about the
underwork of xfs ?

thank you all for your patience and help.