~# cat /proc/mdstat
Personalities : [raid1] [raid0] [raid10] [raid6] [raid5] [raid4]
md3 : active raid1 sda4[0]
869702736 blocks super 1.0 [2/1] [U_]
bitmap: 57/415 pages [228KB], 1024KB chunk

md0 : active raid1 sda1[0]
96376 blocks super 1.0 [2/1] [U_]
bitmap: 1/6 pages [4KB], 8KB chunk

md1 : active (auto-read-only) raid1 sdb2[1] sda2[0]
2096468 blocks super 1.0 [2/2] [UU]
bitmap: 0/8 pages [0KB], 128KB chunk

md124 : active raid1 sdb3[1] sda3[0]
104856180 blocks super 1.0 [2/2] [UU]
bitmap: 8/200 pages [32KB], 256KB chunk

...

for this case, but the behavior which partition is affected is random,
only md124 seems stable (the root fs). The strange md naming was the
result of an upgrade installation. The device details are attached as
well.

It happens, that the active device even *switches* between boots,
which
is a perfect recipe for actually loosing data, hence this md doesn't
raise data security, it is the reason for loosing them.

Could some kind soul tell me, what's going on here?

This looks somewhat familiar. I had a similar issue after install Ubuntu 12.04 on my home server. IIRC udev/mdadm was out of sync, so that the raid was started before all drives were ready. This was fixed around ubuntu 12.04.1. But then again, since it finds some of the partitions, and not losing whole drives, this seems somewhat unlikely.

Vennlige hilsener / Best regards

roy
--
Roy Sigurd Karlsbakk
(+47) 98013356
roy@karlsbakk.net
http://blogg.karlsbakk.net/
GPG Public key: http://karlsbakk.net/roysigurdkarlsbakk.pubkey.txt
--
I all pedagogikk er det essensielt at pensum presenteres intelligibelt. Det er et elementært imperativ for alle pedagoger å unngå eksessiv anvendelse av idiomer med xenotyp etymologi. I de fleste tilfeller eksisterer adekvate og relevante synonymer på norsk.
--
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