Bazzite-deck automount NTFS drives at boot
Bazzite with the deck image mounts all my NTFS drives at boot. How do I stop that?
Solution:Jump to solution
https://github.com/ublue-os/bazzite/pull/2976 this should fix NTFS getting mounted
102 Replies
it shouldnt
rpm-ostree status● ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-deck:stable
Digest: sha256:5a7243860ed83ea6accb3845ba8948a06ee344163cb4696d6fe79b95abad25e9
Version: 42.20250430 (2025-05-01T19:27:27Z)
LayeredPackages: cockpit codium heroic-games-launcher-bin
LocalPackages: cockpit-file-sharing-2.4.5-4.fc39.noarch veracrypt-1.26.20-1.x86_64sudo lsblk -f
when is this start happening
the automounter doesnt even mount drive without label
I don't know, I took notice of it after logging into Steam for the first time on the install and almost wiping my windows steamlibrary
what is
cat /etc/fstab#
# /etc/fstab
# Created by anaconda on Sat Apr 12 16:57:24 2025
#
# Accessible filesystems, by reference, are maintained under '/dev/disk/'.
# See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info.
#
# After editing this file, run 'systemctl daemon-reload' to update systemd
# units generated from this file.
#
# Updated by bootc-fstab-edit.service
UUID=eede1f73-5ea5-49f5-b3b9-51770d4bf25e / btrfs subvol=root,noatime,lazytime,commit=120,discard=async,compress-force=zstd:1,space_cache=v2,x-systemd.device-timeout=0,ro 0 0
UUID=72954668-8394-443f-a30b-6084612715c9 /boot ext4 defaults 1 2
UUID=9DAB-FD7B /boot/efi vfat umask=0077,shortname=winnt 0 2
UUID=eede1f73-5ea5-49f5-b3b9-51770d4bf25e /home btrfs subvol=home,noatime,lazytime,commit=120,discard=async,compress-force=zstd:1,space_cache=v2,x-systemd.device-timeout=0 0 0
UUID=eede1f73-5ea5-49f5-b3b9-51770d4bf25e /var btrfs subvol=var,noatime,lazytime,commit=120,discard=async,compress-force=zstd:1,space_cache=v2,x-systemd.device-timeout=0 0 0im not sure where to check
maybe try
rpm-ostree reset
this will remove all your layer
maybe one of it causing thatThey're still mounted
did you reboot?
Yes
● ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-deck:stable
Digest: sha256:5a7243860ed83ea6accb3845ba8948a06ee344163cb4696d6fe79b95abad25e9
Version: 42.20250430 (2025-05-01T19:27:27Z)Output of
sudo mountit seems it is all being mounted by same thing
similar mount option
someone opened a similar issue on GH 2 weeks ago:
https://github.com/ublue-os/bazzite/issues/2498
GitHub
ntfs drive being automounted when it shouldn't · Issue #2498 · ub...
Describe the bug i have an ntfs formatted drive in my system, in this case a documents drive that also has a steamlibrary, bazzite automounts it for some reason, mount reports it's type as fuse...
sudo udevadm info /dev/whatever_partition
oh wait fuseblk
that could be it
sudo lsblk -o NAME,FSTYPE@Zeglius
A
sudo lsblk -o NAME,FSTYPE:
NAME FSTYPE
sda
├─sda1 vfat
├─sda2 ext4
└─sda3 crypto_LUKS
└─luks-96d4acf0-d6e5-46c7-a6ee-5920029aac97 btrfs
sdb
├─sdb1 vfat
├─sdb2
└─sdb3 ntfs
sdc
└─sdc1 ntfs
sdd
└─sdd1 ntfs
sde
├─sde1 exfat
└─sde2 vfat
zram0 swapOkay, so, in theory it should not mount it given the current udev rules
Unless somewhat is not available to fetch the FSTYPE attribute when is executing
the one without label are even automounted
sudo udevadm info /dev/sdb3:
P: /devices/pci0000:00/0000:00:01.2/0000:02:00.1/ata3/host2/target2:0:0/2:0:0:0/block/sdb/sdb3
M: sdb3
R: 3
J: b8:19
U: block
T: partition
D: b 8:19
N: sdb3
L: 0
S: disk/by-partuuid/ca5624ec-8a0a-4786-9a26-688240311f6a
S: disk/by-path/pci-0000:02:00.1-ata-3.0-part/by-partlabel/Basic\x20data\x20partition
S: disk/by-partlabel/Basic\x20data\x20partition
S: disk/by-path/pci-0000:02:00.1-ata-3-part3
S: disk/by-path/pci-0000:02:00.1-ata-3.0-part/by-partnum/3
S: disk/by-uuid/E4AC67A3AC676F4C
S: disk/by-path/pci-0000:02:00.1-ata-3.0-part3
S: disk/by-path/pci-0000:02:00.1-ata-3.0-part/by-partuuid/ca5624ec-8a0a-4786-9a26-688240311f6a
S: disk/by-id/wwn-0x5001b444a70d0c90-part3
S: disk/by-path/pci-0000:02:00.1-ata-3.0-part/by-uuid/E4AC67A3AC676F4C
S: disk/by-id/ata-WDC_WDS500G2B0A-00SM50_2113DY475302-part3
S: disk/by-diskseq/2-part3
Q: 2
E: DEVPATH=/devices/pci0000:00/0000:00:01.2/0000:02:00.1/ata3/host2/target2:0:0/2:0:0:0/block/sdb/sdb3
E: DEVNAME=/dev/sdb3
E: DEVTYPE=partition
E: DISKSEQ=2
E: PARTN=3
E: PARTNAME=Basic data partition
E: PARTUUID=ca5624ec-8a0a-4786-9a26-688240311f6a
E: MAJOR=8
E: MINOR=19
E: SUBSYSTEM=block
E: USEC_INITIALIZED=10682957
E: ID_ATA=1
E: ID_TYPE=disk
E: ID_BUS=ata
E: ID_MODEL=WDC_WDS500G2B0A-00SM50
E: ID_MODEL_ENC=WDC\x20\x20WDS500G2B0A-00SM50\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20
E: ID_REVISION=401020WD
E: ID_SERIAL=WDC_WDS500G2B0A-00SM50_2113DY475302
E: ID_SERIAL_SHORT=2113DY475302
E: ID_ATA_WRITE_CACHE=1
E: ID_ATA_WRITE_CACHE_ENABLED=1
E: ID_ATA_READ_LOOKAHEAD=1
E: ID_ATA_READ_LOOKAHEAD_ENABLED=1
E: ID_ATA_FEATURE_SET_PM=1
E: ID_ATA_FEATURE_SET_PM_ENABLED=1
E: ID_ATA_FEATURE_SET_SECURITY=1
E: ID_ATA_FEATURE_SET_SECURITY_ENABLED=0
E: ID_ATA_FEATURE_SET_SECURITY_ERASE_UNIT_MIN=2
E: ID_ATA_FEATURE_SET_SECURITY_ENHANCED_ERASE_UNIT_MIN=2
E: ID_ATA_FEATURE_SET_SECURITY_FROZEN=1
E: ID_ATA_FEATURE_SET_SMART=1
E: ID_ATA_FEATURE_SET_SMART_ENABLED=1
E: ID_ATA_FEATURE_SET_APM=1
E: ID_ATA_FEATURE_SET_APM_ENABLED=1Ok now that's weird
E: ID_ATA_FEATURE_SET_APM_CURRENT_VALUE=128yeah, im not even sure where to probe 💀
Ok so this is a good hint, I don't see FSTYPE there
I have the same issue, can't remember exactly when it started happening, but I'm sure it started happening after an update.
If it helps troubleshooting, I can get you some logs when I'm back home on Sunday
Try the udevadm command above
sorry for the late response had a bad hangover on sunday 😄
edit: wrong partition
this is the right one
@Zeglius huh this one has fstype
I may have an I idea why this is happening in my case, I recently switched my boot drives. Win11 was on my nvme and I switched the installation with bazzite on my old sata ssd. Could it be that the sda3 partition is now automounted, because it was my bazzite btrfs partition before?
Nah, it checks for the partition filesystem
Shouldn't be mounting other than ext4 or BTRFS
Ok so what I see in common as well is the partname
So, what would be the ETA for this PR getting downstreamed into Bazzite?
next week probably, afaik bazzite stable is pushed atleast once a week
Hey look that's my issue
So I looked at the pull request and noticed it just does a part name check
My 2nd drive aka the docs drive is labelled, aka "docs" would it even work with the change done since it does a check if the part name matches the ntfs default?
I'm trying to set up my own udev rule right now to tell udisks to ignore the drive (by setting auto to 0 and ignore to 1)
If that doesn't work I might set it up so that when bazzite does automount it, it goes "nuh uh" and unmounts it
Also same with one of the other people
ID_FS_TYPE is correctly marked as ntfs
@traenkeopa @Lara @Lightprod the latest stable have included the latest automounter fix with db preloading, does it work for you guys now?
my Win11 drive is still automounted on boot
Want to see the version
rpm -qa | grep automo
ublue-os-media-automount-udev-0.11-1.fc42.noarchOk now
sudo udevadm info /dev/WINDOWS_PARTITION_DEV, you can check what dev is that windows partition with sudo lsblk --paths --list -o NAME,MOUNTPOINT,LABELkk, now unmount that partition, and run
sudo udevadm trigger --action add /dev/WINDOWS_PARTITION_DEV, and see if it gets mountednope, doesn´t get mounted
Okay, now
/usr/libexec/is_in_fstab.sh /dev/WINDOWS_PARTITION_DEV/usr/libexec/is_in_fstab.sh /dev/sda3
UBLUEOS_PART_IS_IN_FSTAB=0No it's still being mounted
It made no difference
For me it was in the fstab because I tried to see if noauto mount flag would make a difference
I'll remove the label on the partition and see if that makes a difference
Since the check added in that commit shown just checks if the label is "Basic data partition" aka the stock ntfs partition name
Any update regarding this issue?
Got a complete rewrite and shouldn't mount ntfs anymore
It's it on the most recent image?
Yeah
Ok I will check once it updates
It still does.
rpm-ostree status -v:
State: idle
AutomaticUpdates: disabled
Deployments:
● ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-deck:stable (index: 0)
Digest: sha256:b07fe8d109b15e6d6bd87db658daa55f751e5756827fd14aec0b71c70514d2af
Version: 42.20250522.1 (2025-05-22T07:12:55Z)
Commit: 816ef436e79fb00e5c24000ef15f99ac731ef993cee24ecb07775c38612efaf9
Staged: no
StateRoot: default
ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-deck:stable (index: 1)
Digest: sha256:38ef326fd9608171ec85b1fef019bcd3d1883041832e5f5134f93c51db262a7c
Version: 42.20250513 (2025-05-13T16:20:32Z)
Commit: 779a92ff9cdde6d48e40aad6a58f5d46d68a78ff9e04bdcc7b8b266befc27e8f
StateRoot: default
ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-deck:stable (index: 2)
Digest: sha256:5a7243860ed83ea6accb3845ba8948a06ee344163cb4696d6fe79b95abad25e9
Version: 42.20250430 (2025-05-01T19:27:27Z)
Commit: e8c197e7aa33e5d0338cd6a5e6799fe35c1b6ca223651e030e95e0f2ccf58c77
StateRoot: default
Pinned: yes
sudo lsblk -f
That look it's you are the one mounting it, check the fstab
nano /etc/fstab:
#
# /etc/fstab
# Created by anaconda on Sat Apr 12 16:57:24 2025
#
# Accessible filesystems, by reference, are maintained under '/dev/disk/'.
# See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info.
#
# After editing this file, run 'systemctl daemon-reload' to update systemd
# units generated from this file.
#
# Updated by bootc-fstab-edit.service
UUID=eede1f73-5ea5-49f5-b3b9-51770d4bf25e / btrfs subvol=root,noatime,lazytime,commit=120,discard=async,compress-force=zstd:1,space_cache=v2,x-systemd.device-timeout=0,ro 0 0
UUID=72954668-8394-443f-a30b-6084612715c9 /boot ext4 defaults 1 2
UUID=9DAB-FD7B /boot/efi vfat umask=0077,shortname=winnt 0 2
UUID=eede1f73-5ea5-49f5-b3b9-51770d4bf25e /home btrfs subvol=home,noatime,lazytime,commit=120,discard=async,compress-force=zstd:1,space_cache=v2,x-systemd.device-timeout=0 0 0
UUID=eede1f73-5ea5-49f5-b3b9-51770d4bf25e /var btrfs subvol=var,noatime,lazytime,commit=120,discard=async,compress-force=zstd:1,space_cache=v2,x-systemd.device-timeout=0 0 0systemd-escape -p /run/media/anthony/E4AC67A3AC676F4C | xargs systemctl statussystemd-escape -p run/media/anthony/E4AC67A3AC676F4C | xargs systemctl status
Input 'run/media/anthony/E4AC67A3AC676F4C' is not an absolute file system path, escaping is likely not going to be reversible.
Unit run-media-anthony-E4AC67A3AC676F4C.service could not be found.systemctl state /run/media/anthony/E4AC67A3AC676F4C Ok see if this one workssystemctl state /run/media/anthony/E4AC67A3AC676F4C
Unknown command verb 'state', did you mean 'start'?oh
status, my bad 😭● run-media-anthony-E4AC67A3AC676F4C.mount - /run/media/anthony/E4AC67A3AC676F4C
Loaded: loaded (/proc/self/mountinfo)
Active: active (mounted) since Thu 2025-05-22 19:28:31 CEST; 26min ago
Invocation: 1ec3b44efe6d4286b765eb7becc9468c
Where: /run/media/anthony/E4AC67A3AC676F4C
What: /dev/sdb3right, thats weird, maybe gnome disks is playing tricks or something dunno
I tried to umount them through KDE's disk manager and reboot, no effect
Considering it's pretty much a fresh install, should I try to reinstall?
Yeah try that
ok, I will try tomorow
It's automounted on a fresh install
Anthony@arcturus-bazzite:~$ rpm-ostree status -v
State: idle
AutomaticUpdates: disabled
Deployments:
● ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-deck:stable (index: 0)
Digest: sha256:b07fe8d109b15e6d6bd87db658daa55f751e5756827fd14aec0b71c70514d2af
Version: 42.20250522.1 (2025-05-22T07:12:55Z)
Commit: 4815b532d2d4232164255cb84873b98caeaa3cb416018afe3a3d45054e78fd60
Staged: no
StateRoot: default
ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-deck:stable (index: 1)
Digest: sha256:6f8bbe709d2fa6a7c0094c2f02012d097fd3a59e235033f70807668acfe5b7fc
Version: 42.20250511 (2025-05-12T03:51:16Z)
Commit: cefb4a396ed3952d84e359f3f0a3455bb6937de7fc7276fe80fd00ebf39eb04f
StateRoot: default
At that point, is there a way to disable any automount that's not in fstab?
No if we don't know how these getting to be mounted in the first place
If that help: I rebased to the regular bazzite:stable and the ntfs drives are not mounted on login
the desktop image?
Yes
I was testing it on a vm so I noticed it didn't mount them. So I tested on my system.
Still happening on latest image as of today
@Zeglius If it's useful for you: For some reason, when checked with GNOME Disks it shows that the automount is a default user config. On a fresh install
ah right, that means the entry isnt in the fstab
Yes
There is only / ; /boot ; /home; /var in the fstab
Overriding the default options does not work. It added this to fstab but it still was mounted:
/dev/disk/by-uuid/E4AC67A3AC676F4C /mnt/E4AC67A3AC676F4C auto nosuid,nodev,nofail,x-gvfs-show,noauto 0 0well yah that mounts it
It shouldn't with noauto?
mmm, actually,
ls /etc/systemd/{system,user}-generators/
maybe there is a leftover there of the previous automountingbazzite@arcturus:~$ sudo ls /etc/systemd/{system,user}-generators/
[sudo] Mot de passe de bazzite :
ls: impossible d'accéder à '/etc/systemd/system-generators/': Aucun fichier ou dossier de ce nom
ls: impossible d'accéder à '/etc/systemd/user-generators/': Aucun fichier ou dossier de ce nomk nvm then
Weirdly enough, adding ro is not overrulled by whatever is autoumounting
I doubt installing with ventoy is the problem
no ventoy shouldnt be something to factor
So I couldn't recreate the issue on a AMD laptop with the deck image
This is really weird
It feel like I should nuke all partitions on my HTPC and restart fresh
Tried that by disconecting all drives minus my btrfs game nvme drive. Swaped out the ntfs game m.2 sata drive by an empty one.
Reinstalled W11 24H2 LTSC and bazzite-deck on same drive. The Windows partition is still being mounted. @Zeglius
I kid you not when I mean this is an unique case with your setup
All I can say is ignoring the NTFS drive, can't fathom why is getting mounted
I guess I could modify the fstab to mount them as read only, then run a script at boot to dismount them?
Maybe
I just realised
The drive which has the partition that is getting automounted is MBR partitioned
Although I doubt that's the issue
I even removed the label and that didn't fix the mounting issue
Do you use a ASUS AMD motherboard? Just Wondering
Right, so found out it was Steamos automounting udev rules what is triggering NTFS partitions to get mounted
Oh I see
Weird that I could replicate this only on my Gaming PC
Should I expect a fix or do I need to keep using a workaround with a systemd dismounting service at bootup?
you can mask the udev rules by creating an empty file at /etc/udev/rules.d with the same name as these
Sorry but what do I need call the file? I have not dealt with udev rules before still a linux newbie 😄
Honestly, would simply ignore that and let the NTFS partitions be
You can end up breaking your system if you don't know what you are doing
Only if you don't have a Steam Library on those partitions, else Steam pick them up
:glorp: oh
I didn´t have any issues with Steam picking up my Windows library yet, weird...
tuf gaming b550-plus yea
Solution
https://github.com/ublue-os/bazzite/pull/2976 this should fix NTFS getting mounted
Fixed.
bazzite@arcturus:~$ rpm-ostree status
State: idle
Deployments:
● ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-deck:testing
Digest: sha256:6e4dc650003c852dd28a1db7cec7bdbf368b0ed650411a4acbbb156f539bd29d
Version: testing-42.20250724.4 (2025-07-26T16:43:00Z)
ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-deck:stable
Digest: sha256:e7efe7a4715cfa4f74573954245019db49942ae13fd33487a77b43622b9ba435
Version: 42.20250708 (2025-07-08T05:41:28Z)