Gergely Soos wrote:
> your intuition was absolutely correct. The starting point of my
> partition was moved only not up but down 63 sectors (63*512 bytes)
> It all makes sense, the whole partition grew 63*512 bytes = 0x7E (126)
> inodes that is why I found the root inode on inode 0xFE instead of 0x80.
> Now the question remains how the hell should I move it back??
> And what kind of an idiot program moves the partition table without any
> confirmation? That would kill any filesystem.
Strangely, I've seen this before. No idea why, or what is doing it.
Hopefully you have saved copies of all the things you edited & dd'd? So
I'd start by putting those back.
Then you can use a partition editor to move the start of the partition
back where it belongs, I guess. (w/o seeing where you found the
superblocks, I'm not certain).
Or, if I'm reading you right, do you mean that the first "XFSB" is 63
sectors ahead of the start of hdd1? If so, then maybe mounting /dev/hdd
(not /dev/hdd1) just works.
> On Tue, Jan 6, 2009 at 11:54 PM, Eric Sandeen <sandeen@xxxxxxxxxxx
> <mailto:sandeen@xxxxxxxxxxx>> wrote:
> Gergely Soos wrote:
> > That is a good idea, I'm gonna search for the XFSB on the entire disk.
> > I will also give PhotoRec a try if nothing else works.
> > In the meantime, Eric, you can download the metadata from here:
> > http://bluepantherit.net/metadump.bz2
> > It would be real nice from you if you would take a closer look.
> > And one more thing, xfs_check -s /dev/hdd1 prints the following:
> > can't seek in filesystem at bb 58701991023656163
> > can't read agfl block for ag 4082146910
> > can't seek in filesystem at bb 58702015871605112
> ... it's basically reading garbage as block numbers, but they are well
> past the end of the device, so failing.
> Very confused, it is. :)