I’m going to try the FOG trunk route. Moving in this direction, and with my master’s partitioning scheme, should I continue to use the multiple partition/single drive resizable option?
Posts made by groinksan
-
RE: FOG 1.2 - Target partition smaller than source - Windows 7/X-Image
-
FOG 1.2 - Target partition smaller than source - Windows 7/X-Image
I’m brand-new to the whole FOG thing. I’m trying to develop a method to perform a mass roll-out of Dell Latitude and Precision computers. The disk image was sent to us as a Ghost GHO file. I then used Ghost 11 to image a 320GB hard disk drive. After imaging with Ghost, the hard drive is partitioned as follow (using Windows’ DISKPART / LIST PARTITION):
Partition 1 - OSDisk Type - primary Size - 294 GB Offset - 1024KB Partition 2 - BDEDrive Type - primary Size - 3180 MB Offset - 294 GB
The image is Windows 7 64-bit based. The image uses X-Image, which is a Dell product that prepares Windows 7 for the specific hardware platform (kernel, drivers, etc.) So it is like sysprep but on steroids. X-Image is placed into the image before I ever receive it. so I have no control of that process.
When using Ghost, the BDEDrive partition size is untouched, while the OSDisk takes up the remainder of the hard drive, regardless of the hard drive size. So, I’m hoping FOG/Partclone can do the same thing. So even though the original drive is 320GB, I can image a 1TB drive and have the entire drive, minus BDEDrive, dedicated to OSDisk.
Right after Ghosting the master hard drive, with it in pre-X-Image state, I uploaded the hard drive contents to FOG, using the following settings:
Operating System: Windows 7 (5) Image Type: Single Disk - Resizable (1)
The contents of d1.original.partitions generated by FOG are:
unit: sectors /dev/sda1 : start = 2048, size=618625024, Id= 7 /dev/sda2 : start = 618627072, size=6512640, Id= 7, bootable /dev/sda3 : start = 0, size = 0, Id= 0 /dev/sda4 : start = 0, size = 0, Id= 0
I then tried imaging a different computer that has a 1 TB hard drive. The hard drive has been erased, so no partitions are currently on the drive. During imaging, it comes up with the following error in Partclone:
Target partition size(105 MB) is smaller than source(316737 MB). Use option -C to disable size checking(Dangerous).
It works when I use the multiple partition image - single disk (not resizable), but I cannot use this option for the following reason: it places DBEDrive after OSDisk, so once I’m booted into Windows 7, I cannot adjust OSDisk to take up the rest of the free space, as Windows requires contiguous free space (not in this case, since DBEDrive is smack dab in-between OSDisk and the remaining free space.) So I was hoping the Single Disk option would work like Ghost.
Sorry for the long post, but I want to be as thorough as possible! Thanks!