I use Gparted.
Partitions have to be unmounted, so booting from the live CD, should give you that.
Right Click on an unmounted partition.
Select check._________________I have found, in trying to help people, that the things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected

@bigpup
This last screenie has nothing to do with the issue I raised initially. That screenie shows an isobooter created tahr-6.0.6 flash drive.

I posted it to make a point about isobooter created flash drives. In case you don't know, for a single iso like tahr-6.0.6, iso booter creates 2 partitions: sdx1 and sdx4. sdx4 holds the individual files that comprise the ISO and sdx1 is the boot partition. The pupsave is saved there just like it would with a flash boot without a directory. I booted and saved a session, hence the pupsave you see in my sde1 (not booed).

The point was that since isobooter places a copy of the original iso in the boot partition (sdx1) and has the individual files that comprise that iso in sdx4 it is a space inefficient system. That's why I asked rcrsn51 if I could delete the iso in the boot partition.

Let's now look at an old style way of creating a multipup - separate directories for each pup containing initrd, vmlinux, its main sfs and zdrive if included. I have been doing this for years.

I had tahr-6.0.5 running on my drive. When I added tahr-6.0.6 and adjusted syslinux.cfg for the addition, I got the error. As I stated in my previous post to you, on a lark, I placed a copy of puppy_tahr_6.0.6.sfs in the root of the boot partition. Inexplicably it worked and continues to do so.

Now, I have puppy_tahr_6.0.6.sfs in the root of the boot partition (/home/) as well as in the tahr-6.0.6.uefi directory in the root (/home/tahr-6.0.6.uefi). That's duplication . It struck me that it was similar to rcrsn51's.

I asked Bill if the duplicate iso could be safely removed. He igmored my post. He now contends that there is no duplcation; that there are symlinks. This last screeenie of sde1 and sde4 shows that they are files, not symlinks. I challenged him to post similar screenies. But there is no need to wait on him.
The screenie here, clearly shows the boot partition of the flash boot created by isobooter for Pelo with 2 ISOs in the /home - stretch-7.0.0a1.iso, and MintPup-Jwm-Icewm-hybrid-26-07-2015.

Hi bigpup
Re system check using GParted>Check :
I did so with both the flash created by ISObooter and the multiple pup (with extra main sfs in root)
Neither gave any critically bad results as far as I can see. But here are screenies for your detective eyes.
gparted_sbtr_details.txt.gz (isobooter)
gparted_multipup_details.exr.gz (multiple pup - no longer booting since placed in Windows system)

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum