Arch Linux

MinePro120

Member

Registered: 2021-01-26

Posts: 12

[Solved] USB Mass Storage devices not listed in /dev

Hello. I have an issue with USB mass storage devices not listed in /dev (so not appearing with lsblk or fdisk -l), even though they seem to be detected by lsusb (not by lsscsi -d though).
I've tried multiple USB sticks (USB 2.0 and 3.0) on both 2.0 and 3.0 ports. Mice and keyboards work fine. Sometimes everything works fine after a reboot, it's an issue that occurs often though. Everything's up to date. Here's some info:

uname -r
5.10.9-arch1-1

fdisk -l
Disk /dev/sda: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: ST1000LM024 HN-M
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x4290fb4c

Device     Boot      Start        End    Sectors   Size Id Type
/dev/sda1  *          2048 1630560255 1630558208 777.5G  7 HPFS/NTFS/exFAT
/dev/sda2       1743806464 1953525167  209718704   100G 83 Linux
/dev/sda3       1630560256 1735417855  104857600    50G 83 Linux
/dev/sda4       1735417856 1743806463    8388608     4G 82 Linux swap / Solaris

Partition table entries are not in disk order.

lsblk
NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda      8:0    0 931.5G  0 disk
├─sda1   8:1    0 777.5G  0 part
├─sda2   8:2    0   100G  0 part /run/timeshift/backup
├─sda3   8:3    0    50G  0 part
└─sda4   8:4    0     4G  0 part [SWAP]
sr0     11:0    1  1024M  0 rom

lsusb
Bus 001 Device 009: ID 046d:c084 Logitech, Inc. G203 Gaming Mouse
Bus 001 Device 004: ID 04ca:0022 Lite-On Technology Corp. USB Keyboard
Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller
Bus 001 Device 002: ID 0438:7900 Advanced Micro Devices, Inc. Root Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 012: ID 0930:1408 Toshiba Corp. USB FLASH DRIVE    // <- listed
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 003: ID 0c45:6712 Microdia Integrated Webcam HD
Bus 002 Device 004: ID 0cf3:e005 Qualcomm Atheros Communications
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

lsscsi -d
[0:0:0:0]    disk    ATA      ST1000LM024 HN-M 0003  /dev/sda [8:0]
[1:0:0:0]    cd/dvd  TSSTcorp DVD+-RW SU-208GB D100  /dev/sr0 [11:0]

dmesg
[ 7958.343851] usb 3-3: new SuperSpeed Gen 1 USB device number 13 using xhci_hcd
[ 7958.372795] usb 3-3: New USB device found, idVendor=0930, idProduct=1408, bcdDevice= 0.01
[ 7958.372801] usb 3-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 7958.372804] usb 3-3: Product: USB FLASH DRIVE
[ 7958.372805] usb 3-3: Manufacturer: TOSHIBA
[ 7958.372807] usb 3-3: SerialNumber: 7C8BCA144B60C1B100023131

Thanks in advance fellow Arch users.

Last edited by MinePro120 (2021-01-26 15:22:54)

Scimmia

Fellow

Registered: 2012-09-01

Posts: 13,727

Re: [Solved] USB Mass Storage devices not listed in /dev

pacman -Q linux

MinePro120

Member

Registered: 2021-01-26

Posts: 12

Re: [Solved] USB Mass Storage devices not listed in /dev

pacman -Q linux

pacman -Q linux
linux 5.10.10.arch1-1

I've updated and haven't rebooted since to be honest. But nevertheless, the issue seems to resolve itself after a reboot, only to reappear after another start-up.

Scimmia

Fellow

Registered: 2012-09-01

Posts: 13,727

Re: [Solved] USB Mass Storage devices not listed in /dev

Sounds totally normal, then.

progandy

Member

Registered: 2012-05-17

Posts: 5,317

Re: [Solved] USB Mass Storage devices not listed in /dev

If the kernel has been updated without a reboot, then it will be impossible to load new kernel modules necessary to register the flash drives.
You can mitigate the issue by always loading the modules during boot with /etc/modules-load.d: uas usb-storage vfat exfat

---

| alias CUTF='LANG=en_XX.UTF-8@POSIX ' | alias ENGLISH='LANG=C.UTF-8 ' |

MinePro120

Member

Registered: 2021-01-26

Posts: 12

Re: [Solved] USB Mass Storage devices not listed in /dev

So it's possible I was having the issue every time the kernel was updated but I didn't reboot (since kernel updates are quite frequent). Indeed, I can't reproduce the issue, for now. I'll update if anything persists. Thanks for the help!