Unsolved Large Image sizes
0juke last edited by
I’m having a little issue with fog capturing the entirety of the secondary hdd which contains large files and take up more room than required. This is something I do not want, Is there a way just to capture the windows installation and the applications installed on the C drive? I understand that I can capture partitions , but I’m unsure which option to select for just a back up of the C drive as they are numerical.
@george1421 can you please explain with a video tutorial or step by step screenshots. which options i select when i restore only c drive.
@0juke There is no simple rule that makes it possible to translate from drive letters to partition numbers as many partitions are hidden within Windows and don’t get a drive letter assigned. So there is nothing much we can do. You need to check and understand your partition layouts to know which one is which. Start by taking a look at the files called
d1.partitionsthat you find in the image directories on your FOG server. If you can’t make sense of those you might just post the full text here and we can tell you.
Beside that I need to add that there are two more culprits with this:
- We only have the option to image/deploy all or one partitions. There is no option to do a couple (like two or three). To get around this you can setup several image definitions and deploy those one after the other.
- On deployment we don’t write the partition layout information to the disk if only one partition is selected in the image definition. What that means is that you can not deploy an image where only one partition is selected to a fresh clean disk. The disk needs to be “pre-deployed” with the whole image at least once (and every time the layout changes).
So from a practical standpoint I would:
- Define two (or more) images. One includes all drives and partitions and the other one(s) have a single partition selected.
- Deploy all your machines with the “full” image once.
- Now when you make changes to your master machine you need to capture the “full” and the “single” image (there is a hack by copying the
d1px.imgfile over but I won’t go into the details just now).
- From here on you can deploy “single” partition(s) to your clients.
0juke last edited by
@Quazz Well, each system I’m configuring is different so some are sperate and some are just partioned.
Are they actually seperate drives or only seperate partitions on the same drive?
FOG really doesn’t have a concept of a windows disk or the drive because FOG/FOS is based on linux. But you can get something like you want. What you would do is in the image definition pick “Single disk resizable” The if you capture FOS should capture the first disk in the system (which is typically your drive). If FOS picks the wrong disk then in the host definition you define which disk. For a sata attached disk the Primary disk would be
/dev/sdaIf you want the second sata disk but not the first you would enter
/dev/sdbfor the primary disk.