Re: Hello,Re: GPT Table broken on a Raid1
From: Chris Murphy <hidden>
Date: 2012-09-24 21:12:22
On Sep 24, 2012, at 3:06 PM, Günther J. Niederwimmer wrote:
quoted
mdadm -D /dev/md126/dev/md126: Container : /dev/md/imsm0, member 0 Raid Level : raid1 Array Size : 312568832 (298.09 GiB 320.07 GB) Used Dev Size : 312568964 (298.09 GiB 320.07 GB) Raid Devices : 2 Total Devices : 2 State : active
Probably clean. Try: mdadm -E /dev/sda
ARRAY /dev/md/imsm0 metadata=imsm UUID=363f146f:e7f29dc8:f05996c3:577ead6a ARRAY /dev/md/Volume0 container=/dev/md/imsm0 member=0 UUID=ec120401:b6ed52e6:3814fac4:48fcf4fc Question: Why create mdadm also a md127, I found this now ?
Kernel is mapping /dev/md/Volume0 to /dev/md126. It's doing the same on my system, although it's using md126. Not sure if that's controllable or not. Maybe someone else can answer it. Chris Murphy-- To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html