Hello Chris,
Am Montag, 24. September 2012, 14:18:27 schrieb Chris Murphy:
> On Sep 24, 2012, at 1:06 PM, Günther J. Niederwimmer wrote:
> > Disk /dev/sda: 320.1 GB, 320072933376 bytes
> > 256 Köpfe, 63 Sektoren/Spur, 38761 Zylinder, zusammen 625142448 Sektoren
> > Einheiten = Sektoren von 1 × 512 = 512 Bytes
> > Sector size (logical/physical): 512 bytes / 512 bytes
> > I/O size (minimum/optimal): 512 bytes / 512 bytes
> > Disk identifier: 0x00000000
> >
> > Gerät boot. Anfang Ende Blöcke Id System
> >
> > /dev/sda1 1 4294967295 2147483647+ ee GPT
>
> Well that's screwy. But at least the PMBR is protecting all sectors (and
> quite a bit more that don't exist) of this disk.
>
> Last time we checked, the array state was dirty. Is that still the case?
> Report the results from these two:
Yes Sir ;).
> 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
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0
UUID : ec120401:b6ed52e6:3814fac4:48fcf4fc
Number Major Minor RaidDevice State
1 8 0 0 active sync /dev/sda
0 8 16 1 active sync /dev/sdb
> mdadm -Ds
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 ?
/dev/md127:
Version : imsm
Raid Level : container
Total Devices : 2
Working Devices : 2
UUID : 363f146f:e7f29dc8:f05996c3:577ead6a
Member Arrays : /dev/md/Volume0
Number Major Minor RaidDevice
0 8 16 - /dev/sdb
1 8 0 - /dev/sda
--
mit freundlichen Grüßen / best Regards.
Günther J. Niederwimmer
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
