Long boot up time with Ubuntu 24.04.3

I am running Ubuntu 24.04.3 with Gnome Flashback x64

A few weeks ago, we had a power outage after which I experienced exceptionally long boot times (over 15 minutes or more). Another oddity is the first screen I see has some system bios images (2) along with the normal Ubuntu rotating circle.

Before the power failure, usual boot time was in the 1 minute range. Where can I find something that can help me see what is causing this, and what should I be looking for generally? I have looked in /var/log at several of the logs, but I’m not sure what I’m looking for.

Any help would be appreciated

Is this a standalone install or dual-booting?

Do you have more than one drive?

Have you run either SMART checks or filesystem checks?

Show us the output, wrapped with code tags, for the following commands:

systemd-analyze blame | head -20
journalctl -b -p 3 | tail -20

Standard desk top install, no dual boot;

I assume you are speaking of non-system drives, and the answer is yes;

I have run smart check on all drives and they are OK;

systemd-analyze blame | head -20
2min 3.208s smartmontools.service
1min 2.745s mysql.service
    37.932s e2scrub_reap.service
    32.366s plymouth-quit-wait.service
    15.478s media-butch-Ubuntu_Data_Back.mount
    13.532s snapd.seeded.service
    13.160s snapd.service
    10.590s dev-sdb3.device
     9.965s NetworkManager.service
     8.916s accounts-daemon.service
     7.709s udisks2.service
     7.540s gnome-remote-desktop.service
     7.352s power-profiles-daemon.service
     7.309s polkit.service
     5.757s avahi-daemon.service
     5.739s dbus.service
     5.514s switcheroo-control.service
     5.513s thermald.service
     5.423s dev-loop10.device
     5.411s dev-loop9.device

journalctl -b -p 3 | tail -20
Oct 06 18:42:09 cp1 systemd-fstab-generator[2511]: Failed to create unit file '/run/systemd/generator/media-Data.mount', as it already exists. Duplicate entry in '/etc/fstab'?
Oct 06 18:42:09 cp1 (sd-exec-[2498]: /usr/lib/systemd/system-generators/systemd-fstab-generator failed with exit status 1.
Oct 06 18:42:18 cp1 kernel: sd 8:0:0:0: [sdf] tag#0 timing out command, waited 30s
Oct 06 18:42:20 cp1 nologin[2894]: Attempted login by UNKNOWN (UID: 7) on UNKNOWN
Oct 06 18:42:22 cp1 gdm-autologin][2633]: gkr-pam: couldn't unlock the login keyring.
Oct 06 18:42:22 cp1 gdm3[2626]: Gdm: on_display_added: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed
Oct 06 18:42:22 cp1 gdm3[2626]: Gdm: on_display_removed: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed
Oct 06 18:42:32 cp1 systemd-fstab-generator[3636]: Failed to create unit file '/run/systemd/generator/media-Data.mount', as it already exists. Duplicate entry in '/etc/fstab'?
Oct 06 18:42:32 cp1 (sd-exec-[3623]: /usr/lib/systemd/system-generators/systemd-fstab-generator failed with exit status 1.
Oct 06 18:42:40 cp1 systemd[2851]: Failed to start app-gnome-gnome\x2dkeyring\x2dpkcs11-3901.scope - Application launched by gnome-session-binary.
Oct 06 18:42:40 cp1 systemd[2851]: Failed to start app-gnome-gnome\x2dkeyring\x2dsecrets-3903.scope - Application launched by gnome-session-binary.
Oct 06 18:42:57 cp1 kernel: sd 8:0:0:0: [sdf] tag#0 timing out command, waited 60s
Oct 06 18:43:05 cp1 systemd-fstab-generator[4786]: Failed to create unit file '/run/systemd/generator/media-Data.mount', as it already exists. Duplicate entry in '/etc/fstab'?
Oct 06 18:43:05 cp1 (sd-exec-[4773]: /usr/lib/systemd/system-generators/systemd-fstab-generator failed with exit status 1.
Oct 06 18:43:14 cp1 kernel: [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership
Oct 06 18:43:57 cp1 kernel: sd 8:0:0:0: [sdf] tag#0 timing out command, waited 60s
Oct 06 18:43:57 cp1 systemd[1]: Failed to start smartmontools.service - Self Monitoring and Reporting Technology (SMART) Daemon.
Oct 06 18:45:43 cp1 kernel: [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership
Oct 07 00:00:10 cp1 systemd[1]: Failed to start logrotate.service - Rotate log files.
Oct 08 00:00:05 cp1 systemd[1]: Failed to start logrotate.service - Rotate log files.

Is sdf your backup drive?

Seems to be hanging. Try unplugging/detaching and then reboot to see if the slow boot resolves.

Also post output from cat /etc/fstab please.

Disable both these services and prevent them from autostarting at boot.

Oct 06 18:42:18 cp1 kernel: sd 8:0:0:0: [sdf] tag#0 timing out command, waited 30s

Also, as mentioned by @rubi1200, double check that your /etc/fstab is configured correctly for this disk.

Here is my fstab:

$ cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/sda3 during installation
UUID=c98e60b4-4a86-46ee-9009-30cee2eed7c5 /               ext4    errors=remount-ro 0       1
# /boot/efi was on /dev/sda2 during installation
UUID=B476-D2E6  /boot/efi       vfat    umask=0077      0       1
/swapfile                                 none            swap    sw              0       0
#Entry for /dev/sdb :
#Entry for /dev/sdc1 :
# Corrected Entry for External USB Data Backup Drive
UUID=394833f8-06e8-40fe-90cd-a9e669810b5b /media/butch/Ubuntu_Data_Back	auto nosuid,nodev,nofail,x-gvfs-show 0 0 /media/butch/Ubuntu_Data_Back	auto nosuid,nodev,nofail,x-gvfs-show 0 0
# Entry for External USB Data Backup Drive
# UUID=c4f82388-713a-4b9a-9f50-e36446e17520 /media/butch/Ubuntu_Data_Back	auto nosuid,nodev,nofail,x-gvfs-show 0 0
#Entry for NFS Server on drive g on cp2
192.168.1.111:/media/brenda/Ubuntu_Data_Back /nfs/Ubuntu_Data_Back nfs vers=3,auto,nofail,noatime,nolock,intr,tcp,actimeo=1800 0 0
#Entry for NFS Server shared documents on cp2
192.168.1.111:/media/brenda/cp2_data /nfs/cp2_data nfs vers=3,auto,nofail,noatime,nolock,intr,tcp,actimeo=1800 0 0
/dev/disk/by-id/wwn-0x50014ee26bdbfdb4-part1 /mnt/wwn-0x50014ee26bdbfdb4-part1 auto nosuid,nodev,nofail,noauto,x-gvfs-show 0 0
UUID=6f18006e-62f2-4a18-8582-17b9d6480fcd /media/Data ext4 errors=remount-ro,x-gvfs-show 0 1
UUID=21af4737-c65b-4b2b-8db8-51d592789719 /media/Data_Two ext4 errors=remount-ro,x-gvfs-show 0 1
/dev/disk/by-uuid/6f18006e-62f2-4a18-8582-17b9d6480fcd /media/Data auto nosuid,nodev,nofail,x-gvfs-show 0 0

I think there are some extraneous entries for the following:

/media/Data (this is my user data drive)
/media/butch/Ubuntu_Data_Back (this is a backup of my user data)

sdf is a multi-partition (4) drive that contains backups of system and home in two of the partitions.

I will disable them to see if that improves boot time on next reboot. If so, I will create a procedure to start them after boot and disable them before shutdown and/or reboot.

Your fstab appears to show two duplicate /media/Data entries for the same UUID.

I recommend commenting one of them out.

There also seems to be a malformed Ubuntu_Data_Back line with two entries merged in one?

Again, I would suggest editing that to only have one clean line.

Reboot and test if the slowness disappears or improves.

I cleaned up fstab. Now boot shows the normal Ubuntu image while booting. I had to leave it before it completed, so I’m not sure how long it took to boot. Is there a log I can look at to see the time duration for this boot?

Try this:
systemd-analyze time

systemd-analyze time
Startup finished in 18min 8.359s (kernel) + 2min 1.789s (userspace) = 20min 10.149s
graphical.target reached after 2min 1.677s in userspace.

Seens as if I still have some work to do.

Did you test disabling the services @tea-for-one suggested?

If not, perhaps try that next and then run the command again to check.

The preceding times were with the services disabled.

Power on and boot into Ubuntu 24.04
As the process starts, press Esc
This should show text output on your monitor
When the boot process hesitates or stalls, you may be able to identify a reason for the delay?

The first part, kernel, is not normal whereas the userspace time seems about right.

Something hardware or kernel device related is likely the culprit here (at least that is what I would suspect).

Let’s take a look at the output from these commands and see if it is possible to narrow this down:

sudo dmesg --ctime | grep -E "error|fail|timeout|reset"
sudo dmesg --ctime | grep sd
[Fri Oct 10 13:46:48 2025] pcieport 0000:00:1b.3: DPC: error containment capabilities: Int Msg #0, RPExt+ PoisonedTLP+ SwTrigger+ RP PIO Log 4, DL_ActiveErr+
[Fri Oct 10 13:46:48 2025] pcieport 0000:00:1c.1: DPC: error containment capabilities: Int Msg #0, RPExt+ PoisonedTLP+ SwTrigger+ RP PIO Log 4, DL_ActiveErr+
[Fri Oct 10 13:46:50 2025] ACPI: \_TZ_.TZ10: _PSL evaluation failure
[Fri Oct 10 13:46:50 2025] ACPI: \_TZ_.TZ20: _PSL evaluation failure
[Fri Oct 10 13:46:53 2025] sd 6:0:0:0: Power-on or device reset occurred
[Fri Oct 10 13:46:53 2025] sd 6:0:0:1: Power-on or device reset occurred
[Fri Oct 10 13:50:53 2025] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[Fri Oct 10 13:50:53 2025] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[Fri Oct 10 13:52:56 2025] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[Fri Oct 10 13:52:56 2025] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[Fri Oct 10 13:52:56 2025] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[Fri Oct 10 13:52:56 2025] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[Fri Oct 10 13:54:59 2025] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[Fri Oct 10 13:54:59 2025] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[Fri Oct 10 13:54:59 2025] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[Fri Oct 10 13:54:59 2025] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[Fri Oct 10 13:55:53 2025] sd 9:0:0:0: [sde] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_OK
[Fri Oct 10 14:01:53 2025] sd 9:0:0:0: [sde] Test WP failed, assume Write Enabled
[Fri Oct 10 14:04:53 2025] sd 9:0:0:0: [sde] Asking for cache data failed
[Fri Oct 10 14:05:13 2025] vc032x: probe of 1-7.4:1.0 failed with error -32
[Fri Oct 10 14:06:22 2025] vboxdrv: module verification failed: signature and/or required key missing - tainting kernel
[Fri Oct 10 14:06:50 2025] usb 1-7.4: reset high-speed USB device number 11 using xhci_hcd
[Fri Oct 10 14:07:12 2025] EXT4-fs (sdf1): warning: mounting fs with errors, running e2fsck is recommended
[Fri Oct 10 14:12:32 2025] EXT4-fs (sdf1): error count since last fsck: 22
[Fri Oct 10 14:12:32 2025] EXT4-fs (sdf1): initial error at time 1665768587: htree_dirblock_to_tree:1044: inode 65799849
[Fri Oct 10 14:12:32 2025] EXT4-fs (sdf1): last error at time 1665979960: htree_dirblock_to_tree:1044: inode 65799850
[Fri Oct 10 14:42:33 2025] usb 1-2.1: reset high-speed USB device number 4 using xhci_hcd
[Sat Oct 11 14:19:48 2025] EXT4-fs (sdf1): error count since last fsck: 22
[Sat Oct 11 14:19:48 2025] EXT4-fs (sdf1): initial error at time 1665768587: htree_dirblock_to_tree:1044: inode 65799849
[Sat Oct 11 14:19:48 2025] EXT4-fs (sdf1): last error at time 1665979960: htree_dirblock_to_tree:1044: inode 65799850
[Sun Oct 12 00:13:43 2025] evince[51073]: segfault at 92aa0 ip 0000755fde23312f sp 00007fff7d2ef4c0 error 4 in libatk-1.0.so.0.25209.1[755fde22a000+10000] likely on CPU 10 (core 2, socket 0)
[Sun Oct 12 14:47:49 2025] EXT4-fs (sdf1): error count since last fsck: 22
[Sun Oct 12 14:47:49 2025] EXT4-fs (sdf1): initial error at time 1665768587: htree_dirblock_to_tree:1044: inode 65799849
[Sun Oct 12 14:47:49 2025] EXT4-fs (sdf1): last error at time 1665979960: htree_dirblock_to_tree:1044: inode 65799850
sudo dmesg --ctime | grep sd
[Fri Oct 10 13:46:46 2025] ACPI: SSDT 0x000000003DF73000 00203B (v02 CpuRef CpuSsdt  00003000 INTL 20160527)
[Fri Oct 10 13:46:46 2025] ACPI: SSDT 0x000000003DF1D000 0031F9 (v02 SaSsdt SaSsdt   00003000 INTL 20160527)
[Fri Oct 10 13:46:46 2025] ACPI: SSDT 0x000000003DF19000 003EC6 (v02 Intel  PegSsdt  00001000 INTL 20160527)
[Fri Oct 10 13:46:46 2025] ACPI: SSDT 0x000000003DF10000 003961 (v02 INTEL  xh_cmsd4 00000000 INTL 20160527)
[Fri Oct 10 13:46:48 2025] ACPI: SSDT 0xFFFF8D0E4116F200 0000FC (v02 PmRef  Cpu0Psd  00003000 INTL 20160527)
[Fri Oct 10 13:46:48 2025] ACPI: SSDT 0xFFFF8D0E427F8000 000D22 (v02 PmRef  ApPsd    00003000 INTL 20160527)
[Fri Oct 10 13:46:50 2025] ahci 0000:00:17.0: flags: 64bit ncq sntf clo only pio slum part ems deso sadm sds apst 
[Fri Oct 10 13:46:51 2025] sd 2:0:0:0: Attached scsi generic sg2 type 0
[Fri Oct 10 13:46:51 2025] sd 2:0:0:0: [sda] 11721045168 512-byte logical blocks: (6.00 TB/5.46 TiB)
[Fri Oct 10 13:46:51 2025] sd 2:0:0:0: [sda] 4096-byte physical blocks
[Fri Oct 10 13:46:51 2025] sd 2:0:0:0: [sda] Write Protect is off
[Fri Oct 10 13:46:51 2025] sd 2:0:0:0: [sda] Mode Sense: 00 3a 00 00
[Fri Oct 10 13:46:51 2025] sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[Fri Oct 10 13:46:51 2025] sd 2:0:0:0: [sda] Preferred minimum I/O size 4096 bytes
[Fri Oct 10 13:46:51 2025] sd 3:0:0:0: Attached scsi generic sg3 type 0
[Fri Oct 10 13:46:51 2025] sd 3:0:0:0: [sdb] 3907029168 512-byte logical blocks: (2.00 TB/1.82 TiB)
[Fri Oct 10 13:46:51 2025] sd 3:0:0:0: [sdb] 4096-byte physical blocks
[Fri Oct 10 13:46:51 2025] sd 3:0:0:0: [sdb] Write Protect is off
[Fri Oct 10 13:46:51 2025] sd 3:0:0:0: [sdb] Mode Sense: 00 3a 00 00
[Fri Oct 10 13:46:51 2025] sd 3:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[Fri Oct 10 13:46:51 2025] sd 3:0:0:0: [sdb] Preferred minimum I/O size 4096 bytes
[Fri Oct 10 13:46:51 2025] sd 4:0:0:0: Attached scsi generic sg4 type 0
[Fri Oct 10 13:46:51 2025] sd 4:0:0:0: [sdc] 2930277168 512-byte logical blocks: (1.50 TB/1.36 TiB)
[Fri Oct 10 13:46:51 2025] sd 4:0:0:0: [sdc] Write Protect is off
[Fri Oct 10 13:46:51 2025] sd 4:0:0:0: [sdc] Mode Sense: 00 3a 00 00
[Fri Oct 10 13:46:51 2025] sd 4:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[Fri Oct 10 13:46:51 2025] sd 4:0:0:0: [sdc] Preferred minimum I/O size 512 bytes
[Fri Oct 10 13:46:51 2025] sd 5:0:0:0: Attached scsi generic sg5 type 0
[Fri Oct 10 13:46:51 2025] sd 5:0:0:0: [sdd] 7814037168 512-byte logical blocks: (4.00 TB/3.64 TiB)
[Fri Oct 10 13:46:51 2025] sd 5:0:0:0: [sdd] 4096-byte physical blocks
[Fri Oct 10 13:46:51 2025] sd 5:0:0:0: [sdd] Write Protect is off
[Fri Oct 10 13:46:51 2025] sd 5:0:0:0: [sdd] Mode Sense: 00 3a 00 00
[Fri Oct 10 13:46:51 2025] sd 5:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[Fri Oct 10 13:46:51 2025] sd 5:0:0:0: [sdd] Preferred minimum I/O size 4096 bytes
[Fri Oct 10 13:46:51 2025]  sdc: sdc1
[Fri Oct 10 13:46:51 2025] sd 4:0:0:0: [sdc] Attached SCSI disk
[Fri Oct 10 13:46:51 2025] sd 2:0:0:0: [sda] Attached SCSI disk
[Fri Oct 10 13:46:51 2025] sd 5:0:0:0: [sdd] Attached SCSI disk
[Fri Oct 10 13:46:51 2025]  sdb: sdb1 sdb2 sdb3
[Fri Oct 10 13:46:51 2025] sd 3:0:0:0: [sdb] Attached SCSI disk
[Fri Oct 10 13:46:53 2025] sd 9:0:0:0: Attached scsi generic sg6 type 0
[Fri Oct 10 13:46:53 2025] sd 8:0:0:0: Attached scsi generic sg7 type 0
[Fri Oct 10 13:46:53 2025] sd 8:0:0:0: [sdf] Very big device. Trying to use READ CAPACITY(16).
[Fri Oct 10 13:46:53 2025] sd 7:0:0:0: Attached scsi generic sg8 type 0
[Fri Oct 10 13:46:53 2025] sd 7:0:0:0: [sdg] Very big device. Trying to use READ CAPACITY(16).
[Fri Oct 10 13:46:53 2025] sd 9:0:0:0: [sde] Unit Not Ready
[Fri Oct 10 13:46:53 2025] sd 9:0:0:0: [sde] Sense Key : Hardware Error [current] 
[Fri Oct 10 13:46:53 2025] sd 9:0:0:0: [sde] ASC=0x30 <<vendor>>ASCQ=0x81 
[Fri Oct 10 13:46:53 2025] sd 7:0:0:0: [sdg] 7813969920 512-byte logical blocks: (4.00 TB/3.64 TiB)
[Fri Oct 10 13:46:53 2025] sd 7:0:0:0: [sdg] 4096-byte physical blocks
[Fri Oct 10 13:46:53 2025] sd 7:0:0:0: [sdg] Write Protect is off
[Fri Oct 10 13:46:53 2025] sd 7:0:0:0: [sdg] Mode Sense: 47 00 10 08
[Fri Oct 10 13:46:53 2025] sd 7:0:0:0: [sdg] No Caching mode page found
[Fri Oct 10 13:46:53 2025] sd 7:0:0:0: [sdg] Assuming drive cache: write through
[Fri Oct 10 13:46:53 2025] sd 6:0:0:0: Attached scsi generic sg9 type 0
[Fri Oct 10 13:46:53 2025] sd 6:0:0:1: Attached scsi generic sg10 type 0
[Fri Oct 10 13:46:53 2025] sd 6:0:0:0: Power-on or device reset occurred
[Fri Oct 10 13:46:53 2025] sd 6:0:0:0: [sdh] Media removed, stopped polling
[Fri Oct 10 13:46:53 2025] sd 6:0:0:0: [sdh] Attached SCSI removable disk
[Fri Oct 10 13:46:53 2025] sd 6:0:0:1: Power-on or device reset occurred
[Fri Oct 10 13:46:53 2025] sd 6:0:0:1: [sdi] Media removed, stopped polling
[Fri Oct 10 13:46:53 2025] sd 6:0:0:1: [sdi] Attached SCSI removable disk
[Fri Oct 10 13:46:53 2025]  sdg: sdg1
[Fri Oct 10 13:46:53 2025] sd 7:0:0:0: [sdg] Attached SCSI disk
[Fri Oct 10 13:46:57 2025] sd 8:0:0:0: [sdf] 15627986944 512-byte logical blocks: (8.00 TB/7.28 TiB)
[Fri Oct 10 13:46:57 2025] sd 8:0:0:0: [sdf] 4096-byte physical blocks
[Fri Oct 10 13:46:57 2025] sd 8:0:0:0: [sdf] Write Protect is off
[Fri Oct 10 13:46:57 2025] sd 8:0:0:0: [sdf] Mode Sense: 47 00 10 08
[Fri Oct 10 13:46:57 2025] sd 8:0:0:0: [sdf] No Caching mode page found
[Fri Oct 10 13:46:57 2025] sd 8:0:0:0: [sdf] Assuming drive cache: write through
[Fri Oct 10 13:46:57 2025]  sdf: sdf1 sdf2 sdf3 sdf4
[Fri Oct 10 13:46:57 2025] sd 8:0:0:0: [sdf] Attached SCSI disk
[Fri Oct 10 13:49:53 2025] sd 9:0:0:0: [sde] tag#0 timing out command, waited 180s
[Fri Oct 10 13:52:53 2025] sd 9:0:0:0: [sde] tag#0 timing out command, waited 180s
[Fri Oct 10 13:55:53 2025] sd 9:0:0:0: [sde] tag#0 timing out command, waited 180s
[Fri Oct 10 13:55:53 2025] sd 9:0:0:0: [sde] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_OK
[Fri Oct 10 13:55:53 2025] sd 9:0:0:0: [sde] Sense Key : Hardware Error [current] 
[Fri Oct 10 13:55:53 2025] sd 9:0:0:0: [sde] ASC=0x30 <<vendor>>ASCQ=0x81 
[Fri Oct 10 13:58:53 2025] sd 9:0:0:0: [sde] tag#0 timing out command, waited 180s
[Fri Oct 10 13:58:53 2025] sd 9:0:0:0: [sde] 0 512-byte logical blocks: (0 B/0 B)
[Fri Oct 10 13:58:53 2025] sd 9:0:0:0: [sde] 0-byte physical blocks
[Fri Oct 10 14:01:53 2025] sd 9:0:0:0: [sde] tag#0 timing out command, waited 180s
[Fri Oct 10 14:01:53 2025] sd 9:0:0:0: [sde] Test WP failed, assume Write Enabled
[Fri Oct 10 14:04:53 2025] sd 9:0:0:0: [sde] tag#0 timing out command, waited 180s
[Fri Oct 10 14:04:53 2025] sd 9:0:0:0: [sde] Asking for cache data failed
[Fri Oct 10 14:04:53 2025] sd 9:0:0:0: [sde] Assuming drive cache: write through
[Fri Oct 10 14:04:53 2025] sd 9:0:0:0: [sde] Attached SCSI disk
[Fri Oct 10 14:04:53 2025] EXT4-fs (sdb3): mounted filesystem c98e60b4-4a86-46ee-9009-30cee2eed7c5 ro with ordered data mode. Quota mode: none.
[Fri Oct 10 14:05:00 2025] systemd[1]: Mounting proc-fs-nfsd.mount - NFSD configuration filesystem...
[Fri Oct 10 14:05:01 2025] EXT4-fs (sdb3): re-mounted c98e60b4-4a86-46ee-9009-30cee2eed7c5 r/w. Quota mode: none.
[Fri Oct 10 14:05:14 2025] EXT4-fs (sdg1): mounted filesystem 394833f8-06e8-40fe-90cd-a9e669810b5b r/w with ordered data mode. Quota mode: none.
[Fri Oct 10 14:05:23 2025] sd 9:0:0:0: [sde] tag#0 timing out command, waited 30s
[Fri Oct 10 14:05:27 2025] sd 9:0:0:0: [sde] tag#0 timing out command, waited 15s
[Fri Oct 10 14:05:38 2025] sd 9:0:0:0: [sde] tag#0 timing out command, waited 15s
[Fri Oct 10 14:05:42 2025] sd 9:0:0:0: [sde] tag#0 timing out command, waited 15s
[Fri Oct 10 14:05:57 2025] sd 9:0:0:0: [sde] tag#0 timing out command, waited 15s
[Fri Oct 10 14:05:58 2025] EXT4-fs (sda): mounted filesystem 21af4737-c65b-4b2b-8db8-51d592789719 r/w with ordered data mode. Quota mode: none.
[Fri Oct 10 14:06:08 2025] sd 9:0:0:0: [sde] tag#0 timing out command, waited 30s
[Fri Oct 10 14:06:12 2025] sd 9:0:0:0: [sde] tag#0 timing out command, waited 15s
[Fri Oct 10 14:06:12 2025] EXT4-fs (sdd): mounted filesystem 6f18006e-62f2-4a18-8582-17b9d6480fcd r/w with ordered data mode. Quota mode: none.
[Fri Oct 10 14:06:22 2025] NFSD: Using nfsdcld client tracking operations.
[Fri Oct 10 14:06:23 2025] sd 9:0:0:0: [sde] tag#0 timing out command, waited 15s
[Fri Oct 10 14:06:23 2025] audit: type=1400 audit(1760119583.311:222): apparmor="DENIED" operation="capable" class="cap" profile="/usr/sbin/cupsd" pid=2621 comm="cupsd" capability=12  capname="net_admin"
[Fri Oct 10 14:06:23 2025] EXT4-fs (sdc1): mounted filesystem f3676964-3fac-407e-88f9-9b345f83c687 r/w with ordered data mode. Quota mode: none.
[Fri Oct 10 14:06:30 2025] audit: type=1326 audit(1760119590.150:223): auid=4294967295 uid=0 gid=0 ses=4294967295 subj=snap.cups.cupsd pid=3094 comm="cupsd" exe="/snap/cups/1112/sbin/cupsd" sig=0 arch=c000003e syscall=93 compat=0 ip=0x750d8170ba9b code=0x50000
[Fri Oct 10 14:06:30 2025] audit: type=1326 audit(1760119590.872:224): auid=4294967295 uid=0 gid=0 ses=4294967295 subj=snap.cups.cupsd pid=3095 comm="cups-proxyd" exe="/snap/cups/1112/sbin/cups-proxyd" sig=0 arch=c000003e syscall=314 compat=0 ip=0x70a4ea12388d code=0x50000
[Fri Oct 10 14:06:31 2025] audit: type=1326 audit(1760119591.462:225): auid=4294967295 uid=0 gid=0 ses=4294967295 subj=snap.cups.cupsd pid=3094 comm="cupsd" exe="/snap/cups/1112/sbin/cupsd" sig=0 arch=c000003e syscall=93 compat=0 ip=0x750d8170ba9b code=0x50000
[Fri Oct 10 14:07:12 2025] EXT4-fs (sdf1): warning: mounting fs with errors, running e2fsck is recommended
[Fri Oct 10 14:07:12 2025] EXT4-fs (sdf4): mounted filesystem d1f06380-26cb-4b1a-9733-3ba2c18b67b5 r/w with ordered data mode. Quota mode: none.
[Fri Oct 10 14:07:12 2025] EXT4-fs (sdf1): mounted filesystem 90c54104-6a06-4dab-ac09-0bea82aa0ec2 r/w with ordered data mode. Quota mode: none.
[Fri Oct 10 14:07:12 2025] EXT4-fs (sdf3): mounted filesystem d13cc3db-7139-4024-8ff2-0493654d637d r/w with ordered data mode. Quota mode: none.
[Fri Oct 10 14:07:12 2025] EXT4-fs (sdf2): mounted filesystem c2f57970-8eb9-4ea3-b771-5633e0d4faec r/w with ordered data mode. Quota mode: none.
[Fri Oct 10 14:12:32 2025] EXT4-fs (sdf1): error count since last fsck: 22
[Fri Oct 10 14:12:32 2025] EXT4-fs (sdf1): initial error at time 1665768587: htree_dirblock_to_tree:1044: inode 65799849
[Fri Oct 10 14:12:32 2025] EXT4-fs (sdf1): last error at time 1665979960: htree_dirblock_to_tree:1044: inode 65799850
[Fri Oct 10 18:15:26 2025] capability: warning: `gvfsd-admin' uses 32-bit capabilities (legacy support in use)
[Sat Oct 11 00:00:08 2025] audit: type=1400 audit(1760155208.100:510): apparmor="DENIED" operation="capable" class="cap" profile="/usr/sbin/cupsd" pid=39924 comm="cupsd" capability=12  capname="net_admin"
[Sat Oct 11 14:19:48 2025] EXT4-fs (sdf1): error count since last fsck: 22
[Sat Oct 11 14:19:48 2025] EXT4-fs (sdf1): initial error at time 1665768587: htree_dirblock_to_tree:1044: inode 65799849
[Sat Oct 11 14:19:48 2025] EXT4-fs (sdf1): last error at time 1665979960: htree_dirblock_to_tree:1044: inode 65799850
[Sun Oct 12 00:00:10 2025] audit: type=1400 audit(1760241608.900:649): apparmor="DENIED" operation="capable" class="cap" profile="/usr/sbin/cupsd" pid=87076 comm="cupsd" capability=12  capname="net_admin"
[Sun Oct 12 00:13:31 2025] audit: type=1400 audit(1760242410.320:651): apparmor="DENIED" operation="connect" class="file" profile="/usr/bin/evince" name="/run/user/1000/gvfsd/socket-zvb4pHMR" pid=51073 comm="evince" requested_mask="wr" denied_mask="wr" fsuid=1000 ouid=1000
[Sun Oct 12 00:13:31 2025] audit: type=1400 audit(1760242410.321:652): apparmor="DENIED" operation="connect" class="file" profile="/usr/bin/evince" name="/run/user/1000/gvfsd/socket-KtEMi1UP" pid=51073 comm="evince" requested_mask="wr" denied_mask="wr" fsuid=1000 ouid=1000
[Sun Oct 12 00:13:31 2025] audit: type=1400 audit(1760242410.399:653): apparmor="DENIED" operation="connect" class="file" profile="/usr/bin/evince" name="/run/user/1000/gvfsd/socket-B4biFTQp" pid=51073 comm="pool-evince" requested_mask="wr" denied_mask="wr" fsuid=1000 ouid=1000
[Sun Oct 12 00:13:31 2025] audit: type=1400 audit(1760242410.402:654): apparmor="DENIED" operation="connect" class="file" profile="/usr/bin/evince" name="/run/user/1000/gvfsd/socket-4cMDwYzo" pid=51073 comm="evince" requested_mask="wr" denied_mask="wr" fsuid=1000 ouid=1000
[Sun Oct 12 00:13:31 2025] audit: type=1400 audit(1760242410.403:655): apparmor="DENIED" operation="connect" class="file" profile="/usr/bin/evince" name="/run/user/1000/gvfsd/socket-R4rxXUx0" pid=51073 comm="evince" requested_mask="wr" denied_mask="wr" fsuid=1000 ouid=1000
[Sun Oct 12 00:13:31 2025] audit: type=1400 audit(1760242410.404:656): apparmor="DENIED" operation="connect" class="file" profile="/usr/bin/evince" name="/run/user/1000/gvfsd/socket-H2XjYJvb" pid=51073 comm="evince" requested_mask="wr" denied_mask="wr" fsuid=1000 ouid=1000
[Sun Oct 12 00:13:31 2025] audit: type=1400 audit(1760242410.571:657): apparmor="DENIED" operation="connect" class="file" profile="/usr/bin/evince" name="/run/user/1000/gvfsd/socket-6u9rZ6of" pid=51073 comm="pool-evince" requested_mask="wr" denied_mask="wr" fsuid=1000 ouid=1000
[Sun Oct 12 00:17:41 2025] audit: type=1400 audit(1760242660.623:658): apparmor="DENIED" operation="connect" class="file" profile="/usr/bin/evince" name="/run/user/1000/gvfsd/socket-XUNMBItA" pid=87759 comm="evince" requested_mask="wr" denied_mask="wr" fsuid=1000 ouid=1000
[Sun Oct 12 00:17:41 2025] audit: type=1400 audit(1760242660.624:659): apparmor="DENIED" operation="connect" class="file" profile="/usr/bin/evince" name="/run/user/1000/gvfsd/socket-ySMIPcEe" pid=87759 comm="evince" requested_mask="wr" denied_mask="wr" fsuid=1000 ouid=1000
[Sun Oct 12 00:17:42 2025] audit: type=1400 audit(1760242660.698:660): apparmor="DENIED" operation="connect" class="file" profile="/usr/bin/evince" name="/run/user/1000/gvfsd/socket-NkRAPF3t" pid=87759 comm="pool-evince" requested_mask="wr" denied_mask="wr" fsuid=1000 ouid=1000
[Sun Oct 12 00:17:42 2025] audit: type=1400 audit(1760242660.702:661): apparmor="DENIED" operation="connect" class="file" profile="/usr/bin/evince" name="/run/user/1000/gvfsd/socket-v9Mxjo4C" pid=87759 comm="evince" requested_mask="wr" denied_mask="wr" fsuid=1000 ouid=1000
[Sun Oct 12 00:17:42 2025] audit: type=1400 audit(1760242660.703:662): apparmor="DENIED" operation="connect" class="file" profile="/usr/bin/evince" name="/run/user/1000/gvfsd/socket-xIRcfEo5" pid=87759 comm="evince" requested_mask="wr" denied_mask="wr" fsuid=1000 ouid=1000
[Sun Oct 12 00:17:42 2025] audit: type=1400 audit(1760242660.703:663): apparmor="DENIED" operation="connect" class="file" profile="/usr/bin/evince" name="/run/user/1000/gvfsd/socket-zP5jPJYE" pid=87759 comm="evince" requested_mask="wr" denied_mask="wr" fsuid=1000 ouid=1000
[Sun Oct 12 00:17:42 2025] audit: type=1400 audit(1760242660.771:664): apparmor="DENIED" operation="connect" class="file" profile="/usr/bin/evince" name="/run/user/1000/gvfsd/socket-uxY3x47j" pid=87759 comm="pool-evince" requested_mask="wr" denied_mask="wr" fsuid=1000 ouid=1000
[Sun Oct 12 13:29:31 2025] audit: type=1400 audit(1760290169.838:675): apparmor="DENIED" operation="connect" class="file" profile="/usr/bin/evince" name="/run/user/1000/gvfsd/socket-M3dhDbYQ" pid=112240 comm="evince" requested_mask="wr" denied_mask="wr" fsuid=1000 ouid=1000
[Sun Oct 12 13:29:31 2025] audit: type=1400 audit(1760290169.839:676): apparmor="DENIED" operation="connect" class="file" profile="/usr/bin/evince" name="/run/user/1000/gvfsd/socket-hCgqV659" pid=112240 comm="evince" requested_mask="wr" denied_mask="wr" fsuid=1000 ouid=1000
[Sun Oct 12 13:29:31 2025] audit: type=1400 audit(1760290169.914:677): apparmor="DENIED" operation="connect" class="file" profile="/usr/bin/evince" name="/run/user/1000/gvfsd/socket-kU8GPvwe" pid=112240 comm="pool-evince" requested_mask="wr" denied_mask="wr" fsuid=1000 ouid=1000
[Sun Oct 12 13:29:31 2025] audit: type=1400 audit(1760290169.918:678): apparmor="DENIED" operation="connect" class="file" profile="/usr/bin/evince" name="/run/user/1000/gvfsd/socket-7QHyIP06" pid=112240 comm="evince" requested_mask="wr" denied_mask="wr" fsuid=1000 ouid=1000
[Sun Oct 12 13:29:31 2025] audit: type=1400 audit(1760290169.919:679): apparmor="DENIED" operation="connect" class="file" profile="/usr/bin/evince" name="/run/user/1000/gvfsd/socket-zD1V7EPw" pid=112240 comm="evince" requested_mask="wr" denied_mask="wr" fsuid=1000 ouid=1000
[Sun Oct 12 13:29:31 2025] audit: type=1400 audit(1760290169.919:680): apparmor="DENIED" operation="connect" class="file" profile="/usr/bin/evince" name="/run/user/1000/gvfsd/socket-IQMbiJAJ" pid=112240 comm="evince" requested_mask="wr" denied_mask="wr" fsuid=1000 ouid=1000
[Sun Oct 12 13:29:32 2025] audit: type=1400 audit(1760290170.147:681): apparmor="DENIED" operation="connect" class="file" profile="/usr/bin/evince" name="/run/user/1000/gvfsd/socket-cTzIyxsu" pid=112240 comm="pool-evince" requested_mask="wr" denied_mask="wr" fsuid=1000 ouid=1000
[Sun Oct 12 14:47:49 2025] EXT4-fs (sdf1): error count since last fsck: 22
[Sun Oct 12 14:47:49 2025] EXT4-fs (sdf1): initial error at time 1665768587: htree_dirblock_to_tree:1044: inode 65799849
[Sun Oct 12 14:47:49 2025] EXT4-fs (sdf1): last error at time 1665979960: htree_dirblock_to_tree:1044: inode 65799850
[Sun Oct 12 15:05:22 2025] audit: type=1400 audit(1760295920.480:703): apparmor="DENIED" operation="connect" class="file" profile="/usr/bin/evince" name="/run/user/1000/gvfsd/socket-Avf1RSvM" pid=115876 comm="evince" requested_mask="wr" denied_mask="wr" fsuid=1000 ouid=1000
[Sun Oct 12 15:05:22 2025] audit: type=1400 audit(1760295920.480:704): apparmor="DENIED" operation="connect" class="file" profile="/usr/bin/evince" name="/run/user/1000/gvfsd/socket-CtuZaDf7" pid=115876 comm="evince" requested_mask="wr" denied_mask="wr" fsuid=1000 ouid=1000
[Sun Oct 12 15:05:22 2025] audit: type=1400 audit(1760295920.560:705): apparmor="DENIED" operation="connect" class="file" profile="/usr/bin/evince" name="/run/user/1000/gvfsd/socket-s4PSMgkI" pid=115876 comm="pool-evince" requested_mask="wr" denied_mask="wr" fsuid=1000 ouid=1000
[Sun Oct 12 15:05:22 2025] audit: type=1400 audit(1760295920.564:706): apparmor="DENIED" operation="connect" class="file" profile="/usr/bin/evince" name="/run/user/1000/gvfsd/socket-V2aJQFjh" pid=115876 comm="evince" requested_mask="wr" denied_mask="wr" fsuid=1000 ouid=1000
[Sun Oct 12 15:05:22 2025] audit: type=1400 audit(1760295920.565:707): apparmor="DENIED" operation="connect" class="file" profile="/usr/bin/evince" name="/run/user/1000/gvfsd/socket-06w0wEmc" pid=115876 comm="evince" requested_mask="wr" denied_mask="wr" fsuid=1000 ouid=1000
[Sun Oct 12 15:05:22 2025] audit: type=1400 audit(1760295920.565:708): apparmor="DENIED" operation="connect" class="file" profile="/usr/bin/evince" name="/run/user/1000/gvfsd/socket-aC2PD0l3" pid=115876 comm="evince" requested_mask="wr" denied_mask="wr" fsuid=1000 ouid=1000
[Sun Oct 12 15:05:22 2025] audit: type=1400 audit(1760295920.627:709): apparmor="DENIED" operation="connect" class="file" profile="/usr/bin/evince" name="/run/user/1000/gvfsd/socket-ApVCVpDF" pid=115876 comm="pool-evince" requested_mask="wr" denied_mask="wr" fsuid=1000 ouid=1000

Unfortunately, there are some serious issues here.

I will try and break it down clearly and hopefully you can start trying to sort it out and get this fixed.

Your sde drive appears to be failing:

sd 9:0:0:0: [sde] Unit Not Ready
sd 9:0:0:0: [sde] Sense Key : Hardware Error [current]
sd 9:0:0:0: [sde] ASC=0x30 <>ASCQ=0x81
sd 9:0:0:0: [sde] tag#0 timing out command, waited 180s
sd 9:0:0:0: [sde] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_OK
sd 9:0:0:0: [sde] Asking for cache data failed

Your drive at /dev/sde is either physically failing or losing connection intermittently.
The Sense Key : Hardware Error message is a red flag because it indicates that the kernel couldn’t even communicate properly with the device controller.

Recommended actions:

  1. Physically unplug and replug the drive and cable.
  2. Try connecting /dev/sde to a different port (SATA or USB).
  3. Run a SMART test on it

You also have filesystem errors on /dev/sdf1

EXT4-fs (sdf1): warning: mounting fs with errors, running e2fsck is recommended
EXT4-fs (sdf1): error count since last fsck: 22
EXT4-fs (sdf1): initial error at time ...

Despite the fact that there appear to be multiple integrity errors it was still mounted. But there is a risk of data corruption.

sudo umount /dev/sdf1
sudo e2fsck -f -v /dev/sdf1

You must unmount it and run the filesystem check. If you try to do it on a mounted partition it will only make things worse.

If there are multiple partitions then run the check on each unmounted partition separately.

If you manage to get things sorted out, I highly recommend backing up important data as soon as possible before anything else.

If you want to play on the safe side and make sure the correct drives/partitions will be checked then show us this:
lsblk -f

2 Likes

sudo e2fsck -f -v /dev/sdf1
[sudo] password for butch:
e2fsck 1.47.0 (5-Feb-2023)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

 1216582 inodes used (1.00%, out of 122077184)
    9414 non-contiguous files (0.8%)
    2395 non-contiguous directories (0.2%)
         # of inodes with ind/dind/tind blocks: 0/0/0
         Extent depth histogram: 1160396/4517/9

240730943 blocks used (49.30%, out of 488281344)
0 bad blocks
21 large files

  868668 regular files
  292722 directories
       0 character device files
       0 block device files
      73 fifos
 2059545 links
   55106 symbolic links (51575 fast symbolic links)
       4 sockets

 3276118 files

sblk -f
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
loop0
0 100% /snap/bare/5
loop1
0 100% /snap/canonical-livepatch/359
loop2
0 100% /snap/canonical-livepatch/364
loop3
0 100% /snap/chromium/3251
loop4
0 100% /snap/core/17212
loop5
0 100% /snap/core20/2669
loop6
0 100% /snap/core24/1151
loop7
0 100% /snap/cups/1100
loop8
0 100% /snap/core24/1196
loop9
0 100% /snap/firefox/6966
loop10
0 100% /snap/firmware-updater/147
loop11
0 100% /snap/gnome-3-38-2004/143
loop12
0 100% /snap/gnome-42-2204/202
loop13
0 100% /snap/gtk-common-themes/1535
loop14
0 100% /snap/chromium/3217
loop15
0 100% /snap/cups/1112
loop16
0 100% /snap/core20/2599
loop17
0 100% /snap/mesa-2404/912
loop18
0 100% /snap/core22/2045
loop19
0 100% /snap/core22/2133
loop20
0 100% /snap/firefox/6933
loop21
0 100% /snap/gnome-46-2404/125
loop22
0 100% /snap/core/17247
loop23
0 100% /snap/mesa-2404/887
loop24
0 100% /snap/onlyoffice-desktopeditors/604
loop25
0 100% /snap/firmware-updater/167
loop26
0 100% /snap/gnome-42-2204/226
loop27
0 100% /snap/gnome-46-2404/117
loop28
0 100% /snap/onlyoffice-desktopeditors/655
loop29
0 100% /snap/snap-store/1270
loop30
0 100% /snap/snap-store/1300
loop31
0 100% /snap/snapd/24792
loop32
0 100% /snap/snapd/25202
loop33
0 100% /snap/snapd-desktop-integration/253
loop34
0 100% /snap/snapd-desktop-integration/315
loop35
0 100% /snap/spotify/87
loop36
0 100% /snap/spotify/88
sda ext4 1.0 Data_Two 21af4737-c65b-4b2b-8db8-51d592789719 5.1T 0% /media/Data_Two
sdb
├─sdb1

├─sdb2
│ vfat FAT32 B476-D2E6 505.8M 1% /boot/efi
└─sdb3
ext4 1.0 c98e60b4-4a86-46ee-9009-30cee2eed7c5 1.5T 10% /
sdc
└─sdc1
ext4 1.0 Data_Three f3676964-3fac-407e-88f9-9b345f83c687 1.3T 1% /media/butch/Data_Three
sdd ext4 1.0 Data 6f18006e-62f2-4a18-8582-17b9d6480fcd 1.7T 47% /media/Data
sdf
├─sdf1
│ ext4 1.0 SysBack 90c54104-6a06-4dab-ac09-0bea82aa0ec2
├─sdf2
│ ext4 1.0 D3 c2f57970-8eb9-4ea3-b771-5633e0d4faec 2.5T 1% /media/butch/D3
├─sdf3
│ ext4 1.0 D1 d13cc3db-7139-4024-8ff2-0493654d637d 1.6T 12% /media/butch/D1
└─sdf4
ext4 1.0 Home_Backup d1f06380-26cb-4b1a-9733-3ba2c18b67b5 757.2G 0% /media/butch/Home_Backup
sdg
└─sdg1
ext4 1.0 Ubuntu_Data_Back 394833f8-06e8-40fe-90cd-a9e669810b5b 1.7T 47% /media/butch/Ubuntu_Data_Back
sdh
sdi
sr0
sr1

Partition sdf1 looks clean, this is good news!

Now, let’s repeat and check the other partitions on that drive:

sudo umount /dev/sdf2
sudo e2fsck -f -v /dev/sdf2
sudo umount /dev/sdf3
sudo e2fsck -f -v /dev/sdf3
sudo umount /dev/sdf4
sudo e2fsck -f -v /dev/sdf4

Did you check the sde drive? It is not shown in the lsblk output.