Inserting Extended partitions - failed
-
This seems to make no sense to me.
Particularly, does the image you have actually contain “extended” partitions?
-
Im not sure. I think this was the image that you had me put a 1 in the partitions fixed size file for the first partition. Is that related?
-
@coop90 I doubt it, but would you be willing to update to the latest RC and reupload and see if all works?
-
I am on 1.3.5 RC 5. I recaptured and redeployed but “Inserting Extended partitions” is still failing. The rest of the deploy process succeeds and windows begins to boot but then fails. Could it be the switch to an ssd?
-
@coop90 Not likely. Typically when the SSD is present and there are issues, the issues are with the recognition/initialization of the disk.
FOG finds the disk, or the image wouldn’t be pushed.
-
It deployed ok to a regular hard drive last week that’s why I am thinking it is the ssd.
-
@coop90 said in Inserting Extended partitions - failed:
thinking
It could always be possible, what make and model of SSD are you using?
If you use a HDD right now, does the image deploy correctly?
-
I am using the mushkin triactor ssd.
I just tested the deploy to a HDD and it worked ok.
-
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>
