Inserting Extended partitions - failed
-
I wonder if anyone else uses these SSDs… maybe one of them can weigh in.
I apologize for my lack of knowledge here, but we use the Samsung 850 Evo SSDs.
So we have determined that the issue is not the image itself as it will deploy to a standard hard drive without issues.
Is the SSD Smaller in size than the hard drive that the image was captured from?
-
@Jaymes-Driver Yes, it is 250gb as opposed to 500gb. The image is captured as single disk resizable.
-
Can you, for craps and giggles, grab a 250 gb HDD or smaller and deploy to it successfully?
I would be curious to see if capturing the image (before it boots) from that 250 gb HDD if it would also have the same issues you are experiencing above with the same 250 gb SSD when deployed again.
(I’m trying to find the fail point so we can work around it and resolve it)
-
Ill try to find a spare one.
-
@Jaymes-Driver Its not the ssd. I tried a 250gb hdd and have the same issue.
-
@coop90 Believe I may have found the issue.
Please repull and capture the image.
I missed a logic check. It was grabbing 63 blocks of 512 bit segments for the mbr style instead of the mbr itself. (It was gathering this too, but was pushing out into the layout of the disk breaking ‘extended partitions’ and possibly boot ability.
-
@coop90 Hmm, seems to be something else then.
I appreciate you taking the time to work with us so that we could try to resolve your issues.
Please follow Tom’s instructions and see if that fixes your problems with this image.
I apologize for the problems you have had, but we will get to the bottom of it hopefully Tom already has
-
@Tom-Elliott I pulled from the dev-branch but it said already up to date. Is there a different branch I should pull from?
-
@coop90 Just rerun the installer to get the updated inits.
-
@Tom-Elliott I reinstalled, captured and tried deploying but windows is failing at startup still. Should I run the legacy fog prep on the machine before capturing?
-
@coop90 FOGPrep is not required anymore, that was something we did many many moons ago before we understood the sysprep process.
You’re welcome to try, but I HIGHLY doubt it will help in this situation.
It seems to me that the image is having trouble scaling to the proper disk size after imaging, particularly to smaller hard drives than the image was captured on.
-
@coop90 What’s the output of:
ls -lhart /images/<yourrelevantrecapturedimagename> -
-
@Tom-Elliott I am capturing again with RC-6 I will let you know how it goes.
-
@Tom-Elliott Inserting extended partitions is still failing on rc-6
-
This leads me to think it’s not a problem with FOG at this point then.
-
@Tom-Elliott It deploys fine to a similar sized hard drive as the one it was captured from. It is the smaller ones that are an issue. The image is not sysprepped if that helps.
-
@coop90 I’m going to test a theory.
-
I’m going to have the “Inserting Extended partitions” use the minimum partitions file instead of the original partitions file. With any luck, using this mechanism will help.
-
@coop90 FOG is agnostic towards the data. Your selections in the GUI help to define if the image is Linux, Mac, Windows, etc. FOG just does a clone of everything present on the drive, and all partitions if you have set the settings appropriately.
FOG Doesn’t care if the image is sysprepped or not, the OS might, but FOG does not. Sometime in the past there was limited understanding toward sysprep and a special tool was made to assist in making images deploy completely from the FOG server. But again this was to satisfy the OS, not FOG. The data was written to the drive, but the OS was not happy with registry values, and etc that were necessary for the OS to boot.
So I don’t think the fact that the image is not sysprepped is the problem, it could be, but it may not. You can attempt to sysprep one, upload it as a new image and try to deploy and report back. However, I am not certain this is where the issue lies.
What perplexes me is that the image deploys fine to a hard drive that is larger in size. But will not deploy to one smaller. This also bothers me. But THIS is exactly the reason I build my images on literally the smallest hard drive I can find.
I realize this doesn’t exactly answer your question, but It helps me get some thoughts out so I can get on the right track of finding a resolution for your issue. It also arms you with information that you may or may not have known.
