Boot was still reporting systemd 217 startup after upgrade to 218

IMBJR · 2014-12-18 21:02:49

It was until i did:

sudo mkinitcpio -p linux

And then all was well. I noticed before and after this, the journal stated that systemd 218 had actually started.

Is it usual to have to mkinitcpio after a systemd upgrade?

WorMzy · 2014-12-18 21:06:54

You don't need to regenerate your initrd, unless you want to have the latest and greatest binaries in it.

The only time you have to regenerate your initrd is when your kernel is updated, which is why the kernel's install scriptlet does this for you.

dice · 2014-12-18 22:28:43

I just had the systemd update to 218-1 but on boot it says "starting version 217".
Is systemd just showing the wrong version on boot or is something wrong with my system? How can I check systemd version?
According to man systemd you could do

systemd --version

but command systemd does not exist on my system.

Thanks

Last edited by dice (2014-12-18 22:55:03)

jasonwryan · 2014-12-18 22:36:52

Did you regenerate your intird?

Head_on_a_Stick · 2014-12-18 22:45:01

I too have just upgraded and have a 217 message on boot.

`pacman -Q systemd` shows:

systemd 218-1

Also, `journalctl|grep systemd` shows:

Dec 18 22:37:52 Arch systemd-udevd[181]: starting version 218

So the message at boot is wrong.
Maybe a bug?

dice · 2014-12-18 22:54:40

journalctl showed the correct version for me too.
After regeneration of initramfs the correct version also shows up on boot.

It would be nice if there was a message about this during update. I can't recall I had to run mkinitcpio after systemd upgrades before, though.

jasonwryan · 2014-12-18 23:05:21

It is really just cosmetic. I'd be happier if the entire thing was removed, myself...

jasonwryan · 2014-12-18 23:06:17

Merging...

jaco · 2014-12-19 00:36:03

dice wrote:

According to man systemd you could do
systemd --version 
but command systemd does not exist on my system.

init --version

or

systemctl --version

are working

Leonid.I · 2014-12-19 01:42:17

WorMzy wrote:

You don't need to regenerate your initrd, unless you want to have the latest and greatest binaries in it.
The only time you have to regenerate your initrd is when your kernel is updated, which is why the kernel's install scriptlet does this for you.

Actually, you should.

Not because of systemd update but because systemd includes udev, and that is run from your initramfs (note, systemd is not init in initramfs). If a systemd upgrade (e.g. 217 -> 218) didn't involve lots of udev changes, then it's probably OK to have udev 217 in intramfs and udev 218 on the rootfs. But otherwise, I'd still regenerate the initramfs.

Lone_Wolf · 2014-12-19 13:55:59

This has always been happening since archlinux started using an initramfs with udev (in 2008 maybe ?) .

https://wiki.archlinux.org/index.php/Boot

The udev in the initramfs created by mkinitcpio is only used until early userspace (maybe not even until the final stage of that) , then the system switches to the udev version in the running system.

I'm a long time forum user, but can only vaguely remember a few cases where an older udev in the initramfs caused problems.

ANOKNUSA · 2014-12-19 14:57:39

As I understand it the udev bits in the initramfs just quickly find block devices and create nodes for them as init gets executed. From my experience the actual system udev gets loaded at or after the half-way point in the boot process. Kernel and systemd releases at least seem (inadvertently) timed so that a kernel update will rebuild the initramfs automatically before the udev bits in initramfs and systemd-distributed udev wind up more than one version apart. I haven't really looked into it, but I'd guess the time gap between kernel and systemd releases is likely to shrink as kdbus matures and systemd becomes dependent on it.

Leonid.I · 2014-12-19 21:30:46

Lone_Wolf wrote:

This has always been happening since archlinux started using an initramfs with udev (in 2008 maybe ?) .
https://wiki.archlinux.org/index.php/Boot
The udev in the initramfs created by mkinitcpio is only used until early userspace (maybe not even until the final stage of that) , then the system switches to the udev version in the running system.
I'm a long time forum user, but can only vaguely remember a few cases where an older udev in the initramfs caused problems.

For example, https://lists.archlinux.org/pipermail/a … 19457.html . Systemd upstream is under no obligation to maintain backward compatibility. So, different udev versions may use e.g. incompatible databases. Granted this doesn't happen often, but to be 100% sure you need to inspect a systemd changelog..

Arch Linux

#1 2014-12-18 21:02:49

Boot was still reporting systemd 217 startup after upgrade to 218

#2 2014-12-18 21:06:54

Re: Boot was still reporting systemd 217 startup after upgrade to 218

#3 2014-12-18 22:28:43

Re: Boot was still reporting systemd 217 startup after upgrade to 218

#4 2014-12-18 22:36:52

Re: Boot was still reporting systemd 217 startup after upgrade to 218

#5 2014-12-18 22:45:01

Re: Boot was still reporting systemd 217 startup after upgrade to 218

#6 2014-12-18 22:54:40

Re: Boot was still reporting systemd 217 startup after upgrade to 218

#7 2014-12-18 23:05:21

Re: Boot was still reporting systemd 217 startup after upgrade to 218

#8 2014-12-18 23:06:17

Re: Boot was still reporting systemd 217 startup after upgrade to 218

#9 2014-12-19 00:36:03

Re: Boot was still reporting systemd 217 startup after upgrade to 218

#10 2014-12-19 01:42:17

Re: Boot was still reporting systemd 217 startup after upgrade to 218

#11 2014-12-19 13:55:59

Re: Boot was still reporting systemd 217 startup after upgrade to 218

#12 2014-12-19 14:57:39

Re: Boot was still reporting systemd 217 startup after upgrade to 218

#13 2014-12-19 21:30:46

Re: Boot was still reporting systemd 217 startup after upgrade to 218

Board footer