https://bugzilla.suse.com/show_bug.cgi?id=1175850 https://bugzilla.suse.com/show_bug.cgi?id=1175850#c19 --- Comment #19 from Fabian Vogt <fvogt@suse.com> --- (In reply to Franck Bui from comment #18)

(In reply to Fabian Vogt from comment #17)

...

It's about shutdown. udevd needs /etc and /etc needs /var. Somehow unmounting /var triggers udev to start: [ OK ] Stopped Rule-based Manager for Device Events and Files. ... [ OK ] Unmounted /etc. ... Unmounting /var...

Again both /etc and /var are setup in initrd so both shouldn't be unmounted by PID1 during shutdown. If 'x-initrd.mount' option is specified for both, this sequence should not happen.

So is that a systemd bug?

...

I'm not getting any log output from that though:

With "debug console=ttyS0" options in the kernel command line, I can see the logs:

For unlocking through the usb keyboard I had to specify both consoles, so it probably wrote to the wrong one. I switched over to serial over socat and I get this: [ 67.699353] systemd-shutdown[1]: Sending SIGTERM to remaining processes... [ 67.706055] systemd-shutdown[1]: Sending SIGKILL to remaining processes... [ 67.707994] systemd-shutdown[1]: Process 157 (haveged) has been marked to be excluded from killing. It is running from the root file system, and thus likely to block re-mounting of the root file system to read-only. Please consider moving it into an initrd file system instead. [ 67.712326] systemd-shutdown[1]: Unmounting file systems. [ 67.713663] systemd-shutdown[1]: Successfully forked off '(sd-remount)' as PID 2369. [ 67.714012] [2369]: Remounting '/' read-only in with options 'space_cache,subvolid=267,subvol=/@/.snapshots/1/snapshot'. [ 67.717475] BTRFS info (device dm-1): disk space caching is enabled [ 67.777923] systemd-shutdown[1]: All filesystems unmounted. [ 67.779707] systemd-shutdown[1]: Deactivating swaps. [ 67.781239] systemd-shutdown[1]: All swaps deactivated. [ 67.782804] systemd-shutdown[1]: Detaching loop devices. [ 67.784375] systemd-shutdown[1]: sd-device-enumerator: Scan all dirs [ 67.786272] systemd-shutdown[1]: sd-device-enumerator: Scanning /sys/bus [ 67.788220] systemd-shutdown[1]: sd-device-enumerator: Scanning /sys/class [ 67.788994] systemd-shutdown[1]: All loop devices detached. [ 67.789581] systemd-shutdown[1]: Detaching DM devices. [ 67.790140] systemd-shutdown[1]: sd-device-enumerator: Scan all dirs [ 67.790810] systemd-shutdown[1]: sd-device-enumerator: Scanning /sys/bus [ 67.791516] systemd-shutdown[1]: sd-device-enumerator: Scanning /sys/class [ 67.792545] systemd-shutdown[1]: Detaching DM /dev/dm-0 (254:0). [ 67.806188] systemd-shutdown[1]: Not all DM devices detached, 1 left. [ 67.807314] systemd-shutdown[1]: Couldn't finalize remaining DM devices, trying again. [ 67.809246] systemd-shutdown[1]: Detaching DM devices. [ 67.810335] systemd-shutdown[1]: sd-device-enumerator: Scan all dirs [ 67.811638] systemd-shutdown[1]: sd-device-enumerator: Scanning /sys/bus [ 67.813034] systemd-shutdown[1]: sd-device-enumerator: Scanning /sys/class [ 67.814653] systemd-shutdown[1]: Not all DM devices detached, 1 left. [ 67.816156] systemd-shutdown[1]: Detaching DM devices. [ 67.817216] systemd-shutdown[1]: sd-device-enumerator: Scan all dirs [ 67.818263] systemd-shutdown[1]: sd-device-enumerator: Scanning /sys/bus [ 67.819188] systemd-shutdown[1]: sd-device-enumerator: Scanning /sys/class [ 67.820292] systemd-shutdown[1]: Not all DM devices detached, 1 left. [ 67.821183] systemd-shutdown[1]: Cannot finalize remaining DM devices, continuing. [ 67.822380] systemd-shutdown[1]: Successfully forked off '(sd-executor)' as PID 2370. [ 67.823453] systemd-shutdown[1]: (sd-executor) succeeded. [ 67.824193] systemd-shutdown[1]: Failed to finalize DM devices, ignoring. [ 67.825249] systemd-shutdown[1]: Successfully forked off '(sd-sync)' as PID 2371. [ 67.826269] systemd-shutdown[1]: Syncing filesystems and block devices. [ 67.827169] systemd-shutdown[1]: Rebooting. [ 67.854207] reboot: Restarting system [ 67.854659] reboot: machine restart I got rid of haveged, but it still fails. It seems to finalize cr_var properly though, so it's working as expected? -- You are receiving this mail because: You are on the CC list for the bug.