FS#55090 - [util-linux] Boot failure (kernel panic) after upgrade to util-linux-2.30.1-2

Attached to Project: Arch Linux
Opened by Paweł Chwała (cepe) - Wednesday, 09 August 2017, 19:40 GMT
Last edited by Eli Schwartz (eschwartz) - Friday, 11 August 2017, 21:07 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To No-one
Architecture All
Severity Critical
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:
After upgrading util-linux from version 2.29.2-2 to 2.30.1-2 I am experiencing kernel panic during the boot (https://imgur.com/a/sULZS). It occurs after encrypt hook is executed and password provided.

Downgrade of util-linux to 2.29.2-2 version and running:
$ sudo mkinitcpio -p linux
solves the issue.


Additional info:
* I have all (with exception for util-linux) packages up to date

* my disk setup:
cepe@taurus ~ % lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 465.8G 0 disk
sdc 8:32 0 931.5G 0 disk
└─media 254:1 0 931.5G 0 crypt /mnt/media
sdd 8:48 0 111.8G 0 disk
├─sdd1 8:49 0 128M 0 part /boot
└─sdd2 8:50 0 111.7G 0 part
└─cryptedroot 254:0 0 111.7G 0 crypt /


* HOOKS in mkinitcpio:
HOOKS="base udev autodetect modconf keyboard block encrypt filesystems fsck"

* one entry from crypttab:
media UUID=78de2c36-4d5e-4a0b-91d9-7eec4174c622 /luks_keys/media.key nofail

* syslinux entry:
LABEL arch
MENU LABEL Arch Linux
LINUX ../vmlinuz-linux
APPEND root=/dev/mapper/cryptedroot cryptdevice=UUID=2158912b-29d9-4195-84b9-ef3ed353a5a5:cryptedroot:allow-discards -rw
INITRD ../initramfs-linux.img


Steps to reproduce:

* upgrade util-linux:
$ pacman -S util-linux

* run mkinitcpio:
$ mkinitcpio -p linux

* reboot:
$ reboot
This task depends upon

Closed by  Eli Schwartz (eschwartz)
Friday, 11 August 2017, 21:07 GMT
Reason for closing:  Not a bug
Additional comments about closing:  user error
Comment by Alexander Schnaidt (Namarrgon) - Wednesday, 09 August 2017, 23:10 GMT
When you update your system again are both packages, util-linux and libutil-linux, at the same version?
Comment by Paweł Chwała (cepe) - Thursday, 10 August 2017, 04:12 GMT
@ Alexander Schnaidt (Namarrgon)

After upgrade (in case of kernel panic) both util-linux and libutil-linux are in 2.30.1-2 version. Now (when system is operating) I have following versions installed:

cepe@taurus ~ % pacman -Qi libutil-linux
Name : libutil-linux
Version : 2.30.1-2
(...)

cepe@taurus ~ % sudo pacman -S libutil-linux
warning: libutil-linux-2.30.1-2 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...

Packages (1) libutil-linux-2.30.1-2

Total Installed Size: 1.21 MiB
Net Upgrade Size: 0.00 MiB

:: Proceed with installation? [Y/n] n


cepe@taurus ~ % pacman -Qi util-linux
Name : util-linux
Version : 2.29.2-2
(...)

cepe@taurus ~ % sudo pacman -S util-linux :(
resolving dependencies...
looking for conflicting packages...

Packages (1) util-linux-2.30.1-2

Total Installed Size: 10.84 MiB
Net Upgrade Size: 1.00 MiB

:: Proceed with installation? [Y/n] n



Versions are not aligned because I wanted to isolate the problem yesterday - I was trying to upgrade & downgrade a different combinations of packages in order to find one which causes the problem.
Comment by Alexander Schnaidt (Namarrgon) - Friday, 11 August 2017, 12:25 GMT
Update your system again, boot with "break=premount" so that you get dropped to the shell in the initramfs, from there unlock your dmcrypt volume manually and try to mount your /-partition to /new_root. If that works 'exit' the shell and see if the boot process succeeds.
Comment by Paweł Chwała (cepe) - Friday, 11 August 2017, 20:17 GMT
@Alexander Schnaidt (Namarrgon):

I did it. Boot process stopped. I had an opportunity to mount my unlocked device (it was already unlocked, under /dev/mapper/cryptedroot). After mounting it under /new_root I was able to list this directory. I hit exit and saw the same kernel panic as before.
Comment by Paweł Chwała (cepe) - Friday, 11 August 2017, 20:46 GMT
OMG. I had typo in syslinux.cfg ... It became visible after upgrade of utli-linux ...

I had:
APPEND root=/dev/mapper/cryptedroot cryptdevice=UUID=2158912b-29d9-4195-84b9-ef3ed353a5a5:cryptedroot:allow-discards -rw

Shuld be:
APPEND root=/dev/mapper/cryptedroot cryptdevice=UUID=2158912b-29d9-4195-84b9-ef3ed353a5a5:cryptedroot:allow-discards rw

grr...

Sorry for making this issue. Closing ...

Loading...