dirt in the usb socket?
Unlikely. BIOS is detecting the things fine and I'm having no issues with my wireless mouse (I've played some switchabouts between the front sockets to make sure).
Someone suggested that it might be a permissions issue, so I did the following to investigate:
I made a mount point using sudo (
fdisk -l first to find the device ID). The result was:
Code: Select all
mount: wrong fs type, bad option, bad superblock on /dev/sdb, missing codepage or helper program, or other error
In some cases useful info is found in syslog - try dmesg | tail or so.
So I tried
dmesg | tail and the output was:
Code: Select all
[19325.848652] sdb: sdb1 [19325.849499] sd 4:0:0:0: [sdb] Attached SCSI removable disk [19394.251666] [UFW BLOCK] IN=wlp3s0 OUT= MAC=50:3e:aa:56:e6:1b:74:c2:46:a4:b2:3f:08:00 SRC=192.168.0.4 DST=192.168.0.7 LEN=345 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=49410 DPT=52636 LEN=325 [19395.604837] [UFW BLOCK] IN=wlp3s0 OUT= MAC=50:3e:aa:56:e6:1b:74:c2:46:a4:b2:3f:08:00 SRC=192.168.0.4 DST=192.168.0.7 LEN=345 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=49410 DPT=52636 LEN=325 [19396.504528] [UFW BLOCK] IN=wlp3s0 OUT= MAC=50:3e:aa:56:e6:1b:74:c2:46:a4:b2:3f:08:00 SRC=192.168.0.4 DST=192.168.0.7 LEN=345 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=49410 DPT=52636 LEN=325 [19397.636230] [UFW BLOCK] IN=wlp3s0 OUT= MAC=50:3e:aa:56:e6:1b:74:c2:46:a4:b2:3f:08:00 SRC=192.168.0.4 DST=192.168.0.7 LEN=345 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=49410 DPT=52636 LEN=325 [19513.857904] [UFW BLOCK] IN=wlp3s0 OUT= MAC=50:3e:aa:56:e6:1b:74:c2:46:a4:b2:3f:08:00 SRC=192.168.0.4 DST=192.168.0.7 LEN=345 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=49410 DPT=52380 LEN=325 [19515.905946] [UFW BLOCK] IN=wlp3s0 OUT= MAC=50:3e:aa:56:e6:1b:74:c2:46:a4:b2:3f:08:00 SRC=192.168.0.4 DST=192.168.0.7 LEN=345 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=49410 DPT=52380 LEN=325 [19516.725194] [UFW BLOCK] IN=wlp3s0 OUT= MAC=50:3e:aa:56:e6:1b:74:c2:46:a4:b2:3f:08:00 SRC=192.168.0.4 DST=192.168.0.7 LEN=345 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=49410 DPT=52380 LEN=325 [19517.749212] [UFW BLOCK] IN=wlp3s0 OUT= MAC=50:3e:aa:56:e6:1b:74:c2:46:a4:b2:3f:08:00 SRC=192.168.0.4 DST=192.168.0.7 LEN=345 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=49410 DPT=52380 LEN=325
I can't see anything helpful in there, but that may be my ignorance.
FWIW, my original poke with fdisk suggests the file system on the stick I was testing with was fat32.
The other party suggested I try
By this point, however, my system had decided that it wasn't going to even partially detect the flash drive anymore, so even after unplugging and replugging it in, the output was:
Code: Select all
Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors 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: gpt Disk identifier: 6DF21727-54BD-4243-A7C5-80D1D73CDD90
Device Start End Sectors Size Type /dev/sda1 2048 1050623 1048576 512M EFI System /dev/sda2 1050624 1550335 499712 244M Linux filesystem /dev/sda3 1550336 1953523711 1951973376 930.8G Linux LVM
Disk /dev/mapper/bedevere--vg-root: 922.8 GiB, 990870765568 bytes, 1935294464 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/mapper/bedevere--vg-swap_1: 8 GiB, 8535408640 bytes, 16670720 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Welcome to fdisk (util-linux 2.29.2). Changes will remain in memory only, until you decide to write them. Be careful before using the write command.
fdisk: cannot open /dev/sdb: No such file or directory
To make it clear: when I insert a USB drive, its LED turns on or blinks, but it may or may not show up in Thunar, and when it does, it unmounts within a minute. The LED remains on. Rebooting with the drive still in and going into the BIOS menu, the flash drive is clearly detected as it shows up in the boot menu (NB, this stick I was using for testing did not have an iso on it). I switched it with my mouse dongle and the mouse is working fine, and the flash drive is still not behaving right in the other USB port. I used only one flash drive for testing today, but the problems were occurring with three different flash drives on Sunday.
I first noticed something was amiss on Friday and the drives seem to be working properly on my Fedora machine. Which suggests that I've somehow done something to cause this. The only change I can remember making to the system before Friday was a failed attempt at installing a driver for a Brother wifi printer.
Tomorrow I may boot from my recovery DVD just to see what happens.