I'm relatively new to linux mint(4-5 months in [loving it!]) and I have a 2TB USB 3.0 HDD connected (WD Drive in the photo) I'm trying to shrink the main NTFS Partition on said drive, and it says max and min size are the same, therefore i cant change it if you need more info drop a comment

I use VirtualBox on Windows 10 to run a VM using Ubuntu 16.04.1 LTS. I got the VM from my University with a disk size of 20GB which was way to optimistic ... so I want to resize it to 50GB so I already did 0. (on the host) Make a BackUp ;) 1. (on the host) VBoxManage clonehd "source.vmdk" "clone.vdi" --format vdi 2. (on the host) VBoxManage modifyhd "clone.vdi" --resize 51200 3. (on the host) Downloaded GParted.iso 4. (in the VM) Booted into GParted 5. (in the VM) Expanded The Swap from 2GB to 4GB according to the RAM of the VM I also changed Now I see the following image As you can see obviously the new diskspace got added at the end of the disk. But now I'm facing the problem that I cannot expand the primary partition because the swap partition is "in the way". I neither am able to move the swap-partition. **How can I expand the primary partition and/or move the swap partition to the end of the disk?** The Idea I had was: 1. Delete /dev/sda5 2. Delete /dev/sda2 3. Create new Partition /dev/sda2 with file format linux-swap and the end of the disk 4. Expand /dev/sda1 to use the rest of the disk **Is this the way to go? Will Ubuntu automatically "know" where the swap partition will be after this action?**

how to create boot partition on new nonpartitioned disk? UEFI boot,for Linux, single OS on disk. Preferably using GParted.

[Windows 10 User Installed Kali 2.0] This seems to be the issue of many beginner users of Kali Sana. Installing Kali and either formating their windows partitions not making windows bootable any more or setting up kali in a means that windows partitions aren't easily accessible. I think I have done the 1st of the 2 formatted my drive because I don't see it any where when searching Gparted in kali. If there is a way to recover my windows that would be a blessing. Only directions I have seen that look like they may be useful are the installation of software like rEFind and Fixparts.

I have just opened my GParted application and did a format for /dev/sdc1 to exfat type. But while trying to mount the drive after formatting is completed I am getting the following error. It is external hard disk connected through USB port to the Linux system. user-1@inc:~$ sudo mount /dev/sdc1 mount: /dev/sdc1: can't find in /etc/fstab.

how to copy a HD to another if the CPU is freezing after a few GB ? I had to copy w11 of a friend notebook from a 128GB nvme to a 1TB nvme. I put nvne128gb in a usb adapter and the nvme1TB inside the notebook. The only cost free and granted way to copy the hd was thu linux (that i use everyday). I boot it in a usb liveCD ubuntu 24.04. when I try to copy using gparted or dd, the pc freezes everytime around 15GB :( What is going on?

I had a dual-boot setup on my laptop, with the Windows partition first, then Linux. I decided to delete Windows, so I removed its partition and expanded the Linux partition into its space using GParted. e2image then moved all filesystem data back, beginning at the new start of the partition, and leaving the new empty space at the end. On an SSD (so no performance issues caused by fragmentation), is it really necessary to copy everything? I understand that some parts of the filesystem need to be in particular places (although I don't really understand how the filesystem is structured), but it doesn't seem like the file data itself would have this issue. If it is needed, why? If not, is there a way to disable it (either in GParted or manually with e2image) for faster repartitioning?

I block copied a 50 GB linux partition (almost full, 92% used), from a disk which had started to have some errors to a 666 GB partition of a 750 new hard drive using ddrescue -v -d -r 3 -f /dev/... /dev/... After using grub I was able to boot from the new hard drive without any noticeable problems. While I somehow expected that I might need to resize the result of my copying, now both gparted and df report that my new drive is close to being full, however in different ways: gparted says that 660 GB have been used out of 666 GB available in the partition, and df claims the partition has 41 GB in use out of a total of 47 GB. I don't understand what is wrong, nor how to interpret the vastly different sizes of /dev/sda1/ by gparted and df. I am lost and would appreciate suggestions about how one can recover the use of the space in the new disk which I expected to be more than 90% free, even after putting the contents of the old.

Context: Today I was trying to figure out how to install NixOS live usb with a writeable filesystem (dd-ing the iso results in read-only iso9660 fs). I split my usb into two partitions, one empty and one formatted to ext4. I ran something like dd if=(nixos image).iso of=/dev/sdb1. Then I realized that it probably won't work so I opened gparted to delete everything and try something else. This is where I noticed that something strange is happening: gparted said that my 32GB pendrive has only about 1,4GB (size of first partition). It seems that /dev/sdb is the same thing as /dev/sdb1 now. The disk utility sees the second partition but is unable to remove it or to format the entire drive. My windows machine doesn't see the pendrive at all. I also have tried wipefs /dev/sdb How can I bring my pendrive back to usable state? **Update:** The problem is gone after restarting (now i'm embarrassed that I didn't try this earlier). I can't find a way to reproduce it. One thing I forgot to mention is that I've also mounted the iso as a loop device but I later unmounted it. As you can see on the gnome-disks screenshot a loop device was still there, but I'm not sure if it was pointing to the iso or to the first partition on pendrive. So perhaps the loop mount somehow interfered with accessing /dev/sdb? Just to clarify, I have tried zeroing the entire drive as well as just the first megabyte. This didn't work because /dev/sdb was _not_ pointing to what it should(at least that's my interpretation).

When opening GParted on my Fedora 32 system, I receive the following message: I'm not sure what exactly is going wrong here. The system boots fine. I tried running fsck (via adding file /forcefsck and rebooting) but it didn't change anything. EDIT: Partition table is GPT, that's probably relevant eh.

**Edit** Please note that I fixed the original problem of not booting, but I still can't get it to run X-windows after being prompted for language, input, and display resolution. **Original question** I read about the latest gparted, and saw [this article](http://gparted.org/livehd.php) explaining how to install it on a hard drive. Seemed like it would be a good way to both try it out and have it available, but I've been unable to get it to work. No matter what I've done, I get an immediate reboot. I'm pretty confident that I've followed the directions correctly, and specified the correct disk/partition, etc. Here's what I've tried... **Install from hard disk partition** The partition I used was /dev/sdc8. I mounted the partition as specified (sudo mount /dev/sdc8 /dev), and unzipped the archive into the directory (/mnt). I originally renamed the /live directory to /live-hd, as suggested, but later changed it back, because their directions seemed to sometimes get it wrong, so I didn't want to second-guess possible errors. But I got the same results either way. I added this to /etc/grub.d/40_custom: menuentry "GParted live" { set root=(hd2,8) linux /live/vmlinuz boot=live config union=aufs noswap noprompt vga=788 ip=frommedia live-media-path=/live bootfrom=/dev/sdc8 toram=filesystem.squashfs initrd /live/initrd.img } Then, I ran sudo update-grub2 to update my grub menu. **Boot from gparted iso** Next, I tried copying the iso file to /home/isos, and substituted this in /etc/grub.d/40_custom: menuentry "Gparted live" { set isofile="/home/isos/gparted-live-0.22.0-1-amd64.iso" loopback loop $isofile linux (loop)/live/vmlinuz boot=live config union=aufs noswap noprompt vga=788 ip=frommedia toram=filesystem.squashfs findiso=$isofile initrd (loop)/live/initrd.img } Ran sudo upgrade-grub2, rebooted, and got the same instant reboot. I apologize if this is not the appropriate place to ask about this. I posted on the gparted forums, but the forums looked to be pretty sparse, and I've gotten no responses so far. **Edit** I managed to get the iso file to boot by adding a specifier for which partition to use for booting: loopback loop (hd0,gpt1)$isofile (my boot partition is on a gpt formatted ssd). Unfortunately, I have not been able to get X to run so far. So now my question is how to get X up and running, something I never have trouble with using any distros so far. I am prompted for some input parameters, including display resolution and driver. I've tried various resolutions, both vesa and ATI drivers, and auto, but all result in a black screen with a flashing text cursor in the upper left corner.

I tried to unmount the NTFS partition, it failed, so I umount -l /dev/sda5 and then tried resizing partition of ~200GB to 309.99GB. It resized in an instant, I was instructed to restart system by Gparted. It seems now the partition size was resized to 309.99GB, but the filesystem shows ~200GB with 108GB unallocated. I still can mount and access all files. [These are my partitions](https://i.sstatic.net/gkJUf.png) I Check Partition on gparted, this is the error I get, GParted 0.25.0 --enable-libparted-dmraid --enable-online-resize Libparted 3.2 Check and repair file system (ntfs) on /dev/sda5 00:00:01 ( ERROR ) calibrate /dev/sda5 00:00:00 ( SUCCESS ) path: /dev/sda5 (partition) start: 1128448 end: 651218943 size: 650090496 (309.99 GiB) check file system on /dev/sda5 for errors and (if possible) fix them 00:00:01 ( ERROR ) ntfsresize -i -f -v /dev/sda5 00:00:01 ( ERROR ) ntfsresize v2015.3.14AR.1 (libntfs-3g) Device name : /dev/sda5 NTFS volume version: 3.1 Cluster size : 4096 bytes Current volume size: 214748361216 bytes (214749 MB) Current device size: 332846333952 bytes (332847 MB) Checking for bad sectors ... Checking filesystem consistency ... Inode is corrupt (523): Input/output error Inode is corrupt (1179): Input/output error Inode is corrupt (1624): Input/output error Inode is corrupt (1986): Input/output error Inode is corrupt (2441): Input/output error Inode is corrupt (2454): Input/output error Inode is corrupt (3067): Input/output error Inode is corrupt (3178): Input/output error Inode is corrupt (3667): Input/output error Inode is corrupt (3776): Input/output error Inode is corrupt (6049): Input/output error Inode is corrupt (6751): Input/output error Inode is corrupt (7178): Input/output error Inode is corrupt (7513): Input/output error Inode is corrupt (8199): Input/output error Inode is corrupt (8240): Input/output error Inode is corrupt (8249): Input/output error Inode is corrupt (8259): Input/output error Inode is corrupt (8748): Input/output error Inode is corrupt (8996): Input/output error Inode is corrupt (10241): Input/output error Inode is corrupt (11164): Input/output error Inode is corrupt (11392): Input/output error 100.00 percent completed Accounting clusters ... Cluster accounting failed at 9213941 (0x8c97f5): extra cluster in $Bitmap Cluster accounting failed at 12913555 (0xc50b93): extra cluster in $Bitmap Cluster accounting failed at 12913556 (0xc50b94): extra cluster in $Bitmap Cluster accounting failed at 12997529 (0xc65399): extra cluster in $Bitmap Cluster accounting failed at 14930776 (0xe3d358): extra cluster in $Bitmap Cluster accounting failed at 18002283 (0x112b16b): extra cluster in $Bitmap Cluster accounting failed at 18006376 (0x112c168): extra cluster in $Bitmap Cluster accounting failed at 18057343 (0x113887f): extra cluster in $Bitmap Cluster accounting failed at 18057344 (0x1138880): extra cluster in $Bitmap Cluster accounting failed at 20102360 (0x132bcd8): extra cluster in $Bitmap Cluster accounting failed at 20336434 (0x1364f32): extra cluster in $Bitmap Cluster accounting failed at 20342801 (0x1366811): extra cluster in $Bitmap Cluster accounting failed at 20363408 (0x136b890): extra cluster in $Bitmap Cluster accounting failed at 22761869 (0x15b518d): extra cluster in $Bitmap Cluster accounting failed at 23186158 (0x161caee): extra cluster in $Bitmap Cluster accounting failed at 23190248 (0x161dae8): extra cluster in $Bitmap Cluster accounting failed at 23229588 (0x1627494): extra cluster in $Bitmap Cluster accounting failed at 23286726 (0x16353c6): extra cluster in $Bitmap Cluster accounting failed at 25225024 (0x180e740): extra cluster in $Bitmap Cluster accounting failed at 25229120 (0x180f740): extra cluster in $Bitmap Cluster accounting failed at 25331016 (0x1828548): extra cluster in $Bitmap Cluster accounting failed at 25331017 (0x1828549): extra cluster in $Bitmap Cluster accounting failed at 26032472 (0x18d3958): extra cluster in $Bitmap Cluster accounting failed at 26032473 (0x18d3959): extra cluster in $Bitmap Cluster accounting failed at 26032474 (0x18d395a): extra cluster in $Bitmap Cluster accounting failed at 26032475 (0x18d395b): extra cluster in $Bitmap Cluster accounting failed at 26032476 (0x18d395c): extra cluster in $Bitmap Cluster accounting failed at 26872264 (0x19a09c8): extra cluster in $Bitmap Cluster accounting failed at 31681239 (0x1e36ad7): extra cluster in $Bitmap Cluster accounting failed at 31869833 (0x1e64b89): extra cluster in $Bitmap Cluster accounting failed at 31869834 (0x1e64b8a): extra cluster in $Bitmap Cluster accounting failed at 31890301 (0x1e69b7d): extra cluster in $Bitmap Cluster accounting failed at 33387641 (0x1fd7479): extra cluster in $Bitmap Cluster accounting failed at 33387642 (0x1fd747a): extra cluster in $Bitmap Cluster accounting failed at 33387643 (0x1fd747b): extra cluster in $Bitmap Cluster accounting failed at 33387644 (0x1fd747c): extra cluster in $Bitmap Cluster accounting failed at 34055504 (0x207a550): extra cluster in $Bitmap Cluster accounting failed at 34059600 (0x207b550): extra cluster in $Bitmap Cluster accounting failed at 34171512 (0x2096a78): extra cluster in $Bitmap Cluster accounting failed at 35942016 (0x2246e80): extra cluster in $Bitmap Cluster accounting failed at 35946112 (0x2247e80): extra cluster in $Bitmap Cluster accounting failed at 36806769 (0x231a071): extra cluster in $Bitmap Cluster accounting failed at 37213527 (0x237d557): extra cluster in $Bitmap Cluster accounting failed at 37217624 (0x237e558): extra cluster in $Bitmap Cluster accounting failed at 37245163 (0x23850eb): extra cluster in $Bitmap Cluster accounting failed at 38389268 (0x249c614): extra cluster in $Bitmap Cluster accounting failed at 39450765 (0x259f88d): extra cluster in $Bitmap Cluster accounting failed at 39454856 (0x25a0888): extra cluster in $Bitmap Cluster accounting failed at 39497605 (0x25aaf85): extra cluster in $Bitmap Cluster accounting failed at 39497606 (0x25aaf86): extra cluster in $Bitmap Cluster accounting failed at 41476236 (0x278e08c): extra cluster in $Bitmap Cluster accounting failed at 41480688 (0x278f1f0): extra cluster in $Bitmap Cluster accounting failed at 41622533 (0x27b1c05): extra cluster in $Bitmap Cluster accounting failed at 41626624 (0x27b2c00): extra cluster in $Bitmap Cluster accounting failed at 41653232 (0x27b93f0): extra cluster in $Bitmap Cluster accounting failed at 42148141 (0x283212d): extra cluster in $Bitmap Cluster accounting failed at 43912656 (0x29e0dd0): extra cluster in $Bitmap Cluster accounting failed at 47597952 (0x2d64980): extra cluster in $Bitmap Cluster accounting failed at 47602048 (0x2d65980): extra cluster in $Bitmap Cluster accounting failed at 47610240 (0x2d67980): extra cluster in $Bitmap Cluster accounting failed at 47774080 (0x2d8f980): extra cluster in $Bitmap Cluster accounting failed at 47778176 (0x2d90980): extra cluster in $Bitmap Cluster accounting failed at 47786368 (0x2d92980): extra cluster in $Bitmap Cluster accounting failed at 47839879 (0x2d9fa87): extra cluster in $Bitmap Cluster accounting failed at 47843976 (0x2da0a88): extra cluster in $Bitmap Cluster accounting failed at 47852168 (0x2da2a88): extra cluster in $Bitmap Cluster accounting failed at 47884936 (0x2daaa88): extra cluster in $Bitmap Cluster accounting failed at 47889032 (0x2daba88): extra cluster in $Bitmap Cluster accounting failed at 47897224 (0x2dada88): extra cluster in $Bitmap Cluster accounting failed at 48389360 (0x2e25cf0): extra cluster in $Bitmap Cluster accounting failed at 48389361 (0x2e25cf1): extra cluster in $Bitmap Cluster accounting failed at 48389362 (0x2e25cf2): extra cluster in $Bitmap Cluster accounting failed at 48389363 (0x2e25cf3): extra cluster in $Bitmap Cluster accounting failed at 48389364 (0x2e25cf4): extra cluster in $Bitmap Cluster accounting failed at 48389365 (0x2e25cf5): extra cluster in $Bitmap Cluster accounting failed at 48389366 (0x2e25cf6): extra cluster in $Bitmap Cluster accounting failed at 48389367 (0x2e25cf7): extra cluster in $Bitmap Cluster accounting failed at 48389368 (0x2e25cf8): extra cluster in $Bitmap Cluster accounting failed at 48389369 (0x2e25cf9): extra cluster in $Bitmap Cluster accounting failed at 48389370 (0x2e25cfa): extra cluster in $Bitmap Cluster accounting failed at 48415965 (0x2e2c4dd): extra cluster in $Bitmap Cluster accounting failed at 49827041 (0x2f84ce1): extra cluster in $Bitmap Cluster accounting failed at 49827042 (0x2f84ce2): extra cluster in $Bitmap Cluster accounting failed at 49827043 (0x2f84ce3): extra cluster in $Bitmap Cluster accounting failed at 49827044 (0x2f84ce4): extra cluster in $Bitmap Cluster accounting failed at 49827045 (0x2f84ce5): extra cluster in $Bitmap Cluster accounting failed at 49827046 (0x2f84ce6): extra cluster in $Bitmap Cluster accounting failed at 49827047 (0x2f84ce7): extra cluster in $Bitmap Cluster accounting failed at 50553627 (0x303631b): extra cluster in $Bitmap Cluster accounting failed at 50764942 (0x3069c8e): extra cluster in $Bitmap Cluster accounting failed at 50811033 (0x3075099): extra cluster in $Bitmap Cluster accounting failed at 50832504 (0x307a478): extra cluster in $Bitmap Cluster accounting failed at 50836600 (0x307b478): extra cluster in $Bitmap Filesystem check failed! Totally 93 cluster accounting mismatches. ERROR: NTFS is inconsistent. Run chkdsk /f on Windows then reboot it TWICE! The usage of the /f parameter is very IMPORTANT! No modification was and will be made to NTFS by this software until it gets repaired. ======================================== If I backup all files on that disk and delete to create new partition, will it go corrupt? PS. I don't have access to Windows

I'm attempting to increase the size of my Ubuntu root drive. It was suggested to create a live USB of GParted to merge the free space I've created into the root drive. I created said USB, but when I go through the options (the first GParted live option, not touching keymaps, language, and video option), I see a screen on which there are some very fast messages about something nvidia not loading, and some other files I can't identify. Then I get to a view explaining it's Debian and the Debian disclaimer, and then nothing. It hangs on said view. I can hit keys and I can see them appear under the messaging, but otherwise I'm stuck.

I have a Dell Inspiron 5523, which has two drives. One is an HDD (call it sda) and one an SSD (call it sdb). My system is dual boot UEFI with a large part of it being Windows 8 (around 332GB) and a the rest Linux Mint (72GB). My system had a swap space on sdb and on sda I have two partitions: sda9 has all the system files and sda10 has the home folder files. Recently, I wanted to pass some space from sda9 to sda10 because the first was set up with 60GB and the second with only 7.7GB. So I used gparted live CD and moved 30 GB from sda9 to sda10. After the procedure finished with no problem, when rebooting again and choosing the Linux Mint Cinammon option, I got a kernel panic printing the following: Kernel panic - not syncing: Attempted to kill init! exitcode:0x00007f00 CPU: 2 PID: 1 Comm: sh Not tainted 3.16.0-38-generic #52~14.04.1-Ubuntu Call Trace: dump_stack +0x45/0x56 panic+0xc8/0x1fc do_exit+0xa57/0xa60 do_group_exit+0x3f/0xa0 SyS_exit_group+0x14/0x20 System_call_fastpath+0x1a/0x1f Kernel Offset: 0x0 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff) drm_kms_helper: panic ocurred, switching back to text console I have tried to fix grub with grub repair but after successfully doing that I've seen no change (the error stays the same). When trying to boot manually following these instructions , I get the following error: Targeted filesystem doesn't have requested /sbin/init. /bin/sh: 0: can't access tty: Job control turned off # Note that when I write ls on the GRUB command line, I get partitions in the form of (hd0,gpt9) -> sda9

mint@mint ~ $ sudo parted -l
Model: ATA ST500LT012-9WS14 (scsi)
Disk /dev/sda: 500GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Number  Start   End     Size    File system  Name                          Flags
 1      1049kB  525MB   524MB   fat32        EFI system partition          boot
 2      525MB   567MB   41.9MB  fat32        Basic data partition          hidden
 3      567MB   701MB   134MB                Microsoft reserved partition  msftres
 4      701MB   1226MB  524MB   ntfs         Basic data partition          hidden, diag
 5      1226MB  395GB   394GB   ntfs         Basic data partition          msftdata
 8      395GB   395GB   1049kB  fat32                                      boot
 9      395GB   421GB   26.0GB  ext4                                       boot
10      421GB   487GB   65.3GB  ext4
 6      487GB   487GB   473MB   ntfs                                       hidden, diag
 7      487GB   500GB   13.0GB  ntfs         Microsoft recovery partition  hidden, diag

Model: ATA LITEONIT LMT-32L (scsi)
Disk /dev/sdb: 32.0GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number  Start   End     Size    File system     Name                  Flags
 1      1049kB  8589MB  8588MB                  Basic data partition
 2      8589MB  9613MB  1024MB  linux-swap(v1)
 3      9614MB  22.1GB  12.5GB  fat32                                 msftdata
Warning: Unable to open /dev/sr0 read-write (Read-only file system).  /dev/sr0
has been opened read-only.
Error: Can't have a partition outside the disk!

When I use GParted to do some complicated partition and file system manipulation it gives the option to see the details of what steps it took. But this does not give all the details of what underlying commands GParted used. Is it possible to get a log or debug type of output from GParted so I can see exactly all the commands it used to do whatever I asked it to do? The reason is because I want to understand exactly what GParted does to do various manipulations on my btrfs file system AND I want to put these commands in to a script for use elsewhere. Maybe I could run GParted in a debugger and step through while it is for instance shrinking a filesystem/partition? The GParted online forum has closed so I don't know where else to ask this? Flex

Yeah I know I messed up. Just asking if there is a slight chance of recovering data. I have an external SSD for backup, 1TB. Because some time ago I had some windows stuff, it had half ntfs and half exfat. The exfat was full, so I decided to get rid of the windows partition. I wanted, ideally, to finally get at a single ext4 partition of the whole disk. I fired up gparted, first deleted the windows partition and then tried to make the data partition bigger. Somehow that was not working, it was moving the whole partition,but not resizing it. I assume exfat doesn't support that. Then I fatally saw the "Format to" command. I had a momentary loss of awareness, I guess. For some reason I concluded this to mean it would convert the data partition to ext4. So I hit apply. It took me a couple of seconds to realize what was going on...I hit cancel but I guess the damage is complete nonetheless. Is there any chance that I can recover the data? Currently the partition doesn't even mount, surely because I interrupted the operations after starting.

I keep having issues due to my boot drive running out of space. It fills up as soon as I try to sort out packages with apt-get upgrade, or if for any other reason dependencies try to be resolved or similar. And when I clear it out often I break something I'm working on. So as it has inevitably filled up again causing me issues I want to give it some more space. GParted is showing my lvm partition as having only 44MiB of unused space. df shows I'm only using 33% of the total space. Is there any way I can re-organise this partition so that I can free up some space to give to /boot? If not, should I grab another drive and extend the boot partition? ll /boot

**My objective:** create imaging resource on bootable USB drive (256 GB) which will contain finalized laptop configuration. This is to say, I want to boot from the flash drive and use the same flash drive to store the image created by clonezilla and as needed, to restore the image at a later date. **My understanding** Limited. I've used bootable optical media for both clonezilla and gparted, as well as bootable Linux Live CD media, but I'm not a qualified *nix operator. My capabilities are akin to a code kitty(?) / kiddie in that I copy others' work in order to accomplish my occasional *nix objectives, often using Ubuntu. **What I've searched and found** A number of sites providing tutorials/guidance to create dual (or multi-) boot USB drives using Windows utilities (my choice at this stage). I've also found the source .ISO files for both clonezilla and gparted. I've found this answer , which appeared when I created the subject line but it doesn't appear to solve the objective. **Restrictions** One of the laptops does not have an optical drive. I'd prefer to have both machines to use a bootable flash drive for ease of storage. I'm aiming for a minimum *nix install on the flash drive, to allow greater storage for the created image file. The image file will be of the entire drive, all partitions, as the laptops contain multiple partitions which support manufacturer's nuances (Dell Alienware). I'd like to avoid having to boot from one flash drive and store the image file to a second flash drive, simply to avoid the creation of three drives (one boot, two image), but as a last resort, that's acceptable. It is also the route that I can travel without additional support from SE, but the challenge of learning something new vanishes. **Miscellaneous thoughts** If such a solution involves a bootable drive that contains both clonezilla and gparted, I'd find that acceptable, especially as it would provide greater capacity remaining for the image file. My current approach of creating a multi-boot flash drive would eat up twice as much as I'd expect would be necessary. I'm not averse to creating a Live boot drive that can be stripped down to a minimum of the two utilities with no GUI if a tutorial could be found to facilitate such a creation. **What I don't know** When creating the configurations suggested above, will the process use a minimum partition size on the drive, allowing the remaining space for image storage? Adjunct to that, will I have to manually create the unused space for that purpose? Finally, is this a practical approach? **Adjusted objective** Let's say that I can do without the gparted aspect of this project. This means that I can use the canned utilities for Windows to create a bootable USB for clonezilla. I'm comfortable using that program. Now the focus is how to ensure that I can use the minimum flash drive space for this bootable portion and to have the maximum space for the image file. What options do I have now?

Before I describe the problem, I'd like to specify that I'm not confused about the size of the partitions (they haven't been extended yet, so of course they haven't grown) but the size of the actual device GParted sees. I had a vdi file with ArchLinux installed. The size was 8GB. I extended this to 20GB, which I can confirm in the VirtualBox GUI on my host. However, after having loaded the GParted live cd into the VM and booting into it, it says that /dev/sda is an 8GB device. It won't let me resize anything because it doesn't think the drive actually got any bigger. Is there something else I should be doing?

I used gparted to resize a partition successfully, but it does not allow me to shrink it as much as I would actually like. I think it's because of the _Minimum size_. Is there a possibility to reduce the _Minimum size_ value to shrink the partition further than currently allowed? @Ferrybig: @oldfred: sudo parted -L @Tom Yan: It says: Failed to find physical volume "/dev/nvme0n1p3". Correct: I have LVM on LUKS. But I managed to reduce to Minimum size. You write: You might need to shrink the PV.... Can you provide a link or explain in detail. Thanks a lot