Mounting a partition doesn't work

Hello, I am having some problem mounting my partition at boot.

Here are some steps I did to mount at boot:

  1. Add mount point (/mnt/general) in YaST Partitioner, and it added this line to /etc/fstab
UUID=11630039-1c89-42d0-9396-ee4c70b4c218  /mnt/general            ext4   data=journal                  0  0
  1. Reboot to see if it works

  2. It doesn’t work and if I do sudo systemctl status mnt-general.mount, it shows this

● mnt-general.mount - /mnt/general
     Loaded: loaded (/etc/fstab; generated)
     Active: inactive (dead) since Sat 2020-08-22 11:57:43 KST; 1min 34s ago
      Where: /mnt/general
       What: /dev/disk/by-uuid/11630039-1c89-42d0-9396-ee4c70b4c218
       Docs: man:fstab(5)
             man:systemd-fstab-generator(8)

Aug 22 11:57:43 localhost systemd[1]: Unmounting /mnt/general...
Aug 22 11:57:43 localhost systemd[1]: mnt-general.mount: Succeeded.
Aug 22 11:57:43 localhost systemd[1]: Unmounted /mnt/general.

  1. Surprisingly, if I do sudo systemctl start mnt-general.mount, the volume is mounted.
hwsnemo@localhost:~> sudo systemctl status mnt-general.mount
● mnt-general.mount - /mnt/general
     Loaded: loaded (/etc/fstab; generated)
     Active: active (mounted) since Sat 2020-08-22 11:59:31 KST; 1s ago
      Where: /mnt/general
       What: /dev/sdb2
       Docs: man:fstab(5)
             man:systemd-fstab-generator(8)
      Tasks: 0 (limit: 4915)
     Memory: 556.0K
     CGroup: /system.slice/mnt-general.mount

Aug 22 11:59:31 localhost.localdomain systemd[1]: Mounting /mnt/general...
Aug 22 11:59:31 localhost.localdomain systemd[1]: Mounted /mnt/general.

Does anyone know why this happens?

In addition:

  • I tried adding the line manually in fstab, writing a mount service or using volume label, volume label or some things as identifier, and none of them worked.
  • Only way it worked is writing a simple script including mount /dev/disk/by-uuid/<some uuid> /mnt/general and making it a service
  • The exact same fstab line worked just fine in other distros such as Debian, Fedora, Ubuntu and Leap. I just have a script to make distro hopping easier which also adds a line to fstab.
  • This is the third time I installed TW (twice when it’s on 5.7, and once on 5.8) and it never worked.

What kind of device does this pertain to? Is it a USB-attached device that might not be ready when the mount attempt is made perhaps?

Unmounting may be caused by a bug: SDB:Fix btrfsmaintenance-refresh - openSUSE Wiki

Thank you! It fixed the problem :slight_smile:

Is it just a temporary fix or can I just use the current installation just fine after this bug is fixed in future?

You’re welcome. Thanks for reporting back.

Is it just a temporary fix or can I just use the current installation just fine after this bug is fixed in future?
The fix overrides the current vendor version of the service:

erlangen:~ # systemd-delta --type overridden 
[OVERRIDDEN] /etc/systemd/system/btrfsmaintenance-refresh.service → /usr/lib/systemd/system/btrfsmaintenance-refresh.service

--- /usr/lib/systemd/system/btrfsmaintenance-refresh.service    2020-05-30 19:52:02.000000000 +0200
+++ /etc/systemd/system/btrfsmaintenance-refresh.service        2020-04-21 19:26:51.310345932 +0200
@@ -1,11 +1,6 @@
 [Unit]
 Description=Update cron periods from /etc/sysconfig/btrfsmaintenance
-After=local-fs.target
 
 [Service]
 ExecStart=/usr/share/btrfsmaintenance/btrfsmaintenance-refresh-cron.sh systemd-timer
 Type=oneshot
-
-[Install]
-Also=btrfsmaintenance-refresh.path
-WantedBy=multi-user.target

Thus no action is needed when the vendor version provides the fix too. But for clarity it is recommended to remove overriding definitions which do not change anything at all. This will occur with btrfsmaintenance version 0.5.

https://bugzilla.suse.com/show_bug.cgi?id=1165780#c44