Just an update for everyone interested. I solved my issue by one(or multiple) of the following steps. Failing my sdc disk, pasting new superblock, writing new boot sector, partitioning again and adding the disk back. So I am still not sure what caused my problem except I am fairly sure that my 2nd disk had a previous superblock that confused things. Disk was used in another system as part of a md array. What showed me the issue was "mdadm -Es". It showed me two arrays that can be assembled.
Sorry I can not be more helpful except you should run mdadm -Es early on and avoid a lot of tail chasing. If you are seeing an array you did not expect that will cause the problems with "--incremental" when booting up. Before I fixed the issue I was seeing this: root@jamaica:~# mdadm --examine --scan ARRAY /dev/md0 UUID=5551e210:6dbc9e1b:2aa365fc:c3f97a4c ARRAY /dev/md0 UUID=4795c86a:79111507:dbd3f904:98c17f24 After: root@jamaica:~# mdadm --examine --scan ARRAY /dev/md0 UUID=4795c86a:79111507:dbd3f904:98c17f24 Also worth noting is my superblock is 0.90. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/541058 Title: [->UUIDudev] mdadm fails to automatically assemble raid during boot (without mdadm.conf) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/541058/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
