On Wednesday 2015-01-07 10:49, Felix Miata wrote:
# /etc/mdadm.conf DEVICE partitions ARRAY /dev/md0 level=raid1 UUID=7bb80bd1:7190763b:e67858c2:e1709118 ARRAY /dev/md1 level=raid1 UUID=30ea461c:9b926cd0:51ce856f:76aa6ff4 ARRAY /dev/md2 level=raid1 UUID=7e5708a2:0cf651d9:a76e1f13:a4a36c19 ARRAY /dev/md3 level=raid1 UUID=1af29bc5:ec2c3760:02daa1f0:5c28277a ARRAY /dev/md4 level=raid1 UUID=805ab730:c7ff1970:3aece583:fea16d3d ARRAY /dev/md5 level=raid1 UUID=fc3787e2:bc83c66c:8afe6288:1c75f7f0 ARRAY /dev/md6 level=raid1 UUID=cda6eba4:2d28ed19:bc1316ff:d7da2e59 ARRAY /dev/md7 level=raid1 UUID=f7939330:26ee7348:064baf79:480175e0
lsblk output, please.
Doesn't the existant partition type 0xFD provide e2fs a useful clue, or is maybe that what blinds it to what is actually present?
No. The only place where 0xfd partition type is (was) used is kernel-level Linux MD autodetection.
"Was", as in kernel no long autodetects md devices?
Old devices continue to be recognized, but with all the problems that can arise, contemoprary systems no longer recommend nor use kernel-level autodetection. This is now properly done in userspace instead. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org