https://bugs.kde.org/show_bug.cgi?id=507596
--- Comment #11 from szelbi <public+bugs...@szelbi.dev> --- (In reply to Nate Graham from comment #10) > > Oh, I have the qBittorrent app set to start automatically, and it reads > > files from that drive. > > Are there any other cases you can think of where something on the system > expects the drive to be mounted, or will only work when the drive is > mounted? I'm almost certain that's the problem here. > > Of course, if it is, we can do a better job of handling this case. But we > need to figure out what the exact cause of the problem is. Removing these two options from the line in /etc/fstab posted in the original post stops the problem from occurring: `x-systemd.automount,x-systemd.mount-timeout=10` It looks like systemd is just trying to mount it again and again. I think I found these options in this Arch Wiki article about /etc/fstab, but I'm not 100% sure because it was a while ago: https://wiki.archlinux.org/title/Fstab#Automount_with_systemd Removing these two didn't stop automounting at startup when the device is plugged in. However, it did stop automounting when the drive was plugged in after the system was already running, which makes sense and proves that systemd tries to mount it all the time. -- You are receiving this mail because: You are watching all bug changes.
