Fedora 29 does not recognize my usb drive
 

Hi Guy's I am new to this. I am tired of Windows so now I have installed Fedora on my laptop question is

Fedora 29 does not recognize my usb drive which is a lexar drive

the drive blinks but does not show up

How do I get Fedora to recognize this drive

First it would be worth finding out what the kernel thinks of this drive. In Linux, the kernel manages all your hardware.

Plug it in, then open a terminal and type dmesg|tail -20. You will see the last 20 lines of the kernel's message ring in which it should report the new device, its usb vendor and device numbers, and the fact that it is a mass storage device made by Lexar. However, it won't be accessible to you until it has been mounted. Most modern distros mount plug-in devices in the /media folder tree. Often it's done automatically; all you have to do is go to the obvious mountpoint (for example it might be called /media/usb) in your file manager and click on it. But if the kernel doesn't recognise it, there's a problem with the drive.

Thanks Hazel here is the output from the dmesg|tail 29 command

stanlip@localhost ~]$ dmesg|tail -20
[351610.430698] usb 5-1: device not accepting address 7, error -71
[351610.544460] usb 5-1: new high-speed USB device number 8 using xhci_hcd
[351610.544619] usb 5-1: Device not responding to setup address.
[351610.750852] usb 5-1: Device not responding to setup address.
[351610.958696] usb 5-1: device not accepting address 8, error -71
[351610.958769] usb usb5-port1: unable to enumerate USB device
[352306.896263] usb usb3-port1: disabled by hub (EMI?), re-enabling...
[352306.896273] usb 3-1: USB disconnect, device number 79
[352307.154541] usb 3-1: new low-speed USB device number 80 using ohci-pci
[352307.313503] usb 3-1: New USB device found, idVendor=062a, idProduct=0001, bcdDevice= 0.00
[352307.313509] usb 3-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[352307.321135] input: HID 062a:0001 as /devices/pci0000:00/0000:00:12.0/usb3/3-1/3-1:1.0/0003:062A:0001.004B/input/input87
[352307.321726] hid-generic 0003:062A:0001.004B: input,hidraw0: USB HID v1.10 Mouse [HID 062a:0001] on usb-0000:00:12.0-1/input0
[352313.160242] usb usb3-port1: disabled by hub (EMI?), re-enabling...
[352313.160249] usb 3-1: USB disconnect, device number 80
[352313.421379] usb 3-1: new low-speed USB device number 81 using ohci-pci
[352313.580508] usb 3-1: New USB device found, idVendor=062a, idProduct=0001, bcdDevice= 0.00
[352313.580513] usb 3-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[352313.588439] input: HID 062a:0001 as /devices/pci0000:00/0000:00:12.0/usb3/3-1/3-1:1.0/0003:062A:0001.004C/input/input88
[352313.589097] hid-generic 0003:062A:0001.004C: input,hidraw0: USB HID v1.10 Mouse [HID 062a:0001] on usb-0000:00:12.0-1/input0
[stanlip@localhost ~]$


how would I mount this device (sorry I am really green at this stuff)

@stanlip : Welcome to LQ.

There have been kernel updates for CentOS 7 not accepting an USB stick with a Windows© file system.
( CentOS 7 is based on Fedora.)

Instead I have used an USB drive with an ext 3 file system.
... The next kernel update could then be different, and a default USB drive would work again.

An alternative storage could also be e.g. Dropbox or Google Drive.

-

That last line doesn't look very promising - a mouse doesn't make a very good hard disk. Likewise vice versa I suspect.
There have been reports of USB keys being hacked to respond as a mouse (to system events), but this is likely just a mismatch in UDEV rules. Try this from a terminal and post the udevadm.log file it creates - note you will see nothing on the screen. So, enter the command and your password if asked (you will most likely), then insert the disk. Leave it for say 30 seconds, then hit <Ctrl>-c (both keys together to generate an interrupt). The file will have all the events as seen by the kernel and udev as the device is set up - what goes on under the covers to generate the messages in dmesg above.