I'm the maintainer of the G4L disk imaging program, and have a user that has used the program on other systems with no problems, but now has a number of new Acer Veriton M46500G computers with 250G SSD. He boots the G4L from its linux kernel, and it sees the disks with the partitions fine. He then does an image, but normally, on a new system that has had free space cleared, the image should be about 1/10th the disk size, but he is getting images close the to full size of disk. Not clear if this is some access problem, or security feature. System has Windows 10, and INTEL SSD 256G disk. Could it be an issue with the firmware or some BIOS setting to allow access to disk. Program just uses dd to copy the raw data, and then compress it to make a bare image backup. The created image passes compression programs test, so it is valid, but seems more likely it is getting some random data or something from disk rather than real data that should greatly compress? Long distance communications, so trying things takes time.
Any ideals? Thanks.
[Edited the thread to add model name to the title]