Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#23905 - [mdadm] udev based mkinitcpio install hook
Attached to Project:
Arch Linux
Opened by Dave Reisner (falconindy) - Saturday, 23 April 2011, 20:01 GMT
Last edited by Tobias Powalowski (tpowa) - Wednesday, 06 July 2011, 07:09 GMT
Opened by Dave Reisner (falconindy) - Saturday, 23 April 2011, 20:01 GMT
Last edited by Tobias Powalowski (tpowa) - Wednesday, 06 July 2011, 07:09 GMT
|
DetailsThe attached hook is a simplification of the current mdadm hookset, using the upstream udev rule to assemble RAID devices, rather than via /etc/mdadm.conf or by manual specification on the kernel cmdline. Since I realize that not one size fits all, I've named the hook mdadm_udev. I also suggest removing the udev rule from the current mdadm install hook, as its useless without the /sbin/mdadm binary. Including /sbin/mdadm in the current hook will actually cause /sbin/mdassemble will stop the already-assembled devices and reassemble them. So, I think it makes more sense to separate the two. Most users should find that the new hook is sufficient.
|
This task depends upon
mdadm_udev_install
Leaving the udev rule out causes no problems (for me at lest) so long as the root device is specified as /dev/mdx in GRUB. Doesn't GRUB install using device nodes on a fresh installation? In which case leaving out the udev rule should be the default.
Conversely the proposed mdadm_udev hook _requires_ that the root device is specified by-label or by-uuid in GRUB since the device nodes may change from boot to boot.
root=LABEL=rootdevice
root=UUID=3ad81e19-54fc-498a-9775-4effc9cc11c8
Is there a case where you wouldn't want this kind of identification?