<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">If it's partition 3, wouldn't you by
trying to assemble the raid on /dev/sda3 instead? Make sure you
set the partition to type fd for linux raid autodetection.<br>
<br>
mb@host:~$ sudo fdisk /dev/sdi -l<br>
<br>
Disk /dev/sdi: 120.0 GB, 120034123776 bytes<br>
255 heads, 63 sectors/track, 14593 cylinders, total 234441648
sectors<br>
Units = sectors of 1 * 512 = 512 bytes<br>
Sector size (logical/physical): 512 bytes / 512 bytes<br>
I/O size (minimum/optimal): 512 bytes / 512 bytes<br>
Disk identifier: 0x6b7aa52b<br>
<br>
Device Boot Start End Blocks Id System<br>
/dev/sdi1 * 2048 206847 102400 fd Linux raid
autodetect<br>
/dev/sdi2 206848 234441647 117117400 fd Linux raid
autodetect<br>
<br>
..where /dev/sdi1 is /boot, and /dev/sdi2 is my luks crypt volume
and pv for lvm.<br>
<br>
Use gdisk if/when doing gpt, acts largely like fdisk for mbr-based
partitions.<br>
<br>
Try just doing an auto assemble/scan, maybe your raid superblock
got blasted...<br>
<br>
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
mdadm --assemble --scan<br>
<br>
I use gdisk if available, or make sure it is available, but like
ubuntu installs are really stupid these days and don't make these
available at install, but you can still apt-get install gdisk or
mdadm to get them present to rebuild raids.<br>
<br>
I spent a good chunk of a week figuring out idiosyncrasies with
efi, gpt, raid, luks, and lvm. Only thing it told me is everyone
does something different between distros at this point.<br>
<br>
-mb<br>
<br>
<br>
On 02/02/2014 09:25 AM, George Toft wrote:<br>
</div>
<blockquote cite="mid:52EE717B.6000506@georgetoft.com" type="cite">I've
spent over 15 hours on this (google . . . head . . .desk . . .
repeat).
<br>
<br>
I need to recover the data off of one of these hard drives.
<br>
<br>
Background
<br>
Two 3TB hard drives in a Raid 1 mirror, working fine for months.
OS: Centos 6.5
<br>
Woke up a few days ago to a dead system - looks like motherboard
failed. And when it failed, it appears to have corrupted the RAID
partition (supposition - see problems below). I moved the drives
to another system and it will boot then the kernel panics.
<br>
<br>
Partitions
<br>
part 1 - /boot
<br>
part 2 - swap
<br>
part 3 - RAID
<br>
<br>
I think the RAID partition has just one filesystem (/).
<br>
<br>
<br>
What I've done:
<br>
Rescue mode: Boots, unable to assemble raid set:
<br>
<br>
# fdisk -l | egrep "GPT|dev"
<br>
WARNING: GPT (GUID Partition Table) detected on '/dev/sdb'! The
util fdisk doesn't support GPT. Use GNU Parted.
<br>
<br>
WARNING: GPT (GUID Partition Table) detected on '/dev/sdb'! The
util fdisk doesn't support GPT. Use GNU Parted.
<br>
<br>
Disk /dev/sda: 80.0 GB, 80025280000
<br>
Disk /dev/sdb: 3000.6 GB, 3000591900160 bytes
<br>
/dev/sdb1 1 267350 2147483647+
ee GPT
<br>
Disk /dev/sdc: 3000.6 GB, 3000591900160 bytes
<br>
/dev/sdc1 1 267350 2147483647+
ee GPT
<br>
<br>
# mdadm --assemble --run /dev/md0 /dev/sdb
<br>
mdadm: Cannot assemble mbr metadata on /dev/sdb
<br>
mdadm: /dev/sdb has no superblock - assembly aborted
<br>
<br>
# mdadm --assemble --run /dev/md0 /dev/sdb1
<br>
mdadm: cannot open device /dev/sdb1: No such file or directory
<br>
mdadm: /dev/sdb has no superblock - assembly aborted
<br>
<br>
<br>
parted tells me I've found a bug and gives me directions to report
it.
<br>
<br>
-----------
<br>
<br>
Booted Knoppix and ran disktest. I can copy the RAID partition to
another drive as a disk image and I end up with image.dd. When I
try to build an array out of it, I get an error: Not a block
device.
<br>
<br>
Tried commercial RAID recovery software (Disk Internals) - it hung
after identifying 2.445 million files.
<br>
<br>
<br>
-------------
<br>
<br>
Ideas on what to do next?
<br>
<br>
Is anyone here up for a challenge? Anyone need beer money? I need
the data recovered, and will pay :)
<br>
<br>
All help is appreciated :)
<br>
<br>
</blockquote>
<br>
</body>
</html>