@dogandp, do you still see the bug?
The workaround that ceg has suggested, seems to be a standard method, when you
create a MD array after installation. This is because, by default md does not
update initramfs. So you need to do this manually.
A safer way is to first check the contents of /etc/
The workaround generates a mdadm.conf describing active arrays and
updates the initramfs for all kernels, so they will contain the new
file.
--
[->UUIDudev] new array not assembled correctly after reboot
https://bugs.launchpad.net/bugs/469574
You received this bug notification because you are a m
workaround:
# start your arrays manualy
# /usr/share/mdadm/mkconf force-generate /etc/mdadm/mdadm.conf
# update-initramfs -k all -u
--
[->UUIDudev] new array not assembled correctly after reboot
https://bugs.launchpad.net/bugs/469574
You received this bug notification because you are a member of
Your old arrays probably work because they got written to mdadm.conf
during the update.
** Summary changed:
- mdadm does not remember its actions correctly
+ [->UUIDudev] new array not assembled correctly after reboot
** Changed in: mdadm (Ubuntu)
Status: New => Confirmed
--
[->UUIDudev
