You are Here:
Linux Lite 6.6 FINAL Released - Support for 22 Languages Added - See Release Announcement Section



Permissions error mounting USB drive

Author (Read 11940 times)

0 Members and 1 Guest are viewing this topic.

Re: Permissions error mounting USB drive
« Reply #17 on: November 20, 2017, 07:19:13 AM »
 

ian_r_h

  • Merchandise Supporter
  • Forum Regular
  • *****
  • 103
    Posts
  • Reputation: 10
  • Linux Lite Member
    • View Profile
Thanks, Trinidad.

(Only just found your reply, so sorry for not saying earlier.)
Don't worry about artificial intelligence.  Worry about natural stupidity.  :)
 

Re: Permissions error mounting USB drive
« Reply #16 on: November 12, 2017, 10:55:56 AM »
 

trinidad

  • Platinum Level Poster
  • **********
  • 1463
    Posts
  • Reputation: 212
  • Linux Lite Member
    • View Profile
    • dbts-analytics.com

  • CPU: i7 4 cores 8 threads

  • MEMORY: 16Gb

  • VIDEO CARD: Intel HD graphics

  • Kernel: 5.x
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 
All opinions expressed and all advice given by Trinidad Cruz on this forum are his responsibility alone and do not necessarily reflect the views or methods of the developers of Linux Lite. He is a citizen of the United States where it is acceptable to occasionally be uninformed and inept as long as you pay your taxes.
 

Re: Permissions error mounting USB drive
« Reply #15 on: November 12, 2017, 04:10:42 AM »
 

ian_r_h

  • Merchandise Supporter
  • Forum Regular
  • *****
  • 103
    Posts
  • Reputation: 10
  • Linux Lite Member
    • View Profile
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.
Don't worry about artificial intelligence.  Worry about natural stupidity.  :)
 

Re: Permissions error mounting USB drive
« Reply #14 on: November 10, 2017, 07:46:59 AM »
 

ian_r_h

  • Merchandise Supporter
  • Forum Regular
  • *****
  • 103
    Posts
  • Reputation: 10
  • Linux Lite Member
    • View Profile
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

Don't worry about artificial intelligence.  Worry about natural stupidity.  :)
 

Re: Permissions error mounting USB drive
« Reply #13 on: October 10, 2017, 07:31:29 AM »
 

ian_r_h

  • Merchandise Supporter
  • Forum Regular
  • *****
  • 103
    Posts
  • Reputation: 10
  • Linux Lite Member
    • View Profile
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.
Don't worry about artificial intelligence.  Worry about natural stupidity.  :)
 

Re: Permissions error mounting USB drive
« Reply #12 on: October 09, 2017, 10:20:10 AM »
 

trinidad

  • Platinum Level Poster
  • **********
  • 1463
    Posts
  • Reputation: 212
  • Linux Lite Member
    • View Profile
    • dbts-analytics.com

  • CPU: i7 4 cores 8 threads

  • MEMORY: 16Gb

  • VIDEO CARD: Intel HD graphics

  • Kernel: 5.x
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-compress-and-extract-files-using-the-tar-command-on-linux/

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

TC     
All opinions expressed and all advice given by Trinidad Cruz on this forum are his responsibility alone and do not necessarily reflect the views or methods of the developers of Linux Lite. He is a citizen of the United States where it is acceptable to occasionally be uninformed and inept as long as you pay your taxes.
 

Re: Permissions error mounting USB drive
« Reply #11 on: October 09, 2017, 08:33:41 AM »
 

ian_r_h

  • Merchandise Supporter
  • Forum Regular
  • *****
  • 103
    Posts
  • Reputation: 10
  • Linux Lite Member
    • View Profile
Thank you, Trinidad.

Quote
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.

Quote
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.

Quote
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.
Don't worry about artificial intelligence.  Worry about natural stupidity.  :)
 

Re: Permissions error mounting USB drive
« Reply #10 on: October 08, 2017, 11:24:40 AM »
 

trinidad

  • Platinum Level Poster
  • **********
  • 1463
    Posts
  • Reputation: 212
  • Linux Lite Member
    • View Profile
    • dbts-analytics.com

  • CPU: i7 4 cores 8 threads

  • MEMORY: 16Gb

  • VIDEO CARD: Intel HD graphics

  • Kernel: 5.x
Think Linux: simplicity.

1) What are you copying?
2) What Linux software are you using (not the OS) to accomplish the copying?
3) What do you want the data copied to the USB to do or be?

Be specific about these three questions and we can advise you further. Block offset errors suggest the wrong disk format for what you are trying to do. Probably should have run fsck manually after the unplug as well. Other than that I cannot advise you without knowing the answer to the three questions above.

TC
All opinions expressed and all advice given by Trinidad Cruz on this forum are his responsibility alone and do not necessarily reflect the views or methods of the developers of Linux Lite. He is a citizen of the United States where it is acceptable to occasionally be uninformed and inept as long as you pay your taxes.
 

Re: Permissions error mounting USB drive
« Reply #9 on: October 08, 2017, 09:29:09 AM »
 

ian_r_h

  • Merchandise Supporter
  • Forum Regular
  • *****
  • 103
    Posts
  • Reputation: 10
  • Linux Lite Member
    • View Profile
OK.

Booted up 7 year-old entirely different manufacturer/model laptop with essentially the same build of LL, which is my test unit.

Copied data from DVD backup made to this unit (also verifying the SHA256 hashes).

Connected the USB stick.
Again, formatted it using the default options in Menu/Settings/Disks.

This time, the USB stick did not disappear from the Thunar view and desktop.

However, permissions were set to root, so changed in terminal by:

sudo chown -R ian: /media/ian/KINGSTON/

Verified that the permissions appeared identical from right-click on desktop USB icon, which they were.

Copied files from this HD to USB stick without error (this time - we'll see if this continues; before I have had the USB sticks work for a bit and then not, but haven't tested on this laptop before).

Verified that the SHA256 hashes were correct.

So (touch wood), I have a work-around for myself and - should this recur - for anyone else with a second PC/laptop of different spec... subject to this bug not recurring on the test laptop also.  If it does, I'll update in this post.

Meanwhile, though, I'm no closer to understanding what is going on on my main LL laptop.
Don't worry about artificial intelligence.  Worry about natural stupidity.  :)
 

Re: Permissions error mounting USB drive
« Reply #8 on: October 08, 2017, 08:02:14 AM »
 

ian_r_h

  • Merchandise Supporter
  • Forum Regular
  • *****
  • 103
    Posts
  • Reputation: 10
  • Linux Lite Member
    • View Profile
OK.

Again connected USB stick.
Loaded Menu/Settings/Disks.
Selected to quick format using default settings.
USB disappeared from Thunar view and desktop, so waited a minute and manually disconnected and reconnected USB stick.
Checked permissions, which right-clicking desktop icon showed as same as when formatted in Win 10.
The two small files copied.
But when copying the large file, it gets part way and now errors "Failed to open directory 'KINGSTON'.  Error opening directory '/media/ian/KINGSTON': Permission denied." [KINGSTON was the label I applied this time when formatting as above.]
Drive again disappears (dismounted?)
Manually disconnected and reconnected.
Checked permissions by right-clicking desktop icon, which are unchanged:

Owner: ian (ian)
Access: Read & Write
Group: ian
Access: Read only
Others: Read only.

This last error round is familiar from when it was failing in Ubuntu/Unity, where the file manager was reported permission errors; but these may not be identical in this case.
Don't worry about artificial intelligence.  Worry about natural stupidity.  :)
 

Re: Permissions error mounting USB drive
« Reply #7 on: October 08, 2017, 07:54:51 AM »
 

ian_r_h

  • Merchandise Supporter
  • Forum Regular
  • *****
  • 103
    Posts
  • Reputation: 10
  • Linux Lite Member
    • View Profile
OK, error message was just hidden behind the benchmarking window, which closed OK once I cancelled the error message.

Menu/Settings/Disk benchmarking failed after very short time with error:

Error writing 10485760 bytes at offset 309428224: Input/output error (g-io-error-quark, 0)
Don't worry about artificial intelligence.  Worry about natural stupidity.  :)
 

Re: Permissions error mounting USB drive
« Reply #6 on: October 08, 2017, 07:51:51 AM »
 

ian_r_h

  • Merchandise Supporter
  • Forum Regular
  • *****
  • 103
    Posts
  • Reputation: 10
  • Linux Lite Member
    • View Profile
Also:-

Menu/Settings/Disk
Connected USB stick
Clicked tools icon and selected benchmark disk.
Benchmark errored, but error message disappeared before I could note it down!  (Was different to the earlier error message.)
Cannot retry as disk and benchmark windows no longer responding.

Will try rebooting laptop at this point.
Don't worry about artificial intelligence.  Worry about natural stupidity.  :)
 

Re: Permissions error mounting USB drive
« Reply #5 on: October 08, 2017, 07:47:01 AM »
 

ian_r_h

  • Merchandise Supporter
  • Forum Regular
  • *****
  • 103
    Posts
  • Reputation: 10
  • Linux Lite Member
    • View Profile
Quote
Have you tried Menu, Settings, Disks? The Help Manual has a section on formatting disks too.

Thanks, Jerry.

I'll give that a go in a moment.  Below my sign-off is the output of a second attempt.

In brief:
Formatted USB stick (slow version) in Windows 10 to default FAT32 (8kb block) format.
Rebooted LL laptop.
Connected to LL laptop.
Checked permissions.
Managed to copy two small files, but large file gets part-way and errors: ""Error splicing file.  Input/output error.  Do you want to skip it?""
USB stick vanishes from Thunar view and desktop.
Disconnected and reconnected USB stick.
Checked permissions - which were unchanged (below).
Deleted 0 byte version of long file present on USB stick.
Retried copy and paste, with same error part-way.

Log for first attempt from connecting USB to it disappearing detailed below after signature.
Ian

Owner:  ian (ian)
Access: Read & Write
Group: ian
Access: Read only
Others: Read only

Oct  8 12:32:46 linux01 kernel: [  133.998923] usb 1-1: new high-speed USB device number 6 using xhci_hcd
Oct  8 12:32:46 linux01 kernel: [  134.192955] usb 1-1: New USB device found, idVendor=0951, idProduct=1666
Oct  8 12:32:46 linux01 kernel: [  134.192963] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Oct  8 12:32:46 linux01 kernel: [  134.192967] usb 1-1: Product: DataTraveler 3.0
Oct  8 12:32:46 linux01 kernel: [  134.192971] usb 1-1: Manufacturer: Kingston
Oct  8 12:32:46 linux01 kernel: [  134.192974] usb 1-1: SerialNumber: 002618A369C4F051F844241D
Oct  8 12:32:46 linux01 kernel: [  134.193230] usb 1-1: ep 0x81 - rounding interval to 128 microframes, ep desc says 255 microframes
Oct  8 12:32:46 linux01 kernel: [  134.193239] usb 1-1: ep 0x2 - rounding interval to 128 microframes, ep desc says 255 microframes
Oct  8 12:32:46 linux01 mtp-probe: checking bus 1, device 6: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-1"
Oct  8 12:32:46 linux01 mtp-probe: bus: 1, device: 6 was not an MTP device
Oct  8 12:32:46 linux01 kernel: [  134.309823] usb-storage 1-1:1.0: USB Mass Storage device detected
Oct  8 12:32:46 linux01 kernel: [  134.309976] scsi host2: usb-storage 1-1:1.0
Oct  8 12:32:46 linux01 kernel: [  134.310220] usbcore: registered new interface driver usb-storage
Oct  8 12:32:46 linux01 kernel: [  134.322576] usbcore: registered new interface driver uas
Oct  8 12:32:47 linux01 kernel: [  135.308467] scsi 2:0:0:0: Direct-Access     Kingston DataTraveler 3.0      PQ: 0 ANSI: 6
Oct  8 12:32:47 linux01 kernel: [  135.309859] sd 2:0:0:0: Attached scsi generic sg2 type 0
Oct  8 12:32:47 linux01 kernel: [  135.315061] sd 2:0:0:0: [sdb] 30218842 512-byte logical blocks: (15.5 GB/14.4 GiB)
Oct  8 12:32:47 linux01 kernel: [  135.315330] sd 2:0:0:0: [sdb] Write Protect is off
Oct  8 12:32:47 linux01 kernel: [  135.315345] sd 2:0:0:0: [sdb] Mode Sense: 4f 00 00 00
Oct  8 12:32:47 linux01 kernel: [  135.315658] sd 2:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
Oct  8 12:32:47 linux01 kernel: [  135.318484]  sdb: sdb1
Oct  8 12:32:47 linux01 kernel: [  135.319702] sd 2:0:0:0: [sdb] Attached SCSI removable disk
Oct  8 12:32:52 linux01 udisksd[1979]: Mounted /dev/sdb1 at /media/ian/E493-9642 on behalf of uid 1000
Oct  8 12:32:53 linux01 wpa_supplicant[1279]: wlp2s0: Failed to initiate sched scan

Copied two small files (295b and 703.9kB), then copied 387.1Mb of 469.9 Mb before "Error splicing file.  Input/output error.  Do you want to skip it?"

Oct  8 12:33:19 linux01 systemd[1]: Stopping User Manager for UID 108...
Oct  8 12:33:19 linux01 systemd[1500]: Reached target Shutdown.
Oct  8 12:33:19 linux01 systemd[1500]: Stopped target Default.
Oct  8 12:33:19 linux01 systemd[1500]: Starting Exit the Session...
Oct  8 12:33:19 linux01 systemd[1500]: Stopped target Basic System.
Oct  8 12:33:19 linux01 systemd[1500]: Stopped target Timers.
Oct  8 12:33:19 linux01 systemd[1500]: Stopped target Sockets.
Oct  8 12:33:19 linux01 systemd[1500]: Stopped target Paths.
Oct  8 12:33:19 linux01 systemd[1500]: Received SIGRTMIN+24 from PID 2258 (kill).
Oct  8 12:33:19 linux01 systemd[1]: Stopped User Manager for UID 108.
Oct  8 12:33:19 linux01 systemd[1]: Removed slice User Slice of lightdm.
Oct  8 12:33:26 linux01 ntpd[1352]: error resolving pool 0.ubuntu.pool.ntp.org: Temporary failure in name resolution (-3)
Oct  8 12:33:27 linux01 ntpd[1352]: error resolving pool 2.ubuntu.pool.ntp.org: Temporary failure in name resolution (-3)
Oct  8 12:33:29 linux01 ntpd[1352]: error resolving pool 1.ubuntu.pool.ntp.org: Temporary failure in name resolution (-3)
Oct  8 12:33:34 linux01 ntpd[1352]: error resolving pool ntp.ubuntu.com: Temporary failure in name resolution (-3)
Oct  8 12:33:34 linux01 ntpd[1352]: error resolving pool 3.ubuntu.pool.ntp.org: Temporary failure in name resolution (-3)
Oct  8 12:33:48 linux01 wpa_supplicant[1279]: wlp2s0: Failed to initiate sched scan
Oct  8 12:34:30 linux01 ntpd[1352]: error resolving pool 0.ubuntu.pool.ntp.org: Temporary failure in name resolution (-3)
Oct  8 12:34:34 linux01 ntpd[1352]: error resolving pool 2.ubuntu.pool.ntp.org: Temporary failure in name resolution (-3)
Oct  8 12:34:36 linux01 ntpd[1352]: error resolving pool 1.ubuntu.pool.ntp.org: Temporary failure in name resolution (-3)
Oct  8 12:34:41 linux01 ntpd[1352]: error resolving pool ntp.ubuntu.com: Temporary failure in name resolution (-3)
Oct  8 12:34:41 linux01 ntpd[1352]: error resolving pool 3.ubuntu.pool.ntp.org: Temporary failure in name resolution (-3)
Oct  8 12:34:49 linux01 wpa_supplicant[1279]: wlp2s0: Failed to initiate sched scan
Oct  8 12:34:59 linux01 kernel: [  266.988624] usb 1-1: USB disconnect, device number 6
Oct  8 12:34:59 linux01 kernel: [  266.993379] sd 2:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
Oct  8 12:34:59 linux01 kernel: [  266.993394] sd 2:0:0:0: [sdb] tag#0 CDB: Write(10) 2a 00 00 01 2f df 00 00 f0 00
Oct  8 12:34:59 linux01 kernel: [  266.993400] blk_update_request: I/O error, dev sdb, sector 77791
Oct  8 12:34:59 linux01 kernel: [  266.996090] sd 2:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
Oct  8 12:34:59 linux01 kernel: [  266.996101] sd 2:0:0:0: [sdb] tag#0 CDB: Write(10) 2a 00 00 01 30 cf 00 00 f0 00
Oct  8 12:34:59 linux01 kernel: [  266.996107] blk_update_request: I/O error, dev sdb, sector 78031
Oct  8 12:34:59 linux01 udisksd[1979]: Cleaning up mount point /media/ian/E493-9642 (device 8:17 no longer exist)
Oct  8 12:34:59 linux01 kernel: [  267.149194] FAT-fs (sdb1): FAT read failed (blocknr 3662)
Oct  8 12:34:59 linux01 kernel: [  267.149198] ------------[ cut here ]------------
Oct  8 12:34:59 linux01 kernel: [  267.149204] WARNING: CPU: 0 PID: 2279 at /build/linux-Pcn0xK/linux-4.4.0/fs/fs-writeback.c:2113 __mark_inode_dirty+0x293/0x380()
Oct  8 12:34:59 linux01 kernel: [  267.149205] bdi-block not registered
Oct  8 12:34:59 linux01 kernel: [  267.149206] Modules linked in: uas usb_storage rfcomm bnep uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core v4l2_common videodev media arc4 iwlmvm snd_soc_skl snd_soc_skl_ipc snd_hda_ext_core intel_rapl mac80211 snd_soc_sst_ipc x86_pkg_temp_thermal intel_powerclamp snd_soc_sst_dsp coretemp snd_soc_core kvm_intel snd_compress ac97_bus snd_pcm_dmaengine dw_dmac_core snd_hda_codec_hdmi kvm snd_hda_codec_realtek snd_hda_codec_generic btusb btrtl snd_hda_intel snd_hda_codec iwlwifi snd_hda_core snd_hwdep irqbypass cfg80211 snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device mei_me rtsx_pci_ms snd_timer memstick hci_uart snd mei soundcore btbcm btqca shpchp btintel joydev input_leds serio_raw bluetooth intel_lpss_acpi intel_lpss mac_hid acpi_pad ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 xt_hl ip6t_rt nf_conntrack_ipv6 nf_defrag_ipv6 ipt_REJECT nf_reject_ipv4 nf_log_ipv4 nf_log_common xt_LOG xt_limit xt_tcpudp xt_addrtype nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack ip6table_filter ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast nf_nat_ftp nf_nat nf_conntrack_ftp parport_pc ppdev nf_conntrack iptable_filter ip_tables x_tables lp parport autofs4 btrfs xor raid6_pq drbg ansi_cprng algif_skcipher af_alg dm_crypt hid_generic usbhid dm_mirror dm_region_hash dm_log rtsx_pci_sdmmc crct10dif_pclmul i915_bpo crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd intel_ips i2c_algo_bit drm_kms_helper syscopyarea sysfillrect psmouse sysimgblt fb_sys_fops drm r8169 ahci rtsx_pci mii libahci wmi pinctrl_sunrisepoint video pinctrl_intel i2c_hid hid fjes
Oct  8 12:34:59 linux01 kernel: [  267.149274] CPU: 0 PID: 2279 Comm: pool Not tainted 4.4.0-97-generic #120-Ubuntu
Oct  8 12:34:59 linux01 kernel: [  267.149276] Hardware name: Notebook                         W94_95_97JU/W94_95_97JU, BIOS 5.11 03/30/2016
Oct  8 12:34:59 linux01 kernel: [  267.149277]  0000000000000286 b20a51e4f7c60e17 ffff8800641bf770 ffffffff813fabe3
Oct  8 12:34:59 linux01 kernel: [  267.149279]  ffff8800641bf7b8 ffffffff81ce12e0 ffff8800641bf7a8 ffffffff810812e2
Oct  8 12:34:59 linux01 kernel: [  267.149281]  0000000000000000 ffff88015c463050 ffff880159cec348 ffff880159cec3d0
Oct  8 12:34:59 linux01 kernel: [  267.149283] Call Trace:
Oct  8 12:34:59 linux01 kernel: [  267.149287]  [<ffffffff813fabe3>] dump_stack+0x63/0x90
Oct  8 12:34:59 linux01 kernel: [  267.149290]  [<ffffffff810812e2>] warn_slowpath_common+0x82/0xc0
Oct  8 12:34:59 linux01 kernel: [  267.149292]  [<ffffffff8108137c>] warn_slowpath_fmt+0x5c/0x80
Oct  8 12:34:59 linux01 kernel: [  267.149294]  [<ffffffff8123e5f3>] ? locked_inode_to_wb_and_lock_list+0x53/0x100
Oct  8 12:34:59 linux01 kernel: [  267.149296]  [<ffffffff8123f093>] __mark_inode_dirty+0x293/0x380
Oct  8 12:34:59 linux01 kernel: [  267.149300]  [<ffffffff8130553e>] mark_fsinfo_dirty+0x2e/0x30
Oct  8 12:34:59 linux01 kernel: [  267.149302]  [<ffffffff81306307>] fat_alloc_clusters+0x517/0x5c0
Oct  8 12:34:59 linux01 kernel: [  267.149305]  [<ffffffff811ee5ea>] ? kmem_cache_alloc+0x1ca/0x1f0
Oct  8 12:34:59 linux01 kernel: [  267.149307]  [<ffffffff81247731>] ? alloc_buffer_head+0x21/0x60
Oct  8 12:34:59 linux01 kernel: [  267.149309]  [<ffffffff8130773c>] fat_get_block+0x18c/0x200
Oct  8 12:34:59 linux01 kernel: [  267.149311]  [<ffffffff8124965f>] __block_write_begin+0x16f/0x480
Oct  8 12:34:59 linux01 kernel: [  267.149313]  [<ffffffff813075b0>] ? fat_detach+0xd0/0xd0
Oct  8 12:34:59 linux01 kernel: [  267.149316]  [<ffffffff813075b0>] ? fat_detach+0xd0/0xd0
Oct  8 12:34:59 linux01 kernel: [  267.149317]  [<ffffffff812499b6>] block_write_begin+0x46/0x80
Oct  8 12:34:59 linux01 kernel: [  267.149319]  [<ffffffff81249c9b>] cont_write_begin+0x2ab/0x3c0
Oct  8 12:34:59 linux01 kernel: [  267.149321]  [<ffffffff813075b0>] ? fat_detach+0xd0/0xd0
Oct  8 12:34:59 linux01 kernel: [  267.149324]  [<ffffffff81308b54>] fat_write_begin+0x44/0x80
Oct  8 12:34:59 linux01 kernel: [  267.149326]  [<ffffffff813075b0>] ? fat_detach+0xd0/0xd0
Oct  8 12:34:59 linux01 kernel: [  267.149328]  [<ffffffff8118f6ee>] generic_perform_write+0xce/0x1c0
Oct  8 12:34:59 linux01 kernel: [  267.149330]  [<ffffffff81191422>] __generic_file_write_iter+0x1a2/0x1e0
Oct  8 12:34:59 linux01 kernel: [  267.149331]  [<ffffffff81191545>] generic_file_write_iter+0xe5/0x1e0
Oct  8 12:34:59 linux01 kernel: [  267.149334]  [<ffffffff8120f82b>] new_sync_write+0x9b/0xe0
Oct  8 12:34:59 linux01 kernel: [  267.149336]  [<ffffffff8120f896>] __vfs_write+0x26/0x40
Oct  8 12:34:59 linux01 kernel: [  267.149338]  [<ffffffff8120fc2f>] __kernel_write+0x4f/0xf0
Oct  8 12:34:59 linux01 kernel: [  267.149341]  [<ffffffff81241f00>] ? user_page_pipe_buf_steal+0x30/0x30
Oct  8 12:34:59 linux01 kernel: [  267.149343]  [<ffffffff81241f72>] write_pipe_buf+0x72/0xa0
Oct  8 12:34:59 linux01 kernel: [  267.149345]  [<ffffffff8124266e>] __splice_from_pipe+0xfe/0x170
Oct  8 12:34:59 linux01 kernel: [  267.149347]  [<ffffffff81241f00>] ? user_page_pipe_buf_steal+0x30/0x30
Oct  8 12:34:59 linux01 kernel: [  267.149349]  [<ffffffff81243a4e>] splice_from_pipe+0x5e/0x90
Oct  8 12:34:59 linux01 kernel: [  267.149351]  [<ffffffff81243ab9>] default_file_splice_write+0x19/0x30
Oct  8 12:34:59 linux01 kernel: [  267.149354]  [<ffffffff81244049>] SyS_splice+0x329/0x790
Oct  8 12:34:59 linux01 kernel: [  267.149356]  [<ffffffff81103e51>] ? SyS_futex+0x81/0x180
Oct  8 12:34:59 linux01 kernel: [  267.149360]  [<ffffffff818437f2>] entry_SYSCALL_64_fastpath+0x16/0x71
Oct  8 12:34:59 linux01 kernel: [  267.149406] ---[ end trace d7b302c2b2a64c0a ]---
Oct  8 12:34:59 linux01 kernel: [  267.149424] ------------[ cut here ]------------
Oct  8 12:34:59 linux01 kernel: [  267.149427] WARNING: CPU: 0 PID: 2279 at /build/linux-Pcn0xK/linux-4.4.0/fs/fs-writeback.c:2113 __mark_inode_dirty+0x293/0x380()
Oct  8 12:34:59 linux01 kernel: [  267.149428] bdi-block not registered
Oct  8 12:34:59 linux01 kernel: [  267.149429] Modules linked in: uas usb_storage rfcomm bnep uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core v4l2_common videodev media arc4 iwlmvm snd_soc_skl snd_soc_skl_ipc snd_hda_ext_core intel_rapl mac80211 snd_soc_sst_ipc x86_pkg_temp_thermal intel_powerclamp snd_soc_sst_dsp coretemp snd_soc_core kvm_intel snd_compress ac97_bus snd_pcm_dmaengine dw_dmac_core snd_hda_codec_hdmi kvm snd_hda_codec_realtek snd_hda_codec_generic btusb btrtl snd_hda_intel snd_hda_codec iwlwifi snd_hda_core snd_hwdep irqbypass cfg80211 snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device mei_me rtsx_pci_ms snd_timer memstick hci_uart snd mei soundcore btbcm btqca shpchp btintel joydev input_leds serio_raw bluetooth intel_lpss_acpi intel_lpss mac_hid acpi_pad ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 xt_hl ip6t_rt nf_conntrack_ipv6 nf_defrag_ipv6 ipt_REJECT nf_reject_ipv4 nf_log_ipv4 nf_log_common xt_LOG xt_limit xt_tcpudp xt_addrtype nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack ip6table_filter ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast nf_nat_ftp nf_nat nf_conntrack_ftp parport_pc ppdev nf_conntrack iptable_filter ip_tables x_tables lp parport autofs4 btrfs xor raid6_pq drbg ansi_cprng algif_skcipher af_alg dm_crypt hid_generic usbhid dm_mirror dm_region_hash dm_log rtsx_pci_sdmmc crct10dif_pclmul i915_bpo crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd intel_ips i2c_algo_bit drm_kms_helper syscopyarea sysfillrect psmouse sysimgblt fb_sys_fops drm r8169 ahci rtsx_pci mii libahci wmi pinctrl_sunrisepoint video pinctrl_intel i2c_hid hid fjes
Oct  8 12:34:59 linux01 kernel: [  267.149515] CPU: 0 PID: 2279 Comm: pool Tainted: G        W       4.4.0-97-generic #120-Ubuntu
Oct  8 12:34:59 linux01 kernel: [  267.149517] Hardware name: Notebook                         W94_95_97JU/W94_95_97JU, BIOS 5.11 03/30/2016
Oct  8 12:34:59 linux01 kernel: [  267.149518]  0000000000000286 b20a51e4f7c60e17 ffff8800641bfa20 ffffffff813fabe3
Oct  8 12:34:59 linux01 kernel: [  267.149521]  ffff8800641bfa68 ffffffff81ce12e0 ffff8800641bfa58 ffffffff810812e2
Oct  8 12:34:59 linux01 kernel: [  267.149523]  0000000000000000 ffff88015c463050 ffff88014e3f4608 ffff88014e3f4690
Oct  8 12:34:59 linux01 kernel: [  267.149525] Call Trace:
Oct  8 12:34:59 linux01 kernel: [  267.149529]  [<ffffffff813fabe3>] dump_stack+0x63/0x90
Oct  8 12:34:59 linux01 kernel: [  267.149533]  [<ffffffff810812e2>] warn_slowpath_common+0x82/0xc0
Oct  8 12:34:59 linux01 kernel: [  267.149535]  [<ffffffff8108137c>] warn_slowpath_fmt+0x5c/0x80
Oct  8 12:34:59 linux01 kernel: [  267.149539]  [<ffffffff8123e5f3>] ? locked_inode_to_wb_and_lock_list+0x53/0x100
Oct  8 12:34:59 linux01 kernel: [  267.149542]  [<ffffffff8123f093>] __mark_inode_dirty+0x293/0x380
Oct  8 12:34:59 linux01 kernel: [  267.149546]  [<ffffffff813068b3>] fat_truncate_blocks+0x103/0x380
Oct  8 12:34:59 linux01 kernel: [  267.149550]  [<ffffffff811c0704>] ? unmap_mapping_range+0x74/0x130
Oct  8 12:34:59 linux01 kernel: [  267.149554]  [<ffffffff813089bb>] fat_write_failed.isra.13+0x2b/0x30
Oct  8 12:34:59 linux01 kernel: [  267.149557]  [<ffffffff81308b74>] fat_write_begin+0x64/0x80
Oct  8 12:34:59 linux01 kernel: [  267.149560]  [<ffffffff813075b0>] ? fat_detach+0xd0/0xd0
Oct  8 12:34:59 linux01 kernel: [  267.149565]  [<ffffffff8118f6ee>] generic_perform_write+0xce/0x1c0
Oct  8 12:34:59 linux01 kernel: [  267.149568]  [<ffffffff81191422>] __generic_file_write_iter+0x1a2/0x1e0
Oct  8 12:34:59 linux01 kernel: [  267.149571]  [<ffffffff81191545>] generic_file_write_iter+0xe5/0x1e0
Oct  8 12:34:59 linux01 kernel: [  267.149577]  [<ffffffff8120f82b>] new_sync_write+0x9b/0xe0
Oct  8 12:34:59 linux01 kernel: [  267.149580]  [<ffffffff8120f896>] __vfs_write+0x26/0x40
Oct  8 12:34:59 linux01 kernel: [  267.149583]  [<ffffffff8120fc2f>] __kernel_write+0x4f/0xf0
Oct  8 12:34:59 linux01 kernel: [  267.149585]  [<ffffffff81241f00>] ? user_page_pipe_buf_steal+0x30/0x30
Oct  8 12:34:59 linux01 kernel: [  267.149588]  [<ffffffff81241f72>] write_pipe_buf+0x72/0xa0
Oct  8 12:34:59 linux01 kernel: [  267.149590]  [<ffffffff8124266e>] __splice_from_pipe+0xfe/0x170
Oct  8 12:34:59 linux01 kernel: [  267.149593]  [<ffffffff81241f00>] ? user_page_pipe_buf_steal+0x30/0x30
Oct  8 12:34:59 linux01 kernel: [  267.149596]  [<ffffffff81243a4e>] splice_from_pipe+0x5e/0x90
Oct  8 12:34:59 linux01 kernel: [  267.149599]  [<ffffffff81243ab9>] default_file_splice_write+0x19/0x30
Oct  8 12:34:59 linux01 kernel: [  267.149601]  [<ffffffff81244049>] SyS_splice+0x329/0x790
Oct  8 12:34:59 linux01 kernel: [  267.149605]  [<ffffffff81103e51>] ? SyS_futex+0x81/0x180
Oct  8 12:34:59 linux01 kernel: [  267.149609]  [<ffffffff818437f2>] entry_SYSCALL_64_fastpath+0x16/0x71
Oct  8 12:34:59 linux01 kernel: [  267.149611] ---[ end trace d7b302c2b2a64c0b ]---
Oct  8 12:34:59 linux01 kernel: [  267.149662] FAT-fs (sdb1): FAT read failed (blocknr 3290)
Oct  8 12:34:59 linux01 kernel: [  267.149670] FAT-fs (sdb1): unable to read inode block for updating (i_pos 524298)
Oct  8 12:34:59 linux01 kernel: [  267.383565] FAT-fs (sdb1): unable to read boot sector to mark fs as dirty
Oct  8 12:34:59 linux01 kernel: [  267.383571] FAT-fs (sdb1): bread failed in fat_clusters_flush
Oct  8 12:35:37 linux01 ntpd[1352]: error resolving pool 0.ubuntu.pool.ntp.org: Temporary failure in name resolution (-3)
Oct  8 12:35:40 linux01 ntpd[1352]: error resolving pool 2.ubuntu.pool.ntp.org: Temporary failure in name resolution (-3)
Oct  8 12:35:42 linux01 ntpd[1352]: error resolving pool 1.ubuntu.pool.ntp.org: Temporary failure in name resolution (-3)
Oct  8 12:35:46 linux01 ntpd[1352]: error resolving pool ntp.ubuntu.com: Temporary failure in name resolution (-3)
Oct  8 12:35:46 linux01 ntpd[1352]: error resolving pool 3.ubuntu.pool.ntp.org: Temporary failure in name resolution (-3)
Oct  8 12:35:52 linux01 wpa_supplicant[1279]: wlp2s0: Failed to initiate sched scan
Oct  8 12:36:42 linux01 ntpd[1352]: error resolving pool 0.ubuntu.pool.ntp.org: Temporary failure in name resolution (-3)
Oct  8 12:36:45 linux01 ntpd[1352]: error resolving pool 2.ubuntu.pool.ntp.org: Temporary failure in name resolution (-3)
Oct  8 12:36:46 linux01 ntpd[1352]: error resolving pool 1.ubuntu.pool.ntp.org: Temporary failure in name resolution (-3)
Oct  8 12:36:53 linux01 ntpd[1352]: error resolving pool ntp.ubuntu.com: Temporary failure in name resolution (-3)
Oct  8 12:36:53 linux01 ntpd[1352]: error resolving pool 3.ubuntu.pool.ntp.org: Temporary failure in name resolution (-3)
Oct  8 12:36:55 linux01 wpa_supplicant[1279]: wlp2s0: Failed to initiate sched scan

USB stick disappears from file manager (Thunar) view and desktop.
Don't worry about artificial intelligence.  Worry about natural stupidity.  :)
 

Re: Permissions error mounting USB drive
« Reply #4 on: October 08, 2017, 05:25:03 AM »
 

Jerry

  • Linux Lite Creator
  • Administrator
  • Platinum Level Poster
  • *****
  • 8775
    Posts
  • Reputation: 801
  • Linux Lite Member
    • View Profile
    • Linux Lite OS

  • CPU: Intel Core i9-10850K CPU @ 3.60GHz

  • MEMORY: 32Gb

  • VIDEO CARD: nVidia GeForce GTX 1650

  • Kernel: 5.x
Have you tried Menu, Settings, Disks? The Help Manual has a section on formatting disks too.
 

Re: Permissions error mounting USB drive
« Reply #3 on: October 08, 2017, 05:17:16 AM »
 

ian_r_h

  • Merchandise Supporter
  • Forum Regular
  • *****
  • 103
    Posts
  • Reputation: 10
  • Linux Lite Member
    • View Profile
I hope no-one minds me adding my own "replies", but I figure this will be helpful for someone else down the line...

So I have managed to change the permission back to myself (thanks to another thread here) in the terminal:-

sudo chown -R ian: /media/ian/E07F-B980/

But I still don't know how to format it to FAT32 again in gparted, as the option is still greyed out.
Don't worry about artificial intelligence.  Worry about natural stupidity.  :)
 

 

-->
X Close Ad

Linux Lite 6.6 FINAL Released - Support for 22 Languages Added - See Release Announcement Section