Trunk 8093- Deploying Image Failing, Partition Size Error

[Sebastian Roth]

@LJedi Please check the text file /images/<imagename>/d1.fixed_size_partions on your FOG server. From what you describe I suppose the file is empty but it should read 1 or 1: to work properly. Please show us the output of ls -al /images/<imagename>, cat /images/<imagename>/d1.partitions and cat /images/<imagename>/d1.minimum_partitions as well.

[LJedi]

@Sebastian-Roth

Here are my results:

ls -al Optiplex745Win10/
total 7519176
drwxrwxrwx  2 root root       4096 Jun 16 10:19 .
drwxrwxrwx 32 root root       4096 Jun 14 12:10 ..
-rwxrwxrwx  1 root root          1 Jun 14 09:52 d1.fixed_size_partitions
-rwxrwxrwx  1 root root    1048576 Jun 14 09:53 d1.mbr
-rwxrwxrwx  1 root root        190 Jun 14 09:53 d1.minimum.partitions
-rwxrwxrwx  1 root root         30 Jun 14 09:52 d1.original.fstypes
-rwxrwxrwx  1 root root          0 Jun 14 09:52 d1.original.swapuuids
-rwxrwxrwx  1 root root  325089680 Jun 14 09:53 d1p1.img
-rwxrwxrwx  1 root root 7373459536 Jun 14 10:15 d1p2.img
-rwxrwxrwx  1 root root        190 Jun 14 09:52 d1.partitions

/Optiplex745Win10# cat d1.partitions
label: dos
label-id: 0x1288f3ca
device: /dev/sda
unit: sectors

/dev/sda1 : start=        2048, size=     1024000, type=7, bootable
/dev/sda2 : start=     1026048, size=   155273216, type=7
root@RoyFogMasterNode:/images/Optiplex745Win10#

cat d1.minimum.partitions
label: dos
label-id: 0x1288f3ca
device: /dev/sda
unit: sectors

/dev/sda1 : start=        2048, size=     1024000, type=7, bootable
/dev/sda2 : start=     1026048, size=    35327996, type=7

 cat d1.fixed_size_partitions

root@RoyFogMasterNode:/images/Optiplex745Win10#

[Tom Elliott]

Is there anything in the d1.fixed_size_partitions file? I see a 1 byte which means something is there, but what?

[Sebastian Roth]

@Tom-Elliott said:

Is there anything in the d1.fixed_size_partitions file? I see a 1 byte which means something is there, but what?

My guess it’s just a simple new line in that file. But even then I am wondering why it does not like sda1 because in the partition text files it seems like sda1 is not being touched (resized) and therefore shouldn’t cause an issue.

@LJedi Can you please do a debug deploy. After you see the error and got back to the shell please run sfdisk -d /dev/sda and post a picture here.

[LJedi]

@Sebastian-Roth

Here ya go:

[Sebastian Roth]

@LJedi Thanks heaps! So here we go. It does resize your first partition on deploy (shrinking it by only a few sectors). The problem is that you d1.fixed_size_partitions file is empty which shouldn’t be the case. As a quick workaround, can you please edit that file on the FOG server using your favorite text editor and simply put 1: in.

Then please run another debug deploy session and issue the following commands before even starting the deploy:

mkdir -p /mnt
ntfs-3g /dev/sda1 /mnt
ls -al /mnt/Boot/BCD*
umount /mnt
ntfs-3g /dev/sda2 /mnt
ls -al /mnt/Boot/BCD*
umount /mnt

Take a picture and then start deploying (command fog)… Working now?

[LJedi]

@Sebastian-Roth

After editing that file, the image deployed successfully.

Here is that screenshot with the commands before I deployed that image. Thanks for your help.

[Sebastian Roth]

@LJedi Ok, thanks for testing and letting us know.

@Tom-Elliott I think the issue is caused by line 116 in the upload script. As well line number 73 is likely not doing exactly what we want I suppose.

[Wayne Workman]

@Sebastian-Roth said in Trunk 8093- Deploying Image Failing, Partition Size Error:

As a quick workaround, can you please edit that file on the FOG server using your favorite text editor and simply put 1: in.

Why is it that so often that 1: is missing?

[Tom Elliott]

@Wayne-Workman Could be anything. Should be fixed in latest though.

The 1 was being missed I believe, due to the line 73 @Sebastian-Roth pointed out. The 1 would ONLY be created if there was more than one extfs AND/OR ntfs partition present.

That would mean a disk with 5 partitions might only have one extfs or ntfs partition. The one would be missed. I have corrected this suspicion of mine and updated the inits after testing upload/download still worked. I don’t have a way to confirm the exact issue itself though.

[Sebastian Roth]

@LJedi Could you please upgrade to the latest trunk and see if the d1.fixed_size_partitions is now created properly in your case?

Thanks Tom for looking into this and fixing it!