[SOLVED] USB screw ups

[GregM]

Dell Optiplex 990
Kubuntu 18.04

I have front USB plugins and rear USB plugins.

Something has gone wrong.
I can't get Dolphin to recognize USB devices that I plug in to any of the ports.
When it does recognize them it will not allow me to copy files to them.

This is the same computer I have used for previous versions of Kubuntu, XP, and Win7
Never had a problem before 18.04.

All my USB devices work fine on XP and Win7.

This is making me crazy.

Can someone please help

[SpecialEd]

Have you opened up the case recently?

[Snowhog]

Run Konsole. With the konsole window open, insert a USB device into any of the available USB ports, then in the konsole, type: dmesg | tail -20

Copy/paste the output in a reply.

[GregM]

Thank you
greg@greg-OptiPlex-990:~$ dmesg | tail -20
[28624.374245] NVRM: No NVIDIA graphics adapter found!
[28624.374315] nvidia-nvlink: Unregistered the Nvlink Core, major device number 238
[28624.423234] nvidia-nvlink: Nvlink Core is being initialized, major device number 238
[28624.423432] NVRM: No NVIDIA graphics adapter found!
[28624.423503] nvidia-nvlink: Unregistered the Nvlink Core, major device number 238
[28624.578207] nvidia-nvlink: Nvlink Core is being initialized, major device number 238
[28624.578419] NVRM: No NVIDIA graphics adapter found!
[28624.578491] nvidia-nvlink: Unregistered the Nvlink Core, major device number 238
[28624.635675] nvidia-nvlink: Nvlink Core is being initialized, major device number 238
[28624.635886] NVRM: No NVIDIA graphics adapter found!
[28624.635955] nvidia-nvlink: Unregistered the Nvlink Core, major device number 238
[28624.695682] nvidia-nvlink: Nvlink Core is being initialized, major device number 238
[28624.695892] NVRM: No NVIDIA graphics adapter found!
[28624.695963] nvidia-nvlink: Unregistered the Nvlink Core, major device number 238
[28624.765719] nvidia-nvlink: Nvlink Core is being initialized, major device number 238
[28624.765910] NVRM: No NVIDIA graphics adapter found!
[28624.765978] nvidia-nvlink: Unregistered the Nvlink Core, major device number 238
[28624.818699] nvidia-nvlink: Nvlink Core is being initialized, major device number 238
[28624.818896] NVRM: No NVIDIA graphics adapter found!
[28624.818966] nvidia-nvlink: Unregistered the Nvlink Core, major device number 238
greg@greg-OptiPlex-990:~$

[GregM]

I removed all the Nvidia drivers I could and reran the command. It says

greg@greg-OptiPlex-990:~$ dmesg | tail -20
[ 72.197952] FAT-fs (sdc1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[ 225.845905] usb 2-1.3.1: USB disconnect, device number 6
[ 236.820410] usb 2-1.3.1: new high-speed USB device number 7 using ehci-pci
[ 237.427088] usb 2-1.3.1: New USB device found, idVendor=154b, idProduct=0059
[ 237.427090] usb 2-1.3.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 237.427092] usb 2-1.3.1: Product: USB 2.0 FD
[ 237.427093] usb 2-1.3.1: Manufacturer: PNY Technologies
[ 237.427094] usb 2-1.3.1: SerialNumber: AC88HCC1000000367
[ 237.427393] usb-storage 2-1.3.1:1.0: USB Mass Storage device detected
[ 237.427529] scsi host7: usb-storage 2-1.3.1:1.0
[ 238.798258] scsi 7:0:0:0: Direct-Access PNY USB 2.0 FD 4096 PQ: 0 ANSI: 4
[ 238.798861] sd 7:0:0:0: Attached scsi generic sg3 type 0
[ 238.799471] sd 7:0:0:0: [sdc] 7913472 512-byte logical blocks: (4.05 GB/3.77 GiB)
[ 238.800319] sd 7:0:0:0: [sdc] Write Protect is off
[ 238.800320] sd 7:0:0:0: [sdc] Mode Sense: 43 00 00 00
[ 238.801195] sd 7:0:0:0: [sdc] No Caching mode page found
[ 238.801198] sd 7:0:0:0: [sdc] Assuming drive cache: write through
[ 238.805351] sdc: sdc1
[ 238.808195] sd 7:0:0:0: [sdc] Attached SCSI removable disk
[ 239.092958] FAT-fs (sdc1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
greg@greg-OptiPlex-990:~$

[GregM]

It recognizes thumb drives and my camera chip quickly now, but will not allow me to copy files to either?

[Snowhog]

See this: https://www.tecmint.com/fsck-repair-...rors-in-linux/

Please review it first. Then review it again. Ask questions here if in doubt about ANYTHING. DON'T do anything until you fully understand.

[GregM]

I think I will do a clonezilla clone first and then try it.

Maybe I'll try it on the clone disk first.

[GregM]

It seems like running fsck would be the easiest upon system boot.

A question they don't answer...

"After your system boots, check if the file still exists:"
"If it does, you may want to remove it in order to avoid fsck on every system boot."

What would be the command to remove it?

[Snowhog]

That concern would only be relevant IF you had to run fsck on the root file system. That isn't your case.

[GregM]

I certainly won't argue with you but it does say to remove it...

[Snowhog]

Remove it "IF" you created it. If you didn't follow the steps under Force fsck Upon System Boot, then nothing to remove.

[Snowhog]

It seems like running fsck would be the easiest upon system boot.

A question they don't answer...

"After your system boots, check if the file still exists:"
"If it does, you may want to remove it in order to avoid fsck on every system boot."

What would be the command to remove it?

IF it exists, then from a konsole: sudo rm /forcefsck

[GregM]

Perfect.
Thanks
I have my clone made (I'm om it now) and I will give the Force fsck Upon System Boot a whirl.

[GregM]

I guess I'm not doing something right.
I copied the command # touch /forcefsck in to the terminal.
Rebooted and nothing seemed to happen.
Then to check I copied # ls /forcefsck in to the terminal and it returned nothing.

What did I do wrong?