Posts made by obzen

FWIW the system in question is a Dell Wyse 5070 with nvme. It appears that this is so far the problem child, as i have successfully imaged 3 other systems with both spinning disks, ssds and nvme.

@sebastian-roth I thought I followed your instructions correctly by checking the debug option before scheduling the task and iterating through the tasks with ENTER key Is there something I am missing as to how to get the capture of it correctly?

@sebastian-roth said in Partition is too big for the for the disk.:

I think I posted [previously a complete error photo of the error found here.
Though the image says its 65GB i do believe its shrunk because my over all disk space on my fog box is ~100GB which contains two of these “65GB” images. Th biggest file in the image dir is 16gb, d1p3 as seen from the screenshot below.

[iiliev@fog  windows_10_pro_64bit]$ ls -ltrah
total 16G
-rwxrwxrwx. 1 root       root  678 Aug 18 15:06 d1.partitions
-rwxrwxrwx. 1 root       root    0 Aug 18 15:06 d1.original.swapuuids
-rwxrwxrwx. 1 root       root   15 Aug 18 15:06 d1.original.fstypes
-rwxrwxrwx. 1 root       root    6 Aug 18 15:06 d1.fixed_size_partitions
-rwxrwxrwx. 1 root       root  678 Aug 18 15:06 d1.shrunken.partitions
-rwxrwxrwx. 1 root       root 1.0M Aug 18 15:06 d1.mbr
-rwxrwxrwx. 1 root       root  678 Aug 18 15:06 d1.minimum.partitions
-rwxrwxrwx. 1 root       root 9.6M Aug 18 15:06 d1p1.img
-rwxrwxrwx. 1 root       root  773 Aug 18 15:06 d1p2.img
-rwxrwxrwx. 1 root       root  16G Aug 18 15:14 d1p3.img***

Perhaps it seems like there is a disconnect between the GUI (image shown as 65GB) and the actual footprint on the command line.

I did a fog debug you can see the result of it failing here.

Thanks!

@sebastian-roth hi sebastian

take a look below:

[root@fog  windows_10_pro_64bit]# cat d1.partitions
label: gpt
label-id: 0022D61A-2393-4A81-AC68-71D0B3C98212
device: /dev/sda
unit: sectors
first-lba: 34
last-lba: 136314846
sector-size: 512

/dev/sda1 : start=        2048, size=      204800, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=E300D277-3B87-4F46-9E79-340C2B01EED7, name="EFI system partition", attrs="GUID:63"
/dev/sda2 : start=      206848, size=       32768, type=E3C9E316-0B5C-4DB8-817D-F92DF00215AE, uuid=89626C7E-1E8C-41D1-9923-A493121C56E4, name="Microsoft reserved partition", attrs="GUID:63"
/dev/sda3 : start=      239616, size=   136072863, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=444C017D-4B5E-4919-8557-BC2102A054A8, name="Basic data partition"

[root@fog  windows_10_pro_64bit]# cat d1.shrunken.partitions
label: gpt
label-id: 0022D61A-2393-4A81-AC68-71D0B3C98212
device: /dev/sda
unit: sectors
first-lba: 34
last-lba: 136314846
sector-size: 512

/dev/sda1 : start=        2048, size=      204800, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=E300D277-3B87-4F46-9E79-340C2B01EED7, name="EFI system partition", attrs="GUID:63"
/dev/sda2 : start=      206848, size=       32768, type=E3C9E316-0B5C-4DB8-817D-F92DF00215AE, uuid=89626C7E-1E8C-41D1-9923-A493121C56E4, name="Microsoft reserved partition", attrs="GUID:63"
/dev/sda3 : start=      239616, size=   136072863, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=444C017D-4B5E-4919-8557-BC2102A054A8, name="Basic data partition"

[root@fog  windows_10_pro_64bit]# cat d1.minimum.partitions
label: gpt
label-id: 0022D61A-2393-4A81-AC68-71D0B3C98212
device: /dev/sda
unit: sectors
first-lba: 34
last-lba: 136314846
sector-size: 512

/dev/sda1 : start=        2048, size=      204800, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=E300D277-3B87-4F46-9E79-340C2B01EED7, name="EFI system partition", attrs="GUID:63"
/dev/sda2 : start=      206848, size=       32768, type=E3C9E316-0B5C-4DB8-817D-F92DF00215AE, uuid=89626C7E-1E8C-41D1-9923-A493121C56E4, name="Microsoft reserved partition", attrs="GUID:63"
/dev/sda3 : start=      239616, size=   136072863, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=444C017D-4B5E-4919-8557-BC2102A054A8, name="Basic data partition"

thanks

@george1421 thanks for the reply, the largest .img file is 16gb

[root@fog  windows_10_pro_64bit]# ls -ltrh
total 16G
-rwxrwxrwx. 1 root root  678 Aug 18 15:06 d1.partitions
-rwxrwxrwx. 1 root root    0 Aug 18 15:06 d1.original.swapuuids
-rwxrwxrwx. 1 root root   15 Aug 18 15:06 d1.original.fstypes
-rwxrwxrwx. 1 root root    6 Aug 18 15:06 d1.fixed_size_partitions
-rwxrwxrwx. 1 root root  678 Aug 18 15:06 d1.shrunken.partitions
-rwxrwxrwx. 1 root root 1.0M Aug 18 15:06 d1.mbr
-rwxrwxrwx. 1 root root  678 Aug 18 15:06 d1.minimum.partitions
-rwxrwxrwx. 1 root root 9.6M Aug 18 15:06 d1p1.img
-rwxrwxrwx. 1 root root  773 Aug 18 15:06 d1p2.img
-rwxrwxrwx. 1 root root  16G Aug 18 15:14 d1p3.img

[root@fog  windows_10_pro_64bit]# cat d1.minimum.partitions 
label: gpt
label-id: 0022D61A-2393-4A81-AC68-71D0B3C98212
device: /dev/sda
unit: sectors
first-lba: 34
last-lba: 136314846
sector-size: 512

/dev/sda1 : start=        2048, size=      204800, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=E300D277-3B87-4F46-9E79-340C2B01EED7, name="EFI system partition", attrs="GUID:63"
/dev/sda2 : start=      206848, size=       32768, type=E3C9E316-0B5C-4DB8-817D-F92DF00215AE, uuid=89626C7E-1E8C-41D1-9923-A493121C56E4, name="Microsoft reserved partition", attrs="GUID:63"
/dev/sda3 : start=      239616, size=   136072863, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=444C017D-4B5E-4919-8557-BC2102A054A8, name="Basic data partition"

Re pulled image but that didnt help. FWIW the target system has an NVMe drive.

thoughts?

I installed 1.5.9.158 from dev-branch, and tried to deploy with bootfile snponly.efi to the target but same issue persists. I did not recapture the image thought, should i do this before trying to deploy again?

@george1421 Hi george, I will update the system using the link and retry the operation. to answer your first question, the capture system is a VM that runs on ESXi host(VMWare) that has datastores attached to it and serving the VMs. The target has an NVMe disk.
To your second question - Neither does the source or target have multiple disks installed.

may i add that i was using ipxe.efi boot file vs undionly.kpxe.

I was able to image a different system using undionly.kpxe just now but that one doesnt support uefi, its an older system, which makes me think the problem may be related to uefi builds, but i am not 100% sure.

I will try to upgrade the fog install and retry my original test case, in which the target is an uefi system.

Hello,

I’m running latest 1.5.9 version of FOG.
I made a VM with windows 10 pro with only 65GB drive, UEFI boot.
Captured the image with the resizable option.
When I deploy it to a different physical machine, I get the error that the Partition is too big for the disk which doesn’t make sense since the machine has a 256gb drive > the original 65GB.
I also pulled the image with the resizable option.
I read on the forums that the recovery partition could cause this issue, so I removed it and re pulled the image, but deploying it still fails.

Thoughts?