From: Hamid <spam.wax@gmail.com>
To: Stefan Smietanowski <stesmi@stesmi.com>
Cc: Timothy Shimmin <tes@sgi.com>, Eric Sandeen <sandeen@sandeen.net>,
xfs@oss.sgi.com
Subject: Re: XFS: SB validate failed
Date: Fri, 30 May 2008 19:26:54 -0400 [thread overview]
Message-ID: <48408D3E.3090401@gmail.com> (raw)
In-Reply-To: <4840406F.50402@stesmi.com>
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
next prev parent reply other threads:[~2008-05-30 23:26 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-29 17:05 XFS: SB validate failed Spam Magnet
2008-05-29 17:19 ` Eric Sandeen
2008-05-29 19:55 ` Spam Magnet
2008-05-29 20:02 ` Eric Sandeen
2008-05-29 21:00 ` Spam Magnet
2008-05-29 21:06 ` Eric Sandeen
2008-05-29 21:46 ` Spam Magnet
2008-05-29 22:19 ` Eric Sandeen
2008-05-29 22:25 ` Stefan Smietanowski
2008-05-30 5:28 ` Timothy Shimmin
2008-05-30 17:19 ` Spam Magnet
2008-05-30 17:59 ` Stefan Smietanowski
2008-05-30 23:26 ` Hamid [this message]
2008-05-31 0:19 ` Stefan Smietanowski
2008-05-31 0:22 ` Stefan Smietanowski
2008-06-01 7:35 ` Hamid
2008-06-01 10:46 ` Stefan Smietanowski
2008-06-03 17:36 ` Spam Magnet
2008-06-03 17:56 ` Spam Magnet
2008-06-03 18:59 ` Stefan Smietanowski
2008-06-03 19:39 ` Spam Magnet
2008-06-03 20:23 ` Stefan Smietanowski
2008-06-05 16:16 ` Spam Magnet
2008-06-02 2:08 ` Timothy Shimmin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=48408D3E.3090401@gmail.com \
--to=spam.wax@gmail.com \
--cc=sandeen@sandeen.net \
--cc=stesmi@stesmi.com \
--cc=tes@sgi.com \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox