Inserting Extended partitions - failed
-
Please re-run the installer. (You can pull too but it won’t help anything directly.) You should not need to re-capture the original image after this point.
I don’t know if it will make the image bootable though.
-
@Tom-Elliott I reran the installer without pulling and deployed the image again. It said “Inserting extended partitions (minimum) … failed)”
-
@coop90 then I can only guess this image is really captured improperly and possibly from an originally, but corrected for, gpt layout. The corrected for changed this abnormality to a proper MBR layout, though the MBR file you’re currently using is 1 MB in size. This normally happens for Linux style images.
I’m just throwing theories out though. As to what the exact problem is? I haven’t the slightest at this point sorry.
-
@Tom-Elliott Thanks for taking the time to help. In the next two weeks I will try to rebuild the image on a smaller hard drive.
-
@coop90 Sorry I can’t give you a fool-proof “here’s how to fix it”. I still imagine it’s slighly lying with the MBR file itself.
-
As a full informative piece, you’re not setting the ‘1’ in the d1.fixed_size_partitions file are you?
-
@Tom-Elliott I checked disk management on the image and it is set to mbr.
In d1.fixed_size_partitions there is only :3
This is what is in d1.minimum.partitions
-
@coop90 So the d1.minimum.partitions, and I suppose d1.partitions files both have ‘e’ as the the /dev/sda3?
That would lead me to think that the 3rd partition is REALLY odd.
-
@Tom-Elliott Yes. it is ‘e’ in d.partitions also. Let me try deleting that partition and recapturing as a new image.
-
I think that’s going to give you the best bet btw.
-
@Tom-Elliott As usual, you are a genius. It boots fine now! Thank you!
-
@coop90 Glad you got it sorted, sorry it took so long to get to the bottom of it!
