Bazzite-deck automount NTFS drives at boot
Bazzite with the deck image mounts all my NTFS drives at boot. How do I stop that?
28 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