Clone 500Gb HDD to 256GB SSD

[mikmatcr]

Hello, I have an image made with FOG, the base equipment had a 500Gb HDD and the operating system only occupies 100Gb, I need to clone that image on several computers with 256GB SDD.

The size of the OS is not a problem because it is less than 200GB but when trying to clone FOG it does not allow it.

Can a captured image be cloned from one disk to another with a smaller size?

Thanks

[george1421]

@mikmatcr The problem (most likely) is a non resizable partition as the last partition on the disk. This causes the resize to a smaller disk to be an issue. I think the developers have resolved this is a interim beta release of FOG 1.5.10. If you are using fog 1.5.9 you can upgrade to the dev branch. There may also be an init update if you are still running 1.5.9

ref: https://forums.fogproject.org/topic/15025/move-partitions-on-gpt-layouts-need-people-to-test

[mikmatcr]

@george1421 Thank you, I will read the reference you sent me well and update my results.

[mikmatcr]

@george1421 At the moment I have FOG 1.5.7, I must update but first I have to test, for the moment I will use version 1.5.7.

The steps that I must follow to solve the problem are these:
1- Change the init.xz that I have for init-201114, what I did was rename the original one and I named 201114 init.xz
2- Capture the image with this change
3- Deploy the new image on a computer with a smaller SSD

Is the process that I am going to carry out okay?

Do I have to recapture or can I use an old image already captured?

[Sebastian Roth]

@mikmatcr The most important thing you need to consider is: Do you have a proper UEFI installation with GPT partition layout. Unless you can answer yes here, there is no point in going ahead with this.

Beside that you might want to post you current captured partition layout before trying the beta init referenced in the other post! Post the contents of the text filed1.minimum.partitions (you should find that in /images/IMAGENAME/ on your FOG server.

As George said this is still an early stage test init and I recommend you follow the process outlined in the other topic. Especially make sure you create a new image definition before re-capturing the image (yes you have to re-capture!) and as well don’t just substitute the original init.xz with init-201114.xz but put that into the same directory on the FOG server and change host settings.

You are free to do whatever you like but I suggest not to go and just use this as if it’d be an official init. It’s not!!

[mikmatcr]

@sebastian-roth Hello, this is my file d1.minimum.partitions

label: gpt
label-id: 87E47567-415E-4625-932D-EFDCE1443B0F
device: /dev/sda
unit: sectors
first-lba: 34
last-lba: 976773134

/dev/sda1 : start=          34, size=      262144, type=E3C9E316-0B5C-4DB8-817D-F92DF00215AE, uuid=16F81390-E734-4932-B3AA-86D8EAF47983
/dev/sda2 : start=      264192, size=      811372, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=F713774E-136E-44FC-A1D7-86363B97D17D
/dev/sda3 : start=     4204544, size=      204800, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=6FE304CA-8F65-4A30-B7AD-7EDC4BBD5685
/dev/sda4 : start=     4409344, size=   176924176, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=17DA8A56-8457-42AB-936B-AFF1643802B3
/dev/sda5 : start=   974721024, size=       32592, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=11D6F302-FF69-45A7-A541-258EC4AF9169

[Sebastian Roth]

@mikmatcr While a default Windows layout usually hast 4 partitions instead of those 5 I would still say that the mentioned init-201114.xz should be able to capture your layout from a 500 GB disk and deploy to a smaller one.

As I said, use a new image definition, capture using the init-201114.xz and deploy that. Let us know if it works and best if you’d also post d1.partitions and d1.minimum.partitions from that new captured image here as well.

[mikmatcr]

@sebastian-roth Hello, I did it with the new init, I attach the data from the file that you requested.

Thank you very much for the help

label: gpt
label-id: 87E47567-415E-4625-932D-EFDCE1443B0F
device: /dev/sda
unit: sectors
first-lba: 34
last-lba: 976773134
sector-size: 512

/dev/sda1 : start=          34, size=      262144, type=E3C9E316-0B5C-4DB8-817D-F92DF00215AE, uuid=16F81390-E734-4932-B3AA-86D8EAF47983
/dev/sda2 : start=      262178, size=      811372, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=F713774E-136E-44FC-A1D7-86363B97D17D
/dev/sda3 : start=     1075200, size=      204800, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=6FE304CA-8F65-4A30-B7AD-7EDC4BBD5685
/dev/sda4 : start=     1282048, size=   176924176, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=17DA8A56-8457-42AB-936B-AFF1643802B3
/dev/sda5 : start=   178206720, size=       32592, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=11D6F302-FF69-45A7-A541-258EC4AF9169

[Sebastian Roth]

@mikmatcr So does it mean you were able to properly capture the image from the 500 GB disk and deploy to the 256 GB disk?

From the new d1.minimum.partitions it looks like it but just want to make sure I don’t misunderstand.