Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
 Running Out of Disk Space Using Persistence With Mint
#11
continue


Attached Files Thumbnail(s)
               
Reply
#12
continue screenshots


Attached Files Thumbnail(s)
               
Reply
#13
(05-10-2026, 03:29 PM)longpanda Wrote: continue screenshots

SUCCESS! Thank you, @longpanda for all the help! While there are some things I want to learn more about (i.e. break=bottom appears to be something handy to know), as I was looking through all your attachments, one thing immediately stood out. Since I have had a persistence that was working "correctly", I have always booted into the persistence model.One of your screenshots indicated you had to get OUT of persistence for the "ExtendPersistentImg.sh" to work correctly. Sooo, I rebooted and chose to boot without persistence, and ran the ExtendPersistImg.sh command. I got:

Filesystem          Size  Used Avail Use% Mounted on
tmpfs              1.6G  2.1M  1.6G  1% /run
efivarfs            438K  228K  206K  53% /sys/firmware/efi/efivars
/dev/mapper/ventoy  2.9G  2.9G    0 100% /cdrom
/cow                31G  3.4G  26G  12% /
tmpfs              7.7G  4.0K  7.7G  1% /dev/shm
tmpfs              5.0M  8.0K  5.0M  1% /run/lock
tmpfs              7.7G  16K  7.7G  1% /tmp
tmpfs              1.6G  2.6M  1.6G  1% /run/user/1000
mint@mint:~$

COOLNESS! I still want to upgrade to the latest Linux Mint version and upgrade to the latest Ventoy version but, for now, I am happy. Thank you again!

I do have one more question. How do I know when I have exhausted my disk space? I have a 256GB USB 3.0 thumb drive. My initial goal was to have one version of Linux Mint on the drive and have the rest for files/email/etc. I now want to include the Ventoy un-tar'ed and un-zip'ed files (let's call it 50MB). Linux Mint is about 3GB. For simplicity sake, let's be very generous and call it 4GB for Mint and Ventoy. When I initially loaded Ventoy, I did not include any "extra" space. That means I have one 250GB partition (Ventoy) and one 34MB partition (Partition 2 - unknown). I suppose I can keep track myself (just don't ExtendPersistentImg.sh any more than (250-4) 246 GB total). Or, is there a better way (like assuming the ExtendPersistImg.sh script will return failure if I ask for more disk space than available)???
Reply
#14
Your concern makes sense.

I've just updated the ExtendPersistentImg.sh 
script on the official website and added a free space check before the extension process.

Currently, you have a 32GB persistence file. When you run out of free space again, simply run the script once more to extend it by another 32GB (for example).

Once your USB drive is completely full, if you run the script again to try extending by an additional 32GB, it will automatically prompt that there is insufficient free space.


Attached Files Thumbnail(s)
   
Reply
#15
(Yesterday, 01:01 AM)longpanda Wrote: Your concern makes sense.

I've just updated the ExtendPersistentImg.sh 
script on the official website and added a free space check before the extension process.

Currently, you have a 32GB persistence file. When you run out of free space again, simply run the script once more to extend it by another 32GB (for example).

Once your USB drive is completely full, if you run the script again to try extending by an additional 32GB, it will automatically prompt that there is insufficient free space.

Thanks, as always, for the quick response and info.

OK, great. Thanks for adding the additional check, and I'll expect this to be added to version 1.1.13 when it becomes available.
Reply


Forum Jump:


Users browsing this thread: 2 Guest(s)