I'm having issues mounting drives

[sleepy]

Hi, i'm having issues mounting my drives. I used to be able to just click the drives in dolphin and they would mount. The drives in question is NTFS and microsd cards wont mount either now. The only thing I did that was out of the ordinary before the issue was to format a microsd card in KDE partition manager.

Looking in run/media/user i can see at least my drives, and inspecting them the user is root and group is root now. After woogling around i tried to use: sudo chown user:user /run/media/user (they show up there after clicking in dolphin)
This did not work.

Also tried to add the drive to the bottom of fstab like so:
UUID=6e7eb9987eb95993 / run/media/user/backup ntfs-3g defaults 0 0

This resulting in the process timing out when rebooting.

Here is my the results of fdisk -l input:

Disk /dev/nvme0n1: 931,51 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: Samsung SSD 970 EVO Plus 1TB
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 9F041D68-5486-5542-930F-7F0371A72B06

Device          Start        End    Sectors   Size Type
/dev/nvme0n1p1   4096     618495     614400   300M EFI System
/dev/nvme0n1p2 618496 1953520064 1952901569 931,2G Linux filesystem


Disk /dev/sdb: 1,82 TiB, 2000398934016 bytes, 3907029168 sectors
Disk model: WDC WD20EARS-00J
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 5D67E289-D7F5-423B-8E79-6B29742212A6

Device     Start        End    Sectors  Size Type
/dev/sdb1   2048 3907028991 3907026944  1,8T Microsoft basic data


Disk /dev/sda: 223,57 GiB, 240057409536 bytes, 468862128 sectors
Disk model: KINGSTON SA400M8
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 136D92D5-6D4D-1140-8A9C-3ABB3591477A

Device     Start       End   Sectors   Size Type
/dev/sda1   2048     34815     32768    16M Microsoft reserved
/dev/sda2  34816 468860927 468826112 223,6G Microsoft basic data


Disk /dev/zram0: 31,28 GiB, 33584840704 bytes, 8199424 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/sdc: 119,08 GiB, 127865454592 bytes, 249737216 sectors
Disk model: Storage Device
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: FDF0E85A-7A74-4327-A515-A24E04FDD61C

Device     Start       End   Sectors   Size Type
/dev/sdc1   2048 249735167 249733120 119,1G Linux filesystem

garuda-inxi:

System:
Kernel: 6.3.3-AMD-znver2 arch: x86_64 bits: 64 compiler: gcc v: 13.1.1
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-amd-znver2
root=UUID=2f466eca-95cf-416b-bade-e69db71ffa5e rw rootflags=subvol=@
quiet quiet rd.udev.log_priority=3 vt.global_cursor_default=0 loglevel=3
splash ibt=off
Desktop: KDE Plasma v: 5.27.5 tk: Qt v: 5.15.9 wm: kwin_x11 vt: 1 dm: SDDM
Distro: Garuda Linux base: Arch Linux
Machine:
Type: Desktop Mobo: Micro-Star model: MPG X570 GAMING EDGE WIFI (MS-7C37)
v: 1.0 serial: <superuser required> UEFI: American Megatrends LLC. v: 1.K0
date: 02/28/2023
CPU:
Info: model: AMD Ryzen 9 3900X bits: 64 type: MT MCP arch: Zen 2 gen: 3
level: v3 note: check built: 2020-22 process: TSMC n7 (7nm)
family: 0x17 (23) model-id: 0x71 (113) stepping: 0 microcode: 0x8701030
Topology: cpus: 1x cores: 12 tpc: 2 threads: 24 smt: enabled cache:
L1: 768 KiB desc: d-12x32 KiB; i-12x32 KiB L2: 6 MiB desc: 12x512 KiB
L3: 64 MiB desc: 4x16 MiB
Speed (MHz): avg: 3715 high: 3800 min/max: 2200/4672 boost: enabled
scaling: driver: acpi-cpufreq governor: performance cores: 1: 3800 2: 3800
3: 3800 4: 3800 5: 3800 6: 3601 7: 3597 8: 3600 9: 3592 10: 3800 11: 3591
12: 3800 13: 3800 14: 3800 15: 3800 16: 3600 17: 3800 18: 3800 19: 3600
20: 3800 21: 3593 22: 3604 23: 3800 24: 3590 bogomips: 182472
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities: <filter>
Graphics:
Device-1: AMD Vega 10 XL/XT [Radeon RX 56/64] driver: amdgpu v: kernel
arch: GCN-5 code: Vega process: GF 14nm built: 2017-20 pcie: gen: 3
speed: 8 GT/s lanes: 16 ports: active: DP-3 empty: DP-1,DP-2,HDMI-A-1
bus-ID: 2f:00.0 chip-ID: 1002:687f class-ID: 0300
Display: x11 server: X.Org v: 21.1.8 with: Xwayland v: 23.1.1
compositor: kwin_x11 driver: X: loaded: amdgpu unloaded: modesetting
alternate: fbdev,vesa dri: radeonsi gpu: amdgpu display-ID: :0 screens: 1
Screen-1: 0 s-res: 2560x1440 s-dpi: 96 s-size: 677x381mm (26.65x15.00")
s-diag: 777mm (30.58")
Monitor-1: DP-3 mapped: DisplayPort-2 model: Samsung C32HG7x
serial: <filter> built: 2034 res: 2560x1440 hz: 144 dpi: 93 gamma: 1.2
size: 697x392mm (27.44x15.43") diag: 800mm (31.5") ratio: 16:9 modes:
max: 2560x1440 min: 720x400
API: OpenGL v: 4.6 Mesa 23.0.3 renderer: AMD Radeon RX Vega (vega10 LLVM
15.0.7 DRM 3.52 6.3.3-AMD-znver2) direct-render: Yes
Audio:
Device-1: AMD Vega 10 HDMI Audio [Radeon 56/64] driver: snd_hda_intel
v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 2f:00.1
chip-ID: 1002:aaf8 class-ID: 0403
Device-2: AMD Starship/Matisse HD Audio vendor: Micro-Star MSI
driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
bus-ID: 31:00.4 chip-ID: 1022:1487 class-ID: 0403
Device-3: SteelSeries ApS GameDAC driver: hid-generic,snd-usb-audio,usbhid
type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 5-4.2:4
chip-ID: 1038:1282 class-ID: 0300 serial: <filter>
API: ALSA v: k6.3.3-AMD-znver2 status: kernel-api with: aoss
type: oss-emulator tools: N/A
Server-1: PipeWire v: 0.3.71 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: Micro-Star MSI X570-A PRO driver: r8169 v: kernel pcie: gen: 1
speed: 2.5 GT/s lanes: 1 port: d000 bus-ID: 27:00.0 chip-ID: 10ec:8168
class-ID: 0200
IF: enp39s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Device-2: Intel Dual Band Wireless-AC 3168NGW [Stone Peak] driver: iwlwifi
v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 bus-ID: 29:00.0
chip-ID: 8086:24fb class-ID: 0280
IF: wlp41s0 state: down mac: <filter>
IF-ID-1: wgpia0 state: unknown speed: N/A duplex: N/A mac: N/A
Bluetooth:
Device-1: Intel Wireless-AC 3168 Bluetooth driver: btusb v: 0.8 type: USB
rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-4:3 chip-ID: 8087:0aa7
class-ID: e001
Report: bt-adapter ID: hci0 rfk-id: 0 state: down
bt-service: enabled,running rfk-block: hardware: no software: yes
address: <filter>
Drives:
Local Storage: total: 3.06 TiB used: 652.03 GiB (20.8%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung
model: SSD 970 EVO Plus 1TB size: 931.51 GiB block-size: physical: 512 B
logical: 512 B speed: 31.6 Gb/s lanes: 4 tech: SSD serial: <filter>
fw-rev: 2B2QEXM7 temp: 41.9 C scheme: GPT
ID-2: /dev/sda maj-min: 8:0 vendor: Kingston model: SA400M8240G
size: 223.57 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 0004 scheme: GPT
ID-3: /dev/sdb maj-min: 8:16 vendor: Western Digital
model: WD20EARS-00J2GB0 size: 1.82 TiB block-size: physical: 512 B
logical: 512 B speed: 3.0 Gb/s tech: N/A serial: <filter> fw-rev: 0A80
scheme: GPT
ID-4: /dev/sdc maj-min: 8:32 model: Mass Storage Device size: 119.08 GiB
block-size: physical: 512 B logical: 512 B type: USB rev: 2.0 spd: 480 Mb/s
lanes: 1 mode: 2.0 tech: N/A serial: <filter> fw-rev: 1.00 scheme: GPT
SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
ID-1: / raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
used: 652 GiB (70.0%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 29.6 MiB (9.9%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
ID-3: /home raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
used: 652 GiB (70.0%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-4: /var/log raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
used: 652 GiB (70.0%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-5: /var/tmp raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
used: 652 GiB (70.0%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: zram size: 31.28 GiB used: 0 KiB (0.0%) priority: 100
dev: /dev/zram0
Sensors:
System Temperatures: cpu: 37.1 C mobo: N/A gpu: amdgpu temp: 27.0 C
mem: 26.0 C
Fan Speeds (RPM): N/A gpu: amdgpu fan: 0
Info:
Processes: 428 Uptime: 17m wakeups: 0 Memory: available: 31.28 GiB
used: 3.17 GiB (10.1%) Init: systemd v: 253 default: graphical
tool: systemctl Compilers: gcc: 13.1.1 clang: 15.0.7 Packages: pm: pacman
pkgs: 1917 libs: 557 tools: pamac,paru Shell: fish v: 3.6.1 default: Bash
v: 5.1.16 running-in: konsole inxi: 3.3.27
Garuda (2.6.16-1):
System install date:     2023-03-22
Last full system update: 2023-05-24
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut
Windows dual boot:       Probably (Run as root to verify)
Failed units:            cpupower-gui.service

I've got everything on this install the way I like it so I'd hate to resort to formatting and reinstalling garuda.

[anon30283766]

Whenever I have local partition permission issues I open the Disks app (gnome-disk-utility), select the partition, click the pop-up menu to the right of the + button, then "Take Ownership...". Maybe this will work for you as well.

[sleepy]

Found the option but it was grayed out for me and I can't click it.

Looking around gnome-utility i found Edit Mount Options under + and turning off User Session Defaults and checking Mount at system startup and show in user interface, was able to mount the drive. Thanks for the suggestion, now I can get access to my files.

Still not can't mount or take ownership microsd card.

gnome utility gives me this error when trying to take ownership (i get this option on the sdcard).

Error taking ownership of filesystem on /dev/sdc1: Cannot mount /dev/sdc1 at /run/udisks2/temp-mount-ZXK041: wrong fs type, bad option, bad superblock on /dev/sdc1, mission codepage or helper program, or other error (udisks-error-quark, 0)

Shouldn't there be a config file I could reset back to default so I could just click the drives in dolphin and they would mount?

Other user reported issue at https://forum.garudalinux.org/t/can-mount-second-harddisk-ntfs/28678

User Renegade suggested package util-linux-2.39-1 was at fault.
I downgraded the packaged using sudo downgrade util-linux and selected package 2.38.1 and rebooted.

This didn't change anything for me.

Still stuck.

[SGS]

@sleepy

wrong fs type, bad option, bad superblock on /dev/sdc1,

Can you check on other PC?
Hardware lock?
Has it ever worked on this computer with Garuda?

@sleepy

UUID=6e7eb9987eb95993 / run/media/user/backup ntfs-3g defaults 0 0

Looks like you mounted to root
I think the order is also important.

<file system>  <mount point>  <type>  <options>  <dump>  <pass>

@sleepy

ID-4: /dev/sdc maj-min: 8:32 model: Mass Storage Device size: 119.08 GiB
block-size: physical: 512 B logical: 512 B type: USB rev: 2.0 spd: 480 Mb/s
lanes: 1 mode: 2.0 tech: N/A serial: <filter> fw-rev: 1.00 scheme: GPT
SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?

: Unknown USB bridge. Flash drive/Unsupported enclosure?

[BluishHumility]

This came up in another thread recently–other people are also having issues mounting NTFS drives with Dolphin after a recent update. @Renegade has identified the package they believe is causing the issue:

Can mount second harddisk ntfs

Had the same thing happen to me, did an upgrade and dolphin can't mount the NTFS drive anymore. After going through the packages that I had to update, I found out that it's the util-linux-2.39-1 package that is the culprit.

Perhaps downgrading the package would be a help until it is fixed.

downgrade util-linux

[Renegade]

This has been fixed [for me] with util-linux 2.39.3 that happened on the 25th. That resolved my issue. Should be safe to upgrade this package and the associated util-linux-lib package to the same version 2.39.3.

edit: in [ ]