Universal Blue•2w ago

after the latest bazzite update, auto-mounting broked

this problem existed before ublue-os-media-automount-udev came along. and now here it is again

Solution:

also there is a new fix but it havent come up yet

Jump to solution

43 Replies

asen23•2w ago

wdym before, the before is manual mounting

Solution

asen23•2w ago

also there is a new fix but it havent come up yet

j.i.l.lOP•2w ago

kde has auto-mount settings and they dont work. this wasnt a problem since ublue-os-media-automount-udev came out. but now auto-mounts dont work again :c

asen23•2w ago

you can disable it if you want symlink the rule in etc to dev null sudo ln -s /dev/null /etc/udev/rules.d/99-media-automount.rules

j.i.l.lOP•2w ago

do you know why this section was disabled in kde settings?

asen23•2w ago

what section?

j.i.l.lOP•2w ago

its in russian, but anyways

asen23•2w ago

not sure, havent used it

j.i.l.lOP•2w ago

after the update, its still not fixed for me

asen23•2w ago

did you disable the rule before?

j.i.l.lOP•2w ago

asen23•2w ago

sudo lsblk -f

j.i.l.lOP•2w ago

asen23•2w ago

which drive isnt getting automounted?

j.i.l.lOP•2w ago

"hdd" and "backup"

asen23•2w ago

rpm -qa | grep automo

j.i.l.lOP•2w ago

asen23•2w ago

you are currently mounting both from file manager?

j.i.l.lOP•2w ago

ye, via dolphin

asen23•2w ago

have you ever setup any manual mounting?

j.i.l.lOP•2w ago

only that https://discord.com/channels/1072614816579063828/1371700332991873054/1371719561136570530

asen23•2w ago

try unchecking that and rebooting

j.i.l.lOP•2w ago

done. still no auto-mount

asen23•2w ago

sudo udevadm info --no-pager /dev/sda2

j.i.l.lOP•2w ago

cGS5xk7.txt

asen23•2w ago

@Zeglius btrfs partition but partname is Basic data partition

Zeglius•2w ago

Ah ok yeah probably because it was converted, didn't think about that Gonna remove that from the rule, the nfts detection should work now anyways

j.i.l.lOP•2w ago

so in the next update it will be fixed?

Zeglius•2w ago

Maybe, though is weird, there should be a E: UBLUEOS_PART_IS_IN_FSTAB field in that log run this udevadm test --action add /dev/sda2 2>&1 | fpaste and paste the link

j.i.l.lOP•2w ago

https://paste.centos.org/view/2b211d6c

Zeglius•2w ago

mmm, kk seems somewhat the rule exists early, now (udevadm info -a /dev/sda2 | grep 'ATTRS{removable}'); /usr/libexec/is_in_fstab.sh /dev/sda2

j.i.l.lOP•2w ago

Zeglius•2w ago

Ok nvm, the field doesn't appear for me either. So in theory yeah, whenever the next update for the automounter lands, it should work btw tyvm for sitting and dealing with my mess 😓 @asen23

asen23•2w ago

anything for good automounter 😂

j.i.l.lOP•2w ago

if it would help, on 42.20250425 it was working. and broked after 42.20250511

Finster•5d ago

Any chance that fixing this broke it for the rest of us? 🤣 After updating to 20250519, automounting no longer works for me here's my udevadm output:

$ sudo udevadm info --no-pager /dev/nvme1n1p1
P: /devices/pci0000:00/0000:00:02.1/0000:05:00.0/0000:06:00.0/0000:07:00.0/nvme/nvme1/nvme1n1/nvme1n1p1
M: nvme1n1p1
R: 1
J: b259:2
U: block
T: partition
D: b 259:2
N: nvme1n1p1
L: 0
S: disk/by-path/pci-0000:07:00.0-nvme-1-part/by-uuid/66116352-d0d6-4856-bcc1-a08803d6f8ee
S: disk/by-id/nvme-eui.002538522140a56c-part1
S: disk/by-diskseq/4-part1
S: disk/by-uuid/66116352-d0d6-4856-bcc1-a08803d6f8ee
S: disk/by-partuuid/9357e9c1-47b7-4435-91cc-f13575dc43cc
S: disk/by-label/ssd2
S: disk/by-path/pci-0000:07:00.0-nvme-1-part1
S: disk/by-path/pci-0000:07:00.0-nvme-1-part/by-partuuid/9357e9c1-47b7-4435-91cc-f13575dc43cc
S: disk/by-id/nvme-Samsung_SSD_970_EVO_Plus_2TB_S6S2NS0T206213Y_1-part1
S: disk/by-path/pci-0000:07:00.0-nvme-1-part/by-partnum/1
S: disk/by-id/nvme-Samsung_SSD_970_EVO_Plus_2TB_S6S2NS0T206213Y-part1
S: disk/by-path/pci-0000:07:00.0-nvme-1-part/by-label/ssd2
Q: 4
E: DEVPATH=/devices/pci0000:00/0000:00:02.1/0000:05:00.0/0000:06:00.0/0000:07:00.0/nvme/nvme1/nvme1n1/nvme1n1p1
E: DEVNAME=/dev/nvme1n1p1
E: DEVTYPE=partition
E: DISKSEQ=4
E: PARTN=1
E: PARTUUID=9357e9c1-47b7-4435-91cc-f13575dc43cc
E: MAJOR=259
E: MINOR=2
E: SUBSYSTEM=block
E: USEC_INITIALIZED=7582114
E: ID_SERIAL_SHORT=S6S2NS0T206213Y
E: ID_WWN=eui.002538522140a56c
E: ID_MODEL=Samsung SSD 970 EVO Plus 2TB
E: ID_REVISION=4B2QEXM7
E: ID_NSID=1
E: ID_SERIAL=Samsung_SSD_970_EVO_Plus_2TB_S6S2NS0T206213Y_1
E: ID_PATH=pci-0000:07:00.0-nvme-1
E: ID_PATH_TAG=pci-0000_07_00_0-nvme-1
E: ID_PART_TABLE_UUID=4192dc3f-06d2-4cb5-af14-9b23a4626508
E: ID_PART_TABLE_TYPE=gpt
E: ID_FS_LABEL=ssd2
E: ID_FS_LABEL_ENC=ssd2
E: ID_FS_UUID=66116352-d0d6-4856-bcc1-a08803d6f8ee
E: ID_FS_UUID_ENC=66116352-d0d6-4856-bcc1-a08803d6f8ee
E: ID_FS_UUID_SUB=f971745f-296f-4222-b615-93dba5b524ae
E: ID_FS_UUID_SUB_ENC=f971745f-296f-4222-b615-93dba5b524ae
E: ID_FS_BLOCKSIZE=4096
E: ID_FS_LASTBLOCK=488378368
E: ID_FS_SIZE=2000397795328
E: ID_FS_TYPE=btrfs
E: ID_FS_USAGE=filesystem
E: ID_PART_ENTRY_SCHEME=gpt
E: ID_PART_ENTRY_UUID=9357e9c1-47b7-4435-91cc-f13575dc43cc
E: ID_PART_ENTRY_TYPE=0fc63daf-8483-4772-8e79-3d69d8477de4
E: ID_PART_ENTRY_NUMBER=1
E: ID_PART_ENTRY_OFFSET=2048
E: ID_PART_ENTRY_SIZE=3907026944
E: ID_PART_ENTRY_DISK=259:0
E: ID_BTRFS_READY=1
E: DEVLINKS=/dev/disk/by-path/pci-0000:07:00.0-nvme-1-part/by-uuid/66116352-d0d6-4856-bcc1-a08803d6f8ee /dev/disk/by-id/nvme-eui.002538522140a56c-part1 /dev/disk/by-diskseq/4-part1 /dev/disk/by-uuid/66116352-d0d6-4856-bcc1-a08803d6f8ee /dev/disk/by-partuuid/9357e9c1-47b7-4435-91cc-f13575dc43cc /dev/disk/by-label/ssd2 /dev/disk/by-path/pci-0000:07:00.0-nvme-1-part1 /dev/disk/by-path/pci-0000:07:00.0-nvme-1-part/by-partuuid/9357e9c1-47b7-4435-91cc-f13575dc43cc /dev/disk/by-id/nvme-Samsung_SSD_970_EVO_Plus_2TB_S6S2NS0T206213Y_1-part1 /dev/disk/by-path/pci-0000:07:00.0-nvme-1-part/by-partnum/1 /dev/disk/by-id/nvme-Samsung_SSD_970_EVO_Plus_2TB_S6S2NS0T206213Y-part1 /dev/disk/by-path/pci-0000:07:00.0-nvme-1-part/by-label/ssd2
E: TAGS=:systemd:
E: CURRENT_TAGS=:systemd:

$ sudo udevadm info --no-pager /dev/nvme1n1p1
P: /devices/pci0000:00/0000:00:02.1/0000:05:00.0/0000:06:00.0/0000:07:00.0/nvme/nvme1/nvme1n1/nvme1n1p1
M: nvme1n1p1
R: 1
J: b259:2
U: block
T: partition
D: b 259:2
N: nvme1n1p1
L: 0
S: disk/by-path/pci-0000:07:00.0-nvme-1-part/by-uuid/66116352-d0d6-4856-bcc1-a08803d6f8ee
S: disk/by-id/nvme-eui.002538522140a56c-part1
S: disk/by-diskseq/4-part1
S: disk/by-uuid/66116352-d0d6-4856-bcc1-a08803d6f8ee
S: disk/by-partuuid/9357e9c1-47b7-4435-91cc-f13575dc43cc
S: disk/by-label/ssd2
S: disk/by-path/pci-0000:07:00.0-nvme-1-part1
S: disk/by-path/pci-0000:07:00.0-nvme-1-part/by-partuuid/9357e9c1-47b7-4435-91cc-f13575dc43cc
S: disk/by-id/nvme-Samsung_SSD_970_EVO_Plus_2TB_S6S2NS0T206213Y_1-part1
S: disk/by-path/pci-0000:07:00.0-nvme-1-part/by-partnum/1
S: disk/by-id/nvme-Samsung_SSD_970_EVO_Plus_2TB_S6S2NS0T206213Y-part1
S: disk/by-path/pci-0000:07:00.0-nvme-1-part/by-label/ssd2
Q: 4
E: DEVPATH=/devices/pci0000:00/0000:00:02.1/0000:05:00.0/0000:06:00.0/0000:07:00.0/nvme/nvme1/nvme1n1/nvme1n1p1
E: DEVNAME=/dev/nvme1n1p1
E: DEVTYPE=partition
E: DISKSEQ=4
E: PARTN=1
E: PARTUUID=9357e9c1-47b7-4435-91cc-f13575dc43cc
E: MAJOR=259
E: MINOR=2
E: SUBSYSTEM=block
E: USEC_INITIALIZED=7582114
E: ID_SERIAL_SHORT=S6S2NS0T206213Y
E: ID_WWN=eui.002538522140a56c
E: ID_MODEL=Samsung SSD 970 EVO Plus 2TB
E: ID_REVISION=4B2QEXM7
E: ID_NSID=1
E: ID_SERIAL=Samsung_SSD_970_EVO_Plus_2TB_S6S2NS0T206213Y_1
E: ID_PATH=pci-0000:07:00.0-nvme-1
E: ID_PATH_TAG=pci-0000_07_00_0-nvme-1
E: ID_PART_TABLE_UUID=4192dc3f-06d2-4cb5-af14-9b23a4626508
E: ID_PART_TABLE_TYPE=gpt
E: ID_FS_LABEL=ssd2
E: ID_FS_LABEL_ENC=ssd2
E: ID_FS_UUID=66116352-d0d6-4856-bcc1-a08803d6f8ee
E: ID_FS_UUID_ENC=66116352-d0d6-4856-bcc1-a08803d6f8ee
E: ID_FS_UUID_SUB=f971745f-296f-4222-b615-93dba5b524ae
E: ID_FS_UUID_SUB_ENC=f971745f-296f-4222-b615-93dba5b524ae
E: ID_FS_BLOCKSIZE=4096
E: ID_FS_LASTBLOCK=488378368
E: ID_FS_SIZE=2000397795328
E: ID_FS_TYPE=btrfs
E: ID_FS_USAGE=filesystem
E: ID_PART_ENTRY_SCHEME=gpt
E: ID_PART_ENTRY_UUID=9357e9c1-47b7-4435-91cc-f13575dc43cc
E: ID_PART_ENTRY_TYPE=0fc63daf-8483-4772-8e79-3d69d8477de4
E: ID_PART_ENTRY_NUMBER=1
E: ID_PART_ENTRY_OFFSET=2048
E: ID_PART_ENTRY_SIZE=3907026944
E: ID_PART_ENTRY_DISK=259:0
E: ID_BTRFS_READY=1
E: DEVLINKS=/dev/disk/by-path/pci-0000:07:00.0-nvme-1-part/by-uuid/66116352-d0d6-4856-bcc1-a08803d6f8ee /dev/disk/by-id/nvme-eui.002538522140a56c-part1 /dev/disk/by-diskseq/4-part1 /dev/disk/by-uuid/66116352-d0d6-4856-bcc1-a08803d6f8ee /dev/disk/by-partuuid/9357e9c1-47b7-4435-91cc-f13575dc43cc /dev/disk/by-label/ssd2 /dev/disk/by-path/pci-0000:07:00.0-nvme-1-part1 /dev/disk/by-path/pci-0000:07:00.0-nvme-1-part/by-partuuid/9357e9c1-47b7-4435-91cc-f13575dc43cc /dev/disk/by-id/nvme-Samsung_SSD_970_EVO_Plus_2TB_S6S2NS0T206213Y_1-part1 /dev/disk/by-path/pci-0000:07:00.0-nvme-1-part/by-partnum/1 /dev/disk/by-id/nvme-Samsung_SSD_970_EVO_Plus_2TB_S6S2NS0T206213Y-part1 /dev/disk/by-path/pci-0000:07:00.0-nvme-1-part/by-label/ssd2
E: TAGS=:systemd:
E: CURRENT_TAGS=:systemd:

Zeglius•5d ago

systemctl status ublue-os-media-automount.service

Hammer•5d ago

Having the issue also, here's what I get running that:

× ublue-os-media-automount.service - Mount partitons automaticaly
     Loaded: loaded (/usr/lib/systemd/system/ublue-os-media-automount.service; enabled; preset: disabled)
    Drop-In: /usr/lib/systemd/system/service.d
             └─10-timeout-abort.conf
     Active: failed (Result: exit-code) since Mon 2025-05-19 18:33:41 EDT; 57min ago
   Duration: 41ms
 Invocation: 2468ed62c03342629580e0810c65a10e
    Process: 1460 ExecStart=/usr/libexec/ublue-os-media-automount.py (code=exited, status=1/FAILURE)
   Main PID: 1460 (code=exited, status=1/FAILURE)
   Mem peak: 7M
        CPU: 39ms

May 19 18:33:41 bazzite systemd[1]: Started ublue-os-media-automount.service - Mount partitons automaticaly.
May 19 18:33:41 bazzite ublue-os-media-automount.py[1460]: Traceback (most recent call last):
May 19 18:33:41 bazzite ublue-os-media-automount.py[1460]:   File "/usr/libexec/ublue-os-media-automount.py", >
May 19 18:33:41 bazzite ublue-os-media-automount.py[1460]:     main()
May 19 18:33:41 bazzite ublue-os-media-automount.py[1460]:     ~~~~^^
May 19 18:33:41 bazzite ublue-os-media-automount.py[1460]:   File "/usr/libexec/ublue-os-media-automount.py", >
May 19 18:33:41 bazzite ublue-os-media-automount.py[1460]:     raise RuntimeError("we lack root perms to fetch>
May 19 18:33:41 bazzite ublue-os-media-automount.py[1460]: RuntimeError: we lack root perms to fetch fstype
May 19 18:33:41 bazzite systemd[1]: ublue-os-media-automount.service: Main process exited, code=exited, status>
May 19 18:33:41 bazzite systemd[1]: ublue-os-media-automount.service: Failed with result 'exit-code'.

× ublue-os-media-automount.service - Mount partitons automaticaly
     Loaded: loaded (/usr/lib/systemd/system/ublue-os-media-automount.service; enabled; preset: disabled)
    Drop-In: /usr/lib/systemd/system/service.d
             └─10-timeout-abort.conf
     Active: failed (Result: exit-code) since Mon 2025-05-19 18:33:41 EDT; 57min ago
   Duration: 41ms
 Invocation: 2468ed62c03342629580e0810c65a10e
    Process: 1460 ExecStart=/usr/libexec/ublue-os-media-automount.py (code=exited, status=1/FAILURE)
   Main PID: 1460 (code=exited, status=1/FAILURE)
   Mem peak: 7M
        CPU: 39ms

May 19 18:33:41 bazzite systemd[1]: Started ublue-os-media-automount.service - Mount partitons automaticaly.
May 19 18:33:41 bazzite ublue-os-media-automount.py[1460]: Traceback (most recent call last):
May 19 18:33:41 bazzite ublue-os-media-automount.py[1460]:   File "/usr/libexec/ublue-os-media-automount.py", >
May 19 18:33:41 bazzite ublue-os-media-automount.py[1460]:     main()
May 19 18:33:41 bazzite ublue-os-media-automount.py[1460]:     ~~~~^^
May 19 18:33:41 bazzite ublue-os-media-automount.py[1460]:   File "/usr/libexec/ublue-os-media-automount.py", >
May 19 18:33:41 bazzite ublue-os-media-automount.py[1460]:     raise RuntimeError("we lack root perms to fetch>
May 19 18:33:41 bazzite ublue-os-media-automount.py[1460]: RuntimeError: we lack root perms to fetch fstype
May 19 18:33:41 bazzite systemd[1]: ublue-os-media-automount.service: Main process exited, code=exited, status>
May 19 18:33:41 bazzite systemd[1]: ublue-os-media-automount.service: Failed with result 'exit-code'.

Zeglius•5d ago

Alright, on it Ok an emergency update is building Alright, new build is out, update and should be fixed now

Hammer•5d ago

Installed and rebooted and it is indeed fixed. Thanks for the quick solution!

Finster•5d ago

hmm, is it possible that KDE part ed blanked out all the block device metadata? I was faffing about with the mount point in there, and now lsblk lists this for my drive:

{
         "name": "/dev/nvme1n1p1",
         "fstype": null,
         "type": "part",
         "hotplug": false,
         "mountpoints": [
             null
         ],
         "label": null,
         "partlabel": null
      }

{
         "name": "/dev/nvme1n1p1",
         "fstype": null,
         "type": "part",
         "hotplug": false,
         "mountpoints": [
             null
         ],
         "label": null,
         "partlabel": null
      }

udevadm still lists ID_FS_TYPE=btrfs and ID_FS_LABEL=ssd2 anyway, based on the automount script, pretty sure the fstype and label being null is foiling the automount, even though I removed the mount point in KDE part ed

Zeglius•5d ago

You need to use sudo with lsblk Otherwise will show as null

Finster•5d ago

Ah yes, you are right

Gaming

Programming

after the latest bazzite update, auto-mounting broked

Did you find this page helpful?