@sebastian-roth I mean the flags you can see in Windows disk manager. I’m guessing they’re filesystem flags? (such as Active, Boot, System, etc)

I think particularily the System flag is interesting.

@jonathan-cool Dynamic or Static? (Dynamic could cause issues, not to mention it’s slow)

You do seem to have a lot of empty space in your virtual environment, but this shouldn’t really impact the deployment process, imo.

Resizable image type should be able to resize it correctly.

@jonathan-cool Makes sense. With 2:1 it will think that the OS partition shouldn’t get resized, so it reads the original size (which is 160GB) which in turn is bigger than the target hard drive.

I am not sure why :1 by itself wouldn’t work though.

Can you try leaving the file empty and see if that helps?

I have Dutch Windows which also doesn’t get have reserved system picked up properly and for me the file is simply empty. Which seems to work alright.

@jonathan-cool Yes, plus some info on the disk would be nice too.

@jonathan-cool Can you share a picture of the device that fails? (please check for plugged in USB sticks, SD cards and such as well)

@sebastian-roth @george1421

Is it possible to read the partition flags of NTFS partitions? I’m assuming the System Reserved partition will always get the same flags (which are different from the Windows partition and any generic data partition). In particular, it will have a System flag.

After some googling, the Metafiles of NTFS might be interesting, particularily $Volume .

I could be wrong, but I believe that you have to use a different format for the NFS urls

nfs://server-address/images/os/etc

instead of

nfs://server-address:/images/os/etc

Confusion coming of course from the fact that when you try to mount a NFS path like so

mount server-address:/images/os/etc /mnt/image

iPXE website seems to confirm this

http://ipxe.org/gsoc/nfs

OP is using Windows 7 as capture image, so Fast Boot won’t be able to cause issues here (since it doesn’t have that option anyway).

I recommend running a chkdsk /f on the Windows partition to start with. Might also want to do a SMART check as some sectors may be defective.

What’s your current FOG version?

Updating FOG also updates the kernels, btw.

You should also note that memdisk requires (quite a bit) more than the ISO size of RAM in order to function. You’ll notice most ISOs people are booting to be 500MB or more often less.

Think of it this way: it basically emulates the optical drive in memory, but after that it still needs to access it, read the files and load the ones it needs into memory (meaning they are there effectively twice), it generally doesn’t load every file to boot from ISO, but it is something to consider.