Am 07.02.2012 um 18:45 schrieb Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>: > On 02/07/12 18:42, Stefan Priebe wrote: >> Hi Jes, >> >> Am 07.02.2012 17:09, schrieb Jes Sorensen: >>> /dev/md126 looks to be the container, not the actual raid device, from >>> what your mdadm.conf says. >> >> booted from a rescue CD using 2.6.32 kernel. >> >> ~# mdadm -D --scan >> ARRAY /dev/md/imsm0 metadata=imsm UUID=24cdb70d:101f4c4b:23dfa5cb:3f176b6a >> ARRAY /dev/md/RaidStefan_0 container=/dev/md/imsm0 member=0 >> UUID=84aa9982:ed593d80:ee7c7f53:e2944038 >> >> ~# cat /proc/mdstat >> Personalities : [raid1] >> md126 : active (auto-read-only) raid1 sda[1] sdb[0] >> 156288000 blocks super external:/md127/0 [2/2] [UU] >> >> md127 : inactive sdb[1](S) sda[0](S) >> 5544 blocks super external:imsm >> >> unused devices: <none> >> >> so md126 is the real raid. >> >>> What does your /proc/mdstat say? >> >> When booted from disk - output while in initramfs: >> ~# cat /proc/mdstat >> Personalities : [raid1] >> md126 : active (read-only) raid1 sda[1] sdb[0] >> 156288000 blocks super external:/md127/0 [2/2] [UU] >> >> md127 : inactive sdb[1](S) sda[0](S) >> 5544 blocks super external:imsm > > Does it stay read-only if you try to write to it? Yes as it is read-only and not auto-read-only. Greets and thanks, Stefan -- 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
