xfs
[Top] [All Lists]

Re: XFS: SB validate failed

To: Stefan Smietanowski <stesmi@xxxxxxxxxx>
Subject: Re: XFS: SB validate failed
From: Hamid <spam.wax@xxxxxxxxx>
Date: Fri, 30 May 2008 19:26:54 -0400
Cc: Timothy Shimmin <tes@xxxxxxx>, Eric Sandeen <sandeen@xxxxxxxxxxx>, xfs@xxxxxxxxxxx
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; bh=Pje9HwmS4j6903yLdf5mMTciH4AQrMc4sIHGbhoB8gM=; b=Lw3cFB2+0Wrd99d1H6bEVbz8pbTfRpkOcJEBdoxGJreRFDj5utidm4hbpgUwxprJjTQdGExVeYVKqGKiuN8rWiDCPTrwB49UyX2aDkufIOOf4N8V4AF1a89tgczCf7VyrsutwL153oFqT4FGZJ6AOK9gxp9RiqgT65NtGIVhRgU=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; b=JmFP4io0yDEGoqKCNxl0wT8y2aTXjhRd+D+aau8cpN1SR8opVvtZMoHCVCBB1DR/FbVqi/AvGO5z/pSarsMQdwPe0JscT7JTn3p0ipOTXKXTh2qHqu46nXsuTIHrjhH3uvxnukEV0UqQIO0fluDpkLxvUo3a7cjPH1LxPuGXkks=
In-reply-to: <4840406F.50402@xxxxxxxxxx>
References: <3607657a0805291005k457791cej1c5f867da0f95965@xxxxxxxxxxxxxx> <483EE5BD.8020407@xxxxxxxxxxx> <3607657a0805291255i59fd006fi9d6836cf528d19a6@xxxxxxxxxxxxxx> <483F0BC3.2050901@xxxxxxxxxxx> <3607657a0805291400h3c50165lea6fbea919deed0f@xxxxxxxxxxxxxx> <483F1AED.3010808@xxxxxxxxxxx> <3607657a0805291446t79808c63l664780c1cbc3d871@xxxxxxxxxxxxxx> <483F907A.3020108@xxxxxxx> <3607657a0805301019h4a49dc86ne8f1f019629a1c41@xxxxxxxxxxxxxx> <4840406F.50402@xxxxxxxxxx>
Sender: xfs-bounce@xxxxxxxxxxx
User-agent: Thunderbird 2.0.0.14 (Macintosh/20080421)
Stefan Smietanowski wrote:

Are you dd'ing the whole disk or just the partition(s) you want ? I
recommend just doing the partition(s) into seperate files. I'm uncertain
if loopback nowadays handles partitions or not. I know it didn't before
but there were patches back then.

// Stefan

I did the whole disk under Linux:

$ dd if=/dev/sdb of=disk.img conv=noerror,sync

This is how fdisk sees my image:

$ sudo fdisk -ul disk.img
Disk disk.img (SGI disk label): 255 heads, 63 sectors, 0 cylinders
Units = sectors of 1 * 512 bytes

----- partitions -----
Pt#    Device  Info     Start       End   Sectors  Id  System
8: disk.img1            4096   3915599   3911504   a  SGI xfs
9: disk.img2               0      4095      4096   0  SGI volhdr
11: disk.img3               0   3915599   3915600   6  SGI volume
----- Bootinfo -----
Bootfile: /unix
----- Directory Entries -----
0: sgilabel   sector    2 size     512

I could mount the image of the healthy disk using:

$ sudo mount -t xfs -o loop,offset=$((512*4096)) disk.img /mnt

and I was able to browse the content of /mnt :)
Trying to mount the whole image didn't work. I was hoping I could do that so it gives me the possibility of modifying the partition table of the bad disks that refuse to mount under either OS. Basically I want to play with bad disks' images to see if I can recover any data without actually modifying the disks.
Is there any work around for this ?
Should I create a device (rather than a loop) for the whole image ?

I should mention that creating the whole disk image by using dd under Irix6.5 and using the same mount command as above in Linux didn't work! Something might have gone wrong during the file transfer from Irix to Linux. If I get a chance I'll try it again.

Thanks again


<Prev in Thread] Current Thread [Next in Thread>