Deploying image, "~empty image might cause issues," but it initially shows as 65GB then 0.0 after deploy

[Sebastian Roth]

@geardog said in Deploying image, "~empty image might cause issues," but it initially shows as 65GB then 0.0 after deploy:

The error came in when capturing a 4k sector drive and deploying it to a 512 sector drive.

Thanks for all your posts and the information. We (as in the FOG dev team) have discussed about this and it’s been on the forum as well but so far have not had the time to implement proper methods to move from one to the other. It’s quite complicated to try and convert partition layout (sector numbers) without messing things up. It’s interesting to read that you are trying to move from 4096 to 512 block size. Most people I’d expect to wanna move the other way. Makes it even more complicated to get this right in all cases.

[geardog]

@sebastian-roth

I just happen to be harvesting 1TB drives from workstations for server use. The 250GB drives I picked up for $10 each are adequate for the floor computers.

Thank you for the firm point at cause.