10-08-2017, 01:29 PM
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.
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. 