Moderator: Forum moderators
@Jafadmin
I can see your point.
But this happens again when performing the tasks in Gparted, like deleting partition, creating partition table, formatting the partition etc.
That way it had destroyed two USB flash drives.
Both were bought new shortly before using them.
AND:
As I mentioned before, all this doesn't happen in my Tahr Puppy (which is a remastered version of 6.0.2).
My Music:
https://soundcloud.com/user-633698367
Using my own build of Bionic64
The far-left is as fascist as the far-right is!
In general all you need to do is plug in the usb drive, then use Gparted and wait for the strange behaviour to show up, then using a terminal enter the following command:
dmesg > /root/dmesg.txt
The tail end of that dmesg log file may contain some information regarding errors that triggered the mount/unmount behaviour - and will probably also contain a whole lot of earlier messages relating to events before plugging in the usb drive.
Sometimes - if there are many, many errors with the usb drive - then the whole dmesg log may be full with those errors and other important info may be pushed out. In that case you may want to run dmesg before the drive is plugged in also, and maybe run it again during the whole icon flashing saga just to trap all the circumstances.
But it is most likely that there will not be so may errors that the log overfills.
On some puppies you see dmesg errors from the udev utility regarding automatic rules that are actioned as soon as a usb drive becomes visible. Some are normal but maybe some are interfering with gparted.
But this happens again when performing the tasks in Gparted, like deleting partition, creating partition table, formatting the partition etc.
That way it had destroyed two USB flash drives.
The USB drives are not destroyed.
You just need to set them up in a fully correctly working (for you) Gparted.
Use the same (you say) destroyed USB drives.
Do you understand what I am asking you to do in my earlier posts?
You need to try this using Fossapup64 9.5
One specific Puppy version giving you this issue.
We need to troubleshoot it to find the answer to solve this.
taersh,
Is Gparted messing up when only making a fat format or any format???
The things you do not tell us, are usually the clue to fixing the problem.
When I was a kid, I wanted to be older.
This is not what I expected 
Jafadmin,
I think we are basically saying the same thing about the desktop drive icons flashing when Gparted is being used.
You did state it better than I did.
However, earlier versions of Puppy had something that kept the desktop drive icons from doing this flashing effect.
What I am trying to do is figure out why Gparted is not making good working USB drive setups.
The things you do not tell us, are usually the clue to fixing the problem.
When I was a kid, I wanted to be older.
This is not what I expected
Do you understand what I am asking you to do in my earlier posts?
Is Gparted messing up when only making a fat format or any format???
Look here: viewtopic.php?p=31312#p31312
My Music:
https://soundcloud.com/user-633698367
Using my own build of Bionic64
The far-left is as fascist as the far-right is!
Just for grins, forget about the GPartEd gui and try using the command line version, 'parted' instead. Does it still mess up the partitioning and formatting?
(This can help us figure out where it is broke.)
Command line version is much too complicated, if one's not used to it.
I am not used to it! 
My Music:
https://soundcloud.com/user-633698367
Using my own build of Bionic64
The far-left is as fascist as the far-right is!
