FOG will not resize a hard drive after deployment.

[m.fitzgerald]

@sebastian-roth

D1.Fixed
:3

d1.min
label: dos
label-id: 0xae2e5b63
device: /dev/sda
unit: sectors

/dev/sda1 : start= 2048, size= 119716, type=7, bootable
/dev/sda2 : start= 1026048, size= 85513176, type=7
/dev/sda3 : start= 974723072, size= 2048000, type=27

d1.orig
/dev/sda1 ntfs
/dev/sda2 ntfs

d1.part
label: dos
label-id: 0xae2e5b63
device: /dev/sda
unit: sectors

/dev/sda1 : start= 2048, size= 1024000, type=7, bootable
/dev/sda2 : start= 1026048, size= 973697024, type=7
/dev/sda3 : start= 974723072, size= 2048000, type=27

[Sebastian Roth]

@m-fitzgerald Can you please edit d1.fixed_size_partitions and make it 1:3. Then re-deploy that image to a fresh machine and see what you get.

As well can you take a picture of the disk management view in Windows on the source machine and post here?

[m.fitzgerald]

@sebastian-roth That solved the boot issue! Thanks. Now all is working as normal. Hard drives are re-sizing properly now. We have tested it on 4 machines.

Case Solved.

[Sebastian Roth]

@m-fitzgerald Good to hear this fixed the issue for you. Though from my point of view it’s only partly solved. If you capture the image again you will need to edit that file again. So question remains why it does not recognize your boot partition as such. Usually this happens if Windows is not installed as English version or partition labels have been modified by hand. As I said, take a screen shot of the disk management view in Windows and post here. I am fairly sure we can figure out why that is.

Follow on question though. How do I edit the order of Storage Nodes?

We try to keep topics separate. Please open a new thread for this! Won’t answer here.