Usb drive detected but doesn't show up in /devusb

Hi there. This is making me mad.
I have this usb drive that just stopped working. I am on Manjaro if it can help.

When looking at similar posts I’ve seen people do these commands and those are my results :

sudodmesg | grep usb
[90412.630251] usb 2-1: new SuperSpeed USB device number 2 using xhci_hcd
[90412.648045] usb 2-1: New USB device found, idVendor=18a5, idProduct=0243, bcdDevice=11.00
[90412.648058] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[90412.648065] usb 2-1: Product: STORE N GO
[90412.648070] usb 2-1: Manufacturer: Verbatim
[90412.648075] usb 2-1: SerialNumber: 0112102063201201
[90412.790476] usb-storage 2-1:1.0: USB Mass Storage device detected
[90412.790721] scsi host6: usb-storage 2-1:1.0
[90412.790768] usbcore: registered new interface driver usb-storage
[90412.794830] usbcore: registered new interface driver uas
[90436.107173] usb 2-1: reset SuperSpeed USB device number 2 using xhci_hcd

And

lsusb 
Bus 002 Device 002: ID 18a5:0243 Verbatim, Ltd Flash Drive (Store'n'Go)

I’ve rebooted plenty of times. I don"t think my kernel modules aren’t loaded. I don’t know what’s wrong.
Last time I “could use”, it it showed a 100% filled drive and I couldn’t move my files (it crashed and disconnected when I tried). I have tried on Windows and Mac. But it still doesn’t work.

If my usb drive is not salvageable do you think there is a way to scrap the data on it ?

1 Like

To me, both messages say that the device does show up.
Just not where you expect to find it, though.
/devusb is definitely wrong - that “thing” does not exist and never will
(unless you created it yourself, as a mount point …)

lsblk -f
could help

1 Like

First remove the stick and run

lsblk

Then attach the stick and one more time - the new device is your USB

lsblk

Check the filesystem of the device added to the list - X is device letter and y is partition no - usually there’s only one - but who knows - I have USB devices with more than one partition :slight_smile:

lsblk -o FSTYPE /dev/sdXy

If it is a linux type != ntfs then run

sudo fsck /dev/sdXy

Depending on the outcome - you may be able to mount the device

Create a temporary folder - in you rhome - to mount the device

mkdir ~/temp

Then mount the device partition (same rule as above apply)

sudo mount /dev/sdXy ~/temp

If successful - open the folder in your favorite file manager

When done close your filemanager and unmount

sudo umount ~/temp
 ~ $lsblk
NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
sda           8:0    0 465.8G  0 disk 
└─sda1        8:1    0 465.8G  0 part /run/media/...
sdb           8:16   0   1.8T  0 disk 
└─sdb1        8:17   0   1.8T  0 part /run/media/...
nvme0n1     259:0    0 232.9G  0 disk 
├─nvme0n1p1 259:1    0   300M  0 part /boot/efi
└─nvme0n1p2 259:2    0 232.6G  0 part /

~ $lsblk
NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
sda           8:0    0 465.8G  0 disk 
└─sda1        8:1    0 465.8G  0 part /run/media/...
sdb           8:16   0   1.8T  0 disk 
└─sdb1        8:17   0   1.8T  0 part /run/media/...
nvme0n1     259:0    0 232.9G  0 disk 
├─nvme0n1p1 259:1    0   300M  0 part /boot/efi
└─nvme0n1p2 259:2    0 232.6G  0 part /

This is the result on top unplugged, bottom plugged.

plus the /dev/ doesn’t change either.


/dev $ls
ashmem           dma_heap  hugepages     null              psaux   snapshot  tty15  tty27  tty39  tty50  tty62   ttyS16  ttyS28   uinput   vcsa    vcsu5
autofs           dri       input         nvidia0           ptmx    snd       tty16  tty28  tty4   tty51  tty63   ttyS17  ttyS29   urandom  vcsa1   vcsu6
block            fb0       kmsg          nvidiactl         ptp0    stderr    tty17  tty29  tty40  tty52  tty7    ttyS18  ttyS3    usb      vcsa2   vcsu63
bsg              fd        kvm           nvidia-modeset    pts     stdin     tty18  tty3   tty41  tty53  tty8    ttyS19  ttyS30   userio   vcsa3   vfio
btrfs-control    full      log           nvidia-uvm        random  stdout    tty19  tty30  tty42  tty54  tty9    ttyS2   ttyS31   v4l      vcsa4   vga_arbiter
bus              fuse      loop-control  nvidia-uvm-tools  rfkill  tty       tty2   tty31  tty43  tty55  ttyS0   ttyS20  ttyS4    vcs      vcsa5   vhci
char             hidraw0   mapper        nvme0             rtc     tty0      tty20  tty32  tty44  tty56  ttyS1   ttyS21  ttyS5    vcs1     vcsa6   vhost-net
console          hidraw1   media0        nvme0n1           rtc0    tty1      tty21  tty33  tty45  tty57  ttyS10  ttyS22  ttyS6    vcs2     vcsa63  vhost-vsock
core             hidraw2   mei0          nvme0n1p1         sda     tty10     tty22  tty34  tty46  tty58  ttyS11  ttyS23  ttyS7    vcs3     vcsu    video0
cpu              hidraw3   mem           nvme0n1p2         sda1    tty11     tty23  tty35  tty47  tty59  ttyS12  ttyS24  ttyS8    vcs4     vcsu1   video1
cpu_dma_latency  hidraw4   mqueue        nvram             sdb     tty12     tty24  tty36  tty48  tty6   ttyS13  ttyS25  ttyS9    vcs5     vcsu2   watchdog
cuse             hidraw5   net           port              sdb1    tty13     tty25  tty37  tty49  tty60  ttyS14  ttyS26  udmabuf  vcs6     vcsu3   watchdog0
disk             hpet      ng0n1         ppp               shm     tty14     tty26  tty38  tty5   tty61  ttyS15  ttyS27  uhid     vcs63    vcsu4   zero

/dev $ls
ashmem           dma_heap  hugepages     null              psaux   snapshot  tty15  tty27  tty39  tty50  tty62   ttyS16  ttyS28   uinput   vcsa    vcsu5
autofs           dri       input         nvidia0           ptmx    snd       tty16  tty28  tty4   tty51  tty63   ttyS17  ttyS29   urandom  vcsa1   vcsu6
block            fb0       kmsg          nvidiactl         ptp0    stderr    tty17  tty29  tty40  tty52  tty7    ttyS18  ttyS3    usb      vcsa2   vcsu63
bsg              fd        kvm           nvidia-modeset    pts     stdin     tty18  tty3   tty41  tty53  tty8    ttyS19  ttyS30   userio   vcsa3   vfio
btrfs-control    full      log           nvidia-uvm        random  stdout    tty19  tty30  tty42  tty54  tty9    ttyS2   ttyS31   v4l      vcsa4   vga_arbiter
bus              fuse      loop-control  nvidia-uvm-tools  rfkill  tty       tty2   tty31  tty43  tty55  ttyS0   ttyS20  ttyS4    vcs      vcsa5   vhci
char             hidraw0   mapper        nvme0             rtc     tty0      tty20  tty32  tty44  tty56  ttyS1   ttyS21  ttyS5    vcs1     vcsa6   vhost-net
console          hidraw1   media0        nvme0n1           rtc0    tty1      tty21  tty33  tty45  tty57  ttyS10  ttyS22  ttyS6    vcs2     vcsa63  vhost-vsock
core             hidraw2   mei0          nvme0n1p1         sda     tty10     tty22  tty34  tty46  tty58  ttyS11  ttyS23  ttyS7    vcs3     vcsu    video0
cpu              hidraw3   mem           nvme0n1p2         sda1    tty11     tty23  tty35  tty47  tty59  ttyS12  ttyS24  ttyS8    vcs4     vcsu1   video1
cpu_dma_latency  hidraw4   mqueue        nvram             sdb     tty12     tty24  tty36  tty48  tty6   ttyS13  ttyS25  ttyS9    vcs5     vcsu2   watchdog
cuse             hidraw5   net           port              sdb1    tty13     tty25  tty37  tty49  tty60  ttyS14  ttyS26  udmabuf  vcs6     vcsu3   watchdog0
disk             hpet      ng0n1         ppp               shm     tty14     tty26  tty38  tty5   tty61  ttyS15  ttyS27  uhid     vcs63    vcsu4   zero

Same here unplugged on top and plugged on the bottom.

/dev $lsusb   
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 003: ID 1532:0531 Razer USA, Ltd Razer Seiren Mini
Bus 003 Device 002: ID 1bcf:2284 Sunplus Innovation Technology Inc. FULL HD webcam
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
Bus 001 Device 004: ID 046d:c24a Logitech, Inc. G600 Gaming Mouse
Bus 001 Device 003: ID 2516:0145 Cooler Master Co., Ltd. CK550 V2 Gaming Mechanical Keyboard
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

/dev $lsusb                                                                                                                                                ✔ 
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 003: ID 1532:0531 Razer USA, Ltd Razer Seiren Mini
Bus 003 Device 002: ID 1bcf:2284 Sunplus Innovation Technology Inc. FULL HD webcam
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 008: ID 18a5:0243 Verbatim, Ltd Flash Drive (Store'n'Go)
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
Bus 001 Device 004: ID 046d:c24a Logitech, Inc. G600 Gaming Mouse
Bus 001 Device 003: ID 2516:0145 Cooler Master Co., Ltd. CK550 V2 Gaming Mechanical Keyboard
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

:bangbang: Tip: :bangbang:

When posting terminal output, copy the output and paste it here, wrapped in three (3) backticks, before AND after the pasted text. Like this:

```
pasted text
```

This will just cause it to be rendered like this:

Sed
sollicitudin dolor
eget nisl elit id
condimentum
arcu erat varius
cursus sem quis eros.

Instead of like this:

Sed sollicitudin dolor eget nisl elit id condimentum arcu erat varius cursus sem quis eros.

Alternatively, paste the text you wish to format as terminal output, select all pasted text, and click the </> button on the taskbar. This will indent the whole pasted section with one TAB, causing it to render the same way as described above.

Thereby increasing legibility thus making it easier for those trying to provide assistance.

For more information, please see:


:bangbang::bangbang: Also, if your language isn’t English, please prepend any and all terminal commands with LC_ALL=C. For example:

LC_ALL=C bluetoothctl

This will just cause the terminal output to be in English, making it easier to understand and debug.

thank you, sorry.

Even lsusb - shows the device is present - there is no new block devices.

To me - this point towards the device storage units has been blown somehow.

It is entirely possible the controller part of the stick (the one that identifies itself to the system and read/write the storage) works but the storage has gone.

that’s what I’ve been thinking, and in the original post I was wondering if someone knew a way to still dump the data ?

Unless you have some extremely valuable data and are willing to cough up the price of a new motor bike - you should break (a hammer and a hard surface usully does the trick) and discard it at the local electronics recycling business.

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.