The latest update of the NVIDIA drivers sent my system into a buggy boot and subsequent emergency mode.
Found the solution on NVIDIA drivers installation - Ubuntu Server documentation :
sudo ubuntu-drivers install
and reboot.
Just lucky? For now?
Curious, which drivers were updated and by which means, e.g. Ubuntu repositories or NVIDIAās?
That combined with the emergency mode on reboot suggests that the driver wasnāt installed at all, at least not in the initial RAM disk for the boot environment, i.e. update-initramfs didnāt run.
You can get some more info from the APT and DPKG logs in /var/log/apt/* and /var/log/dpkg.log*.
The update was regular using Discover. Nothing out of the ordinary
As far as I can reconstruct it installed linux-modules-6.8.0-117-generic (6.8.0-117.117).
Term.log states :
Log started: 2026-05-18 03:40:12
Selecting previously unselected package linux-modules-6.8.0-117-generic.
(Reading database ...
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 260697 files and directories currently installed.)
Preparing to unpack .../00-linux-modules-6.8.0-117-generic_6.8.0-117.117_amd64.deb ...
Unpacking linux-modules-6.8.0-117-generic (6.8.0-117.117) ...
Selecting previously unselected package linux-image-6.8.0-117-generic.
Preparing to unpack .../01-linux-image-6.8.0-117-generic_6.8.0-117.117_amd64.deb ...
Unpacking linux-image-6.8.0-117-generic (6.8.0-117.117) ...
Selecting previously unselected package linux-modules-extra-6.8.0-117-generic.
Preparing to unpack .../02-linux-modules-extra-6.8.0-117-generic_6.8.0-117.117_amd64.deb ...
Unpacking linux-modules-extra-6.8.0-117-generic (6.8.0-117.117) ...
Preparing to unpack .../03-linux-generic_6.8.0-117.117_amd64.deb ...
Unpacking linux-generic (6.8.0-117.117) over (6.8.0-111.111) ...
Preparing to unpack .../04-linux-image-generic_6.8.0-117.117_amd64.deb ...
Unpacking linux-image-generic (6.8.0-117.117) over (6.8.0-111.111) ...
Selecting previously unselected package linux-headers-6.8.0-117.
Preparing to unpack .../05-linux-headers-6.8.0-117_6.8.0-117.117_all.deb ...
Unpacking linux-headers-6.8.0-117 (6.8.0-117.117) ...
Selecting previously unselected package linux-headers-6.8.0-117-generic.
Preparing to unpack .../06-linux-headers-6.8.0-117-generic_6.8.0-117.117_amd64.deb ...
Unpacking linux-headers-6.8.0-117-generic (6.8.0-117.117) ...
Preparing to unpack .../07-linux-headers-generic_6.8.0-117.117_amd64.deb ...
Unpacking linux-headers-generic (6.8.0-117.117) over (6.8.0-111.111) ...
Preparing to unpack .../08-linux-libc-dev_6.8.0-117.117_amd64.deb ...
Unpacking linux-libc-dev:amd64 (6.8.0-117.117) over (6.8.0-111.111) ...
Selecting previously unselected package linux-modules-nvidia-595-open-6.8.0-117-generic.
Preparing to unpack .../09-linux-modules-nvidia-595-open-6.8.0-117-generic_6.8.0-117.117_amd64.deb ...
Unpacking linux-modules-nvidia-595-open-6.8.0-117-generic (6.8.0-117.117) ...
Preparing to unpack .../10-linux-modules-nvidia-595-open-generic_6.8.0-117.117_amd64.deb ...
Unpacking linux-modules-nvidia-595-open-generic (6.8.0-117.117) over (6.8.0-111.111+1) ...
Preparing to unpack .../11-linux-modules-nvidia-590-open-generic_6.8.0-117.117_amd64.deb ...
Unpacking linux-modules-nvidia-590-open-generic (6.8.0-117.117) over (6.8.0-111.111+1) ...
Preparing to unpack .../12-linux-tools-common_6.8.0-117.117_all.deb ...
Unpacking linux-tools-common (6.8.0-117.117) over (6.8.0-111.111) ...
Selecting previously unselected package linux-tools-6.8.0-117.
Preparing to unpack .../13-linux-tools-6.8.0-117_6.8.0-117.117_amd64.deb ...
Unpacking linux-tools-6.8.0-117 (6.8.0-117.117) ...
Selecting previously unselected package linux-tools-6.8.0-117-generic.
Preparing to unpack .../14-linux-tools-6.8.0-117-generic_6.8.0-117.117_amd64.deb ...
Unpacking linux-tools-6.8.0-117-generic (6.8.0-117.117) ...
Setting up linux-libc-dev:amd64 (6.8.0-117.117) ...
Setting up linux-headers-6.8.0-117 (6.8.0-117.117) ...
Setting up linux-headers-6.8.0-117-generic (6.8.0-117.117) ...
/etc/kernel/header_postinst.d/dkms:
* dkms: running auto installation service for kernel 6.8.0-117-generic
Sign command: /usr/bin/kmodsign
Signing key: /var/lib/shim-signed/mok/MOK.priv
Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der
Building module:
Cleaning build area...
unset ARCH; [ ! -h /usr/bin/cc ] && export CC=/usr/bin/gcc; env NV_VERBOSE=1 'make' -j12 NV_EXCLUDE_BUILD_MODULES='' KERNEL_UNAME=6.8.0-117-generic IGNORE_XEN_PRESENCE=1 IGNORE_CC_MISMATCH=1 SYSSRC=/lib/modules/6.8.0-117-generic/build LD=/usr/bin/ld.bfd CONFIG_X86_KERNEL_IBT= modules............
Signing module /var/lib/dkms/nvidia/595.58.03/build/nvidia.ko
Signing module /var/lib/dkms/nvidia/595.58.03/build/nvidia-modeset.ko
Signing module /var/lib/dkms/nvidia/595.58.03/build/nvidia-drm.ko
Signing module /var/lib/dkms/nvidia/595.58.03/build/nvidia-uvm.ko
Signing module /var/lib/dkms/nvidia/595.58.03/build/nvidia-peermem.ko
Cleaning build area...
nvidia.ko:
Running module version sanity check.
Module version 595.58.03 for nvidia.ko
exactly matches what is already found in kernel 6.8.0-117-generic.
DKMS will not replace this module.
You may override by specifying --force.
nvidia-modeset.ko:
Running module version sanity check.
Module version 595.58.03 for nvidia-modeset.ko
exactly matches what is already found in kernel 6.8.0-117-generic.
DKMS will not replace this module.
You may override by specifying --force.
nvidia-drm.ko:
Running module version sanity check.
Module version 595.58.03 for nvidia-drm.ko
exactly matches what is already found in kernel 6.8.0-117-generic.
DKMS will not replace this module.
You may override by specifying --force.
nvidia-uvm.ko:
Running module version sanity check.
Module version 595.58.03 for nvidia-uvm.ko
exactly matches what is already found in kernel 6.8.0-117-generic.
DKMS will not replace this module.
You may override by specifying --force.
nvidia-peermem.ko:
Running module version sanity check.
Module version 595.58.03 for nvidia-peermem.ko
exactly matches what is already found in kernel 6.8.0-117-generic.
DKMS will not replace this module.
You may override by specifying --force.
depmod...
dkms autoinstall on 6.8.0-117-generic/x86_64 succeeded for nvidia
* dkms: autoinstall for kernel 6.8.0-117-generic
...done.
Setting up linux-tools-common (6.8.0-117.117) ...
Setting up linux-modules-6.8.0-117-generic (6.8.0-117.117) ...
Setting up linux-tools-6.8.0-117 (6.8.0-117.117) ...
Setting up linux-image-6.8.0-117-generic (6.8.0-117.117) ...
I: /boot/vmlinuz.old is now a symlink to vmlinuz-6.8.0-111-generic
I: /boot/initrd.img.old is now a symlink to initrd.img-6.8.0-111-generic
I: /boot/vmlinuz is now a symlink to vmlinuz-6.8.0-117-generic
I: /boot/initrd.img is now a symlink to initrd.img-6.8.0-117-generic
Setting up linux-modules-extra-6.8.0-117-generic (6.8.0-117.117) ...
Setting up linux-tools-6.8.0-117-generic (6.8.0-117.117) ...
Setting up linux-headers-generic (6.8.0-117.117) ...
Setting up linux-modules-nvidia-595-open-6.8.0-117-generic (6.8.0-117.117) ...
Setting up linux-modules-nvidia-595-open-generic (6.8.0-117.117) ...
Setting up linux-image-generic (6.8.0-117.117) ...
Setting up linux-generic (6.8.0-117.117) ...
Setting up linux-modules-nvidia-590-open-generic (6.8.0-117.117) ...
Processing triggers for man-db (2.12.0-4build2) ...
Processing triggers for linux-image-6.8.0-117-generic (6.8.0-117.117) ...
/etc/kernel/postinst.d/dkms:
* dkms: running auto installation service for kernel 6.8.0-117-generic
* dkms: autoinstall for kernel 6.8.0-117-generic
...done.
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-6.8.0-117-generic
/etc/kernel/postinst.d/zz-update-grub:
Sourcing file `/etc/default/grub'
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-6.8.0-117-generic
Found initrd image: /boot/initrd.img-6.8.0-117-generic
Found linux image: /boot/vmlinuz-6.8.0-111-generic
Found initrd image: /boot/initrd.img-6.8.0-111-generic
Found linux image: /boot/vmlinuz-6.8.0-110-generic
Found initrd image: /boot/initrd.img-6.8.0-110-generic
Found memtest86+x64 image: /boot/memtest86+x64.bin
Warning: os-prober will not be executed to detect other bootable partitions.
Systems on them will not be added to the GRUB boot configuration.
Check GRUB_DISABLE_OS_PROBER documentation entry.
Adding boot menu entry for UEFI Firmware Settings ...
done
Log ended: 2026-05-18 03:41:01
Looks like a clean upgrade, so I was wrong. Thanks for clearing that up!
On a more general note, can you please put such output in pre-formatted text / code blocks (the </> icon in the editor)? Especially the first part of the log is very hard to follow, because the blockquote element messes up the line endings. Also, such code blocks can be easily copied by that little clipboard icon in the top-right corner of the element, to paste into a file which can be read and searched with a pager, for instance.
Optional helper script
If you are so inclined, I took it upon myself to provide a little helper script for that. 
It would be really nice if you edited your post with the little āpencilā icon at the bottom.
What is the version of your install? According to kernel version it is 24.04.
Are you trying to do this on desktop or server?
Also are you using Ubuntu or Kubuntu? Only Kubuntu uses Discover.
Iām asking this because this is very confusing, since you provide very little information. It would help a lot if you could provide more information about your system and version you are using.
1 Like
I considered that but chose to leave that for if requested.
Which is now.
**Operating System**
Kubuntu 24.04 Desktop
**Software**
KDE Plasma Version: 5.27.12
KDE Frameworks Version: 5.115.0
Qt Version: 5.15.13
Kernel Version: 6.8.0-117-generic (64-bit)
Graphics Platform: X11
**Hardware**
Motherboard: ASRock B550 Extreme4
Processors: 12 Ć AMD Ryzen 5 5600X 6-Core Processor
Memory: 62,7 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 3060/PCIe/SSE2
Internal HD: WD Black SN850X HS 2000GB
1 Like
Well, not so āclean upgradeā using Discover. 
The command line upgrade seems to have solved it. Iāll see if it stay that way during next boots.
I did use </> inititially but it didnāt format the first part correctly. I does now (I think).
I said it looks like one, so this may hint at a bug. 
But I also didnāt pay enough attention, because I was too focused on update-initramfs:
Why was there already an exact match to begin with? Have you also installed some NVIDIA stuff that had already done that? Or is that from the ubuntu-drivers install run?
Thanks for fixing the formatting; much appreciated!
Iāve done nothing special other than installing the required NVIDIA software following the initial install of 24.04. Mostly following 'Itās FOSSā.
But I noticed before that some earlier upgrades mentioned āalready latest versionā.
So I would assume that the packagers also include earlier components just making sure that all dependencies are covered.
And to be fair, upgrades do have a tendency to mess with the installed base. But not complaining since Kubuntu 8.04.
How did you install it? Is there any 3rd party software directly from NVIDIA installed? Because that might explain the duplication; something seems to have done the job already.
Must be a specialty of NVIDIA then, because I havenāt seen anything like that on an AMD mobile APU.
You could try to investigate what was logged to the journal on that faulty boot:
journalctl -p err --boot <negative number>
You just need to set a negative number to go backwards in boot history, so if it was five system (re)starts ago, just set --boot -5.
I am clearly out of my depth here. Thnx for helping me out.
Yesterday I needed t0 boot 3x to get to login.
And a 4th due to not coming out if hibernation.
So I first disabled hibernation. Little use anyway with an SSD.
As for journalctl -p err --boot (tnx Peter) see below.
I did have some issues mounting an external HD, but those seem unrelated to me.
Other sources suggested the following commands in order to analyze.:
- systemd-analyze time
- systemd-analyze blame
- systemctl list-units --state failed
- systemd-analyze critical-chain
- sudo dmesg -T --color=always --level=err,warn | more
Anyone? TIA.
Regards,
Peter
____________________
journalctl -p err --boot -1
mei 21 13:38:41 Wielewaal kernel:
mei 21 13:40:11 Wielewaal systemd[1]: Timed out waiting for device dev-sdb1.device - /dev/sdb1.
mei 21 15:16:34 Wielewaal kernel: Buffer I/O error on dev sdb1, logical block 544944264, async page read
mei 21 15:16:34 Wielewaal kernel: Buffer I/O error on dev sdb1, logical block 544944264, async page read
mei 21 15:16:34 Wielewaal kernel: Buffer I/O error on dev sdb1, logical block 544944264, async page read
mei 21 15:16:34 Wielewaal kernel: Buffer I/O error on dev sdb1, logical block 544944264, async page read
mei 21 15:16:34 Wielewaal kernel: Buffer I/O error on dev sdb1, logical block 544944264, async page read
mei 21 15:16:34 Wielewaal kernel: Buffer I/O error on dev sdb1, logical block 544944264, async page read
mei 21 15:16:34 Wielewaal kernel: Buffer I/O error on dev sdb1, logical block 544944264, async page read
mei 21 15:16:34 Wielewaal kernel: Buffer I/O error on dev sdb1, logical block 544944264, async page read
mei 21 15:16:36 Wielewaal kernel: Buffer I/O error on dev sdb1, logical block 545165448, async page read
mei 21 15:16:42 Wielewaal kernel: Buffer I/O error on dev sdb1, logical block 153584385, async page read
mei 21 15:16:42 Wielewaal kernel: Buffer I/O error on dev sdb1, logical block 153584385, async page read
mei 21 15:16:42 Wielewaal kernel: Buffer I/O error on dev sdb1, logical block 153584385, async page read
mei 21 15:16:42 Wielewaal kernel: Buffer I/O error on dev sdb1, logical block 153584385, async page read
mei 21 15:16:42 Wielewaal kernel: Buffer I/O error on dev sdb1, logical block 248738851, async page read
mei 21 15:16:42 Wielewaal kernel: Buffer I/O error on dev sdb1, logical block 248738851, async page read
mei 21 15:16:42 Wielewaal kernel: Buffer I/O error on dev sdb1, logical block 248738851, async page read
mei 21 15:16:42 Wielewaal kernel: Buffer I/O error on dev sdb1, logical block 248738851, async page read
mei 21 15:16:42 Wielewaal kernel: Buffer I/O error on dev sdb1, logical block 212949285, async page read
mei 21 15:16:42 Wielewaal kernel: Buffer I/O error on dev sdb1, logical block 212949285, async page read
mei 21 15:16:49 Wielewaal kernel: Buffer I/O error on dev sdb1, logical block 153584385, async page read
mei 21 15:16:49 Wielewaal kernel: Buffer I/O error on dev sdb1, logical block 153584385, async page read
mei 21 15:16:49 Wielewaal kernel: Buffer I/O error on dev sdb1, logical block 153584385, async page read
mei 21 15:25:07 Wielewaal kernel: Buffer I/O error on dev sdb1, logical block 146561078, async page read
mei 21 15:25:07 Wielewaal kernel: Buffer I/O error on dev sdb1, logical block 146561078, async page read
mei 21 15:27:10 Wielewaal kernel: Buffer I/O error on dev sdb1, logical block 611986168, async page read
mei 21 15:27:10 Wielewaal kernel: Buffer I/O error on dev sdb1, logical block 146561078, async page read
mei 21 15:30:57 Wielewaal kernel: Buffer I/O error on dev sdb1, logical block 146561078, async page read
mei 22 02:41:32 Wielewaal systemd[1]: Failed unmounting run-user-1000.mount - /run/user/1000.
mei 22 02:41:33 Wielewaal systemd[1]: Failed unmounting run-snapd-ns.mount - /run/snapd/ns.
lines 1-32/32 (END)
____________________
journalctl -p err --boot -2
mei 21 09:36:01 Wielewaal kernel:
mei 21 09:37:30 Wielewaal systemd[1]: Timed out waiting for device dev-sdb1.device - /dev/sdb1.
mei 21 09:47:53 Wielewaal kernel: usb 1-5.2: cmd cmplt err -108
mei 21 09:47:53 Wielewaal kernel: sd 8:0:0:0: [sdc] Asking for cache data failed
mei 21 09:48:00 Wielewaal kernel: usb 1-5-port2: disabled by hub (EMI?), re-enabling...
mei 21 09:48:00 Wielewaal kernel: I/O error, dev sdc, sector 5971720 op 0x0:(READ) flags 0x80700 phys_seg 1 p>
mei 21 09:48:00 Wielewaal kernel: device offline error, dev sdc, sector 5971720 op 0x0:(READ) flags 0x0 phys_>
mei 21 09:48:00 Wielewaal kernel: Buffer I/O error on dev sdc1, logical block 5969672, async page read
mei 21 09:48:00 Wielewaal kernel: device offline error, dev sdc, sector 5971721 op 0x0:(READ) flags 0x0 phys_>
mei 21 09:48:00 Wielewaal kernel: Buffer I/O error on dev sdc1, logical block 5969673, async page read
mei 21 09:48:00 Wielewaal kernel: device offline error, dev sdc, sector 5971722 op 0x0:(READ) flags 0x0 phys_>
mei 21 09:48:00 Wielewaal kernel: Buffer I/O error on dev sdc1, logical block 5969674, async page read
mei 21 09:48:00 Wielewaal kernel: device offline error, dev sdc, sector 5971723 op 0x0:(READ) flags 0x0 phys_>
mei 21 09:48:00 Wielewaal kernel: Buffer I/O error on dev sdc1, logical block 5969675, async page read
mei 21 09:48:00 Wielewaal kernel: device offline error, dev sdc, sector 5971724 op 0x0:(READ) flags 0x0 phys_>
mei 21 09:48:00 Wielewaal kernel: Buffer I/O error on dev sdc1, logical block 5969676, async page read
mei 21 09:48:00 Wielewaal kernel: device offline error, dev sdc, sector 5971725 op 0x0:(READ) flags 0x0 phys_>
mei 21 09:48:00 Wielewaal kernel: Buffer I/O error on dev sdc1, logical block 5969677, async page read
mei 21 09:48:00 Wielewaal kernel: Buffer I/O error on dev sdc1, logical block 5969678, async page read
mei 21 09:48:00 Wielewaal kernel: Buffer I/O error on dev sdc1, logical block 5969679, async page read
mei 21 09:48:00 Wielewaal kernel: Buffer I/O error on dev sdc1, logical block 5969672, lost async page write
mei 21 09:48:00 Wielewaal kernel: Buffer I/O error on dev sdc1, logical block 5969673, lost async page write
lines 1-22/22 (END)
____________________
journalctl -p err --boot -3
mei 21 09:32:40 Wielewaal kernel:
mei 21 09:34:09 Wielewaal systemd[1]: Timed out waiting for device dev-sdb1.device - /dev/sdb1.
____________________
journalctl -p err --boot -4
mei 21 09:27:06 Wielewaal systemd[1]: Timed out waiting for device dev-sdb1.device - /dev/sdb1.
____________________
journalctl -p err --boot -5
mei 21 09:13:55 Wielewaal kernel:
mei 21 09:15:24 Wielewaal systemd[1]: Timed out waiting for device dev-sdb1.device - /dev/sdb1.
mei 21 09:17:06 Wielewaal systemd[1]: Timed out waiting for device dev-sdb1.device - /dev/sdb1.
mei 21 09:19:14 Wielewaal systemd[1]: Timed out waiting for device dev-sdb1.device - /dev/sdb1.
____________________
journalctl -p err --boot -6
mei 21 09:09:57 Wielewaal kernel:
mei 21 09:11:26 Wielewaal systemd[1]: Timed out waiting for device dev-sdb1.device - /dev/sdb1.
____________________
journalctl -p err --boot -7
mei 21 09:07:51 Wielewaal kernel:
mei 21 09:09:21 Wielewaal systemd[1]: Timed out waiting for device dev-sdb1.device - /dev/sdb1.
____________________
journalctl -p err --boot -8
mei 20 18:07:35 Wielewaal kernel:
mei 20 22:43:09 Wielewaal kernel: BUG: Bad page state in process Isolated Web Co pfn:5dacec
____________________
journalctl -p err --boot -9
mei 20 18:06:53 Wielewaal kernel:
____________________
journalctl -p err --boot -10
mei 20 11:45:32 Wielewaal systemd[1]: Timed out waiting for device dev-sdb1.device - /dev/sdb1.
mei 20 18:06:06 Wielewaal systemd[1]: Failed unmounting run-user-1000.mount - /run/user/1000.
____________________
journalctl -p err --boot -11
mei 20 11:40:50 Wielewaal kernel:
mei 20 11:42:19 Wielewaal systemd[1]: Timed out waiting for device dev-sdb1.device - /dev/sdb1.
____________________
journalctl -p err --boot -12
mei 19 17:24:30 Wielewaal kernel:
mei 19 17:26:00 Wielewaal systemd[1]: Timed out waiting for device dev-sdb1.device - /dev/sdb1.
mei 19 17:50:50 Wielewaal systemd[2069]: Failed to start app-dkms-7523a19677394d208adbbb2b8625e1b9.scope - dk>
mei 19 18:27:06 Wielewaal kernel: device offline error, dev sdb, sector 2579395080 op 0x1:(WRITE) flags 0x480>
mei 19 18:27:06 Wielewaal kernel: Buffer I/O error on dev sdb1, logical block 322424129, lost async page write
mei 19 18:27:06 Wielewaal kernel: Buffer I/O error on dev sdb1, logical block 322424130, lost async page write
mei 19 18:27:06 Wielewaal kernel: Buffer I/O error on dev sdb1, logical block 322424131, lost async page write
mei 19 18:27:06 Wielewaal kernel: Buffer I/O error on dev sdb1, logical block 322424132, lost async page write
mei 19 18:27:06 Wielewaal kernel: Buffer I/O error on dev sdb1, logical block 322424133, lost async page write
mei 19 18:27:06 Wielewaal kernel: Buffer I/O error on dev sdb1, logical block 322424134, lost async page write
mei 19 18:27:06 Wielewaal kernel: Buffer I/O error on dev sdb1, logical block 322424135, lost async page write
mei 19 18:27:06 Wielewaal kernel: Buffer I/O error on dev sdb1, logical block 322424136, lost async page write
mei 19 18:27:06 Wielewaal kernel: Buffer I/O error on dev sdb1, logical block 322424137, lost async page write
mei 19 18:27:06 Wielewaal kernel: Buffer I/O error on dev sdb1, logical block 322424138, lost async page write
mei 19 18:27:06 Wielewaal kernel: device offline error, dev sdb, sector 6820946072 op 0x1:(WRITE) flags 0x104>
mei 19 18:27:06 Wielewaal kernel: device offline error, dev sdb, sector 2579395320 op 0x1:(WRITE) flags 0x480>
mei 19 18:27:06 Wielewaal kernel: device offline error, dev sdb, sector 2579395560 op 0x1:(WRITE) flags 0x480>
mei 19 18:27:06 Wielewaal kernel: device offline error, dev sdb, sector 6820946312 op 0x1:(WRITE) flags 0x104>
mei 19 18:27:06 Wielewaal kernel: device offline error, dev sdb, sector 2579395800 op 0x1:(WRITE) flags 0x800>
mei 19 18:27:06 Wielewaal kernel: device offline error, dev sdb, sector 2579622296 op 0x1:(WRITE) flags 0x480>
mei 19 18:27:06 Wielewaal kernel: device offline error, dev sdb, sector 6820946552 op 0x1:(WRITE) flags 0x104>
mei 19 18:27:06 Wielewaal kernel: device offline error, dev sdb, sector 2579622536 op 0x1:(WRITE) flags 0x480>
mei 19 18:27:06 Wielewaal kernel: device offline error, dev sdb, sector 2579622776 op 0x1:(WRITE) flags 0x480>
mei 20 02:52:50 Wielewaal kernel: BUG: Bad page state in process KIO::WorkerThre pfn:5dacec
mei 20 03:21:16 Wielewaal systemd[1]: Failed unmounting run-user-1000.mount - /run/user/1000.
mei 20 03:21:17 Wielewaal systemd[1]: Failed unmounting run-snapd-ns.mount - /run/snapd/ns.
lines 1-26/26 (END)
____________________
journalctl -p err --boot -13
mei 19 17:20:17 Wielewaal systemd[1]: Timed out waiting for device dev-sdb1.device - /dev/sdb1.
mei 19 17:22:34 Wielewaal systemd[1]: Timed out waiting for device dev-sdb1.device - /dev/sdb1.
____________________
journalctl -p err --boot -14
mei 19 17:17:09 Wielewaal kernel:
____________________
journalctl -p err --boot -15
19 17:14:38 Wielewaal kernel:
mei 19 17:14:39 Wielewaal systemd[1]: Failed to mount media-pjw.mount - /media/pjw.
mei 19 17:14:40 Wielewaal systemd[1]: Failed to mount media-pjw.mount - /media/pjw.
____________________
journalctl -p err --boot -16
19 16:18:51 Wielewaal systemd[1]: Timed out waiting for device dev-sdb1.device - /dev/sdb1.
mei 19 17:13:59 Wielewaal systemd[1]: Failed unmounting run-user-1000.mount - /run/user/1000.
____________________
journalctl -p err --boot -17
19 16:16:00 Wielewaal kernel:
____________________
journalctl -p err --boot -18
19 16:14:28 Wielewaal systemd[1]: Failed to mount media-pjw-Elements.mount - /media/pjw/Elements.
____________________
journalctl -p err --boot -19
19 12:21:05 Wielewaal kernel:
____________________
journalctl -p err --boot 20
18 11:30:52 Wielewaal kernel:
18 11:30:52 Wielewaal kernel:
mei 18 14:15:58 Wielewaal systemd[2529]: Failed to start app-libreoffice\x2dwriter-d0d9de0fd33f453d9d298a5b4c257573.scope - LibreOffice Writer - Word Processor.
mei 18 14:16:05 Wielewaal systemd[2529]: Failed to start app-libreoffice\x2dwriter-cf983dc724ec4f1d8d666f46f5bf6dad.scope - LibreOffice Writer - Word Processor.
mei 18 14:16:16 Wielewaal systemd[2529]: Failed to start app-libreoffice\x2dwriter-125339aaa4d643ecae0d810e68198e6a.scope - LibreOffice Writer - Word Processor.
mei 18 14:17:02 Wielewaal systemd[2529]: Failed to start app-libreoffice\x2dwriter-d0cdbebb9f9946a4b68b0578b3684e5a.scope - LibreOffice Writer - Word Processor.
mei 18 14:18:26 Wielewaal systemd[2529]: Failed to start app-libreoffice\x2dwriter-c13299222f46488281bc38630bc9a2fa.scope - LibreOffice Writer - Word Processor.
mei 18 17:24:17 Wielewaal kernel: I/O error, dev sdc, sector 7527472 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2
mei 18 17:24:17 Wielewaal kernel: device offline error, dev sdc, sector 7527472 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
mei 18 17:24:17 Wielewaal kernel: Buffer I/O error on dev sdc1, logical block 940678, async page read
mei 18 17:24:17 Wielewaal kernel: device offline error, dev sdc, sector 6301560 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2
mei 18 17:24:17 Wielewaal kernel: device offline error, dev sdc, sector 6301560 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
mei 18 17:24:17 Wielewaal kernel: Buffer I/O error on dev sdc1, logical block 787439, async page read
mei 18 17:24:17 Wielewaal kernel: device offline error, dev sdc, sector 6321656 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2
mei 18 17:24:17 Wielewaal kernel: device offline error, dev sdc, sector 6321656 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
mei 18 17:24:17 Wielewaal kernel: Buffer I/O error on dev sdc1, logical block 789951, async page read
mei 18 17:24:17 Wielewaal kernel: device offline error, dev sdc, sector 7045248 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2
mei 18 17:24:17 Wielewaal kernel: device offline error, dev sdc, sector 7045248 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
mei 18 17:24:17 Wielewaal kernel: Buffer I/O error on dev sdc1, logical block 880400, async page read
mei 18 17:24:17 Wielewaal kernel: device offline error, dev sdc, sector 6323600 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2
mei 18 17:24:17 Wielewaal kernel: device offline error, dev sdc, sector 6323600 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
mei 18 17:24:17 Wielewaal kernel: Buffer I/O error on dev sdc1, logical block 790194, async page read
mei 18 17:24:17 Wielewaal kernel: Buffer I/O error on dev sdc1, logical block 979678, async page read
mei 18 17:24:17 Wielewaal kernel: Buffer I/O error on dev sdc1, logical block 980087, async page read
mei 18 17:24:17 Wielewaal kernel: Buffer I/O error on dev sdc1, logical block 1138318, async page read
mei 18 17:24:17 Wielewaal kernel: Buffer I/O error on dev sdc1, logical block 1138317, async page read
mei 18 17:24:17 Wielewaal kernel: Buffer I/O error on dev sdc1, logical block 1149355, async page read
mei 18 17:50:20 Wielewaal kernel: EXT4-fs (dm-1): unable to read superblock
mei 18 17:50:34 Wielewaal kernel: Buffer I/O error on dev dm-0, logical block 976781312, lost sync page write
mei 18 17:50:34 Wielewaal kernel: JBD2: I/O error when updating journal superblock for dm-0-8.
mei 18 17:50:34 Wielewaal kernel: Aborting journal on device dm-0-8.
mei 18 17:50:34 Wielewaal kernel: Buffer I/O error on dev dm-0, logical block 976781312, lost sync page write
mei 18 17:50:34 Wielewaal kernel: JBD2: I/O error when updating journal superblock for dm-0-8.
mei 18 17:50:34 Wielewaal kernel: EXT4-fs error (device dm-0): ext4_put_super:1345: comm umount: Couldn't clean up the journal
____________________
journalctl -p err --boot -21
18 03:41:35 Wielewaal kernel:
____________________
journalctl -p err --boot -22
18 03:40:11 Wielewaal kernel:
mei 18 03:40:13 Wielewaal nvidia-persistenced[1156]: Failed to query NVIDIA devices. Please ensure that the NVIDIA device files (/dev/nvidia*) exist, and that user 122 has read and write permissions for those files.
mei 18 03:40:13 Wielewaal systemd[1]: Failed to start nvidia-persistenced.service - NVIDIA Persistence Daemon.
Is your power supply beefy enough to drive all the pieces attached ?
You seem to have at least one faulty storage device; see all the I/O errors. Donāt be fooled that itās sdb one time an sdc the other; that could just be the same device, as outlined here. That could also explain your initial issue with the faulty driver installation. You should consider backing up the device and replacing it. Or see if itās a power supply issue, as @ogra suggested. Or it could just be a loose cable/connector, so best check that first.
(order adjusted for logical grouping)
These commands are for boot performance analysis.
I am not a fan of the legacy dmesg; journalctl is much more powerful and does the same, including the | more ā well, | less, technically, b/c more got replaced by less a long time ago ā when run like this:
journalctl --boot --dmesg --priority warning
or
journalctl -b -kp warning
for short. But that also limits the output to kernel messages; I wanted to see all messages of priority err or higher, which includes services as well.
Good point. But Iād think so : be quiet! STRAIGHT POWER12 750W ATX3.0 P 
Did some checking on sdb1 and noticed it was flagged for boot.
That would explain the messages about the system waiting for sdb and sdb1 during booting, since I only connect the external drive (= backup drive) when needed.
So I already removed the boot flag on it and will reboot later this evening or tomorrow.
Also in de process of moving the contents of that drive to a fresh one.
The power supply is hardly likely to be the culprit : be quiet! STRAIGHT POWER12 750W ATX3.0 P
Dying PSUās can have funky effects on the hardware they are driving, so donāt just rule out yours because of its output rating.
FWIW, very beefy PSUās can get unstable in real low power states; the rule of thumb says that you should at least have 20% load. But I doubt thatās the issue here; itās only to illustrate that hardware issues arenāt straight forward to diagnose most of the time.
Yeah, 750W sounds enough to make it drive circles around your houseā¦
You really shouldnāt be too hung up on sdb1! Especially when removable hardware is involved!!!
An external drive present when trying to boot, can have that effect. But when you do fix the boot flag best double check the actual device first. If you do get it wrong, your system will be unbootable.
Consider yourself thoroughly warned.
journalctl --boot --dmesg --priority warning :
mei 22 11:13:42 Wielewaal kernel: i8042: PNP: PS/2 appears to have AUX port disabled, if this is incorrect please>
mei 22 11:13:42 Wielewaal kernel: device-mapper: core: CONFIG_IMA_DISABLE_HTABLE is disabled. Duplicate IMA measu>
mei 22 11:13:42 Wielewaal systemd-fstab-generator[495]: Mount point none is not a valid path, ignoring.
mei 22 11:13:42 Wielewaal kernel: nvidia: loading out-of-tree module taints kernel.
mei 22 11:13:42 Wielewaal kernel:
mei 22 11:13:43 Wielewaal kernel: NVRM: loading NVIDIA UNIX Open Kernel Module for x86_64 580.159.03 Release Bu>
mei 22 11:15:13 Wielewaal kernel: block nvme0n1: No UUID available providing old NGUID
mei 22 11:15:13 Wielewaal systemd-fstab-generator[1606]: Mount point none is not a valid path, ignoring.
mei 22 11:15:14 Wielewaal kernel: set_capacity_and_notify: 26 callbacks suppressed
mei 22 11:27:11 Wielewaal kernel: kauditd_printk_skb: 189 callbacks suppressed
mei 22 11:27:29 Wielewaal kernel: kauditd_printk_skb: 38 callbacks suppressed
mei 22 13:50:18 Wielewaal systemd-fstab-generator[24672]: Mount point none is not a valid path, ignoring.
mei 22 13:50:21 Wielewaal systemd-fstab-generator[24824]: Mount point none is not a valid path, ignoring.
mei 22 13:54:19 Wielewaal kernel: kauditd_printk_skb: 27 callbacks suppressed
mei 22 15:57:00 Wielewaal kernel: [UFW BLOCK] IN=enp4s0 OUT= MAC= SRC=192.168.1.7 DST=239.255.255.250 LEN=635 TOS>
mei 22 15:57:00 Wielewaal kernel: [UFW BLOCK] IN=enp4s0 OUT= MAC= SRC=fe80:0000:0000:0000:bb41:2c51:9899:6e48 DST>
mei 22 15:57:01 Wielewaal kernel: [UFW BLOCK] IN=enp4s0 OUT= MAC= SRC=192.168.1.7 DST=239.255.255.250 LEN=635 TOS>
mei 22 15:57:01 Wielewaal kernel: [UFW BLOCK] IN=enp4s0 OUT= MAC= SRC=fe80:0000:0000:0000:bb41:2c51:9899:6e48 DST>
mei 22 15:57:11 Wielewaal kernel: ..........ready
mei 22 15:57:11 Wielewaal kernel: sd 7:0:0:0: [sdb] No Caching mode page found
mei 22 15:57:11 Wielewaal kernel: sd 7:0:0:0: [sdb] Assuming drive cache: write through
mei 22 16:01:25 Wielewaal systemd-fstab-generator[35503]: Mount point none is not a valid path, ignoring.
mei 22 16:02:41 Wielewaal systemd-fstab-generator[35764]: Mount point none is not a valid path, ignoring.
mei 22 16:03:14 Wielewaal kernel: usb 1-5.4: device descriptor read/64, error -71
mei 22 16:03:14 Wielewaal kernel: [UFW BLOCK] IN=enp4s0 OUT= MAC= SRC=192.168.1.7 DST=239.255.255.250 LEN=635 TOS>
mei 22 16:03:14 Wielewaal kernel: [UFW BLOCK] IN=enp4s0 OUT= MAC= SRC=fe80:0000:0000:0000:bb41:2c51:9899:6e48 DST>
mei 22 16:03:16 Wielewaal kernel: ..ready
mei 22 16:03:16 Wielewaal kernel: sd 8:0:0:0: [sdc] Preferred minimum I/O size 512 bytes not a multiple of physic>
mei 22 16:03:16 Wielewaal kernel: sd 8:0:0:0: [sdc] Optimal transfer size 33553920 bytes not a multiple of physic>
mei 22 16:03:17 Wielewaal kernel: request_module fs-ntfs3 succeeded, but still no fs?
mei 22 16:08:06 Wielewaal kernel: [UFW BLOCK] IN=enp4s0 OUT= MAC= SRC=192.168.1.7 DST=239.255.255.250 LEN=635 TOS>
mei 22 16:08:06 Wielewaal kernel: [UFW BLOCK] IN=enp4s0 OUT= MAC= SRC=fe80:0000:0000:0000:bb41:2c51:9899:6e48 DST>
mei 22 17:23:18 Wielewaal kernel: kauditd_printk_skb: 7575 callbacks suppressed
mei 22 18:13:58 Wielewaal kernel: [UFW BLOCK] IN=enp4s0 OUT= MAC= SRC=192.168.1.7 DST=239.255.255.250 LEN=635 TOS>
mei 22 18:13:58 Wielewaal kernel: [UFW BLOCK] IN=enp4s0 OUT= MAC= SRC=fe80:0000:0000:0000:bb41:2c51:9899:6e48 DST>
mei 22 18:15:15 Wielewaal kernel: [UFW BLOCK] IN=enp4s0 OUT= MAC= SRC=192.168.1.7 DST=239.255.255.250 LEN=635 TOS>
mei 22 18:15:15 Wielewaal kernel: [UFW BLOCK] IN=enp4s0 OUT= MAC= SRC=fe80:0000:0000:0000:bb41:2c51:9899:6e48 DST>
mei 22 18:15:16 Wielewaal kernel: [UFW BLOCK] IN=enp4s0 OUT= MAC= SRC=192.168.1.7 DST=239.255.255.250 LEN=635 TOS>
mei 22 18:15:16 Wielewaal kernel: [UFW BLOCK] IN=enp4s0 OUT= MAC= SRC=fe80:0000:0000:0000:bb41:2c51:9899:6e48 DST>
mei 22 18:15:26 Wielewaal kernel: ..........ready
mei 22 18:15:26 Wielewaal kernel: sd 7:0:0:0: [sdb] No Caching mode page found
mei 22 18:15:26 Wielewaal kernel: sd 7:0:0:0: [sdb] Assuming drive cache: write through
journalctl -b -kp warning
mei 22 11:13:42 Wielewaal kernel: i8042: PNP: PS/2 appears to have AUX port disabled, if this is incorrect please>
mei 22 11:13:42 Wielewaal kernel: device-mapper: core: CONFIG_IMA_DISABLE_HTABLE is disabled. Duplicate IMA measu>
mei 22 11:13:42 Wielewaal systemd-fstab-generator[495]: Mount point none is not a valid path, ignoring.
mei 22 11:13:42 Wielewaal kernel: nvidia: loading out-of-tree module taints kernel.
mei 22 11:13:42 Wielewaal kernel:
mei 22 11:13:43 Wielewaal kernel: NVRM: loading NVIDIA UNIX Open Kernel Module for x86_64 580.159.03 Release Bu>
mei 22 11:15:13 Wielewaal kernel: block nvme0n1: No UUID available providing old NGUID
mei 22 11:15:13 Wielewaal systemd-fstab-generator[1606]: Mount point none is not a valid path, ignoring.
mei 22 11:15:14 Wielewaal kernel: set_capacity_and_notify: 26 callbacks suppressed
mei 22 11:27:11 Wielewaal kernel: kauditd_printk_skb: 189 callbacks suppressed
mei 22 11:27:29 Wielewaal kernel: kauditd_printk_skb: 38 callbacks suppressed
mei 22 13:50:18 Wielewaal systemd-fstab-generator[24672]: Mount point none is not a valid path, ignoring.
mei 22 13:50:21 Wielewaal systemd-fstab-generator[24824]: Mount point none is not a valid path, ignoring.
mei 22 13:54:19 Wielewaal kernel: kauditd_printk_skb: 27 callbacks suppressed
mei 22 15:57:00 Wielewaal kernel: [UFW BLOCK] IN=enp4s0 OUT= MAC= SRC=192.168.1.7 DST=239.255.255.250 LEN=635 TOS>
mei 22 15:57:00 Wielewaal kernel: [UFW BLOCK] IN=enp4s0 OUT= MAC= SRC=fe80:0000:0000:0000:bb41:2c51:9899:6e48 DST>
mei 22 15:57:01 Wielewaal kernel: [UFW BLOCK] IN=enp4s0 OUT= MAC= SRC=192.168.1.7 DST=239.255.255.250 LEN=635 TOS>
mei 22 15:57:01 Wielewaal kernel: [UFW BLOCK] IN=enp4s0 OUT= MAC= SRC=fe80:0000:0000:0000:bb41:2c51:9899:6e48 DST>
mei 22 15:57:11 Wielewaal kernel: ..........ready
mei 22 15:57:11 Wielewaal kernel: sd 7:0:0:0: [sdb] No Caching mode page found
mei 22 15:57:11 Wielewaal kernel: sd 7:0:0:0: [sdb] Assuming drive cache: write through
mei 22 16:01:25 Wielewaal systemd-fstab-generator[35503]: Mount point none is not a valid path, ignoring.
mei 22 16:02:41 Wielewaal systemd-fstab-generator[35764]: Mount point none is not a valid path, ignoring.
mei 22 16:03:14 Wielewaal kernel: usb 1-5.4: device descriptor read/64, error -71
mei 22 16:03:14 Wielewaal kernel: [UFW BLOCK] IN=enp4s0 OUT= MAC= SRC=192.168.1.7 DST=239.255.255.250 LEN=635 TOS>
mei 22 16:03:14 Wielewaal kernel: [UFW BLOCK] IN=enp4s0 OUT= MAC= SRC=fe80:0000:0000:0000:bb41:2c51:9899:6e48 DST>
mei 22 16:03:16 Wielewaal kernel: ..ready
mei 22 16:03:16 Wielewaal kernel: sd 8:0:0:0: [sdc] Preferred minimum I/O size 512 bytes not a multiple of physic>
mei 22 16:03:16 Wielewaal kernel: sd 8:0:0:0: [sdc] Optimal transfer size 33553920 bytes not a multiple of physic>
mei 22 16:03:17 Wielewaal kernel: request_module fs-ntfs3 succeeded, but still no fs?
mei 22 16:08:06 Wielewaal kernel: [UFW BLOCK] IN=enp4s0 OUT= MAC= SRC=192.168.1.7 DST=239.255.255.250 LEN=635 TOS>
mei 22 16:08:06 Wielewaal kernel: [UFW BLOCK] IN=enp4s0 OUT= MAC= SRC=fe80:0000:0000:0000:bb41:2c51:9899:6e48 DST>
mei 22 17:23:18 Wielewaal kernel: kauditd_printk_skb: 7575 callbacks suppressed
mei 22 18:13:58 Wielewaal kernel: [UFW BLOCK] IN=enp4s0 OUT= MAC= SRC=192.168.1.7 DST=239.255.255.250 LEN=635 TOS>
mei 22 18:13:58 Wielewaal kernel: [UFW BLOCK] IN=enp4s0 OUT= MAC= SRC=fe80:0000:0000:0000:bb41:2c51:9899:6e48 DST>
mei 22 18:15:15 Wielewaal kernel: [UFW BLOCK] IN=enp4s0 OUT= MAC= SRC=192.168.1.7 DST=239.255.255.250 LEN=635 TOS>
mei 22 18:15:15 Wielewaal kernel: [UFW BLOCK] IN=enp4s0 OUT= MAC= SRC=fe80:0000:0000:0000:bb41:2c51:9899:6e48 DST>
mei 22 18:15:16 Wielewaal kernel: [UFW BLOCK] IN=enp4s0 OUT= MAC= SRC=192.168.1.7 DST=239.255.255.250 LEN=635 TOS>
mei 22 18:15:16 Wielewaal kernel: [UFW BLOCK] IN=enp4s0 OUT= MAC= SRC=fe80:0000:0000:0000:bb41:2c51:9899:6e48 DST>
mei 22 18:15:26 Wielewaal kernel: ..........ready
mei 22 18:15:26 Wielewaal kernel: sd 7:0:0:0: [sdb] No Caching mode page found
mei 22 18:15:26 Wielewaal kernel: sd 7:0:0:0: [sdb] Assuming drive cache: write through
I concur.
But now I started with unflagging the external HD I forgot to edit fstab.
UUID=c0d76448-59ba-48e6-b5e7-d5ed878a3193 / ext4 defaults 0 1
/swapfile swap swap defaults 0 0
tmpfs /tmp tmpfs noatime,mode=1777 0 0
/dev/sdb1 /media/pjw/ ntfs users 0 0
/dev/mapper/luks-d8f38af3-83a8-4dd7-a6e9-48e280799831 none ext4 users 0 0
So cleaned up fstab by removing the lines for sdb1 and luks.
UUID=c0d76448-59ba-48e6-b5e7-d5ed878a3193 / ext4 defaults 0 1
/swapfile swap swap defaults 0 0
tmpfs /tmp tmpfs noatime,mode=1777 0 0
And now initial boot-up is blistering fast, with a slight delay until login screen.
Mounting issues for the external drive are gone too.
Check on the external drive showed it to be fine. Still going to move its contents to a fresh drive.
Iāll do some more digging - like for the ārestart iconā keeping popping up - but for now it seems like a FU on my part. 
Your help was effective and very much appreciated.
You guys rock!
1 Like