#RESIZE ROOT FROM GPARTED LIVE USB INSTALL#
#RESIZE ROOT FROM GPARTED LIVE USB ISO#
#RESIZE ROOT FROM GPARTED LIVE USB FREE#
#RESIZE ROOT FROM GPARTED LIVE USB WINDOWS#

Or maybe it expects some files to be physically located at some addresses? (originally Root directory start at cluster 2, after resize Root directory start at cluster 969656 )ДЄnd what does that task mean about 'changing geometry'? Why? Didn't it just resized a partition with a previous task? at sectors of previously reserved blocks location. Maybe graphical frontend of gparted just ignored that maybe needed information with the actually data? Because originally Data area starts at byte 16777216 (sector 32768), but after resize Data area starts at byte 14393344 (sector 28112), i.e. I suspect that it could contain some needed information in that reserved blocks (originally there were 3018 of them, after resize there are just 46 of them). Maybe somebody who knows FAT32 internals could help me?

It was able to boot, so uuid does not matter. I also tryed to modify uuid of fat32 partition (using this manual) and checked bootableness. I tryed to change 'MSWIN4.1' on unbootable-after-resise drive to 'MSDOS5.0' and it was still unbootable.ДЄlso I tryed to change original 'MSDOS5.0' on bootable-before-resizing drive to 'MSWIN4.1' and surprise it was still booting. Then I downloaded corresponding bytes with dd, edited them with hex editor and then uploaded them back with dd. So I counted offset of this messages (there are two of them): 0010:00:0C03 in my case. Originally it was 'MSDOS5.0', but gparted and kde partition manager are changing it to 'MSWIN4.1'. I do not know utility that could change OEM ID I thought that bytes from 512 to 2047 could contain something, but they are untouched and contains zeroes, so it is not a reason. Mbr is not a reason, because 446 bytes are untouched and only bytes about partition placement are changed.ДЇiles of bootable drive are untouched at their tree position, so they are not the reason. dev/sdb1: 59 files, 969072/1794374 clustersД«oot flag was still on partition, so this is not cause Root directory start at cluster 969656 (arbitrary size)Дata area starts at byte 14393344 (sector 28112) Some task for changing geometry (maybe this is cause?):Д¬hanging geometry of partition В«/dev/sdb1В»: First sector: 2048, length: 14383104 : DoneДЇirst FAT starts at byte 23552 (sector 46) Successfully resized file system using internal backend functions. Resizing a fat32 file system using internal backend functions. Root directory start at cluster 2 (arbitrary size)Дata area starts at byte 16777216 (sector 32768) Here is log of applying operation of resizing fat 32 partition:Д¬hecking we can access the last sector of the filesystemДЇirst FAT starts at byte 1545216 (sector 3018) How can I determine reason why it becomes unbootable? But I do not want to store 8 Gb image with remaining half just containing empty space. If I clone originaly backed up image to flash drive, it becomes bootable again.

Not unbootable at all, but I can watch black screen with blinking cursor. After resising fat32 partition, live usb becomes unbootable. I did this with kde partition manager and also tried with gparted.

#RESIZE ROOT FROM GPARTED LIVE USB FREE#

Later I decided to cut free space from bootable partition because there was only 3,7 Gb used.

#RESIZE ROOT FROM GPARTED LIVE USB ISO#

And because I do not know utilities which can do correct iso from live usb I decided to make a DD clone of the entire live usb.

#RESIZE ROOT FROM GPARTED LIVE USB WINDOWS#

Windows did not provide an option to create an iso file to be able to create bootable usb when you want. Of cource boot order is set to load from usb first. Under windows I have created a bootable recovery usb flash drive.ДЄfter that I have checked that that bootable drive is working normal. Of course, copy snapshot on some external HDD before wiping/re-partitioning whole hdd.I have a laptop with bios and there is windows installed on it.

#RESIZE ROOT FROM GPARTED LIVE USB INSTALL#

That way you have saved all changes, you already made on MX LinuxДЄfter you create your snapshot, that can be used to install back YOUR version of MX, then either use gparted and if anything goes bad, you use your snapshot to install MX back again or, you simple wipe HDD, re-partition it, as you want, then use your snapshot to install back your system to be exactly as it was at the moment you created snapshot.

I did it few times and never lose any data, but it could happen. Is it possible to make a partition bigger post installation? I dont wanna lose any of the updates I already installed on MX Linux.

Resize root from gparted live usb