I tried it, rebooted once more and created the raidset using Intel OROM (CTRL+I).
Afterwards there are still two seperate disks visible and they cannot be assembled using mdadm.
After recreating container and array the array it stays like this:
# cat /proc/mdstat
Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
md1 : active (read-only) raid1 sdd[1] sdc[0]
1925185536 blocks super external:/md0/0 [2/2] [UU] resync=PENDING
md0 : inactive sdd[1](S) sdc[0](S)
2210 blocks super external:imsm
unused devices: <none>
Trying to write to the generated /dev/md1 using sfdisk and parted leads to the reported kernel bug.
I tried it, rebooted once more and created the raidset using Intel OROM (CTRL+I).
Afterwards there are still two seperate disks visible and they cannot be assembled using mdadm.
After recreating container and array the array it stays like this:
resync= PENDING
# cat /proc/mdstat
Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
md1 : active (read-only) raid1 sdd[1] sdc[0]
1925185536 blocks super external:/md0/0 [2/2] [UU]
md0 : inactive sdd[1](S) sdc[0](S)
2210 blocks super external:imsm
unused devices: <none>
Trying to write to the generated /dev/md1 using sfdisk and parted leads to the reported kernel bug.