I have an USB stick formatted to FAT so it can be used in a Windows system. Frequently I copy a folder of mp3s to the stick using either Krusader or Dolphin. The folders shows the files have copied, indeed they can be played. Click on the “remove” icon in the device manager and remove stick. Reinsert the stick and the files are missing, the folder is still there but empty. This does not happen with a newly formatted stick.
Suse 12.2 KDE 4.10
Any ideas please?
John F.
On 2013-02-20 16:56, jfarrar wrote:
> Any ideas please?
fsck
–
Cheers / Saludos,
Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)
On Wed 20 Feb 2013 03:56:01 PM CST, jfarrar wrote:
I have an USB stick formatted to FAT so it can be used in a Windows
system. Frequently I copy a folder of mp3s to the stick using either
Krusader or Dolphin. The folders shows the files have copied, indeed
they can be played. Click on the “remove” icon in the device manager
and remove stick. Reinsert the stick and the files are missing, the
folder is still there but empty. This does not happen with a newly
formatted stick.
Suse 12.2 KDE 4.10
Any ideas please?
John F.
Hi
After copying and before unmounting device, open a terminal and run the
command;
sync
Then after unmounting the device and before removing from the usb port,
run the above again.
Does this help?
–
Cheers Malcolm °¿° (Linux Counter #276890)
openSUSE 12.2 (x86_64) Kernel 3.4.28-2.20-desktop
up 1 day 20:41, 3 users, load average: 0.03, 0.04, 0.08
CPU Intel® i5 CPU M520@2.40GHz | GPU Intel® Ironlake Mobile
On Wed 20 Feb 2013 04:08:06 PM CST, Carlos E. R. wrote:
On 2013-02-20 16:56, jfarrar wrote:
> Any ideas please?
fsck
Hi
Rather than just asking the user to run some random command, please
explain yourself, short one liners are pretty useless without some form
of explanation as how does one expect to learn?
–
Cheers Malcolm °¿° (Linux Counter #276890)
openSUSE 12.2 (x86_64) Kernel 3.4.28-2.20-desktop
up 1 day 20:43, 3 users, load average: 0.06, 0.05, 0.07
CPU Intel® i5 CPU M520@2.40GHz | GPU Intel® Ironlake Mobile
Running “sync” as described does not have any affect. I assumed that I needed to change to the /media directory?
Fsck refers to ext2 systems, the stick is FAT.
And another thought, the copy (or move) of the files is much slower when it actually works properly.
Thanks for the help.
This is not normal behaviour
I use 12.2 with kde 4.10 and also have FAT USB pen drives
Some such drives are slow, at least the write to rate is.
Are you sure Dolphin has given the Notification that the transfer is complete.
I do find that it is wise to wait for said Notification to hide before doing ‘Safely Remove’
On 2013-02-20, caf4926 <caf4926@no-mx.forums.opensuse.org> wrote:
> Are you sure Dolphin has given the Notification that the transfer is
> complete.
I know the feeling. Whenever transferring files and folders to/from USB pens using X-based file browsers, I’m never
confident when the transfer is complete and have learnt from bad experiences just simply not to trust the waitbars.
Whenever I’ve performed similar transfers with bash, it’s never failed and so I just stick to that.
Yes the notification pops up and goes down. I can click on one of the files and open it in Amarok and it plays. Close down the files manager and eject the stick in the normal fashion and the mp3s have disappeared.
Weird…
This is something to do with the USB sticks. They are 8Gb formatted to FAT. I have just tried one in an Ubuntu based system with the same results. However, a 2Gb stick, also FAT works perfectly.
Never happened in nautilus. maybe you should try some other file manager like midnight command 
Or that particular stick is faulty
I have a whole bunch of sticks ranging from 512MB > 32 GB (inc. 3 8GB) and no issues
I’ve ordered a couple of Kingston 8Gbs. So I’ll see how they do.
Thanks all for the help.
John F.
On 2013-02-20 17:22, malcolmlewis wrote:
> Hi
> Rather than just asking the user to run some random command, please
> explain yourself, short one liners are pretty useless without some form
> of explanation as how does one expect to learn?
I don’t know the level of experience of the user. Instead of assuming
novices, I assume expertise and that a simple hint is enough.
I’m simply hinting that the filesystem on that stick is corrupted, and
needs to be at least verified.
On 2013-02-20 17:46, jfarrar wrote:
> Fsck refers to ext2 systems, the stick is FAT.
No, fsck refers to any type of filesystem, even FAT. It is a wrapper
which calls the appropriate binary, which in this case would be
‘fsck.vfat’, a symlink to ‘dosfsck’.
You have to make sure the stick is plugged but not mounted, and then run
the checker on it. The man page explains the available options (Malcolm:
to give the exact options needed, I would have to read the man page
myself and speculate on possibilities, then write a long paragraph,
which I don’t know if it is needed).
Alternatively, you can use the equivalent tool in Windows.
–
Cheers / Saludos,
Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)
@robin if we want to to do full filesystem fsck at boot will the actions in the below link suffice?
link
You can’t do full fsck on boot for a device that is not present on boot. And USB sticks rarely are.
For permanently connected disks yes, this still works.
On 2013-02-21 04:36, vazhavandan wrote:
>
> @robin if we want to to do full filesystem fsck at boot will the actions
> in the below link suffice?
> ‘link’ (http://tinyurl.com/a3gnnyf)
The device has to be listed on fstab and the sixth field has to be nonzero.
–
Cheers / Saludos,
Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)
Yes, but please don’t add your USB to fstab to accomplish checking at boot. The system won’t boot properly when the USB device is not connected. And the thread is about USB devices.
On 2013-02-21 15:06, Knurpht wrote:
> Yes, but please don’t add your USB to fstab to accomplish checking at
> boot. The system won’t boot properly when the USB device is not
> connected. And the thread is about USB devices.
Oh, absolutely.
If it fails for any reason, be it device not present, or that there is a
problem with the filesystem, you are dumped into emergency mode, in text
mode, which is confusing for many people. Specially if it is systemd,
because it gives no hints of the cause.
And believe me, handling this is more difficult than reading the
fsck.vfat man page and doing it by hand on a normal system
–
Cheers / Saludos,
Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)
Hmmm, most files copied using Windows 7, so I dunno.