On Mon, 27 Dec 2010 21:35:48 +0100 Laurent Pinchart <laurent.pinchart@xxxxxxxxxxxxxxxx> wrote: > > So something odd is happening, and more logs are needed to guess what. > > I'll try to get more logs. In the meantime I've found something weird. If I > run mdadm --assemble --scan twice in a row, the partitions are correctly > created the second time. > > The next problem will be that the array is created in read-only mode. mdadm -- > readwrite /dev/md126 doesn't help there, but echo active > > /sys/class/block/md126/md/array_state does. The array is read-only because 'mdmon' is not running. When mdadm assembles the array it starts mdmon to monitor the array. This is needed when the array uses a metadata format that the kernel doesn't understand. It is mdmon's job to switch the array to read-write I cannot think why mdmon is not being started, unless maybe it doesn't exist on the initramfs - it should be in /sbin. The logs you sent show that the partitions aren't getting detected at all, so it isn't the case that they get detected and then removed. I don't remember exactly what triggers the partition detection. Maybe just opening the array device... It is entirely possible that once you get the mdmon issue sorted out, the other will disappear. You could try mdmon md126 & and see if that makes the array read/write and creates the partitions. Also check with ps to confirm that mdmon isn't running. NeilBrown > > I forgot to mention that I'm running 2.6.36.5 with mdadm 3.1.4. > -- 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
