Arch Linux

jmsardev

Member

Registered: 2019-02-07

Posts: 12

[SOLVED] Last Systemd update broke my system

LVM2 with LUKS and Systemd-boot system. After upgrading to the recently updated packages system would ask for drive password but then would timeout trying to mount the root partition. Fixed it by using the LiveUSB and downgrading theses packages:

[2019-04-11 11:06] [ALPM] downgraded systemd-libs (241.93-1 -> 241.67-1)
[2019-04-11 11:06] [ALPM] downgraded device-mapper (2.02.184-2 -> 2.02.184-1)
[2019-04-11 11:06] [ALPM] downgraded lvm2 (2.02.184-2 -> 2.02.184-1)
[2019-04-11 11:06] [ALPM] downgraded systemd (241.93-1 -> 241.67-1)

and just in case I reinstalled the systemd-boot with bootctl --path=/boot install

And after reboot it's working perfectly.

PD: I'm not sure if it's just one of those packages or the whole, just went back on the last pacman transaction

Last edited by jmsardev (2019-04-12 13:24:15)

WorMzy

Forum Moderator

From: Scotland

Registered: 2010-06-16

Posts: 11,845

Website

Re: [SOLVED] Last Systemd update broke my system

Besides the package versions, this topic has very little useful information -- what was it actually failing on? Are you dropped to a shell after the timeout? Did the crypt device open successfully? Did the LVM scan run? Can you mount the partition manually?

FWIW, I installed Arch in a LVM on LUKS, with a systemd-based initrd setup yesterday evening, so I'll see if I can reproduce this when I get home.

---

Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD

Making lemonade from lemons since 2015.

jmsardev

Member

Registered: 2019-02-07

Posts: 12

Re: [SOLVED] Last Systemd update broke my system

Just saw that lvm2 and device-mapper got a new build, "2.02.184-3" so I updated and rebooted and it's working, so probably there was something messed up with "2.02.184-2"

WorMzy

Forum Moderator

From: Scotland

Registered: 2010-06-16

Posts: 11,845

Website

Re: [SOLVED] Last Systemd update broke my system

That seems to be the case: https://git.archlinux.org/svntogit/pack … 67c2fd7acb

Note that there's another build in testing that hopefully fixes the issue that -2 was meant to fix, while not breaking systemd initrds. You might want to test it and feed back.

In any case, please remember to mark your thread as solved.

https://wiki.archlinux.org/index.php/Co … ow_to_post

---

Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD

Making lemonade from lemons since 2015.

alpinist

Member

Registered: 2019-04-11

Posts: 1

Re: [SOLVED] Last Systemd update broke my system

Sorry - please ignore.

Last edited by alpinist (2019-04-11 14:51:22)

DebauchedSloth

Member

Registered: 2014-12-08

Posts: 29

Re: [SOLVED] Last Systemd update broke my system

I'm still seeing this with the latest lvm2 and devicemapper.  Booting with an old initrd (systemd 240) or reverting to systemd 241 both result in successful boots.

loqs

Member

Registered: 2014-03-06

Posts: 17,323

Re: [SOLVED] Last Systemd update broke my system

I'm still seeing this with the latest lvm2 and devicemapper.  Booting with an old initrd (systemd 240) or reverting to systemd 241 both result in successful boots.

Please open a new thread in the testing repo forum providing details of the issue at minimum the full package versions of systemd with and without the issue and the journal from a boot with and without the issue.