Like the Title says, it is really easy to set up automount in the settings, but every time I log in I have to type my password again. It is a mild inconvenience, and I’m wondering why this is the case, and if there is any fix other than mounting it in konsole.
Thanks in advance!
Automount of what? What protocol? How is it started, in desktop file, fstab, system unit file? Either way, post the exec line.
It is an extra 4TB ssd I want to use for extra storage. I’m not sure if I found the proper logs but here is what I’ve found from Journal. nvme1n1p1 is the storage I have set up to automount.
AME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sda 8:0 0 931.5G 0 disk
├─sda1 8:1 0 16M 0 part
└─sda2 8:2 0 931.5G 0 part
zram0 251:0 0 8G 0 disk [SWAP]
nvme1n1 259:0 0 3.6T 0 disk
└─nvme1n1p1 259:2 0 3.6T 0 part /run/media/jstephenson/Samsung 4TB
nvme0n1 259:1 0 1.8T 0 disk
├─nvme0n1p1 259:3 0 600M 0 part /boot/efi
├─nvme0n1p2 259:4 0 1G 0 part /boot
└─nvme0n1p3 259:5 0 1.8T 0 part /home
AUDIT1100 pid=3552 uid=1000 auid=1000 ses=3 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 msg='op=PAM:authentication grantors=pam_unix acct=“jstephenson” exe=“/usr/lib/polkit-1/polkit-ag>
Dec 27 12:56:33 fedora audit[3552]: AUDIT1101 pid=3552 uid=1000 auid=1000 ses=3 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 msg='op=PAM:accounting grantors=pam_unix acct=“jstephenson” exe=”/usr/lib/polkit-1/polkit-agent->
Dec 27 12:56:33 fedora kernel: BTRFS: device label Samsung 4TB devid 1 transid 11 /dev/nvme1n1p1 (259:2) scanned by pool-1 (3509)
Dec 27 12:56:33 fedora kernel: BTRFS info (device nvme1n1p1): first mount of filesystem ad8655dc-4fbb-4c29-8fa8-c6cd5a7adc07
Dec 27 12:56:33 fedora kernel: BTRFS info (device nvme1n1p1): using crc32c (crc32c-lib) checksum algorithm
Dec 27 12:56:33 fedora kernel: BTRFS info (device nvme1n1p1): enabling ssd optimizations
Dec 27 12:56:33 fedora kernel: BTRFS info (device nvme1n1p1): turning on async discard
Dec 27 12:56:33 fedora kernel: BTRFS info (device nvme1n1p1): enabling free space tree
Dec 27 12:56:34 fedora systemd[1]: Stopping user@985.service - User Manager for UID 985…
Dec 27 12:56:34 fedora systemd[2321]: Activating special unit exit.target…
Dec 27 12:56:34 fedora systemd[2321]: Stopped target default.target - Main User Target.
Dec 27 12:56:34 fedora systemd[2321]: Stopped target sound.target - Sound Card.
Dec 27 12:56:34 fedora systemd[2321]: Stopping pipewire-pulse.service - PipeWire PulseAudio…
Dec 27 12:56:34 fedora systemd[2321]: Stopping unity-gtk-module.service - Unity GTK Module Environment variables…
Dec 27 12:56:34 fedora systemd[2321]: Stopping xdg-permission-store.service - sandboxed app permission store…
Dec 27 12:56:34 fedora systemd[2321]: Stopped pipewire-pulse.service - PipeWire PulseAudio.
Dec 27 12:56:34 fedora systemd[2321]: Stopping unity-gtk-module.service - Unity GTK Module Environment variables…
Dec 27 12:56:34 fedora systemd[2321]: Stopping xdg-permission-store.service - sandboxed app permission store…
Dec 27 12:56:34 fedora systemd[2321]: Stopped pipewire-pulse.service - PipeWire PulseAudio.
Dec 27 12:56:34 fedora systemd[2321]: Stopped xdg-permission-store.service - sandboxed app permission store.
Dec 27 12:56:34 fedora systemd[2321]: Stopping wireplumber.service - Multimedia Service Session Manager…
Dec 27 12:56:34 fedora systemd[2321]: Stopped wireplumber.service - Multimedia Service Session Manager.
Dec 27 12:56:34 fedora systemd[2321]: Stopping pipewire.service - PipeWire Multimedia Service…
Dec 27 12:56:34 fedora systemd[2321]: Stopped pipewire.service - PipeWire Multimedia Service.
Dec 27 12:56:34 fedora systemd[2321]: Stopped unity-gtk-module.service - Unity GTK Module Environment variables.
Dec 27 12:56:34 fedora systemd[2321]: Stopped target basic.target - Basic System.
Dec 27 12:56:34 fedora systemd[2321]: Stopped target paths.target - Paths.
Dec 27 12:56:34 fedora systemd[2321]: Stopped drkonqi-sentry-postman.path - Submitting pending crash events (file monitor).
Dec 27 12:56:34 fedora systemd[2321]: Stopped target sockets.target - Sockets.
Dec 27 12:56:34 fedora systemd[2321]: Stopped target timers.target - Timers.
Dec 27 12:56:34 fedora systemd[2321]: Stopped systemd-tmpfiles-clean.timer - Daily Cleanup of User’s Temporary Directories.
Dec 27 12:56:34 fedora systemd[2321]: Closed pipewire-pulse.socket - PipeWire PulseAudio.
Dec 27 12:56:34 fedora systemd[2321]: Closed pipewire.socket - PipeWire Multimedia System Sockets.
Dec 27 12:56:34 fedora systemd[2321]: Closed systemd-ask-password.socket - Query the User Interactively for a Password.
Dec 27 12:56:34 fedora dbus-broker[2343]: Dispatched 972 messages @ 2(±9)μs / message.
Dec 27 12:56:34 fedora systemd[2321]: Stopping dbus-broker.service - D-Bus User Message Bus…
Dec 27 12:56:34 fedora systemd[2321]: Stopped systemd-tmpfiles-setup.service - Create User Files and Directories.
Dec 27 12:56:34 fedora systemd[2321]: Stopped dbus-broker.service - D-Bus User Message Bus.
Dec 27 12:56:34 fedora systemd[2321]: Removed slice session.slice - User Core Session Slice.
Dec 27 12:56:34 fedora systemd[2321]: Closed dbus.socket - D-Bus User Message Bus Socket.
Dec 27 12:56:34 fedora systemd[2321]: Removed slice app.slice - User Application Slice.
Dec 27 12:56:34 fedora systemd[2321]: Reached target shutdown.target - Shutdown.
Dec 27 12:56:34 fedora systemd[2321]: Finished systemd-exit.service - Exit the Session.
Dec 27 12:56:34 fedora systemd[2321]: Reached target exit.target - Exit the Session.
Dec 27 12:56:34 fedora systemd-logind[1529]: Removed session 1.
Dec 27 12:56:34 fedora systemd[1]: user@985.service: Deactivated successfully.
Dec 27 12:56:34 fedora systemd[1]: Stopped user@985.service - User Manager for UID 985.
Dec 27 12:56:34 fedora audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg=‘unit=user@985 comm=“systemd” exe=“/usr/lib/systemd/systemd” hostname=? addr=? terminal=? res=success’
Dec 27 12:56:35 fedora systemd[1]: Stopping user-runtime-dir@985.service - User Runtime Directory /run/user/985…
Dec 27 12:56:35 fedora systemd[1]: run-user-985.mount: Deactivated successfully.
Dec 27 12:56:35 fedora systemd[1]: user-runtime-dir@985.service: Deactivated successfully.
Dec 27 12:56:35 fedora systemd[1]: Stopped user-runtime-dir@985.service - User Runtime Directory /run/user/985.
Dec 27 12:56:35 fedora audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=user-runtime-dir@985 comm=“systemd” exe=“/usr/lib/systemd/systemd” hostname=? addr=? terminal=? res=suc>
Dec 27 12:56:35 fedora systemd[1]: Removed slice user-985.slice - User Slice of UID 985.
Dec 27 12:56:35 fedora systemd[1]: user-985.slice: Consumed 5.098s CPU time, 811.9M memory peak.
Dec 27 12:56:36 fedora systemd[1]: dbus-:1.3-org.kde.kded.smart@0.service: Deactivated successfully.
Dec 27 12:56:36 fedora audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=dbus-:1.3-org.kde.kded.smart@0 comm=“systemd” exe=“/usr/lib/systemd/systemd” hostname=? addr=? terminal>
Dec 27 12:56:37 fedora systemd[1]: dbus-:1.3-org.kde.powerdevil.chargethresholdhelper@0.service: Deactivated successfully.
Dec 27 12:56:37 fedora audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=dbus-:1.3-org.kde.powerdevil.chargethresholdhelper@0 comm=“systemd” exe=“/usr/lib/systemd/systemd” host>
Dec 27 12:56:37 fedora systemd[1]: dbus-:1.3-org.kde.powerdevil.discretegpuhelper@0.service: Deactivated successfully.
You need to tell us where you configure the disk to be mounted as @hfine asked.
Did you all to /etc/fstab for example?
I’m not sure I just went to device automount in my system settings, and selected it for on login to automount.
[EDITED] You didn’t tell me how you mounted it, I’m just guessing it’s either with Gnome disks or KDE’s disk manager. The drive is btrfs which is great and automounts on boot without errors.
So short answer? My guess is the password has nothing to do with that drive. The audit log shows: AUDIT1100 pid=3552 uid=1000 auid=1000 ... op=PAM:authentication ... acct="jstephenson"
I think you are conflating the new drive with a kwallet prompt which is unrelated. Is the drive encrypted? That might result in a password being asked. What makes you so sure it’s the drive?
EDIT: Another thought. Again, I don’t know how you mounted it, you can show us your /etc/fstab file. But if you mounted it as root, you bet it would ask you for a password.
If it was me, I would not be using automount, it’s mounting it to a place where USB sticks usually go. I would do it the old way:
Find the UUID: You should run lsblk -f to get the unique ID of nvme1n1p1.
sudo mkdir -p /mnt/storagesudo chown jstephenson:jstephenson /mnt/storageAnd then edit your fstab file. Example:
<file system> <mount point> <type> <options> <dump> <pass>
UUID=1234-abcd-5678-efgh /mnt/storage btrfs defaults,nofail,x-systemd.device-timeout=5ms 0 2
Yes I just mounted it using Auto mount in the system settings. Wouldn’t I want it as root so I can use it seamlessly between between different programs as extra storage? I’m guessing automount defaults to this setting?
Old way is best then. Thank you for the specific instructions!
Edit: no I did not explicitly encrypt the drive when I formatted it. Unless KDE Partition manager does it by default.
Anytime you edit the fstab file before you reboot you should test to make sure there are no errors in the file. You can do that once you’ve made the edit and you’re back at the shell command by typing…
sudo mount -a
The place you were auto mounting was a place where you would mount things that you plug in and take out such as USB keys, the system detects the insertion and mounts it. What you want is a permanently mounted drive to act as a source for additional storage, to be part of your permanent directory tree. The fstab file is the right place to do that.
You also asked earlier about mounting as root so you can access your files. Absolutely not. It files are created by Joe then you can access them by user Joe and you can save them to that mount as user Joe.
Don’t you need to tell systemd to reload it’s config first with systemctl daemon-reload?
Otherwise the old version of /etc/fstab is used I think?
Yes, sudo systemctl daemon-reload first to reload systemd configuration and regenerate mount units from fstab. Then use sudo mount -a
At that point you can cd to the mount point and type ls -al to list files. Of course dolphin will also see it.
When you reboot it will auto mount. Just be careful not to mess with the existing text in fstab. Real careful. Know how to exit out of your editor without saving if you even susopect you messed it up
@hfine and @barryascott, I’ve the same problem, for I’ve also enabled automatic storage device mounture via kcm_device_automounter:
I’ve asked about this beforehand: [1]
Though, I wonder whether forums.opensuse.org/t/170048/9 is relevant, too:
cat -n --show-nonprinting /etc/fstab 1
2 #
3 # /etc/fstab
4 # Created by anaconda on Sun Mar 9 10:52:04 2025
5 #
6 # Accessible filesystems, by reference, are maintained under '/dev/disk/'.
7 # See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info.
8 #
9 # After editing this file, run 'systemctl daemon-reload' to update systemd
10 # units generated from this file.
11 #
12 UUID=e70e2a08-dcc9-4696-9a41-1b34ee1b4b94 / btrfs subvol=root,compress=zstd:1 0 0
13 UUID=7faeafbb-6206-458a-a6d4-36de13a6f8fd /boot ext4 defaults 1 2
14 UUID=8C16-B16E /boot/efi vfat umask=0077,shortname=winnt 0 2
15 UUID=e70e2a08-dcc9-4696-9a41-1b34ee1b4b94 /home btrfs subvol=home,compress=zstd:1 0 0
16 /var/swap/swapfile none swap defaults 0 0
Hey all, I found a way to get my new storage drive to automount at system start up without editing Fstab in the Konsole.
The Disks software for The GNOME Project, works great, even with KDE setup.
Within here you can format and mount your drives.
Once you have it formatted and mounted to your liking you can enter the “Edit Mount Options” setting.
Within here you can change the mount point to what you want it to be. After saving these settings you will be able to reboot, and it will always be availble for use on your desktop.
So yeah this is the most painless way I’ve found so far to mount storage, and I’m a big fan of this software. 
@leroyrouge, KDE Partition Manager also provides that, by default, on Plasma.
