ArcoLinux -D -B 19.5 iso's have been released

[INFO] Systemd update causes broken boot

First check the forums - Do not know where to put it then put it here
Post Reply
BloodWolf
Crewman
Posts: 13
Joined: Sun Mar 11, 2018 10:19 pm
Wales
[INFO] Systemd update causes broken boot

Post by BloodWolf » Wed Jan 09, 2019 9:11 pm

HI everyone.

Not sure if this is in the correct section so if an admin/mod could tell me where to put it that would be great.

This is just a quick heads up to say that after the latest update of arcolinux, systemd is also update, this has broken all 4 of my real world arcolinux installs and multiple virtual machine installs.

After the installation of systemd version 240 I get a message on shutdown saying a stop job is running for user pid 1000 and it takes around 2 minutes. On reboot it informs me that hibernation device cannot be found and forces me into a root shell without any keyboard availability.

A quick fix for this, if you have already updated your systemd and are experiencing this is to boot an arcolinux iso and chroot into your broken system then downgrade the systemd package to the last working version.

Here is the pacman command to do just that. pacman -U https://archive.archlinux.org/packages/ ... pkg.tar.xz

This will downgrade systemd to the version specified in the arch linux archive link. I hope this helps everyone.

User avatar
erikdubois
Captain
Posts: 2054
Joined: Tue Nov 07, 2017 3:45 pm
Location: Belgium
Contact:
Belgium
Re: [OPEN] Systemd update causes broken boot

Post by erikdubois » Wed Jan 09, 2019 10:45 pm

I have seen the message on many of SSD's after the update a countdown till 2 minutes if you shutdown the computer after this huge update.

I have hard shutdown my computer and I have let it count down.

In both cases my system rebooted fine.

I still have like a 20 SSD's to go when I will get this message. I am not to bothered by it.

This seems not be in your case.

I never hibernate or have an extra harddrive and just one SSD.

Might have something to do with your hardware or how many harddisks you have.

If you are dualbooting (which do not have), might be even other factors in play.

Downgrading sounds like a solution for you and maybe also for others.

Thanks for sharing.

Like to hear your thoughts on this.

How did you set up your system?
Learn, have fun and enjoy.
But first use the power of the Arch Wiki
use the tutorials on https://www.youtube.com/erikdubois
then use the power of google
then use the power of our moderators.

User avatar
erikdubois
Captain
Posts: 2054
Joined: Tue Nov 07, 2017 3:45 pm
Location: Belgium
Contact:
Belgium
Re: [OPEN] Systemd update causes broken boot

Post by erikdubois » Wed Jan 09, 2019 11:09 pm

I think this comes close to what you describe.

https://bugs.archlinux.org/task/61324?p ... ng=systemd
which leads to boot into emergency console
Suggest to downgrade to 239 till the patch not get upstream.
Learn, have fun and enjoy.
But first use the power of the Arch Wiki
use the tutorials on https://www.youtube.com/erikdubois
then use the power of google
then use the power of our moderators.

BloodWolf
Crewman
Posts: 13
Joined: Sun Mar 11, 2018 10:19 pm
Wales
Re: [OPEN] Systemd update causes broken boot

Post by BloodWolf » Thu Jan 10, 2019 12:12 am

erikdubois wrote:
Wed Jan 09, 2019 11:09 pm
I think this comes close to what you describe.

https://bugs.archlinux.org/task/61324?p ... ng=systemd
which leads to boot into emergency console
Suggest to downgrade to 239 till the patch not get upstream.
Yeah that's what I was looking at when I was trying to figure out what went wrong. Running mkinitcpio done nothing though.

As for how my system is set up. I have one 6TB drive with Arcolinux on it and one 6TB drive with Win10
on it so as to avoid windows wrecking my bootloader when they force an update on me. There are two more 6TB hard drives in here as well. One for backups and the other for media storage. No operating systems on them.

I do not hibernate or sleep my drives.

The same things happens on both my laptops which only have Arcolinux installed as well as with all of the virtual machines in vmware and virtualbox on both windows and Arcolinux hosts.

The only way I can reproduce this bug is by updating systemd to 240 and then downgrading again to fix it.


Post Reply

Return to “General Questions”