Deployed image boot loop - black screen & Press Ctrl Alt Delete
-
Disk partitions in Windows:
Output from GDisk -l:
Output from FDisk -l:
Any help greatly appreciated.
-
@TomcatKZN Thanks for the pictures. Although I am sure we have found the issue we still need to figure out what exactly is causing this. I need more information on where those pictures were taken. I’ve tried to replicate this in a test VM but was not successful yet. So I guess my assumptions are wrong.
Please let me know where and when exactly those gdisk and fdisk output pictures were taken. I surely see this is a FOG debug task but was this on a fresh untouched client before capture, after capture or on another machine before / after deployment?
What I am sure is that the partition start positions are moved at some point. And because of that Windows cannot boot. Though I am still not sure if the initial partition layout is crappy or if this is something FOG is causing.
-
@sebastian-roth said in Deployed image boot loop - black screen & Press Ctrl Alt Delete:
@TomcatKZN Thanks for the pictures. Although I am sure we have found the issue we still need to figure out what exactly is causing this. I need more information on where those pictures were taken. I’ve tried to replicate this in a test VM but was not successful yet. So I guess my assumptions are wrong.
Please let me know where and when exactly those gdisk and fdisk output pictures were taken. I surely see this is a FOG debug task but was this on a fresh untouched client before capture, after capture or on another machine before / after deployment?
What I am sure is that the partition start positions are moved at some point. And because of that Windows cannot boot. Though I am still not sure if the initial partition layout is crappy or if this is something FOG is causing.
The Gdisk and FDisk output is from a freshly deployed Client which failed.
The same client from which the image was taken.
The picture from windows is before the capture and deploy.
I will install an untouched disk and generate the same output from before the capture. -
GDisk -PreImage:
FDisk-PreImage:
Does this help identify the problem with capturing this image?
-
I also ran Easus partition manager and posted the output.
Seems the 1st partition is fat16. perhaps thats the problem.
Wonder if I can change it to fat32 if it will still work.
What do you think? -
@TomcatKZN Ok thanks, I think Ich found what’s causing this. Just need a little more time to fix. Will get back to you soon.
-
@sebastian-roth said in Deployed image boot loop - black screen & Press Ctrl Alt Delete:
@TomcatKZN Ok thanks, I think Ich found what’s causing this. Just need a little more time to fix. Will get back to you soon.
Awesome. Much appreciated.
-
@TomcatKZN We have a proposal of a fix ready but I want to discuss this with the other developers before we release the fix. The resizing code is crucial and shouldn’t be messed with. Will let you know as soon as possible.
-
Understood. Thank you.
-
@TomcatKZN Discussing this with the other developers I came to the conclusion that using “Single disk - Resizable” in your case might not be a good thing anyway. You want to have a clean backup of the original state on disk as far as I understand. From that point of view you should just use “Single disk - Multiple partitions” which does not touch the partition layout. The Resizable method does work in many cases but there is some magic involved which you don’t want to rely on for your backing up the original disk state I suppose.
I am not saying that we won’t fix things! But from my point of view you just shouldn’t be using the Resizable Image Type for what you are trying to achieve.
I’d suggest creating a new image definition in the web UI using the “Single disk - Multiple partitions” image type and upload from a fresh untouched system again.
Edit: Moved to bug reports!
-
Okay. You have a point about backing up the original disk.
I’ll give that a bash and check if it works.
