2

I'm trying to use a USB flash drive that was working perfectly until some time ago, after which I have made no changes to the system that can affect this.

When I plug in my USB device and run $ lsblk && lsusb this is the output I received.

NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda      8:0    0 931.5G  0 disk 
├─sda1   8:1    0   512M  0 part /boot/efi
├─sda2   8:2    0    28G  0 part /
├─sda3   8:3    0   7.9G  0 part [SWAP]
└─sda4   8:4    0 895.2G  0 part /home
sr0     11:0    1  1024M  0 rom  
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 8087:07dc Intel Corp. 
Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller
Bus 001 Device 002: ID 1bcf:2b90 Sunplus Innovation Technology Inc. 
Bus 001 Device 005: ID 0781:5581 SanDisk Corp. Ultra
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

I can note the SanDisk Corp. Ultra at Bus 001 Device 005: ID 0781:5581 in the above output.

I do not understand why it was not mounted automatically and why I am unable to mount it. Please help me out with how to mount the device. Thanks in advance :)

Edit: This is happening with all USB devices, I did try connecting an external hard disk. The same thing happened.

Edit: I'm extremely sorry that I did not provide the basic information. I'm Using Debian 10 (Buster) with a the latest kernel i.e. 5.8.0-rc1-00001-gc1966b82e604

When I run sudo journalctl -f

Jun 20 19:24:12 pesu.pes.edu kernel: usb 1-3: new high-speed USB device number 6 using xhci_hcd
Jun 20 19:24:12 pesu.pes.edu kernel: usb 1-3: New USB device found, idVendor=0781, idProduct=5581, bcdDevice= 1.00
Jun 20 19:24:12 pesu.pes.edu kernel: usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jun 20 19:24:12 pesu.pes.edu kernel: usb 1-3: Product: Ultra
Jun 20 19:24:12 pesu.pes.edu kernel: usb 1-3: Manufacturer: SanDisk
Jun 20 19:24:12 pesu.pes.edu kernel: usb 1-3: SerialNumber: 4C530001161117117402
Jun 20 19:24:12 pesu.pes.edu mtp-probe[2747]: checking bus 1, device 6: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-3"
Jun 20 19:24:12 pesu.pes.edu mtp-probe[2747]: bus: 1, device: 6 was not an MTP device
Jun 20 19:24:12 pesu.pes.edu mtp-probe[2750]: checking bus 1, device 6: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-3"
Jun 20 19:24:12 pesu.pes.edu mtp-probe[2750]: bus: 1, device: 6 was not an MTP device
Jun 20 19:24:18 pesu.pes.edu kernel: usb 1-3: USB disconnect, device number 6

When I run sudo tail -f /var/log/syslog this is the output i get.

Jun 20 19:24:12 pesu kernel: [ 1110.256157] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jun 20 19:24:12 pesu kernel: [ 1110.256162] usb 1-3: Product: Ultra
Jun 20 19:24:12 pesu kernel: [ 1110.256166] usb 1-3: Manufacturer: SanDisk
Jun 20 19:24:12 pesu kernel: [ 1110.256170] usb 1-3: SerialNumber: 4C530001161117117402
Jun 20 19:24:12 pesu mtp-probe: checking bus 1, device 6: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-3"
Jun 20 19:24:12 pesu mtp-probe: bus: 1, device: 6 was not an MTP device
Jun 20 19:24:12 pesu mtp-probe: checking bus 1, device 6: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-3"
Jun 20 19:24:12 pesu mtp-probe: bus: 1, device: 6 was not an MTP device
Jun 20 19:24:18 pesu kernel: [ 1116.267124] usb 1-3: USB disconnect, device number 6
10
  • What's your OS and version? Can you sudo journalctl -f while you plug things in? Or must you tail -f /var/log/syslog ? Or read the most recently changed log file as shown by ls -lrt /var/log?
    – waltinator
    Commented Jun 20, 2020 at 13:40
  • Hey @waltinator ,Thank you for responding. Extremely sorry for not providing that information earlier. I've made an edit :) Commented Jun 20, 2020 at 13:58
  • Please show the output of lsblk to see whether the USB device got mapped to a block (disk type) device. You can leave out the details about your main hard disk.
    – Ned64
    Commented Jun 20, 2020 at 13:59
  • Hi @Ned64 I've already shown the output of lsblk in the first piece of code, the command was $ lsblk && lsusb Commented Jun 20, 2020 at 14:01
  • Oops, sorry. There is no entry. Then no mount command will help. You would expect usbcore to register a usb-storage device which hasn't happened. Have you made a system update without rebooting? Or, have you blacklisted any usb (kernel) modules? Or, have you changed udev rules by hand? Also: please check systemctl status systemd-udevd.
    – Ned64
    Commented Jun 20, 2020 at 14:08

1 Answer 1

2

Your kernel needs the modules usbcore and usb_storage to recognise USB devices as USB storage devices. This includes USB thumb drives.

According to your output in the comments above, quoting here:

$ sudo modprobe usb_storage
modprobe: FATAL: Module usb_storage not found in directory /lib/modules/5.8.0-rc1-00001-gc1966b82e604

The kernel does not have the usb_storage module/code available.

Solution 1: Compile your kernel with usb_storage included (Y not M).

Solution 2: Fix your issues compiling your kernel modules (need more info to solve that issue, feel free to add kernel module compilation/installation errors by editing your question, or (perhaps better) open a new question since it is a different problem).

9
  • Hi, I'm sorry but this is what my .config file says. Can you please tell me exactly what i need to modify over here? I seem to be messing it up. Thanks# # NOTE: USB_STORAGE depends on SCSI but BLK_DEV_SD may # # # also be needed; see USB_STORAGE Help for more info # CONFIG_USB_STORAGE=m # CONFIG_USB_STORAGE_DEBUG is not set because make seems to have issues when I change that m to a y Commented Jun 20, 2020 at 14:55
  • What happens if you do what it says: Change BLK_DEV_SD and SCSI to Y (not M)?
    – Ned64
    Commented Jun 20, 2020 at 15:07
  • I did not see INSTALL drivers/usb/usb_storage.o while executing su -c "make modules_install install" hence, same problem again. I did change the following lines /to in the .config file BLK_DEV_SD=y and CONFIG_SCSI=y Commented Jun 20, 2020 at 15:13
  • If you say "Y" not "M" you would not see NAME.o installation because code is not compiled into a module file but included into the kernel itself. The code will still be in the kernel (unless an error occurs) and things should work. I have suggested the "Y not M" approach because you seem to have module installation problems (see your previous comment above). If these are gone "M" should work, too.
    – Ned64
    Commented Jun 20, 2020 at 15:41
  • I changed them to Y as suggested, and rebuilt it. It still doesn't work Commented Jun 20, 2020 at 15:46

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .