Posts made by rwilsonadvantage

@Sebastian-Roth
HUZZAH!!! A man of Quality!! the image was able to pull once i was able to remove the old partitions. You guys are awesome!!! How do i mark this as solved?

@Sebastian-Roth
Since we aren’t using them, we are “hoping” they aren’t needed. Fingers crossed, last set of updates before the new image pull.

@george1421
So i double checked the source, and it was pulled from a 256 sdd, but in looking at the dis structure, i found 2 “OEM” Partitions that were located at the end of the drive. I have deleted those, and am pulling an image now. I hope that solves the issue. I will keep everyone posted.

@george1421
Ok, quick question, with it “resizable” shouldn’t that correct the issue? The image is only 60gb or so, and the ssd is 250. The source should have been a 256 ssd. but i am pulling to confirm.

@george1421
You are completely correct. I missed that completely. I am attaching both outputs here. I am also attaching the output for the image in fog itself, that way you can see it also.

@george1421

[root@serv-mitch-fog Win10HP]# ls -la
total 44958000
drwxrwxrwx. 2 fogproject root         238 Nov  8 08:52 .
drwxrwxrwx. 5 fogproject root          76 Sep 19 16:11 ..
-rwxrwxrwx. 1 fogproject root           9 Sep 19 15:54 d1.fixed_size_partitions
-rwxrwxrwx. 1 fogproject root     1048576 Nov  8 08:51 d1.mbr
-rwxrwxrwx. 1 fogproject root        1082 Sep 19 15:54 d1.minimum.partitions
-rwxrwxrwx. 1 fogproject root          60 Sep 19 15:54 d1.original.fstypes
-rwxrwxrwx. 1 fogproject root           0 Sep 19 15:54 d1.original.swapuuids
-rwxrwxrwx. 1 fogproject root    31647083 Sep 19 15:54 d1p1.img
-rwxrwxrwx. 1 fogproject root   113433917 Sep 19 15:54 d1p2.img
-rwxrwxrwx. 1 fogproject root 28878471852 Sep 19 16:07 d1p3.img
-rwxrwxrwx. 1 fogproject root   689768015 Sep 19 16:07 d1p4.img
-rwxrwxrwx. 1 fogproject root 16322594957 Sep 19 16:11 d1p5.img
-rwxrwxrwx. 1 fogproject root        1082 Sep 19 15:54 d1.partitions
[root@serv-mitch-fog Win10HP]#

@george1421 the drive is 2.5 Sata SSD. Part number CT250MX500SSD1Z.PK01

@Sebastian-Roth

@Sebastian-Roth image is set to resizable. We have a very basic config, and only have 1 image. I see the error here, but it is confusing because the image works on the other machines, and this machine with another drive. 

I have a system, HP Probook 450 g3, that will image just fine, until i install a new crucial 2.5 250gb ssd. Once we do that, the image process fails at"Restoring Partition Tables (GPT) CMD Tried sgdisk -gl /images(correct image path)/d1.mbr /dev/sda." I have tried other hard drives, and it works great, but once i place a crucial 250 gb drive in the system it fails. I have tried 3 of the crucial drives, and get the same result. I can use larger or smaller normal drives (disk), and they work fine, along with m.2 ssd drives.

Yes i know this is a duplicated post, but as i have an entire batch of systems that i can no longer use until i correct the issue, i figured i would try here.

I have a system, HP Probook 450 g3, that will image just fine, until i install a new crucial 2.5 250gb ssd. Once we do that, the image process fails at"Restoring Partition Tables (GPT) CMD Tried sgdisk -gl /images(correct image path)/d1.mbr /dev/sda." I have tried other hard drives, and it works great, but once i place a crucial 250 gb drive in the system it fails. I have tried 3 of the crucial drives, and get the same result. I can use larger or smaller normal drives (disk), and they work fine, along with m.2 ssd drives.