08-07-2025, 06:17 AM
According to previous posts, unsupported FileSystems, when being imaged, can only do sector-by-sector imaging since HBS knows nothing of "used sectors"/etc. when confronted with unsupported FileSystems.
So, after imaging (FULL at 7.6gB) only my Ubuntu partition, I logged into my dual-BOOT Ubuntu/Windows System and under Ubuntu I first TRIMmed the ROOT partition then ran an update of my Linux System. Upon completion of that update, I re-logged into my Windows System and, using Hasleo, ran an INCREMENTAL image of that FULL done at the beginning. I expected an image size equal to or larger (due to updates) than the original FULL... mainly 'cause HBS don't know ext<n> FileSystems. Instead I wound up with a 4gB INCREMENTAL image... much smaller than the original FULL. I then ran an additional FULL (following my updates) that resulted in a 9.3gB image.
Looking at my previous paragraph... how is that even possible with no knowledge of "used sectors" in an ext<n> FileSystem?
Inquiring minds really wanna know about this one...
So, after imaging (FULL at 7.6gB) only my Ubuntu partition, I logged into my dual-BOOT Ubuntu/Windows System and under Ubuntu I first TRIMmed the ROOT partition then ran an update of my Linux System. Upon completion of that update, I re-logged into my Windows System and, using Hasleo, ran an INCREMENTAL image of that FULL done at the beginning. I expected an image size equal to or larger (due to updates) than the original FULL... mainly 'cause HBS don't know ext<n> FileSystems. Instead I wound up with a 4gB INCREMENTAL image... much smaller than the original FULL. I then ran an additional FULL (following my updates) that resulted in a 9.3gB image.
Looking at my previous paragraph... how is that even possible with no knowledge of "used sectors" in an ext<n> FileSystem?
Inquiring minds really wanna know about this one...