After a recent update my install of Gnome Disk manager(46.1-2) no longer auto mounts drives and I cannot figure out why or what even happened? Gnome-Disk-utility was installed from the Extra repository
kde: 6.7.3
kde framework: 6.28
qt version: 6.11.1
Kernel: 6.12.96-1-MANJARO (64-bit)
Wayland
My crystal ball is telling me you are trying to mount ntfs, and at the bottom of the window with mounting options you have “filesystem type - auto” which you have to change to ntfs3 (or ntfs or ntfs-3g, i forgot the exact trick).
If the crystal ball is wrong, please provide an inxi, lsblk etc.
Nope all btrfs. as mentioned in my post it worked fine for month then simply stopped working. Nothing changed just an update from a few days ago. Nothing on my sys has actually really changed
Can’t include inxi since copying and pasting it counts as posting a link, and I cant upload a screenshot for some reason
Mod edit:- Please avoid consecutive posts. If there has not been a reply since your last post edit that post, instead, to include additional content. Remedied, no charge.
Ok, besides inxi -zv8 and lsblk -fa post also cat /etc/fstab
First click the <> button, then paste between the rows of ticks.
Not sure how every attempt to do so is blocked either because the site thinks its a link or the fact it wont let me upload media
I’ve tried everything I can think of I have no clue how i’m supposed to give you that information
Mod edit:- Please avoid consecutive posts. If there has not been a reply since your last post edit that post, instead, to include additional content. Remedied, no charge.
Open a console of your choice. Type in inxi -zv8 and select the entire output with your mouse. Right-click -> Copy. Select Reply in this thread. Click in the left-hand field, then click on </>, then press CTRL+V and followed by Reply in the down left corner!
Teo: fixed it for you 
The gnome disk utility never auto mount devices.
You can use gnome disks to configure the system to auto mount a device but this is done by editing the file /etc/fstab.
So this is likely not an issue with gnome disks but rather a failure in the file system.
btrfs is known to block access to damaged file systems, thus preventing further damage to occur.
System:
Kernel: 6.12.96-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 16.1.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-6.12-x86_64
root=UUID=c53cde03-926a-4cc8-82e4-019749e954c1 rw rootflags=subvol=@
quiet splash udev.log_priority=3
Desktop: KDE Plasma v: 6.7.3 tk: Qt v: N/A info: frameworks v: 6.28.0
wm: kwin_wayland vt: 1 dm: SDDM Distro: Manjaro base: Arch Linux
Machine:
Type: Desktop System: ASUS product: N/A v: N/A serial: <superuser required>
Mobo: ASUSTeK model: ProArt X870E-CREATOR WIFI v: Rev 1.xx
serial: <superuser required> part-nu: SKU uuid: <superuser required>
Firmware: UEFI vendor: American Megatrends v: 1512 date: 06/05/2025
Battery:
Device-1: ps-controller-battery-58:10:31:04:38:51 model: N/A serial: N/A
charge: N/A status: discharging
Memory:
System RAM: total: 32 GiB available: 30.49 GiB used: 10.36 GiB (34.0%)
Message: For most reliable report, use superuser + dmidecode.
Array-1: capacity: 256 GiB slots: 4 modules: 2 EC: None
max-module-size: 64 GiB note: est.
Device-1: Channel-A DIMM 0 type: no module installed
Device-2: Channel-A DIMM 1 type: DDR5 detail: synchronous unbuffered
(unregistered) size: 16 GiB speed: spec: 4800 MT/s actual: 6000 MT/s
volts: note: check curr: 1 min: 1 max: 1 width (bits): data: 64 total: 64
manufacturer: G Skill Intl part-no: F5-6000U4040E16G serial: N/A
Device-3: Channel-B DIMM 0 type: no module installed
Device-4: Channel-B DIMM 1 type: DDR5 detail: synchronous unbuffered
(unregistered) size: 16 GiB speed: spec: 4800 MT/s actual: 6000 MT/s
volts: note: check curr: 1 min: 1 max: 1 width (bits): data: 64 total: 64
manufacturer: G Skill Intl part-no: F5-6000U4040E16G serial: N/A
PCI Slots:
Permissions: Unable to run dmidecode. Root privileges required.
CPU:
Info: model: AMD Ryzen 7 9800X3D bits: 64 type: MT MCP arch: Zen 5 gen: 5
level: v4 note: check built: 2024+ process: TSMC n4 (4nm) family: 0x1A (26)
model-id: 0x44 (68) stepping: 0 microcode: 0xB404035
Topology: cpus: 1x dies: 1 clusters: 1 cores: 8 threads: 16 tpc: 2
smt: enabled cache: L1: 640 KiB desc: d-8x48 KiB; i-8x32 KiB L2: 8 MiB
desc: 8x1024 KiB L3: 96 MiB desc: 1x96 MiB
Speed (MHz): avg: 5362 min/max: 600/5269 boost: enabled scaling:
driver: amd-pstate-epp governor: performance cores: 1: 5362 2: 5362 3: 5362
4: 5362 5: 5362 6: 5362 7: 5362 8: 5362 9: 5362 10: 5362 11: 5362 12: 5362
13: 5362 14: 5362 15: 5362 16: 5362 bogomips: 150170
Flags: 3dnowprefetch abm adx aes amd_lbr_pmc_freeze amd_lbr_v2 aperfmperf
apic arat avic avx avx2 avx512_bf16 avx512_bitalg avx512_vbmi2
avx512_vnni avx512_vp2intersect avx512_vpopcntdq avx512bw avx512cd
avx512dq avx512f avx512ifma avx512vbmi avx512vl avx_vnni bmi1 bmi2 bpext
bus_lock_detect cat_l3 cdp_l3 clflush clflushopt clwb clzero cmov
cmp_legacy constant_tsc cpb cppc cpuid cqm cqm_llc cqm_mbm_local
cqm_mbm_total cqm_occup_llc cr8_legacy cx16 cx8 de decodeassists erms
extapic extd_apicid f16c flush_l1d flushbyasid fma fpu fsgsbase fsrm fxsr
fxsr_opt gfni ht hw_pstate ibpb ibrs ibrs_enhanced ibs invpcid irperf
lahf_lm lbrv lm mba mca mce misalignsse mmx mmxext monitor movbe
movdir64b movdiri msr mtrr mwaitx nonstop_tsc nopl npt nrip_save nx ospke
osvw overflow_recov pae pat pausefilter pclmulqdq pdpe1gb perfctr_core
perfctr_llc perfctr_nb perfmon_v2 pfthreshold pge pku pni popcnt pse
pse36 rapl rdpid rdpru rdrand rdseed rdt_a rdtscp rep_good sep sha_ni
skinit smap smca smep ssbd sse sse2 sse4_1 sse4_2 sse4a ssse3 stibp
succor svm svm_lock syscall tce topoext tsc tsc_adjust tsc_scale umip
user_shstk v_spec_ctrl v_vmsave_vmload vaes vgif vmcb_clean vme vmmcall
vnmi vpclmulqdq wbnoinvd wdt x2avic xgetbv1 xsave xsavec xsaveerptr
xsaveopt xsaves xtopology
Vulnerabilities:
Type: gather_data_sampling status: Not affected
Type: indirect_target_selection status: Not affected
Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: mmio_stale_data status: Not affected
Type: reg_file_data_sampling status: Not affected
Type: retbleed status: Not affected
Type: spec_rstack_overflow mitigation: IBPB on VMEXIT only
Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
prctl
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
sanitization
Type: spectre_v2 mitigation: Enhanced / Automatic IBRS; IBPB:
conditional; STIBP: always-on; PBRSB-eIBRS: Not affected; BHI: Not
affected
Type: srbds status: Not affected
Type: tsa status: Not affected
Type: tsx_async_abort status: Not affected
Type: vmscape mitigation: IBPB on VMEXIT
Graphics:
Device-1: NVIDIA AD102 [GeForce RTX 4090] driver: nvidia v: 610.43.03
alternate: nouveau,nvidia_drm non-free: 550-6xx.xx+
status: current (as of 2026-07) arch: Lovelace code: AD1xx
process: TSMC n4 (5nm) built: 2022+ pcie: gen: 4 speed: 16 GT/s lanes: 8
link-max: lanes: 16 ports: active: DP-3,DP-4,DP-5 empty: HDMI-A-2
bus-ID: 01:00.0 chip-ID: 10de:2684 class-ID: 0300
Device-2: Advanced Micro Devices [AMD/ATI] Granite Ridge [Radeon Graphics]
vendor: ASUSTeK driver: amdgpu v: kernel arch: RDNA-2 code: Navi-2x
process: TSMC n7 (7nm) built: 2020-22 pcie: gen: 4 speed: 16 GT/s
lanes: 16 ports: active: none empty: DP-1, DP-2, HDMI-A-1, Writeback-1
bus-ID: 7a:00.0 chip-ID: 1002:13c0 class-ID: 0300 temp: 38.0 C
Display: wayland server: X.org v: 1.21.1.24 with: Xwayland v: 24.1.13
compositor: kwin_wayland driver: X: loaded: nvidia
gpu: nv_platform,nvidia,nvidia-nvswitch d-rect: 5120x4208 display-ID: 0
Monitor-1: DP-3 pos: bottom-r model: Dell 1704FPT serial: <filter>
built: 2005 res: mode: 1280x1024 hz: 75 scale: 100% (1) dpi: 96 gamma: 1.2
chroma: red: x: 0.639 y: 0.341 green: x: 0.290 y: 0.612 blue: x: 0.137
y: 0.071 white: x: 0.310 y: 0.329 size: 338x270mm (13.31x10.63")
diag: 433mm (17") ratio: 5:4 modes: 1280x1024, 1152x864, 1024x768,
800x600, 640x480
Monitor-2: DP-4 pos: top-right model: Dell 1703FP serial: <filter>
built: 2003 res: mode: 1280x1024 hz: 75 scale: 100% (1) dpi: 96 gamma: 1.2
chroma: red: x: 0.639 y: 0.329 green: x: 0.298 y: 0.600 blue: x: 0.149
y: 0.059 white: x: 0.310 y: 0.329 size: 338x270mm (13.31x10.63")
diag: 433mm (17") ratio: 5:4 modes: 1280x1024, 1152x864, 1024x768,
800x600, 640x480
Monitor-3: DP-5 pos: middle-l model: Samsung Odyssey G8 serial: <filter>
built: 2022 res: mode: 3840x2160 hz: 240 scale: 140% (1.4) to: 2743x1543
dpi: 139 gamma: 1.2 chroma: red: x: 0.682 y: 0.306 green: x: 0.271
y: 0.667 blue: x: 0.153 y: 0.055 white: x: 0.314 y: 0.329
size: 697x392mm (27.44x15.43") diag: 806mm (31.7") ratio: 16:9
modes: 3840x2160, 2560x1440, 1920x1080, 1680x1050, 1600x900, 1280x1024,
1440x900, 1280x800, 1280x720, 1024x768, 800x600, 720x480, 640x480
EDID-Warnings: 1: parse_edid: unhandled CEA mode 97 2: parse_edid:
unhandled CEA mode 95 3: parse_edid: unhandled CEA mode 118 4: parse_edid:
unknown tag 112
API: EGL v: 1.5 hw: drv: nvidia drv: amd radeonsi platforms: device: 0
drv: nvidia device: 2 drv: radeonsi device: 3 drv: swrast gbm: drv: nvidia
surfaceless: drv: nvidia wayland: drv: nvidia x11: drv: nvidia
inactive: device-1
API: OpenGL v: 4.6.0 compat-v: 4.6 vendor: nvidia mesa v: 610.43.03
glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce RTX 4090/PCIe/SSE2
memory: 23.43 GiB display-ID: :1.0
API: Vulkan v: 1.4.350 layers: 12 device: 0 type: discrete-gpu
name: NVIDIA GeForce RTX 4090 driver: nvidia v: 610.43.03
device-ID: 10de:2684 surfaces: N/A device: 1 type: integrated-gpu name: AMD
Ryzen 7 9800X3D 8-Core Processor (RADV RAPHAEL_MENDOCINO)
driver: mesa radv v: 26.1.5-arch1.1 device-ID: 1002:13c0 surfaces: N/A
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
de: kscreen-console,kscreen-doctor gpu: nvidia-settings,nvidia-smi
wl: wayland-info x11: xdpyinfo, xprop, xrandr
Audio:
Device-1: NVIDIA AD102 High Definition Audio driver: snd_hda_intel v: kernel
pcie: gen: 4 speed: 16 GT/s lanes: 8 link-max: lanes: 16 bus-ID: 01:00.1
chip-ID: 10de:22ba class-ID: 0403
Device-2: Advanced Micro Devices [AMD/ATI] Radeon High Definition Audio
vendor: ASUSTeK driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s
lanes: 16 bus-ID: 7a:00.1 chip-ID: 1002:1640 class-ID: 0403
Device-3: Advanced Micro Devices [AMD] Ryzen HD Audio vendor: ASUSTeK
driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
bus-ID: 7a:00.6 chip-ID: 1022:15e3 class-ID: 0403
Device-4: RODE Microphones RØDE NT-USB Mini
driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 2.0 speed: 12 Mb/s
lanes: 1 mode: 1.1 bus-ID: 1-2:2 chip-ID: 19f7:0015 class-ID: 0300
serial: <filter>
API: ALSA v: k6.12.96-1-MANJARO status: kernel-api with: aoss
type: oss-emulator tools: alsactl,alsamixer,amixer
Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
Server-2: JACK v: 1.9.22 status: off tools: N/A
Server-3: PipeWire v: 1.6.8 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Intel Wi-Fi 6E AX210/AX1675 2x2 [Typhoon Peak] driver: iwlwifi
v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 1 bus-ID: 0a:00.0
chip-ID: 8086:2725 class-ID: 0280
IF: wlp10s0 state: up mac: <filter>
IP v4: <filter> type: dynamic noprefixroute scope: global
broadcast: <filter>
IP v6: <filter> type: noprefixroute scope: link
Device-2: Intel Ethernet I226-V vendor: ASUSTeK driver: igc v: kernel
pcie: gen: 2 speed: 5 GT/s lanes: 1 port: N/A bus-ID: 0b:00.0
chip-ID: 8086:125c class-ID: 0200
IF: enp11s0 state: up speed: 2500 Mbps duplex: full mac: <filter>
IP v4: <filter> type: dynamic noprefixroute scope: global
broadcast: <filter>
IP v6: <filter> type: dynamic noprefixroute scope: global
IP v6: <filter> type: noprefixroute scope: link
Device-3: Aquantia AQtion AQC113 NBase-T/IEEE 802.3an Ethernet [Antigua
10G] vendor: ASUSTeK driver: atlantic v: kernel pcie: gen: 3 speed: 8 GT/s
lanes: 2 link-max: gen: 4 speed: 16 GT/s lanes: 4 port: N/A
bus-ID: 0c:00.0 chip-ID: 1d6a:04c0 class-ID: 0200
IF: enp12s0 state: down mac: <filter>
Info: services: NetworkManager, systemd-timesyncd, wpa_supplicant
WAN IP: <filter>
Bluetooth:
Device-1: Intel AX210 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-6:8 chip-ID: 8087:0032
class-ID: e001
Report: rfkill ID: hci0 rfk-id: 2 state: up address: see --recommends
Logical:
Message: No logical block device data found.
RAID:
Message: No RAID data found.
Drives:
Local Storage: total: 20.48 TiB used: 8.64 TiB (42.2%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:2 vendor: Samsung model: SSD 980 PRO 1TB
size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
lanes: 4 tech: SSD serial: <filter> fw-rev: 5B2QGXA7 temp: 34.9 C
scheme: GPT
ID-2: /dev/nvme1n1 maj-min: 259:7 vendor: Western Digital
model: WD BLACK SN850 PS5 1TB size: 931.51 GiB block-size: physical: 512 B
logical: 512 B speed: 63.2 Gb/s lanes: 4 tech: SSD serial: <filter>
fw-rev: 615000WD temp: 34.9 C scheme: GPT
ID-3: /dev/nvme2n1 maj-min: 259:0 vendor: Samsung model: SM951 NVMe 512GB
size: 476.94 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
lanes: 4 tech: SSD serial: <filter> fw-rev: BXW75D0Q temp: 32.9 C
scheme: GPT
ID-4: /dev/sda maj-min: 8:0 vendor: Hitachi model: HUS724040ALE641
size: 3.64 TiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
tech: HDD rpm: 7200 serial: <filter> fw-rev: A5F0 scheme: GPT
ID-5: /dev/sdb maj-min: 8:16 vendor: Crucial model: CT4000MX500SSD1
size: 3.64 TiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 046 scheme: GPT
ID-6: /dev/sdc maj-min: 8:32 vendor: Samsung model: SSD 870 EVO 2TB
size: 1.82 TiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 3B6Q scheme: GPT
ID-7: /dev/sdd maj-min: 8:48 vendor: Crucial model: CT1000MX500SSD1
size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 046 scheme: GPT
ID-8: /dev/sde maj-min: 8:64 vendor: Crucial model: CT1000MX500SSD1
size: 931.51 GiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 046 scheme: GPT
ID-9: /dev/sdf maj-min: 8:80 vendor: Samsung model: SSD 870 EVO 4TB
size: 3.64 TiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 3B6Q scheme: GPT
ID-10: /dev/sdg maj-min: 8:96 vendor: Crucial model: CT4000MX500SSD1
size: 3.64 TiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 046 scheme: GPT
Message: No optical or floppy data found.
Partition:
ID-1: / raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
used: 373.27 GiB (40.1%) fs: btrfs dev: /dev/nvme1n1p2 maj-min: 259:9
label: N/A uuid: c53cde03-926a-4cc8-82e4-019749e954c1
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 668 KiB (0.2%) fs: vfat dev: /dev/nvme1n1p1 maj-min: 259:8 label: N/A
uuid: 6FDA-2AF8
ID-3: /home raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
used: 373.27 GiB (40.1%) fs: btrfs dev: /dev/nvme1n1p2 maj-min: 259:9
label: N/A uuid: c53cde03-926a-4cc8-82e4-019749e954c1
ID-4: /mnt/Blue raw-size: 931.13 GiB size: 931.13 GiB (100.00%)
used: 813.21 GiB (87.3%) fs: btrfs dev: /dev/sde3 maj-min: 8:67 label: Blue
uuid: c5946428-c1eb-4fb9-b62b-f5a7960830f8
ID-5: /mnt/Cargobay raw-size: 931.51 GiB size: 931.51 GiB (100.00%)
used: 755.06 GiB (81.1%) fs: btrfs dev: /dev/sdd1 maj-min: 8:49
label: Cargobay uuid: 61754390-15dc-4cf6-a084-6a57144d434e
ID-6: /mnt/Cyan raw-size: 1.82 TiB size: 1.82 TiB (100.00%)
used: 1.53 TiB (84.2%) fs: btrfs dev: /dev/sdc2 maj-min: 8:34 label: Cyan
uuid: d3dbcb88-0b8b-424d-bbb0-733bda861b08
ID-7: /mnt/HDD raw-size: 3.64 TiB size: 3.64 TiB (100.00%)
used: 1.55 TiB (42.7%) fs: btrfs dev: /dev/sda1 maj-min: 8:1 label: Heavy3s
uuid: 98d484cd-3601-4e29-b707-88fb413029d7
ID-8: /mnt/SSD raw-size: 3.64 TiB size: 3.64 TiB (100.00%)
used: 1.5 TiB (41.3%) fs: btrfs dev: /dev/sdf1 maj-min: 8:81 label: Lingame2
uuid: 5711a371-b756-4659-aad2-c7851a800f0a
ID-9: /mnt/Winspeed raw-size: 476.94 GiB size: 476.94 GiB (100.00%)
used: 224.56 GiB (47.1%) fs: btrfs dev: /dev/nvme2n1p1 maj-min: 259:1
label: winspeed uuid: c9e6a273-5643-4aea-b01b-6c8b9575ebb7
ID-10: /run/media/alex/Heavy2 raw-size: 3.64 TiB size: 3.64 TiB (100.00%)
used: 1.94 TiB (53.3%) fs: ntfs dev: /dev/sdg2 maj-min: 8:98 label: Heavy2
uuid: 0214B76E14B762F9
ID-11: /var/cache raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
used: 373.27 GiB (40.1%) fs: btrfs dev: /dev/nvme1n1p2 maj-min: 259:9
label: N/A uuid: c53cde03-926a-4cc8-82e4-019749e954c1
ID-12: /var/log raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
used: 373.27 GiB (40.1%) fs: btrfs dev: /dev/nvme1n1p2 maj-min: 259:9
label: N/A uuid: c53cde03-926a-4cc8-82e4-019749e954c1
Swap:
Alert: No swap data was found.
Unmounted:
ID-1: /dev/nvme0n1p1 maj-min: 259:3 size: 50 MiB fs: ntfs
label: System Reserved uuid: 9A3E07BC3E079105
ID-2: /dev/nvme0n1p2 maj-min: 259:4 size: 929.73 GiB fs: ntfs
label: Windows uuid: 2C00084700081B0A
ID-3: /dev/nvme0n1p3 maj-min: 259:5 size: 1.14 GiB fs: ntfs label: N/A
uuid: 68083AAB083A7860
ID-4: /dev/nvme0n1p4 maj-min: 259:6 size: 100 MiB fs: vfat label: N/A
uuid: 3C5C-8928
ID-5: /dev/sdb1 maj-min: 8:17 size: 16 MiB fs: <superuser required>
label: N/A uuid: N/A
ID-6: /dev/sdb2 maj-min: 8:18 size: 3.64 TiB fs: ntfs label: Heavy1
uuid: 0C28C45F28C44A02
ID-7: /dev/sdc1 maj-min: 8:33 size: 16 MiB fs: <superuser required>
label: N/A uuid: N/A
ID-8: /dev/sde1 maj-min: 8:65 size: 260 MiB fs: vfat label: SYSTEM
uuid: 34FA-2568
ID-9: /dev/sde2 maj-min: 8:66 size: 128 MiB fs: <superuser required>
label: N/A uuid: N/A
ID-10: /dev/sdg1 maj-min: 8:97 size: 16 MiB fs: <superuser required>
label: N/A uuid: N/A
USB:
Hub-1: 1-0:1 info: hi-speed hub with single TT ports: 12 rev: 2.0
speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
class-ID: 0900
Device-1: 1-2:2 info: RODE Microphones RØDE NT-USB Mini type: audio,HID
driver: hid-generic,snd-usb-audio,usbhid interfaces: 4 rev: 2.0
speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 power: 100mA
chip-ID: 19f7:0015 class-ID: 0300 serial: <filter>
Hub-2: 1-4:3 info: Genesys Logic Hub ports: 4 rev: 2.1
speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 100mA
chip-ID: 05e3:0610 class-ID: 0900
Device-1: 1-4.2:5 info: Razer USA RC30-0305 Gaming Mouse Dongle [Viper
Ultimate (Wireless)] type: mouse,keyboard driver: hid-generic,usbhid
interfaces: 3 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1
power: 500mA chip-ID: 1532:007b class-ID: 0300
Device-2: 1-4.3:7 info: Razer USA RC30-030502 Mouse Dock
type: mouse,keyboard driver: hid-generic,usbhid interfaces: 3 rev: 2.0
speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 power: 500mA
chip-ID: 1532:007e class-ID: 0300
Device-3: 1-6:8 info: Intel AX210 Bluetooth type: bluetooth driver: btusb
interfaces: 2 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1
power: 100mA chip-ID: 8087:0032 class-ID: e001
Device-4: 1-7:6 info: ASUSTek AURA LED Controller type: HID
driver: hid-generic,usbhid interfaces: 2 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s)
lanes: 1 mode: 1.1 power: 16mA chip-ID: 0b05:19af class-ID: 0300
serial: <filter>
Hub-3: 2-0:1 info: super-speed hub ports: 5 rev: 3.1
speed: 20 Gb/s (2.33 GiB/s) lanes: 2 mode: 3.2 gen-2x2 chip-ID: 1d6b:0003
class-ID: 0900
Hub-4: 3-0:1 info: hi-speed hub with single TT ports: 12 rev: 2.0
speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
class-ID: 0900
Hub-5: 4-0:1 info: super-speed hub ports: 5 rev: 3.1
speed: 20 Gb/s (2.33 GiB/s) lanes: 2 mode: 3.2 gen-2x2 chip-ID: 1d6b:0003
class-ID: 0900
Hub-6: 5-0:1 info: hi-speed hub with single TT ports: 2 rev: 2.0
speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
class-ID: 0900
Hub-7: 6-0:1 info: super-speed hub ports: 2 rev: 3.1
speed: 20 Gb/s (2.33 GiB/s) lanes: 2 mode: 3.2 gen-2x2 chip-ID: 1d6b:0003
class-ID: 0900
Hub-8: 7-0:1 info: hi-speed hub with single TT ports: 2 rev: 2.0
speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
class-ID: 0900
Hub-9: 8-0:1 info: super-speed hub ports: 2 rev: 3.1
speed: 10 Gb/s (1.16 GiB/s) lanes: 1 mode: 3.2 gen-2x1 chip-ID: 1d6b:0003
class-ID: 0900
Hub-10: 9-0:1 info: hi-speed hub with single TT ports: 2 rev: 2.0
speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
class-ID: 0900
Hub-11: 9-2:2 info: Logitech G11/G15 Keyboard / USB Hub ports: 4 rev: 1.1
speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 power: 100mA
chip-ID: 046d:c223 class-ID: 0900
Device-1: 9-2.1:3 info: Logitech G11/G15 Keyboard / type: keyboard,HID
driver: hid-generic,usbhid interfaces: 2 rev: 2.0
speed: 1.5 Mb/s (183 KiB/s) lanes: 1 mode: 1.0 power: 100mA
chip-ID: 046d:c221 class-ID: 0300
Device-2: 9-2.4:4 info: Logitech G15 Keyboard / LCD type: HID
driver: lg-g15,usbhid interfaces: 1 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s)
lanes: 1 mode: 1.1 power: 100mA chip-ID: 046d:c222 class-ID: 0300
Hub-12: 10-0:1 info: super-speed hub ports: 2 rev: 3.1
speed: 10 Gb/s (1.16 GiB/s) lanes: 1 mode: 3.2 gen-2x1 chip-ID: 1d6b:0003
class-ID: 0900
Hub-13: 11-0:1 info: hi-speed hub with single TT ports: 1 rev: 2.0
speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
class-ID: 0900
Sensors:
System Temperatures: cpu: 45.0 C mobo: 36.8 C gpu: amdgpu temp: 38.0 C
Fan Speeds (rpm): N/A
Repos:
Packages: 1862 pm: pacman pkgs: 1825 libs: 529 tools: pamac pm: flatpak
pkgs: 37
Active pacman repo servers in: /etc/pacman.d/mirrorlist
1: https://forksystems.mm.fcix.net/manjaro/stable/$repo/$arch
2: https://volico.mm.fcix.net/manjaro/stable/$repo/$arch
3: https://mirrors.gigenet.com/manjaro/stable/$repo/$arch
4: https://codingflyboy.mm.fcix.net/manjaro/stable/$repo/$arch
5: https://mirror.raiolanetworks.com/manjaro/stable/$repo/$arch
6: https://mirror.init7.net/manjaro/stable/$repo/$arch
7: https://mirror.phoepsilonix.love/manjaro/stable/$repo/$arch
8: https://ftp.gwdg.de/pub/linux/manjaro/stable/$repo/$arch
Processes:
CPU top: 5 of 662
1: cpu: 47.6% command: Z:\home\alex\Documents\Vita pid: 14606
mem: 418.6 MiB (1.3%)
2: cpu: 17.3% command: chromium pid: 15589 mem: 664.4 MiB (2.1%)
3: cpu: 7.4% command: Proton pid: 14533 mem: 17.8 MiB (0.0%)
4: cpu: 4.9% command: steam pid: 4406 mem: 501.3 MiB (1.6%)
5: cpu: 4.5% command: konsole pid: 17779 mem: 233.6 MiB (0.7%)
Memory top: 5 of 662
1: mem: 770.2 MiB (2.4%) command: plasmashell pid: 1429 cpu: 0.6%
2: mem: 689.0 MiB (2.2%) command: kwin_wayland pid: 1281 cpu: 3.5%
3: mem: 681.7 MiB (2.1%) command: steamwebhelper pid: 4735 cpu: 2.7%
4: mem: 664.4 MiB (2.1%) command: chromium pid: 15589 cpu: 17.3%
5: mem: 601.7 MiB (1.9%) command: chromium pid: 2034 cpu: 0.8%
Info:
Processes: 662 Power: uptime: 2h 8m states: freeze,mem,disk suspend: deep
avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 12.11 GiB services: org_kde_powerdevil,
power-profiles-daemon, upowerd Init: systemd v: 261 default: graphical
tool: systemctl
Compilers: clang: 22.1.8 gcc: 16.1.1 alt: 14/15 Shell: Zsh v: 5.9.2
running-in: konsole inxi: 3.3.41
Thank you
Mod edit:- Please avoid consecutive posts. If there has not been a reply since your last post edit that post, instead, to include additional content. Remedied, no charge.
I want to point you to a couple of disks which you need to run maintenance on.
The btrfs file system is not a set and forget type - and especially if you keep filling data onto them, the file system may shut down - regular maintenance is a must do when using btrfs.
Their used: is close to or beyond what the file system is capable of handling without issues.
used: 813.21 GiB (87.3%)used: 755.06 GiB (81.1%)used: 1.53 TiB (84.2%) ID-4: /mnt/Blue raw-size: 931.13 GiB size: 931.13 GiB (100.00%)
used: 813.21 GiB (87.3%) fs: btrfs dev: /dev/sde3 maj-min: 8:67 label: Blue
uuid: c5946428-c1eb-4fb9-b62b-f5a7960830f8
ID-5: /mnt/Cargobay raw-size: 931.51 GiB size: 931.51 GiB (100.00%)
used: 755.06 GiB (81.1%) fs: btrfs dev: /dev/sdd1 maj-min: 8:49
label: Cargobay uuid: 61754390-15dc-4cf6-a084-6a57144d434e
ID-6: /mnt/Cyan raw-size: 1.82 TiB size: 1.82 TiB (100.00%)
used: 1.53 TiB (84.2%) fs: btrfs dev: /dev/sdc2 maj-min: 8:34 label: Cyan
uuid: d3dbcb88-0b8b-424d-bbb0-733bda861b08
I cannot tell you what to do - I have no experience with btrfs but I have seen enough topics relating to btrfsfile systems running full to know that you need to do something.
You have at least one ntfs formatted disk in the unmounted listing, which may or may not mount depending on the active driver.
ID-6: /dev/sdb2 maj-min: 8:18 size: 3.64 TiB fs: ntfs label: Heavy1
uuid: 0C28C45F28C44A02
That one was only a temp mount to move stuff around NTFS drives arent meant to auto mount
I’ve moved forward with btrfsmaintenance and Btrfs Assistant (just because i’m lazy and like Gui’s) so i’ll see if that makes any difference
After balancing and scrubbing these drives I found boot times the be a bit snappier but that’s the only difference I found. The drives still will not auto-mount
Mod edit: Consecutive posts merged.
If there are no intervening replies, please edit your previous post instead to add further information. Cheers!
If there were a generic issue mounting partitions, topics on the matter would spread like wild-fire.
As there is no evidence of such generic issue, one is left to think it is an issue local to your system and the configuration of it.
We know of two situations where a mount might fail, a dirty ntfs or a dirty btrfs file system, and you have dismissed both.
I recognise that you have the issue; but it is impossible to guess where your issue is coming from or what causes it.
You say an update to Gnome Disk causes it - that is impossible, because Gnome Disk is only modifying the fstab according to the user’s instructions.
A thought:
If the configured folder does not exist when the system tries to mount the device, and the mount options includes nofail the system will continue without issues.
This may happen if the configured mount point is pointing to /run/user/$USER/<something>.
In such case it is recommended to reconfigured the mounts to point to an existing folder, that is not recreated on every run.
And if this is a volume containing data belonging to only one user — i.e. your machine is not set up as a multi-user system — then make sure the mountpoint is a directory in your $HOME, and that it is owned by and writable to you.
I never said gnome disks updating caused the issue? Maybe I wasn’t very clear, as system update caused the problem I should’ve clarified i’m aware all gnome disks does is write to fstab and that this is a personal issue. As mentioned no NTFS drive is mounted or ever meant to be mounted beyond a very brief period. Would posting my Fstab be of any use?
This was a new drive put in today to test if the drives themselves were at fault this also didnt auto mount
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
UUID=6FDA-2AF8 /boot/efi vfat umask=0077 0 2
UUID=c53cde03-926a-4cc8-82e4-019749e954c1 / btrfs subvol=/@,compress=zstd:1 0 0
UUID=c53cde03-926a-4cc8-82e4-019749e954c1 /home btrfs subvol=/@home,compress=zstd:1 0 0
UUID=c53cde03-926a-4cc8-82e4-019749e954c1 /var/cache btrfs subvol=/@cache,compress=zstd:1 0 0
UUID=c53cde03-926a-4cc8-82e4-019749e954c1 /var/log btrfs subvol=/@log,compress=zstd:1 0 0
tmpfs /tmp tmpfs noatime,mode=1777 0 0
/dev/disk/by-uuid/11124601-9c64-41ac-bc0e-f0654e955121 /mnt/11124601-9c64-41ac-bc0e-f0654e955121 auto nosuid,nodev,nofail,x-gvfs-show 0 0
/dev/sdh2 /mnt ntfs nofail 0 0
/dev/disk/by-uuid/c9e6a273-5643-4aea-b01b-6c8b9575ebb7 /mnt/Winspeed btrfs nosuid,nodev,nofail,x-gvfs-show 0 0
/dev/disk/by-uuid/98d484cd-3601-4e29-b707-88fb413029d7 /mnt/HDD btrfs nosuid,nodev,nofail,x-gvfs-show 0 0
/dev/disk/by-uuid/d3dbcb88-0b8b-424d-bbb0-733bda861b08 /mnt/Cyan btrfs nosuid,nodev,nofail,x-gvfs-show 0 0
/dev/disk/by-uuid/61754390-15dc-4cf6-a084-6a57144d434e /mnt/Cargobay btrfs nosuid,nodev,nofail,x-gvfs-show 0 0
/dev/disk/by-uuid/c5946428-c1eb-4fb9-b62b-f5a7960830f8 /mnt/Blue btrfs nosuid,nodev,nofail,x-gvfs-show 0 0
/dev/disk/by-uuid/5711a371-b756-4659-aad2-c7851a800f0a /mnt/SSD btrfs nosuid,nodev,nofail,x-gvfs-show 0 0
LABEL=Heavy2 /mnt/Heavy2 auto nosuid,nodev,nofail,x-gvfs-show 0 0
I think this fstab has more than one problems. For starter, are you sure all the /mnt subpaths actually exist? Then i see a type “auto”. But mainly, for all the btrfs disks, there is no subvolume specified (see the system disk entries above).
If by the subpaths you mean the folders named “blue, winspeed, cyan, hdd etc etc” yes they do indeed exist. the drives all mount without error, “sudo mount -a” doesn’t give me any problems outside of sdh2, and I have no clue what sdh2 was.
You are mounting it to /mnt try creating a mount point for it /mnt/sdh2, then try mounting it.
Well you did set the title to
Having problems with Gnome Disks no longer auto mounting after updating?
And your topic states
Both places state that Gnome Disk is to blame.
I am merely pointing out that Gnome Disk is not auto mounting anything and the point of failure must lie somewhere else.
I see a that all the extra devices has the nofail option.
Therefore the device will not be mounted if it is not present when fstab is parsed by systemd.
I suggest you re-evaluate how you mount devices and make sure they are accessible when accessed.
The following guides was migrated from the previous forum in August 2020, but they are equally valid today.
[root tip] [How To] Use systemd to mount ANY device
[root tip] [How To] systemd mount unit samples
Sampling the required units for your last addition
Example of mount unit if devices is NOT removable
File /etc/systemd/system/Heavy2.mount
[Unit]
Description=Mount Heavy2
[Mount]
What=/dev/disk/by-partlabel/Heavy2
Where=/mnt/Heavy2
Type=auto
# the following lines should be omitted when using automount unit
# omitting them will prevent direct activation by `systemctl enable` command
[Install]
WantedBy=multi-user.target
Example of automount unit if device is removable - can be omitted if it permanently attached to your system.
File `/etc/systemd/system/Heavy2.automount
[Unit]
Description=Automount Heavy2
ConditionPathExists=/mnt/Heavy2
[Automount]
Where=/mnt/Heavy2
TimeoutIdleSec=3600 # if idle for more than an hour unmount it
[Install]
WantedBy=multi-user.target
Depending on whether the device is removable or not you will start and enable ONLY one of the units. NEVER enable both - only one or the other.
If removable - enable ONLY the automount unit - which will then trigger the mount unit when you access the mountpoint - e.g. using your file manager.
systemctl enable --now Heavy2.automount
Otherwise you can enable and start the mount unit
systemctl enable --now Heavy2.mount
Neither do we. However, extrapolating from the information given in that entry, it was an NTFS formatted volume, on the second partition of a disk. It wasn’t an automated entry, which means to say that you created the reference.
Beyond that, if you have no clue, then we certainly don’t either.
I’d suggest commenting that entry, as it seems obviously invalid:
This is important. Each of those entries mounts the default btrfs subvolume — by default, this will be the filesystem root — at the given mountpoint.
If they are all distinct btrfs volumes — and the differing UUIDs do suggest so — then it’s fine, but then why use btrfs in the first place?