You are not logged in.

#1 2014-06-07 23:00:16

flecha
Member
Registered: 2009-01-16
Posts: 26

[SOLVED] Updating systemd sometimes causes total freeze and unbootable

Hello,

It's the second time this happens...

Today, when updating systemd-213-6-x86_64, systemd-sysvcompat-213-6-x86_64 and libsystemd-213-6-x86_64, my notebook freezed. Couldn't go from X to ttys, move mouse or type anything. After a few minutes I powered off.
On boot, after entering my pass (I use dm-crypt for the entire Arch partition), it showed some lines about fixing the journal and then droped to a console, saying I had no init script.
Had to use a live pen to reinstall systemd and libsystemd. Some lib files were corrupted (zero size for file), and some systemd files had disappeard.

The first time it happend, these files got corrupted:

libgudev-1.0.so.0.2.0
libsystemd-daemon.so.0.0.12
libsystemd-id128.so.0.0.28
libsystemd-journal.so.0.11.5
libsystemd-login.so.0.9.3
libsystemd.so.0.2.0
libudev.so.1.4.1
(besides some libcups*)

If I remember, I was updating to systemd-213-4-x86_64.

Today I only took note after reinstalling systemd and libsystemd, but after this, these files were still corrupted:

ldconfig: File /usr/lib/libhunspell-1.3.so.0 is empty, not checked.
ldconfig: File /usr/lib/libfontembed.so is empty, not checked.
ldconfig: File /usr/lib/libhunspell-1.3.so is empty, not checked.
ldconfig: File /usr/lib/libhunspell.so is empty, not checked.
ldconfig: File /usr/lib/libhpmud.so.0.0.6 is empty, not checked.
ldconfig: File /usr/lib/libfontembed.so.1 is empty, not checked.
ldconfig: File /usr/lib/libhpmud.so is empty, not checked.
ldconfig: File /usr/lib/libhpip.so is empty, not checked.
ldconfig: File /usr/lib/libhpip.so.0.0.1 is empty, not checked.
ldconfig: File /usr/lib/libcupsfilters.so is empty, not checked.
ldconfig: File /usr/lib/libhunspell-1.3.so.0.0.0 is empty, not checked.
ldconfig: File /usr/lib/libcupsfilters.so.1.0.0 is empty, not checked.
ldconfig: File /usr/lib/libhpip.so.0 is empty, not checked.
ldconfig: File /usr/lib/libfontembed.so.1.0.0 is empty, not checked.
ldconfig: File /usr/lib/libhpmud.so.0 is empty, not checked.
ldconfig: File /usr/lib/libcupsfilters.so.1 is empty, not checked.

This problem started only after I encrypted my partition, but I am not sure it's related.
I use pm-hibernate to be able to "secure suspend".
The systemd-213-5-x86_64 update caused no error.
Maybe it only happens if I am running after a resume and not in a fresh boot?


Thanks for the attention and for any help.

EDIT: Added code tags attending WonderWoofy's request.
EDIT2: I am using EXT4.

Last edited by flecha (2014-06-11 13:05:51)

Offline

#2 2014-06-07 23:49:47

WonderWoofy
Member
From: Los Gatos, CA
Registered: 2012-05-19
Posts: 8,412

Re: [SOLVED] Updating systemd sometimes causes total freeze and unbootable

Please use code tags

Offline

#3 2014-06-10 13:53:20

flecha
Member
Registered: 2009-01-16
Posts: 26

Re: [SOLVED] Updating systemd sometimes causes total freeze and unbootable

Yesterday had the same problem again. To do the test I did a pm-hibernate, resumed and then updated:

[2014-06-09 21:22] [PACMAN] Running 'pacman --color auto -S -u'
[2014-06-09 21:22] [PACMAN] starting full system upgrade
[2014-06-09 21:22] [ALPM-SCRIPTLET] >>> Updating module dependencies. Please wait ...
[2014-06-09 21:22] [ALPM-SCRIPTLET] >>> Generating initial ramdisk, using mkinitcpio.  Please wait...
[2014-06-09 21:22] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
[2014-06-09 21:22] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
[2014-06-09 21:22] [ALPM-SCRIPTLET] ==> Starting build: 3.15.0-1-ARCH
[2014-06-09 21:22] [ALPM-SCRIPTLET]   -> Running build hook: [base]
[2014-06-09 21:22] [ALPM-SCRIPTLET]   -> Running build hook: [keyboard]
[2014-06-09 21:22] [ALPM-SCRIPTLET]   -> Running build hook: [udev]
[2014-06-09 21:22] [ALPM-SCRIPTLET]   -> Running build hook: [autodetect]
[2014-06-09 21:22] [ALPM-SCRIPTLET]   -> Running build hook: [modconf]
[2014-06-09 21:22] [ALPM-SCRIPTLET]   -> Running build hook: [block]
[2014-06-09 21:22] [ALPM-SCRIPTLET]   -> Running build hook: [keymap]
[2014-06-09 21:22] [ALPM-SCRIPTLET]   -> Running build hook: [encrypt]
[2014-06-09 21:22] [ALPM-SCRIPTLET]   -> Running build hook: [resume]
[2014-06-09 21:22] [ALPM-SCRIPTLET]   -> Running build hook: [filesystems]
[2014-06-09 21:22] [ALPM-SCRIPTLET]   -> Running build hook: [fsck]
[2014-06-09 21:22] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2014-06-09 21:22] [ALPM-SCRIPTLET] ==> Creating gzip initcpio image: /boot/initramfs-linux.img
[2014-06-09 21:23] [ALPM-SCRIPTLET] ==> Image generation successful
[2014-06-09 21:23] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
[2014-06-09 21:23] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
[2014-06-09 21:23] [ALPM-SCRIPTLET] ==> Starting build: 3.15.0-1-ARCH
[2014-06-09 21:23] [ALPM-SCRIPTLET]   -> Running build hook: [base]
[2014-06-09 21:23] [ALPM-SCRIPTLET]   -> Running build hook: [keyboard]
[2014-06-09 21:23] [ALPM-SCRIPTLET]   -> Running build hook: [udev]
[2014-06-09 21:23] [ALPM-SCRIPTLET]   -> Running build hook: [modconf]
[2014-06-09 21:23] [ALPM-SCRIPTLET]   -> Running build hook: [block]
[2014-06-09 21:23] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: aic94xx
[2014-06-09 21:23] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: smsmdtv
[2014-06-09 21:23] [ALPM-SCRIPTLET]   -> Running build hook: [keymap]
[2014-06-09 21:23] [ALPM-SCRIPTLET]   -> Running build hook: [encrypt]
[2014-06-09 21:23] [ALPM-SCRIPTLET]   -> Running build hook: [resume]
[2014-06-09 21:23] [ALPM-SCRIPTLET]   -> Running build hook: [filesystems]
[2014-06-09 21:23] [ALPM-SCRIPTLET]   -> Running build hook: [fsck]
[2014-06-09 21:23] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2014-06-09 21:23] [ALPM-SCRIPTLET] ==> Creating gzip initcpio image: /boot/initramfs-linux-fallback.img
[2014-06-09 21:23] [ALPM-SCRIPTLET] ==> Image generation successful
[2014-06-09 21:23] [PACMAN] upgraded linux (3.14.6-1 -> 3.15-1)
[2014-06-09 21:23] [PACMAN] upgraded bbswitch (0.8-8 -> 0.8-10)
[2014-06-09 21:23] [PACMAN] upgraded x265 (1.0-1 -> 1.1-1)
[2014-06-09 21:23] [PACMAN] upgraded ffmpeg (1:2.2.3-1 -> 1:2.2.3-2)
[2014-06-09 21:23] [PACMAN] upgraded libsystemd (213-6 -> 213-8)
[2014-06-09 21:23] [PACMAN] upgraded lirc-utils (1:0.9.0-71 -> 1:0.9.0-72)
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@

Freezed when updating systemd, 213-6 -> 213-8. Now I am sure.
This time got these files with size 0 in /usr/lib:

./libavdevice.so.55.10.100
./libavfilter.so.4.2.100
./libavcodec.so.55.52.102
./libswresample.so.0.18.100
./libpostproc.so.52.3.100
./libswscale.so.2.5.102
./libavformat.so.55.33.100
./syslinux/bios/liblua.c32
./syslinux/bios/libcom32.c32
./syslinux/bios/libgpl.c32
./syslinux/bios/libutil.c32
./syslinux/bios/libmenu.c32
./syslinux/efi32/liblua.c32
./syslinux/efi32/libcom32.c32
./syslinux/efi32/libgpl.c32
./syslinux/efi32/libutil.c32
./syslinux/efi32/libmenu.c32
./syslinux/efi64/liblua.c32
./syslinux/efi64/libcom32.c32
./syslinux/efi64/libgpl.c32
./syslinux/efi64/libutil.c32
./syslinux/efi64/libmenu.c32
./libavresample.so.1.2.0
./liblirc_client.so.0.2.1
./perl5/core_perl/CORE/libperl.so
./perl5/core_perl/lib.pm
./libx265.so.1.1
./libqpdf.so.13.1.2
./libavutil.so.52.66.100
./pkgconfig/libswresample.pc
./pkgconfig/libavutil.pc
./pkgconfig/libavformat.pc
./pkgconfig/libqpdf.pc
./pkgconfig/libavcodec.pc
./pkgconfig/libavresample.pc
./pkgconfig/libpostproc.pc
./pkgconfig/libavfilter.pc
./pkgconfig/libswscale.pc
./pkgconfig/libavdevice.pc

Had to reinstall the kernel too.
Apparently the files corrupted depends on what was being updated.

Offline

#4 2014-06-10 15:29:16

WonderWoofy
Member
From: Los Gatos, CA
Registered: 2012-05-19
Posts: 8,412

Re: [SOLVED] Updating systemd sometimes causes total freeze and unbootable

Are you suspending or hibernating?  Those are two very different things.  Updating the kernel and then hibernating is not a safe thing to do whatsoever and it is unsurprising that you are having issues there.

Offline

#5 2014-06-10 16:22:51

flecha
Member
Registered: 2009-01-16
Posts: 26

Re: [SOLVED] Updating systemd sometimes causes total freeze and unbootable

I am using pm-hibernate, so it should be hibernating.
But I am not exactly "updating the kernel and then hibernating", I am going the other way around, hibernating and then updating systemd.
Seems it's a problem too.
Didn't know it could cause this type of corruption. Shouldn't there be a notice here about this?
https://wiki.archlinux.org/index.php/Pm-utils

Offline

#6 2014-06-10 21:24:36

WonderWoofy
Member
From: Los Gatos, CA
Registered: 2012-05-19
Posts: 8,412

Re: [SOLVED] Updating systemd sometimes causes total freeze and unbootable

I honestly don't really know what to tell you if the issue is with hibernation.  I haven't used hibernation for a couple years now, and have always found it to be a bit flimsy.  Hopefully someone else might be able to jump in here and give you a hand.  Still I really really don't think you should be using pm-utils for suspending or hibernating.

Offline

#7 2014-06-10 21:41:28

flecha
Member
Registered: 2009-01-16
Posts: 26

Re: [SOLVED] Updating systemd sometimes causes total freeze and unbootable

Thanks for the advice... any other tool you would recomend for hibernation?
I need hibernation because it's the only way I know to lock the file system, besides power off, but that's not always convinent when using a notebook.

Offline

#8 2014-06-10 22:07:17

WonderWoofy
Member
From: Los Gatos, CA
Registered: 2012-05-19
Posts: 8,412

Re: [SOLVED] Updating systemd sometimes causes total freeze and unbootable

systemctl

Offline

#9 2014-06-11 02:40:48

cfr
Member
From: Cymru
Registered: 2011-11-27
Posts: 6,000

Re: [SOLVED] Updating systemd sometimes causes total freeze and unbootable

While I agree, I don't think hibernating and then updating should cause this kind of corruption. I was quite surprised that pm-utils is still in the repos. pm-utils keeps logs when it suspends/hibernates, if I remember correctly, so I think you should be looking there and for problems showing up in journalctl after hibernation but before updating. I have only ever hibernated a couple of times just for testing. I suspend all the time but otherwise I'd just power off. (Hibernation didn't seem much quicker than rebooting, to be honest, and that is the main reason people prefer it.)

See https://wiki.archlinux.org/index.php/Po … th_systemd. Note that the wiki page you linked to on pm-utils has large warning notices at the top because it is not really current with updates and changes to the system, especially systemd.

Last edited by cfr (2014-06-11 02:43:00)


How To Ask Questions The Smart Way | Help Vampires

Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Corporation Wireless 8265 / 8275 | US keyboard with Euro | 512G NVMe INTEL SSDPEKKF512G7L

Offline

#10 2014-06-11 05:02:25

WonderWoofy
Member
From: Los Gatos, CA
Registered: 2012-05-19
Posts: 8,412

Re: [SOLVED] Updating systemd sometimes causes total freeze and unbootable

cfr wrote:

While I agree, I don't think hibernating and then updating should cause this kind of corruption.

Yeah I was under the inital impression that the OP had potentially updated before hibernating.  So if that had been the case and the kernel was upgraded, it would have explained the instability and potentially the corruption.  Alas, it doesn't sound as though that was the case.

Offline

#11 2014-06-11 13:03:08

flecha
Member
Registered: 2009-01-16
Posts: 26

Re: [SOLVED] Updating systemd sometimes causes total freeze and unbootable

WonderWoofy wrote:

systemctl

Great! Didn't know about that. Tested here and worked.
I just don't know if it won't crash when updating systemd too.

cfr wrote:

Note that the wiki page you linked to on pm-utils has large warning notices at the top because it is not really current with updates and changes to the system, especially systemd.

One thing is to say that the module isn't updated, other is to corrupt and let your system unbootable.
I am talking about a BIG RED warning.

I will consider the thread as solved with this lesson:
- Don't use pm-utils
- Use systemctl hibernate
And:
- Don't update libsystemd, systemd or linux and than hibernate (or the other way around).

EDIT: Edited the wiki: https://wiki.archlinux.org/index.php/Pm-utils

Last edited by flecha (2014-06-11 13:33:08)

Offline

Board footer

Powered by FluxBB