Boot stops on "Reached target Remote File Systems"

Some days ago OpenSUSE installation began to stop on boot after cold restart. The last “OK” message on display is “Reached target Remote File Systems” and then the endless “A job is running for /dev/sda2” waiting is present (/dev/sda2 is a swap partition). However, Ctrl-Alt-Del key combitation can lead to successful boot, usually two or three arrempts are required. Warm reboot works: when I reboot the system from the KDE GUI “Restart” button, computer restarts normally.

Is this a hardware problem or something else?

Are there other partitions on sda used by the system? When not it could be that sda is late in coming alive and that that is only detected with sda2.

Yes, uefi, system and home partitions are also present. Swap partition is the first in the fstab.

That can be right. But nevertheless initrd is loaded from sda into ram and started.

It was just a thought. But when all others are available, I do not see a reason for sda2 (Swap) not be.

Please post the output of “lsblk --fs”.

  • Normally, given an EFI system, the Swap partition should be be the 3rd partition on the primary drive …

Please, also, post the output of “ systemctl list-unit-files | grep -i ‘swap’ ” –

  • There should be a generated entry for the UUID of the Swap partition …

Are you mounting by means of UUID?
[HR][/HR]Please check the output of “ journalctl --this-boot --output=short-monotonic --no-hostname | grep -i ‘swap’ ” –

  • It should look something like this:

    0.328199] kernel: Spectre V1 : Mitigation: usercopy/swapgs barriers and __user pointer sanitization
    1.896313] kernel: zswap: loaded using pool lzo/zbud
    1.902401] kernel: Lockdown: swapper/0: hibernation is restricted; see man kernel_lockdown.7
    3.949117] systemd[1]: Reached target Swap.
    4.603615] systemd[1]: Stopped target Swap.
    5.541243] systemd[1]: Activating swap /dev/disk/by-uuid/e96bee61-d116-4700-a761-c72153babfde...
    5.741729] kernel: Adding 2097600k swap on /dev/sda3.  Priority:-2 extents:1 across:2097600k SSFS
    5.597079] systemd[1]: Activated swap /dev/disk/by-uuid/e96bee61-d116-4700-a761-c72153babfde.
    5.628818] systemd[1]: Reached target Swap.

dcurtisfra,

# lsblk --fs                            
NAME   FSTYPE FSVER LABEL UUID                                 FSAVAIL FSUSE% MOUNTPOINT
sda                                                                            
├─sda1 vfat   FAT16       6DC8-CD83                             150.8M     3% /boot/efi
├─sda2 swap   1           edb46985-ea0d-484c-bfbc-055c50199c7e                [SWAP]
├─sda3 btrfs              31e8df4d-26ce-4afa-b741-0dcbf64fe722   15.4G    58% /var/spool
└─sda4 xfs                492e6195-f9e7-4fb4-98f5-49f553533b3e  424.2G    52% /home
sdb                                                                            
└─sdb1 xfs                3c7f4138-8338-474f-9534-a22aed8bba8a    1.4T    22% /disk2
sr0                         

# systemctl list-unit-files | grep -i 'swap'
dev-disk-by\x2duuid-edb46985\x2dea0d\x2d484c\x2dbfbc\x2d055c50199c7e.**swap** generated       -             
**swap**.target 

# journalctl --this-boot --output=short-monotonic --no-hostname | grep -i 'swap'
    0.133308] kernel: Spectre V1 : Mitigation: usercopy/**swap**gs barriers and __user pointer sanitization
    1.270619] kernel: z**swap**: loaded using pool lzo/zbud
    1.570617] systemd[1]: Reached target **Swap**.
    4.257689] systemd[1]: Stopped target **Swap**.
    7.870400] systemd[1]: Activating **swap** /dev/disk/by-uuid/edb46985-ea0d-484c-bfbc-055c50199c7e...
    8.063695] kernel: Adding 2104316k **swap** on /dev/sda2.  Priority:-2 extents:1 across:2104316k FS
    8.112655] systemd[1]: Activated **swap** /dev/disk/by-uuid/edb46985-ea0d-484c-bfbc-055c50199c7e.
    8.116150] systemd[1]: Reached target **Swap**.

Show all output of ‘journalctl -b -u init.scope’ and ’ journalctl -b -u ‘mount’.

Where is your system partition?

  • You seem to have mounted a Btrfs partition which is more than ½ full on “/var/spool” …
  • Is this by chance the System Partition?

[INDENT=2]If it is, then, it should be mounted on “/” …
[/INDENT]

I think we need

cat /etc/fstab

and

mount

The output was too big, so I cut it:

# journalctl -b -u init.scope
-- Logs begin at Fri 2020-06-12 15:23:48 MSK, end at Wed 2021-06-16 16:20:52 MSK. --июн 16 09:19:59 pilgrim systemd[1]: Started Rule-based Manager for Device Events and Files.
июн 16 09:19:59 pilgrim systemd[1]: Condition check resulted in dracut pre-trigger hook being skipped.
июн 16 09:19:59 pilgrim systemd[1]: Starting Coldplug All udev Devices...
июн 16 09:19:59 pilgrim systemd[1]: Finished Coldplug All udev Devices.
июн 16 09:19:59 pilgrim systemd[1]: Starting dracut initqueue hook...
июн 16 09:19:59 pilgrim systemd[1]: Starting Show Plymouth Boot Screen...
июн 16 09:19:59 pilgrim systemd[1]: Received SIGRTMIN+20 from PID 304 (plymouthd).
июн 16 09:19:59 pilgrim systemd[1]: Started Show Plymouth Boot Screen.
июн 16 09:19:59 pilgrim systemd[1]: Condition check resulted in Dispatch Password Requests to Console Directory Watch being skipped.
июн 16 09:19:59 pilgrim systemd[1]: Started Forward Password Requests to Plymouth Directory Watch.
июн 16 09:19:59 pilgrim systemd[1]: Reached target Paths.
июн 16 09:20:00 pilgrim systemd[1]: Found device WDC_WD10EZEX-00WN4A0 primary.
июн 16 09:20:00 pilgrim systemd[1]: Found device WDC_WD10EZEX-00WN4A0 primary.
июн 16 09:20:00 pilgrim systemd[1]: Starting Resume from hibernation using device /dev/sda2...
июн 16 09:20:00 pilgrim systemd[1]: systemd-hibernate-resume@dev-sda2.service: Succeeded.
июн 16 09:20:00 pilgrim systemd[1]: Finished Resume from hibernation using device /dev/sda2.
июн 16 09:20:00 pilgrim systemd[1]: Reached target Local File Systems (Pre).
июн 16 09:20:00 pilgrim systemd[1]: Reached target Local File Systems.
июн 16 09:20:00 pilgrim systemd[1]: Starting Create Volatile Files and Directories...
июн 16 09:20:00 pilgrim systemd[1]: Finished Create Volatile Files and Directories.
июн 16 09:20:00 pilgrim systemd[1]: Reached target System Initialization.
июн 16 09:20:00 pilgrim systemd[1]: Reached target Basic System.
июн 16 09:20:01 pilgrim systemd[1]: Found device WDC_WD10EZEX-00WN4A0 primary.
июн 16 09:20:01 pilgrim systemd[1]: Reached target Initrd Root Device.
июн 16 09:20:01 pilgrim systemd[1]: Finished dracut initqueue hook.
июн 16 09:20:01 pilgrim systemd[1]: Reached target Remote File Systems (Pre).
июн 16 09:20:01 pilgrim systemd[1]: Reached target Remote File Systems.
июн 16 09:20:01 pilgrim systemd[1]: Condition check resulted in dracut pre-mount hook being skipped.
июн 16 09:20:01 pilgrim systemd[1]: Starting File System Check on /dev/disk/by-uuid/31e8df4d-26ce-4afa-b741-0dcbf64fe722...
июн 16 09:20:01 pilgrim systemd[1]: Finished File System Check on /dev/disk/by-uuid/31e8df4d-26ce-4afa-b741-0dcbf64fe722.
июн 16 09:20:01 pilgrim systemd[1]: Mounting /sysroot...
июн 16 09:20:02 pilgrim systemd[1]: Mounted /sysroot.
июн 16 09:20:02 pilgrim systemd[1]: Reached target Initrd Root File System.
июн 16 09:20:02 pilgrim systemd[1]: Starting Reload Configuration from the Real Root...
июн 16 09:20:02 pilgrim systemd[1]: Reloading.
июн 16 09:20:02 pilgrim systemd[1]: /usr/lib/systemd/system/plymouth-start.service:15: Unit configured to use KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update your service to use a safer KillMode=, such as 'mixed' or 'control-group'. Support for KillMode=none is deprecated and will eventually be removed.
июн 16 09:20:02 pilgrim systemd[1]: initrd-parse-etc.service: Succeeded.
июн 16 09:20:02 pilgrim systemd[1]: Finished Reload Configuration from the Real Root.
июн 16 09:20:02 pilgrim systemd[1]: Reached target Initrd File Systems.
июн 16 09:20:02 pilgrim systemd[1]: Reached target Initrd Default Target.
июн 16 09:20:02 pilgrim systemd[1]: Condition check resulted in dracut mount hook being skipped.
июн 16 09:20:02 pilgrim systemd[1]: Condition check resulted in dracut pre-pivot and cleanup hook being skipped.
июн 16 09:20:02 pilgrim systemd[1]: Starting Cleaning Up and Shutting Down Daemons...
июн 16 09:20:02 pilgrim systemd[1]: Stopped target Initrd Default Target.
июн 16 09:20:02 pilgrim systemd[1]: Stopped target Basic System.
июн 16 09:20:02 pilgrim systemd[1]: Stopped target Initrd Root Device.
июн 16 09:20:02 pilgrim systemd[1]: Stopped target Paths.
июн 16 09:20:02 pilgrim systemd[1]: Stopped target Remote File Systems.
июн 16 09:20:02 pilgrim systemd[1]: Stopped target Remote File Systems (Pre).
июн 16 09:20:02 pilgrim systemd[1]: Stopped target Slices.
июн 16 09:20:02 pilgrim systemd[1]: Stopped target Sockets.
июн 16 09:20:02 pilgrim systemd[1]: Stopped target System Initialization.
июн 16 09:20:02 pilgrim systemd[1]: Stopped target Swap.
июн 16 09:20:02 pilgrim systemd[1]: Stopped target Timers.
июн 16 09:20:02 pilgrim systemd[1]: dracut-initqueue.service: Succeeded.
июн 16 09:20:02 pilgrim systemd[1]: Stopped dracut initqueue hook.
июн 16 09:20:02 pilgrim systemd[1]: Starting Plymouth switch root service...
июн 16 09:20:02 pilgrim systemd[1]: systemd-sysctl.service: Succeeded.
июн 16 09:20:02 pilgrim systemd[1]: Stopped Apply Kernel Variables.
июн 16 09:20:02 pilgrim systemd[1]: systemd-modules-load.service: Succeeded.
июн 16 09:20:02 pilgrim systemd[1]: Stopped Load Kernel Modules.
июн 16 09:20:02 pilgrim systemd[1]: systemd-tmpfiles-setup.service: Succeeded.
июн 16 09:20:02 pilgrim systemd[1]: Stopped Create Volatile Files and Directories.
июн 16 09:20:02 pilgrim systemd[1]: Stopped target Local File Systems.
июн 16 09:20:02 pilgrim systemd[1]: Stopped target Local File Systems (Pre).
июн 16 09:20:02 pilgrim systemd[1]: systemd-udev-trigger.service: Succeeded.
июн 16 09:20:02 pilgrim systemd[1]: Stopped Coldplug All udev Devices.
июн 16 09:20:02 pilgrim systemd[1]: Stopping Rule-based Manager for Device Events and Files...
июн 16 09:20:02 pilgrim systemd[1]: initrd-cleanup.service: Succeeded.
июн 16 09:20:02 pilgrim systemd[1]: Finished Cleaning Up and Shutting Down Daemons.
июн 16 09:20:02 pilgrim systemd[1]: systemd-udevd.service: Succeeded.
июн 16 09:20:02 pilgrim systemd[1]: Stopped Rule-based Manager for Device Events and Files.
июн 16 09:20:02 pilgrim systemd[1]: systemd-udevd-control.socket: Succeeded.
июн 16 09:20:02 pilgrim systemd[1]: Closed udev Control Socket.
июн 16 09:20:02 pilgrim systemd[1]: systemd-udevd-kernel.socket: Succeeded.
июн 16 09:20:02 pilgrim systemd[1]: Closed udev Kernel Socket.
июн 16 09:20:02 pilgrim systemd[1]: dracut-pre-udev.service: Succeeded.
июн 16 09:20:02 pilgrim systemd[1]: Stopped dracut pre-udev hook.
июн 16 09:20:02 pilgrim systemd[1]: dracut-cmdline.service: Succeeded.
июн 16 09:20:02 pilgrim systemd[1]: Stopped dracut cmdline hook.
июн 16 09:20:02 pilgrim systemd[1]: dracut-cmdline-ask.service: Succeeded.
июн 16 09:20:02 pilgrim systemd[1]: Stopped dracut ask for additional cmdline parameters.
июн 16 09:20:02 pilgrim systemd[1]: Starting Cleanup udev Database...
июн 16 09:20:02 pilgrim systemd[1]: systemd-tmpfiles-setup-dev.service: Succeeded.
июн 16 09:20:02 pilgrim systemd[1]: Stopped Create Static Device Nodes in /dev.
июн 16 09:20:02 pilgrim systemd[1]: kmod-static-nodes.service: Succeeded.
июн 16 09:20:02 pilgrim systemd[1]: Stopped Create list of static device nodes for the current kernel.
июн 16 09:20:02 pilgrim systemd[1]: initrd-udevadm-cleanup-db.service: Succeeded.
июн 16 09:20:02 pilgrim systemd[1]: Finished Cleanup udev Database.
июн 16 09:20:02 pilgrim systemd[1]: Reached target Switch Root.
июн 16 09:20:02 pilgrim systemd[1]: Finished Plymouth switch root service.
июн 16 09:20:02 pilgrim systemd[1]: Starting Switch Root...
июн 16 09:20:02 pilgrim systemd[1]: Switching root.
...
июн 16 09:20:10 pilgrim systemd[1]: Mounted /home.
июн 16 09:20:10 pilgrim systemd[1]: Reached target Local File Systems.
июн 16 09:20:10 pilgrim systemd[1]: Starting Restore /run/initramfs on shutdown...
июн 16 09:20:10 pilgrim systemd[1]: Starting Tell Plymouth To Write Out Runtime Data...
...

# journalctl -b -u '*mount*'
-- Logs begin at Fri 2020-06-12 15:23:48 MSK, end at Wed 2021-06-16 16:26:16 MSK. --
июн 16 09:20:01 pilgrim systemd[1]: Condition check resulted in dracut pre-mount hook being skipped.
июн 16 09:20:01 pilgrim systemd[1]: Mounting /sysroot...
июн 16 09:20:02 pilgrim systemd[1]: Mounted /sysroot.
июн 16 09:20:02 pilgrim systemd[1]: Condition check resulted in dracut mount hook being skipped.
июн 16 09:20:06 pilgrim systemd[1]: Mounting FUSE Control File System...
июн 16 09:20:06 pilgrim systemd[1]: Mounted FUSE Control File System.
июн 16 09:20:09 pilgrim systemd[1]: Mounting /.snapshots...
июн 16 09:20:09 pilgrim systemd[1]: Mounting /boot/efi...
июн 16 09:20:09 pilgrim systemd[1]: Mounting /boot/grub2/i386-pc...
июн 16 09:20:09 pilgrim systemd[1]: Mounting /boot/grub2/x86_64-efi...
июн 16 09:20:09 pilgrim systemd[1]: Mounting /opt...
июн 16 09:20:09 pilgrim systemd[1]: Mounting /srv...
июн 16 09:20:09 pilgrim systemd[1]: tmp.mount: Directory /tmp to mount over is not empty, mounting anyway.
июн 16 09:20:09 pilgrim systemd[1]: Mounting /tmp...
июн 16 09:20:09 pilgrim systemd[1]: Mounting /usr/local...
июн 16 09:20:09 pilgrim systemd[1]: var-cache.mount: Directory /var/cache to mount over is not empty, mounting anyway.
июн 16 09:20:09 pilgrim systemd[1]: Mounting /var/cache...
июн 16 09:20:09 pilgrim systemd[1]: Mounting /var/crash...
июн 16 09:20:09 pilgrim systemd[1]: Mounting /var/lib/libvirt/images...
июн 16 09:20:09 pilgrim systemd[1]: Mounting /var/lib/machines...
июн 16 09:20:09 pilgrim systemd[1]: Mounting /var/lib/mailman...
июн 16 09:20:09 pilgrim systemd[1]: Mounting /var/lib/mariadb...
июн 16 09:20:09 pilgrim systemd[1]: Mounting /var/lib/mysql...
июн 16 09:20:09 pilgrim systemd[1]: Mounting /var/lib/named...
июн 16 09:20:09 pilgrim systemd[1]: Mounting /var/lib/pgsql...
июн 16 09:20:09 pilgrim systemd[1]: Condition check resulted in Lock Directory being skipped.
июн 16 09:20:09 pilgrim systemd[1]: Mounting /var/log...
июн 16 09:20:09 pilgrim systemd[1]: Mounting /var/opt...
июн 16 09:20:09 pilgrim systemd[1]: Condition check resulted in Runtime Directory being skipped.
июн 16 09:20:09 pilgrim systemd[1]: Mounting /var/spool...
июн 16 09:20:09 pilgrim systemd[1]: Mounting /var/tmp...
июн 16 09:20:09 pilgrim systemd[1]: Mounted /.snapshots.
июн 16 09:20:09 pilgrim systemd[1]: Mounted /boot/grub2/i386-pc.
июн 16 09:20:09 pilgrim systemd[1]: Mounted /boot/grub2/x86_64-efi.
июн 16 09:20:09 pilgrim systemd[1]: Mounted /opt.
июн 16 09:20:09 pilgrim systemd[1]: Mounted /srv.
июн 16 09:20:09 pilgrim systemd[1]: Mounted /tmp.
июн 16 09:20:09 pilgrim systemd[1]: Mounted /usr/local.
июн 16 09:20:09 pilgrim systemd[1]: Mounted /var/cache.
июн 16 09:20:09 pilgrim systemd[1]: Mounted /var/crash.
июн 16 09:20:09 pilgrim systemd[1]: Mounted /var/lib/libvirt/images.
июн 16 09:20:09 pilgrim systemd[1]: Mounted /var/lib/machines.
июн 16 09:20:09 pilgrim systemd[1]: Mounted /var/lib/mailman.
июн 16 09:20:09 pilgrim systemd[1]: Mounted /var/lib/mariadb.
июн 16 09:20:09 pilgrim systemd[1]: Mounted /var/lib/mysql.
июн 16 09:20:09 pilgrim systemd[1]: Mounted /var/lib/named.
июн 16 09:20:09 pilgrim systemd[1]: Mounted /var/lib/pgsql.
июн 16 09:20:09 pilgrim systemd[1]: Mounted /var/opt.
июн 16 09:20:09 pilgrim systemd[1]: Mounted /var/log.
июн 16 09:20:09 pilgrim systemd[1]: Mounted /var/spool.
июн 16 09:20:09 pilgrim systemd[1]: Mounted /var/tmp.
июн 16 09:20:09 pilgrim systemd[1]: Mounting /disk2...
июн 16 09:20:09 pilgrim systemd[1]: Mounting /home...
июн 16 09:20:09 pilgrim systemd[1]: Mounted /boot/efi.
июн 16 09:20:09 pilgrim systemd[1]: Condition check resulted in Lock Directory being skipped.
июн 16 09:20:09 pilgrim systemd[1]: Condition check resulted in Runtime Directory being skipped.
июн 16 09:20:09 pilgrim systemd[1]: Mounted /disk2.
июн 16 09:20:10 pilgrim systemd[1]: Mounted /home.

[QUOTE=dcurtisfra;]Where is your system partition?

  • You seem to have mounted a Btrfs partition which is more than ½ full on “/var/spool” …
  • Is this by chance the System Partition?

If it is, then, it should be mounted on “/” …[/QUOTE]I think this is because of btrfs subvolumes. The /dev/sda3 is mounted on /:

# mount | grep sda3
/dev/sda3 on / type btrfs (rw,relatime,space_cache,subvolid=259,subvol=/@/.snapshots/1/snapshot)
/dev/sda3 on /.snapshots type btrfs (rw,relatime,space_cache,subvolid=258,subvol=/@/.snapshots)
/dev/sda3 on /boot/grub2/i386-pc type btrfs (rw,relatime,space_cache,subvolid=260,subvol=/@/boot/grub2/i386-pc)
/dev/sda3 on /boot/grub2/x86_64-efi type btrfs (rw,relatime,space_cache,subvolid=261,subvol=/@/boot/grub2/x86_64-efi)
/dev/sda3 on /opt type btrfs (rw,relatime,space_cache,subvolid=262,subvol=/@/opt)
/dev/sda3 on /srv type btrfs (rw,relatime,space_cache,subvolid=263,subvol=/@/srv)
/dev/sda3 on /var/cache type btrfs (rw,relatime,space_cache,subvolid=1238,subvol=/@/var/cache)
/dev/sda3 on /tmp type btrfs (rw,relatime,space_cache,subvolid=264,subvol=/@/tmp)
/dev/sda3 on /var/crash type btrfs (rw,relatime,space_cache,subvolid=266,subvol=/@/var/crash)
/dev/sda3 on /var/lib/pgsql type btrfs (rw,relatime,space_cache,subvolid=272,subvol=/@/var/lib/pgsql)
/dev/sda3 on /var/lib/named type btrfs (rw,relatime,space_cache,subvolid=271,subvol=/@/var/lib/named)
/dev/sda3 on /var/lib/mysql type btrfs (rw,relatime,space_cache,subvolid=270,subvol=/@/var/lib/mysql)
/dev/sda3 on /var/lib/mariadb type btrfs (rw,relatime,space_cache,subvolid=269,subvol=/@/var/lib/mariadb)
/dev/sda3 on /var/lib/mailman type btrfs (rw,relatime,space_cache,subvolid=268,subvol=/@/var/lib/mailman)
/dev/sda3 on /var/lib/libvirt/images type btrfs (rw,relatime,space_cache,subvolid=267,subvol=/@/var/lib/libvirt/images)
/dev/sda3 on /var/lib/machines type btrfs (rw,relatime,space_cache,subvolid=1296,subvol=/@/var/lib/machines)
/dev/sda3 on /usr/local type btrfs (rw,relatime,space_cache,subvolid=265,subvol=/@/usr/local)
/dev/sda3 on /var/opt type btrfs (rw,relatime,space_cache,subvolid=274,subvol=/@/var/opt)
/dev/sda3 on /var/log type btrfs (rw,relatime,space_cache,subvolid=273,subvol=/@/var/log)
/dev/sda3 on /var/tmp type btrfs (rw,relatime,space_cache,subvolid=276,subvol=/@/var/tmp)
/dev/sda3 on /var/spool type btrfs (rw,relatime,space_cache,subvolid=275,subvol=/@/var/spool)

@Mikhailo: Clear out the nonempty mountpoints, show space available by running:

erlangen:~ # btrfs filesystem usage -T /
Overall:
    Device size:                  51.69GiB
    Device allocated:             37.04GiB
    Device unallocated:           14.65GiB
    Device missing:                  0.00B
    Used:                         24.41GiB
    Free (estimated):             25.61GiB      (min: 25.61GiB)
    Free (statfs, df):            25.61GiB
    Data ratio:                       1.00
    Metadata ratio:                   1.00
    Global reserve:               75.05MiB      (used: 0.00B)
    Multiple profiles:                  no

                  Data     Metadata System              
Id Path           single   single   single   Unallocated
-- -------------- -------- -------- -------- -----------
 1 /dev/nvme0n1p3 34.01GiB  3.00GiB 32.00MiB    14.65GiB
-- -------------- -------- -------- -------- -----------
   Total          34.01GiB  3.00GiB 32.00MiB    14.65GiB
   Used           23.05GiB  1.36GiB 16.00KiB            
erlangen:~ # 

Should I boot from external drive, or I can unmount /tmp and /var/cache on main system and just delete files there?

I booted from linux dvd and removed the /tmp and /var/cache content. After rebooting the main system the log journal has no warnings about mounting not-empty directories.

# sudo btrfs filesystem usage -T /
[sudo] password for root:  
Overall:
    Device size:                  40.00GiB
    Device allocated:             35.82GiB
    Device unallocated:            4.18GiB
    Device missing:                  0.00B
    Used:                         23.22GiB
    Free (estimated):             15.39GiB      (min: 13.30GiB)
    Data ratio:                       1.00
    Metadata ratio:                   2.00
    Global reserve:               61.31MiB      (used: 0.00B)

             Data     Metadata  System               
Id Path      single   DUP       DUP      Unallocated
-- --------- -------- --------- -------- -----------
 1 /dev/sda3 33.01GiB   2.75GiB 64.00MiB     4.18GiB
-- --------- -------- --------- -------- -----------
   Total     33.01GiB   1.38GiB 32.00MiB     4.18GiB
   Used      21.80GiB 726.31MiB 16.00KiB 

That looks good. You have unallocated space. What about boot? I have:

**erlangen:~ #** journalctl -b -u init.scope --grep reached -o short-monotonic  
-- Logs begin at Fri 2021-06-04 21:27:14 CEST, end at Wed 2021-06-16 20:39:59 CEST. -- 
    1.859812] erlangen systemd[1]: Reached target System Initialization. 
    1.878587] erlangen systemd[1]: Reached target Paths. 
    1.878611] erlangen systemd[1]: Reached target Basic System. 
    1.999581] erlangen systemd[1]: Reached target Initrd Root Device. 
    2.712085] erlangen systemd[1]: Reached target Remote File Systems (Pre). 
    2.712247] erlangen systemd[1]: Reached target Remote File Systems. 
    2.741873] erlangen systemd[1]: Reached target Initrd Root File System. 
    2.918589] erlangen systemd[1]: Reached target Initrd File Systems. 
    2.918617] erlangen systemd[1]: Reached target Initrd Default Target. 
    2.948009] erlangen systemd[1]: Reached target Switch Root. 
    3.535892] erlangen systemd[1]: Reached target Local File Systems (Pre). 
    3.591373] erlangen systemd[1]: Reached target Local File Systems. 
    3.829552] erlangen systemd[1]: Reached target System Initialization. 
    3.848536] erlangen systemd[1]: Reached target Paths. 
    3.848831] erlangen systemd[1]: Reached target Sockets. 
    3.848893] erlangen systemd[1]: Reached target Basic System. 
    3.953298] erlangen systemd[1]: Reached target Network. 
    3.953369] erlangen systemd[1]: Reached target Network is Online. 
    3.953425] erlangen systemd[1]: Reached target Host and Network Name Lookups. 
    4.026348] erlangen systemd[1]: Reached target System Time Synchronized. 
    4.037556] erlangen systemd[1]: Reached target Timers. 
    4.273615] erlangen systemd[1]: Reached target Sound Card. 
    4.306877] erlangen systemd[1]: Reached target Login Prompts. 
    4.521029] erlangen systemd[1]: Reached target Multi-User System. 
    4.816289] erlangen systemd[1]: Reached target Graphical Interface. 
**erlangen:~ #**

Do you run btrfs maintenance routines?

Now the system boots without any problems. I don’t know what it was.