Problems with mounting usb drives

[knivesron]

so im using dragonized gaming garuda.

if i have 2 usb drive’s pluged in on start up, neither will mount and i have to restart, take one out and it will mount then once its started plug the other one in to mount it.

ive looked around for a fix but cant figure it out.

this is prolly the biggest issue i have with linux right now and im sure theres an easy fix but i just dont know enough to fix it.

thanks for any help

System:
Kernel: 6.16.4-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 15.2.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=707f693e-9dc7-415f-9242-ba69e2d02599 rw rootflags=subvol=@
quiet loglevel=3
Desktop: KDE Plasma v: 6.4.4 tk: Qt v: N/A info: frameworks v: 6.17.0
wm: kwin_wayland vt: 1 dm: SDDM Distro: Garuda base: Arch Linux
Machine:
Type: Desktop Mobo: Gigabyte model: B85M-Gaming 3 v: x.x
serial: <superuser required> uuid: <superuser required>
UEFI: American Megatrends v: F1 date: 09/05/2014
CPU:
Info: model: Intel Core i7-4790 bits: 64 type: MT MCP arch: Haswell
gen: core 4 level: v3 note: check built: 2013-15 process: Intel 22nm
family: 6 model-id: 0x3C (60) stepping: 3 microcode: 0x28
Topology: cpus: 1x dies: 1 clusters: 4 cores: 4 threads: 8 tpc: 2
smt: enabled cache: L1: 256 KiB desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB
desc: 4x256 KiB L3: 8 MiB desc: 1x8 MiB
Speed (MHz): avg: 3698 min/max: 800/4000 scaling: driver: intel_cpufreq
governor: performance cores: 1: 3698 2: 3698 3: 3698 4: 3698 5: 3698 6: 3698
7: 3698 8: 3698 bogomips: 57463
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities: <filter>
Graphics:
Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics
vendor: Gigabyte driver: i915 v: kernel arch: Gen-7.5 process: Intel 22nm
built: 2013 ports: active: none empty: HDMI-A-4,VGA-1 bus-ID: 00:02.0
chip-ID: 8086:0412 class-ID: 0300
Device-2: NVIDIA GP104 [GeForce GTX 1080] vendor: Gigabyte driver: nvidia
v: 580.76.05 alternate: nouveau,nvidia_drm non-free: 550-570.xx+
status: current (as of 2025-04; EOL~2026-12-xx) arch: Pascal code: GP10x
process: TSMC 16nm built: 2016-2021 pcie: gen: 3 speed: 8 GT/s lanes: 8
link-max: lanes: 16 ports: active: none off: DP-1 empty: DP-2, DP-3,
HDMI-A-1, HDMI-A-2, HDMI-A-3 bus-ID: 01:00.0 chip-ID: 10de:1b80
class-ID: 0300
Display: wayland server: X.org v: 1.21.1.18 with: Xwayland v: 24.1.8
compositor: kwin_wayland driver: X: loaded: modesetting,nvidia
unloaded: nouveau alternate: fbdev,intel,nv,vesa dri: crocus
gpu: nvidia,nvidia-nvswitch display-ID: 0
Monitor-1: DP-1 model: LG (GoldStar) TV SSCR2 serial: <filter> built: 2022
res: mode: 3840x2160 hz: 60 scale: 100% (1) dpi: 61 gamma: 1.2
size: 1600x900mm (62.99x35.43") diag: 1836mm (72.3") ratio: 16:9 modes:
max: 3840x2160 min: 640x480
API: EGL v: 1.5 hw: drv: intel crocus drv: nvidia platforms: device: 0
drv: nvidia device: 1 drv: crocus device: 3 drv: swrast gbm: drv: crocus
surfaceless: drv: nvidia wayland: drv: nvidia x11: drv: nvidia
inactive: device-2
API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 580.76.05
glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce GTX 1080/PCIe/SSE2
memory: 7.81 GiB display-ID: :1.0
API: Vulkan v: 1.4.321 layers: 15 device: 0 type: discrete-gpu
name: NVIDIA GeForce GTX 1080 driver: nvidia v: 580.76.05
device-ID: 10de:1b80 surfaces: N/A device: 1 type: integrated-gpu
name: Intel HD Graphics 4600 (HSW GT2) driver: mesa intel
v: 25.2.1-arch1.5 device-ID: 8086:0412 surfaces: N/A device: 2 type: cpu
name: llvmpipe (LLVM 20.1.8 256 bits) driver: mesa llvmpipe
v: 25.2.1-arch1.5 (LLVM 20.1.8) device-ID: 10005:0000 surfaces: N/A
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
de: kscreen-console,kscreen-doctor gpu: corectrl, nvidia-settings,
nvidia-smi wl: wayland-info x11: xdpyinfo, xprop, xrandr
Audio:
Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio
driver: snd_hda_intel v: kernel bus-ID: 00:03.0 chip-ID: 8086:0c0c
class-ID: 0403
Device-2: Intel 8 Series/C220 Series High Definition Audio
vendor: Gigabyte driver: snd_hda_intel v: kernel bus-ID: 00:1b.0
chip-ID: 8086:8c20 class-ID: 0403
Device-3: NVIDIA GP104 High Definition Audio vendor: Gigabyte
driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 8
link-max: lanes: 16 bus-ID: 01:00.1 chip-ID: 10de:10f0 class-ID: 0403
API: ALSA v: k6.16.4-zen1-1-zen status: kernel-api with: aoss
type: oss-emulator tools: N/A
Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
Server-2: PipeWire v: 1.4.7 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: Intel Ethernet I217-V vendor: Gigabyte driver: e1000e v: kernel
port: f080 bus-ID: 00:19.0 chip-ID: 8086:153b class-ID: 0200
IF: eno1 state: up speed: 1000 Mbps duplex: full mac: <filter>
Info: services: NetworkManager, smbd, systemd-timesyncd
Bluetooth:
Device-1: TP-Link TP- driver: btusb v: 0.8 type: USB rev: 1.1 speed: 12 Mb/s
lanes: 1 mode: 1.1 bus-ID: 1-9:4 chip-ID: 2357:0604 class-ID: e001
serial: <filter>
Report: btmgmt ID: hci0 rfk-id: 0 state: up address: N/A
Drives:
Local Storage: total: 1.82 TiB used: 1.74 TiB (95.5%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 860 QVO 1TB
size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 1B6Q scheme: GPT
ID-2: /dev/sdb maj-min: 8:16 model: # + - size: 931.51 GiB block-size:
physical: 512 B logical: 512 B type: USB rev: 2.0 spd: 480 Mb/s lanes: 1
mode: 2.0 tech: HDD rpm: 59353 serial: <filter> scheme: MBR
Partition:
ID-1: / raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
used: 860.16 GiB (92.4%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 616 KiB (0.2%) fs: vfat dev: /dev/sda1 maj-min: 8:1
ID-3: /home raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
used: 860.16 GiB (92.4%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
ID-4: /var/log raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
used: 860.16 GiB (92.4%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
ID-5: /var/tmp raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
used: 860.16 GiB (92.4%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 15.51 GiB used: 11.31 GiB (72.9%)
priority: 100 comp: zstd avail: lzo-rle,lzo,lz4,lz4hc,deflate,842
dev: /dev/zram0
Sensors:
System Temperatures: cpu: 91.0 C mobo: N/A
Fan Speeds (rpm): N/A
Info:
Memory: total: 16 GiB available: 15.51 GiB used: 13.79 GiB (88.9%)
Processes: 358 Power: uptime: 7h 57m states: freeze,mem,disk suspend: deep
avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 6.11 GiB services: org_kde_powerdevil,
power-profiles-daemon, upowerd Init: systemd v: 257 default: graphical
tool: systemctl
Packages: pm: pacman pkgs: 2115 libs: 601 tools: octopi,pamac,paru
Compilers: clang: 20.1.8 gcc: 15.2.1 Shell: Bash v: 5.3.3 default: fish
v: 4.0.2 running-in: konsole inxi: 3.3.38
Garuda (2.8.2-2):
System install date:     2024-07-30
Last full system update: 2025-09-03
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut nvidia-dkms
Windows dual boot:       No/Undetected
Failed units:
--- System Health Check Report ---
22/23 checks run in 1.93 seconds ⌛
Powered by garuda-health 🦅

--- LOW ---
- Old Btrfs snapshots found that can be deleted (fix available)

Run garuda-health --fix to apply fixes.

[Apocalypticus]

Hi and welcome

You may have forgotten or overlooked to post the terminal output from garuda-inxi, as requested in the template for your post.
This output is essential for receiving assistance on this forum. Otherwise, your post will be moved to https://forum.garudalinux.org/c/4xx/precondition-failed/33.

You can now easily edit your initial post and subsequently post the output from Garuda Inxi.
Format it as a code block by clicking the preformatted text button (</>), or put three tildes (~) above and below the output text.

[gampel]

@knivesron

UEFI: American Megatrends v: F1 date: 09/05/2014

Not your issue but F2 is out (2015)
Pls Bios update (think on the right settings after)
https://www.gigabyte.com/Motherboard/GA-B85M-Gaming-3-rev-10/support#dl

@knivesron

theres an easy fix

Sorry, no

@knivesron

if i have 2 usb drive’s pluged in on start up, neither will mount and i have to restart

What you mean exactly with this ? On boot /startup metal ? After grub or login screen ?
Using on boot isn’t possible only if it’s a bootable drive. Mounting after grub/ plasma login is possible over fstab or auto mount options plasma, udev rule/s or autofs.
Find the bios both drives if connected ? (first start not reboot)
Which settings exist for “auto” mount in plasma ?

Perhaps faulty metal (cable, usb port, chipset, drive, power supply) ; connect, post: lsblk -f (both usb drives); i hope no entry in /etc/fstab for usb and if with the right options.
Think on it, some metal from the system is current more then 10 years old.

[Apocalypticus]

KDE Plasma Automount

[knivesron]

i can auto mount drives.

either drive will auto mount seperatly after ive booted to desktop.

its only when i try to turn my pc on with 2 or more plugged in.

i read somewhere there might be an issue with both mounting to quickly and breaking each other. some delay between mounts was a fix i read but i couldent figure out how to do it.

its frustrating cause if i leave me usb plugged in when i shut down then both dont work untill i do another restart

[knivesron]

pretty sure its not a “my hardware” problem. its an issue with the way the mounting works. either this is a garuda or linux issue but i dont know enough about linux to troubleshoot.

and thanks for the help every one i appriciate it

[knivesron]

turn your pc off.
plug in 2 or more usb drives. flesh drives, external usb hdd’s etc
then turn pc on
when it gets into desktop both drives are unmountable.

reset pc
take all drives out but 1
when it gets to desktop that one drive will be mounted
then you plug the other one in and it will mount.

seems to be a conflict during mounting on start up.
its like the drives try mount at the same time and conflict with each other causing neither to work.

you should be able to replicate this

[Locutus]

This seems to be a recent issue for a lot of people. My workaround is to disable the drives from a hub when I can simple cut there connection with a push of a button. I choose restart, once Outside of the OS I disconnect the drives, reconnect them once the system gets to the login screen and once logged in they’re available. Two AM5 machines with different mobos and same issue.

[tbg]

Not a fix, but an adequate workard is to rescan the USB bus. I’ve used this method for many years.

There are lots of ways to do this. A bash script can be executed to easily rescan all USB devices, which then will hopefully result in your device being detected and remounted.

Here’s one method:

Wesley Aptekar-Cassels | How to reset the USB stack on Linux.

Above is not the script I usually use. I have it stored on my computer at home, but I’m currently on my Cel.

The one caveat is to make sure you are not writing data to any USB device when the script is executed.

You can even create a desktop launcher to easily execute the script with a mouse click.

Might not actually correct your problem, but it’s close enough to make it no big deal anymore.

If you have problems, let me know later and I’ll look for the script I usually use. As always, don’t forget to make the script executable.

Good luck, and welcome to Garuda.

[knivesron]

i think im just going to use my workaround which is to unplug one every time i boot.

this has been an issue for me for about 6 months or so, as long as ive been on linux/garuda.

this will be a huge issue for ppl coming from windows as windows handles this really well, with no issues. maby something for the team to work on and get sorted.

thanks every one for your help

[Locutus]

It’s mobo related.

[gampel]

Not only mobo related.
Some PC power supplies lose their ATX specifications due to age, or their tolerance limits are or become too high. (special if you turn on, it need to long time to have the right voltage) Only 0.01 V too low and USB problems begin, and the voltage converters on the motherboard can’t compensate for it or aren’t responsible for these voltages. Even with 80+ platinum certification is this possible. (i had this problem with a power supply and it wasn’t a “no-name” product)
But also important is the bios settings for usb. (ErP S4 - S5)
If activated, yes, less on power consumption, but that need more time then (wake up) even on boot and then you can have this result. (my mind)
For this i like a a journal log that tells me the kernel can not managed this. Reason ErP is deactivated, but only on desktop pc.

garudacomp kernel: usb: port power management may be unreliable