This is a bug with mdadm --incremental not doing hotplug, because it looks for permission to do so in mdadm.conf.
On hotplug systems mdadm.conf should not have contain any specific references, maybe it should explicity mention "any" like this:? DEVICE <any> HOMEHOST <any> ARRAY <any> This whole bussiness of locking down array assembly (homehost,ARRAY) may just be due to the historical (suboptimal) mdadm design to assamble raids going by major/minor numbers saved in the superblocks. Those should always be considered being dynamic(depreciated). Using --assemble --uuid mdadm takes a UUID and match this unique but same UUID on all member devices. Of course we should refrain from running arrays that are not complete (avoid leading them to desync by subsequent writes), unless we are required to recover data from a specific failed array and --run it manually or by a startup script. -- boot fails: mdadm not looking for UUIDs but hostname in superblocks https://bugs.launchpad.net/bugs/226484 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
