FS#49071 - [mdadm] mdadm mkinitcpio hook -- md devices need to build before LVM2 hook triggers
Attached to Project:
Arch Linux
Opened by Volker Schmidt (connaisseur) - Sunday, 24 April 2016, 17:09 GMT
Last edited by Giancarlo Razzolini (grazzolini) - Thursday, 21 March 2019, 02:06 GMT
Opened by Volker Schmidt (connaisseur) - Sunday, 24 April 2016, 17:09 GMT
Last edited by Giancarlo Razzolini (grazzolini) - Thursday, 21 March 2019, 02:06 GMT
|
Details
Description:
When a md devices holds LVM2 volume groups, the LVM2 hook tries to enable all VGs with a run_earlyhook() function. This currently fails, because mdhook has only the run_hook() function. Therefore the order in the hooks line of /etc/minitcpio.conf isn't correctly hit! My HOOKS line looks like this: HOOKS="base udev autodetect modconf block mdadm lvm2 filesystems keyboard fsck shutdown" FIX: change run_hook() to run_earlyhook() --> rebuild initrd, boot, works! See suggested patch file (attached). Additional info: * mdadm 3.4-1 Steps to reproduce: Build a md-device (e.g. raid1), have a lvm2 VG on it. Then make logical volumes with Filesystems in it. Have a correct UUID-based line in /etc/fstab. This system will hang booting, throwing you into emergency shell. You'll find inactive VGs and inactive logical devices. Check with vgscan && lvscan. |
This task depends upon
Closed by Giancarlo Razzolini (grazzolini)
Thursday, 21 March 2019, 02:06 GMT
Reason for closing: Works for me
Thursday, 21 March 2019, 02:06 GMT
Reason for closing: Works for me
But with mdadm_udev hook it was not that easy to track down.