I do not think this is a duplicate, even though this bug is marked as such currently. As soon as I added a proper entry in /etc/mdadm/mdadm.conf for my /dev/md2 device and rebooted, everything came back up as expected (after upgrading to jaunty). This is clearly not related to a udev rule problem.
I do not think this is a duplicate, even though this bug is marked as such currently. As soon as I added a proper entry in /etc/mdadm/ mdadm.conf for my /dev/md2 device and rebooted, everything came back up as expected (after upgrading to jaunty). This is clearly not related to a udev rule problem.