Whenever I plug in my usb, Fedora doesnt detect my drive. I cannot find it in files either. When I type in lsblk, I see my usb drive appear as sda, however it shows up nowhere else. I have tried it on different devices just to make sure that the usb works, there seems to be no issues whenever I plug it into any other machine. Might there be an issue with mounting?
Welcome to 
@luisf
Can you paste the reults of lsblk here for us in preformatted text </>
1 Like
Of course,
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sda 8:0 1 58.6G 0 disk
zram0 252:0 0 8G 0 disk [SWAP]
nvme0n1 259:0 0 476.9G 0 disk
├─nvme0n1p1 259:1 0 529M 0 part
├─nvme0n1p2 259:2 0 100M 0 part /boot/efi
├─nvme0n1p3 259:3 0 16M 0 part
├─nvme0n1p4 259:4 0 375.7G 0 part
├─nvme0n1p5 259:5 0 619M 0 part
├─nvme0n1p6 259:6 0 1G 0 part /boot
└─nvme0n1p7 259:7 0 99G 0 part /home
/
1 Like
It does not look to be mounted. Does it have a file system on it?
You can try to mount it using mount /dev/sda /path/to-mount
2 Likes
What filesystem is on the USB drive? Are the other machines running linux? If so, the output from lsblk on a system where it mounts might help us understand the issue.
1 Like
Others have given you some good ideas, but I’m also going to suggest that, on the current boot session and after you’ve plugged in your device, you take a look at your system journal
sudo journalctl -b 0
and do a search for lines containing “usb” to see exactly what your system thinks it’s seeing when you’ve plugged in your device. I’m pretty sure you’ll know what the important event is when you see it in the log. Whatever it is, it should provide some clue on why the disk isn’t automounting.
Afterwards, please get back to folks here to make your question more specific.
I agree with this idea, but I would suggest opening a terminal window and running journalctl -f then watching that output when the usb device is plugged it. That should give a real-time output so the information is immediately available.
Also, the fact that usb device does not reveal a partition may be the issue in itself, depending upon the file system which may or may not be on the device.
More info would also be available with either lsblk -f or sudo fdisk -l
3 Likes
I always do things the hardest way possible. 
2 Likes
The first thing I’d test is that the usb subsystem is remotely acting normally. That is, run this:
dmesg -w
to “follow” the dmesg buffer messages, then plug in the USB drive. A normal, formatted usb key drive should show a ‘dmesg’ message dump after doing that of that looks something like:
[ 8594.847082] usb 2-2: new SuperSpeed USB device number 3 using xhci_hcd
[ 8594.861271] usb 2-2: New USB device found, idVendor=0951, idProduct=1666, bcdDevice= 1.10
[ 8594.861288] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 8594.861296] usb 2-2: Product: DataTraveler 3.0
[ 8594.861303] usb 2-2: Manufacturer: Kingston
[ 8594.861310] usb 2-2: SerialNumber: E0D55E6B6365E3C1495101D8
[ 8594.862601] usb-storage 2-2:1.0: USB Mass Storage device detected
[ 8594.863027] scsi host2: usb-storage 2-2:1.0
[ 8595.914600] scsi 2:0:0:0: Direct-Access Kingston DataTraveler 3.0 PMAP PQ: 0 ANSI: 6
[ 8595.915202] sd 2:0:0:0: Attached scsi generic sg0 type 0
[ 8596.013955] sd 2:0:0:0: [sda] 121208832 512-byte logical blocks: (62.1 GB/57.8 GiB)
[ 8596.014473] sd 2:0:0:0: [sda] Write Protect is off
[ 8596.014484] sd 2:0:0:0: [sda] Mode Sense: 45 00 00 00
[ 8596.014781] sd 2:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[ 8596.019359] sd 2:0:0:0: [sda] Attached SCSI removable disk
3 Likes
Hi,
Apologize for the late response. I was able to fix my issue by formatting the usb to an exFat file type and then mounting using this command. Thank you.
3 Likes