From: Veedar Hokstadt <veedar@gmail.com>
To: linux-raid@vger.kernel.org
Subject: mdadm -E won't examine loop back device, works ok on source disk
Date: Sun, 22 Apr 2012 17:00:04 -0400 [thread overview]
Message-ID: <CANb3qHeDF10CoRiteo_wwUSvGtpjcNWPh95xdatkFoY+GyAZJQ@mail.gmail.com> (raw)
Consider a SATA drive /dev/sdb which is a member of an imsm RAID0 array...
% sum /dev/sdb
25645 156290904
The drive was imaged to a file without error and mounted as a loopback device...
% sum /dev/loop2
25645 156290904
The checksums match as expected. But I can not examine the loopback I get....
% mdadm -E -v /dev/loop2
mdadm: No md superblock detected on /dev/loop2.
But I can examine the physical source drive /dev/sdb...
% mdadm -E -v /dev/sdb
/dev/sdb:
Magic : Intel Raid ISM Cfg Sig.
Version : 1.0.00
Orig Family : e92a11d9
Family : e92a11d9
Generation : 00001608
UUID : 25137636:2ff64e75:10ae5444:4e8f609b
Checksum : e1237b20 correct
MPB Sectors : 1
Disks : 2
RAID Devices : 1
Disk01 Serial : 8068C3QVT
State : active
Id : 00010000
Usable Size : 312577294 (149.05 GiB 160.04 GB)
[Volume0]:
UUID : 72acd5fa:35c5a901:995af79b:83a29de1
RAID Level : 0
Members : 2
This Slot : 1
Array Size : 625154048 (298.10 GiB 320.08 GB)
Per Dev Size : 312577283 (149.05 GiB 160.04 GB)
Sector Offset : 0
Num Stripes : 1221004
Chunk Size : 128 KiB
Reserved : 0
Migrate State : idle
Map State : normal
Dirty State : clean
Disk00 Serial : 809BC541T
State : active failed
Id : 00000000
Usable Size : 312577294 (149.05 GiB 160.04 GB)
I'm trying to recover data from a failed RAID0.
I can successfully reassemble the RAID0 from the image files using
other proprietary recovery software.
But I would like to get it working with mdadm if at all possible.
Any ideas?
Regards,
V
next reply other threads:[~2012-04-22 21:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-22 21:00 Veedar Hokstadt [this message]
2012-04-22 21:58 ` mdadm -E won't examine loop back device, works ok on source disk NeilBrown
2012-04-23 4:46 ` Veedar Hokstadt
2012-04-23 5:04 ` NeilBrown
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=CANb3qHeDF10CoRiteo_wwUSvGtpjcNWPh95xdatkFoY+GyAZJQ@mail.gmail.com \
--to=veedar@gmail.com \
--cc=linux-raid@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).