If the files are still present in your USB drive, then just plug in the usb when you are in windows or in linux, and a file-manager window showing the existing files will appear... (ie, pretty normally)
If you want to see the files of the USB while running from the Live USB then, you will need to:
find out what is your USB drive dev directory (ex: /dev/sda1). Try looking with df -h (I'm not sure if the usb drive will appear there while running from a live image...try it)
create a mount-directory: cd && mkdir my_usb
mount the usb device into the mount-directory: sudo mount /dev/sda1 my_usb (replace /dev/sda1 with your usb-dev-directory)
see the usb-drive files by looking inside the directory my_usb
From this moment untill you turnoff the pc, you can access (read and write) the files of your USB which will appear inside the my_usb directory
Tell if you got it working - cheers
It’s not just happening to you :-) The problem is due to how linux works and the default settings that Ubuntu gives you. The file copy tool is reading a chunk of the source file then writing it to the destination, and updates the progress bar each time it finishes a write. However, to speed things up, Linux takes the data that is meant to be written and immediately tells the program that is has been written, while doing the work in the background. Linux allows some percentage of system memory to be used for this purpose, which with the size of memory these days is usually more than the entire file, so a program can think it has written the whole thing when in reality the copy has just begun. But, when a program tries to close the file, Linux makes it wait for the operation to complete. (else the program might try doing something with a half-written file)
You see this the most when writing large files to slow devices, like USB, but it can show up in other situations too and make it look like the computer is locking up.
The thing I do to “fix” the problem is tell Linux to buffer less data. That way an application can’t get so far ahead of the actual progress. This involves changing a kernel parameter, which is a power-user thing that should be done with care. You need to add “vm.dirty_bytes=15000000” to /etc/sysctl.conf
echo vm.dirty_bytes=15000000 | sudo tee -a /etc/sysctl.conf
then reboot.
That sets the buffer size to 15MB, which is a number I picked, and roughly translates to “half a second writing to a fast USB2 device”. You can choose larger (or smaller, but probably not too much smaller) as you like.
The disadvantage of this setting is that high-throughput operations might run slower, like running a bunch of file copies simultaneously. It could also cause a laptop drive to come out of sleep mode more frequently.
Best Answer
So for me it was a simple question of waiting, letting it hang on '0 seconds left' until it eventually finished and changed to 'copied'. Looks like the file manager indicator can get pretty inaccurate and the whole workings were also explained at Gnome, nautilus copy files to USB stops at 100% or near.