Imaging Dual Boot on M.2 SSD

[jamcdonald120]

I am attempting to image a room of 24 identical computers with 512 M.2 SSDs. On one of the machines I have constructed my Image containing Windows 10 Anniversary and Ubuntu 16.4, the boot loader is grub. So far I think I have successfully pulled the image using image type raw, other as operating system, and standard compression, but I have not yet been able to push the image to another machine, when ever I try the other computer complains about the partition table and my image size (on the fog server) gets set to 0Bi (from 400 some GB), but the size on the hard drive remains unchanged (65 GB). What am I doing wrong? and How do I fix it?
Computer Specs https://pcpartpicker.com/list/TK6nyf

[Wayne Workman]

What version of FOG? What’s the model of the 24 computers?

[jamcdonald120]

Fog version 1.3.0-RC-30
the computers are custom build with MSI mother Boards, Intel I7 Processors and Samsung M.2 SSDs

[Wayne Workman]

Found a historical thread (below) that isn’t too old, and what’s said doesn’t surprise me, FOG can’t resize extended partitions, so this could be the problem.

Set the Operating System to “Windows, Other” and set Image Type to “Multiple Partition Image - Single Disk Not Resizable” and set Partition to “Everything” and try to re-upload from a good system.

If you get any errors during the upload, take photographs of them (full screen, well focused, no glare) and post them here.

@Almeida said in Deploy dual boot image W7/Ubuntu:

Hello,

The problem was the extended partition if you have a dual boot.

[jamcdonald120]

@Wayne-Workman I just tried an image with your recommended settings, but it is only getting 1 partition of the drive and reporting a device size of 262.1 GB rather than 512GB, on the previous times I have tried multi-partition not resizeable (with other rather than windows other os) the final was no different

[jamcdonald120]

Thank you for the help, I managed to figure it out, the solution that worked for me was to take the image using type 4 Raw image and other as an OS, resulting file was named Raw.000, renamed to Raw an pushed to other machine and it worked (refused to work with file Raw.000)

[Wayne Workman]

@jamcdonald120 said in Imaging Dual Boot on M.2 SSD:

and reporting a device size of 262.1 GB rather than 512GB,

FOG only reports on size used in the image, not drive size. RAW is the last resort because it takes up so much room and is so slow. Asking @Sebastian-Roth for his input on your dual-booting issue.

[george1421]

@jamcdonald120 said in Imaging Dual Boot on M.2 SSD:

… resulting file was named Raw.000, renamed to Raw an pushed to other machine and it worked (refused to work with file Raw.000)

I find this statement a bit suspicious in nature. Not so much that you said it, but that you had to do it to make it work.

I’m pretty sure the developers are about to go on their Christmas break from coding, but I think the @Developers might want to take a look at the code around the Raw images in the new year. I’ll try to duplicate the condition tomorrow for confirmation with a small 500MB disk. The size of the disk shouldn’t matter on the naming convention used.

[Tom Elliott]

@george1421 Well that was an oversight :(.

Basically, it appears, it’s creating a file based on the image’s name.

@jamcdonald120 I’m assuming your image’s name is actually set to “Raw”?

I’ve found the issue and hopefully it will work as expected.

Please rerun the installer to get the “fixed” inits. Hopefully this will help out (and sorry I missed the raw imaging bug.)

[jamcdonald120]

@Tom-Elliott thanks, we managed to push the image with our work around in time, I can try your fix out soon when we re image the machines