After installation with architect on a system that uses LVM, I started to see these errors. > mkdir: can't create directory '/run/lvm': File exists > Failed to acquire lock on /run/lvmetad.pid. Already running? The cause as described by [gabe.rust](https://forum.manjaro.org/u/gabe.rust) in [this forum post](https://forum.manjaro.org/t/bug-resolution-installing-manjaro-architect-with-lvm-on-luks-produces-errors-that-prevent-manjaro-from-booting/104399) was multiple `lvm2` entries being added to `HOOKS=` in `/etc/mkinicpio.conf`. Example: `HOOKS=(base udev autodetect modconf block lvm2 lvm2 filesystems keyboard)` The cause seems to be `sed` statements found here [util-desktop.sh#L389-398](https://gitlab.manjaro.org/applications/manjaro-architect/blob/master/lib/util-desktop.sh#L389-398) and here [util-base.sh#L322-331](https://gitlab.manjaro.org/applications/manjaro-architect/blob/master/lib/util-base.sh#L322-331). When the aforementioned code is run after [util-desktop.sh#L435-437](https://gitlab.manjaro.org/applications/manjaro-architect/blob/master/lib/util-desktop.sh#L435-437) and [util-base.sh#L368-370](https://gitlab.manjaro.org/applications/manjaro-architect/blob/master/lib/util-base.sh#L368-370), duplicate modules will be added. https://gitlab.manjaro.org/applications/manjaro-architect/merge_requests/253 should resolve the duplicates by updating the `sed` statements to only insert if the module being added isn't already present in the line.