Permissions error mounting USB drive

[ian_r_h]

Thank you, Trinidad.

1) What are you copying?

It's a .tar.gz file freshly created by Archive Manager (from a right-click), and tested by extracting back to the HD first.

2) What Linux software are you using (not the OS) to accomplish the copying?

New to Linux here; otherwise I would have also tried from the terminal.

I'm using the default File Manager for LL (Thunar, as I understand it).  Again, right-click Copy from HD and then left-click, Paste to USB stick.

3) What do you want the data copied to the USB to do or be?

I'm not sure I understand the question.  I'm just trying to copy the .tar.gz archive to the USB stick.  I would have expected this to be a straightforward data transfer.

Update:

As said in last post, it copied OK from another LL laptop (different make and model), after using the Menu/Settings/Disk menu to reformat the partition to default and sudo chown -R ian: /media/ian/NAME/ to change permissions from root to me.

Update 2:
I have also successfully copied from the HD on this laptop today, using a different USB stick (same make and model, bought at the same time), on a different USB port on the machine.

This also follows, of course, a shut down overnight and restart this morning.

[trinidad]

Sounds like you have solved it. I would create a directory on the USB disk first, call it anything you want, like "savedfiles" and then open Thunar as administrator and copy the tar file you created and paste to the USB directory. You can also try using an ext2,3,4 partition on the USB which will allow you to directly compress files on the USB in some cases. Tar usage has a long history. It's worth experimenting with and mastering. Below are a couple of decent starter links.

https://www.howtogeek.com/248780/how-to-...-on-linux/

http://www.thegeekstuff.com/2010/04/unix...-examples/

TC   

[ian_r_h]

Thanks, Trinidad.

Some year ago I used to do this kind of thing for a living (just never on Linux or a *nix system).  Out of practice is all (I hope!).

OK.  For the benefit of anyone else should this arise.

Just successfully backup up to a third USB stick today - again, identical make and model and again, on the physical USB port I tried yesterday.  I've had no joy Googling the problem yet.

Since these are daily backups, and I will be rotating between two physical laptops once per month, it may take me a while to establish which combinations of physical laptop, physical USB port and physical USB stick work - and which don't.  It could be an intermittent problem, or it could be the physical port on which it failed previously (or possibly a USB extension cable, though this works fine on Windows 7 and 10).

I'll report back on this thread whether it continues to work (in which case I'm thinking a dodgy USB port), or whether it recurs on the second USB port and/or other laptop(s), in which case it's some kind of intermittent problem.  In the latter case, if I should find a solution myself meantime, I will also post it back here.

But for now, I think I need to carry on doind the daily backups in the same way on the same port and see what happens...

Thanks for your help so far.

[ian_r_h]

OK.

The posts above refer to one of my two assumed identical linux boxes - by which I mean that I asked my computer shop to provide two identical hardware specified units.  The unit in the posts above refer to "linux01".  The following refer to "linux02".  I have a third unit "linuxtest", which is a 6 year old Acer Aspire laptop of different specs.

On linux02, using the same spec'd USB stick (daily03) as the one previously tried on linux01 (daily01) - both Kingston Data Traveller G4 16Gb rated as USB 3 and as Linux-compatible, and bought at the same time.  On the same physical positioned USB port on linux02 this USB stick also errored and seemed to auto-dismount.  Again, the connection is also using an extension cable which has been working fine on Windows 7 and 10 (different PCs to each other and the linux laptops).

So what's the same:-

linux01 and linux02 should be physically the same spec,
daily01 and daily03 are the same make and model of USB stick,
the same USB extension cable...

On the same physically located (USB3) port, not using the extension cable, both daily01 and daily03 usb sticks work just fine on both linux01 and linux02.

On the same physically located (USB2?) port on linux02, using the extension cable, the daily03 stick has now errored when writing files (and on that port location on linux01 the daily01 stick also errored as above).

The purist in me wants to try without the extension cable, just to rule that out.  I get to daily02 - a third USB stick of this make and model also working fine on the USB3 port on both linux01 and linux02, on Sunday, so I will try that on the USB2(?) port without the extension cable.

In all cases, daily01 and daily03 are formatted by default to FAT.  I'll double-check which version of FAT also.

If I recall, linuxtest (the Acer unit) has only USB2 ports, and they seemed to work fine on that; but I haven't tested as thoroughly.

I'm leaning to some kind of compatibility issue with the "faulty" USB port on both units - at least when attaching this make and model, and possibly any USB3, device.  Maybe a driver issue?

The problem is minor for me, as the USB3 port works fine on both units, and I am happily able to double-up backups onto DVD-RW anyway.  My main concern now is if the problem occurred and wiped by USB EHD drive(s).  But if I could, with help, diagnose the problem, I suppose there is potential to help someone else down the line.

The error log for today's attempt on linux02 on the faulting USB port (via extension cable) on the daily03 stick is below.  To my inexpert eye (with the Linux log, as yet), this looks subtly different to the error on daily01 on linux01 above.  I welcome any thoughts:-

Nov 10 10:55:35 linux02 udisksd[2109]: Cleaning up mount point /media/ian/Data 2017-11-10~ (device 11:0 is not mounted)
Nov 10 10:55:35 linux02 udisksd[2109]: Unmounted /dev/sr0 on behalf of uid 1000
Nov 10 10:56:00 linux02 kernel: [13292.820403] usb 1-1: new high-speed USB device number 7 using xhci_hcd
Nov 10 10:56:00 linux02 kernel: [13293.015077] usb 1-1: New USB device found, idVendor=0951, idProduct=1666
Nov 10 10:56:00 linux02 kernel: [13293.015090] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Nov 10 10:56:00 linux02 kernel: [13293.015098] usb 1-1: Product: DataTraveler 3.0
Nov 10 10:56:00 linux02 kernel: [13293.015104] usb 1-1: Manufacturer: Kingston
Nov 10 10:56:00 linux02 kernel: [13293.015109] usb 1-1: SerialNumber: 0026185260A8F051F83A4B71
Nov 10 10:56:00 linux02 kernel: [13293.015625] usb 1-1: ep 0x81 - rounding interval to 128 microframes, ep desc says 255 microframes
Nov 10 10:56:00 linux02 kernel: [13293.015648] usb 1-1: ep 0x2 - rounding interval to 128 microframes, ep desc says 255 microframes
Nov 10 10:56:01 linux02 mtp-probe: checking bus 1, device 7: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-1"
Nov 10 10:56:01 linux02 mtp-probe: bus: 1, device: 7 was not an MTP device
Nov 10 10:56:01 linux02 kernel: [13293.234229] usb-storage 1-1:1.0: USB Mass Storage device detected
Nov 10 10:56:01 linux02 kernel: [13293.234308] scsi host2: usb-storage 1-1:1.0
Nov 10 10:56:01 linux02 kernel: [13293.234415] usbcore: registered new interface driver usb-storage
Nov 10 10:56:01 linux02 kernel: [13293.261139] usbcore: registered new interface driver uas
Nov 10 10:56:02 linux02 kernel: [13294.232968] scsi 2:0:0:0: Direct-Access    Kingston DataTraveler 3.0      PQ: 0 ANSI: 6
Nov 10 10:56:02 linux02 kernel: [13294.233317] sd 2:0:0:0: Attached scsi generic sg2 type 0
Nov 10 10:56:02 linux02 kernel: [13294.233881] sd 2:0:0:0: [sdb] 30218842 512-byte logical blocks: (15.5 GB/14.4 GiB)
Nov 10 10:56:02 linux02 kernel: [13294.234059] sd 2:0:0:0: [sdb] Write Protect is off
Nov 10 10:56:02 linux02 kernel: [13294.234063] sd 2:0:0:0: [sdb] Mode Sense: 4f 00 00 00
Nov 10 10:56:02 linux02 kernel: [13294.234226] sd 2:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
Nov 10 10:56:02 linux02 kernel: [13294.239158]  sdb: sdb1
Nov 10 10:56:02 linux02 kernel: [13294.240531] sd 2:0:0:0: [sdb] Attached SCSI removable disk
Nov 10 10:56:07 linux02 udisksd[2109]: Mounted /dev/sdb1 at /media/ian/9CA9-475E on behalf of uid 1000
Nov 10 10:56:17 linux02 kernel: [13309.269194] usb 1-1: USB disconnect, device number 7
Nov 10 10:56:17 linux02 kernel: [13309.374831] sd 2:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
Nov 10 10:56:17 linux02 kernel: [13309.374846] sd 2:0:0:0: [sdb] tag#0 CDB: Write(10) 2a 00 00 91 f3 ff 00 00 f0 00
Nov 10 10:56:17 linux02 kernel: [13309.374853] blk_update_request: I/O error, dev sdb, sector 9565183
Nov 10 10:56:17 linux02 kernel: [13309.376714] sd 2:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
Nov 10 10:56:17 linux02 kernel: [13309.376719] sd 2:0:0:0: [sdb] tag#0 CDB: Write(10) 2a 00 00 91 f4 ef 00 00 f0 00
Nov 10 10:56:17 linux02 kernel: [13309.376722] blk_update_request: I/O error, dev sdb, sector 9565423
Nov 10 10:56:17 linux02 kernel: [13309.395187] FAT-fs (sdb1): unable to read inode block for updating (i_pos 524303)
Nov 10 10:56:17 linux02 udisksd[2109]: Cleaning up mount point /media/ian/9CA9-475E (device 8:17 no longer exist)
Nov 10 10:56:17 linux02 kernel: [13309.758244] FAT-fs (sdb1): unable to read boot sector to mark fs as dirty
Nov 10 10:56:56 linux02 kernel: [13348.519910] usb 1-1: new high-speed USB device number 8 using xhci_hcd
Nov 10 10:56:56 linux02 kernel: [13348.715155] usb 1-1: New USB device found, idVendor=0951, idProduct=1666
Nov 10 10:56:56 linux02 kernel: [13348.715168] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Nov 10 10:56:56 linux02 kernel: [13348.715176] usb 1-1: Product: DataTraveler 3.0
Nov 10 10:56:56 linux02 kernel: [13348.715182] usb 1-1: Manufacturer: Kingston
Nov 10 10:56:56 linux02 kernel: [13348.715187] usb 1-1: SerialNumber: 0026185260A8F051F83A4B71
Nov 10 10:56:56 linux02 kernel: [13348.715882] usb 1-1: ep 0x81 - rounding interval to 128 microframes, ep desc says 255 microframes
Nov 10 10:56:56 linux02 kernel: [13348.715908] usb 1-1: ep 0x2 - rounding interval to 128 microframes, ep desc says 255 microframes
Nov 10 10:56:56 linux02 kernel: [13348.721884] usb-storage 1-1:1.0: USB Mass Storage device detected
Nov 10 10:56:56 linux02 kernel: [13348.722211] scsi host3: usb-storage 1-1:1.0
Nov 10 10:56:56 linux02 mtp-probe: checking bus 1, device 8: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-1"
Nov 10 10:56:56 linux02 mtp-probe: bus: 1, device: 8 was not an MTP device
Nov 10 10:56:57 linux02 kernel: [13349.721453] scsi 3:0:0:0: Direct-Access    Kingston DataTraveler 3.0      PQ: 0 ANSI: 6
Nov 10 10:56:57 linux02 kernel: [13349.722715] sd 3:0:0:0: Attached scsi generic sg2 type 0
Nov 10 10:56:57 linux02 kernel: [13349.724681] sd 3:0:0:0: [sdb] 30218842 512-byte logical blocks: (15.5 GB/14.4 GiB)
Nov 10 10:56:57 linux02 kernel: [13349.724938] sd 3:0:0:0: [sdb] Write Protect is off
Nov 10 10:56:57 linux02 kernel: [13349.724953] sd 3:0:0:0: [sdb] Mode Sense: 4f 00 00 00
Nov 10 10:56:57 linux02 kernel: [13349.725184] sd 3:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
Nov 10 10:56:57 linux02 kernel: [13349.728586]  sdb: sdb1
Nov 10 10:56:57 linux02 kernel: [13349.731469] sd 3:0:0:0: [sdb] Attached SCSI removable disk
Nov 10 10:57:03 linux02 kernel: [13355.329331] FAT-fs (sdb1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Nov 10 10:57:03 linux02 udisksd[2109]: Mounted /dev/sdb1 at /media/ian/9CA9-475E on behalf of uid 1000
Nov 10 10:57:16 linux02 udisksd[2109]: Cleaning up mount point /media/ian/9CA9-475E (device 8:17 is not mounted)
Nov 10 10:57:16 linux02 udisksd[2109]: Unmounted /dev/sdb1 on behalf of uid 1000

[ian_r_h]

The purist in me wants to try without the extension cable, just to rule that out.  I get to daily02 - a third USB stick of this make and model also working fine on the USB3 port on both linux01 and linux02, on Sunday, so I will try that on the USB2(?) port without the extension cable.

And the purist would be right!

Despite working fine with Windows, the common factor is the USB extension cable:-

On linux01 with daily01, on "port01", using the extension cable resulted in an error;
On linux01 with all usb sticks, on "port02", without the extension cable the data copies and hashes.
On linux02 with daily03, on "port01", using the extension cable resulted in an error;
On linus02 with all usb sticks, on "port02", without the extension cable the data copies and hashes.
On linux02 with daily02, on "port01", without the extension cable the data copied and hashed.

So unless by some coincidence daily02 is OK and daily01 and daily03 usb sticks error but strangely only on port01 and not port02 and on both physical LL laptops, I conclude the fault is caused by the extension cable - even though it works fine on my Windows 7 and 10 units.

Conclusion:  compatibility issue with the usb extension cable, oddly restricted either to the physical setup of the (identical) LL laptops or with linux and not Windows variants.

Solved.

[trinidad]

My advice: Don't use the extension cable or buy a new pure data transfer cable. The rabbit hole could go very deep here, involving ACPI, and the relation of the kernel to the motherboard and cpu that is causing under-voltages, but it is more likely that you have a dual purpose cable, or an old external USB HDD connection cable, or a USB smart card reader cable, all of which are high resistance. Windows 7,8,10 kernel detects all types based on the voltages. Not necessarily the case with Linux. Make sure if your BIOS are older versions that PnP is disabled.

TC 

[ian_r_h]

Thanks, Trinidad.

(Only just found your reply, so sorry for not saying earlier.)