Multiple Partition Image to Blank Hard Drive
The issue I’m having is as the title suggests; I have a Mac OSX image that has one disk with three partitions on it and I’d like to upload this image to a brand new hard drive to test a major operating system upgrade in a test environment. The error that I get says:
No image file(s) found that would match the partition(s) to be restored (performRestore)
Args Passed: /dev/sda /images/IMAGE-NAME all
Normal variables and settings:
BOOT_IMAGE=/boot/bzImage loglevel=4 initrd=init.xz root=/dev/ram0 rw ramdisk_size=12700 keymap= web=10.1.10.32
I presumed that this means the blank hard drive literally had no partition table on it so I took it into GParted (and eventually straight up fdisk) on a Ubuntu live disk and added 1 partition to see if the error would change. Unfortunately, it doesn’t look like it changed anything. I went back into the Ubuntu live disk and it apparently didn’t write correctly because it was still “unallocated”. At this point, I’m not sure if it’s an issue with FOG reading partitions or my partitioning software but I still have on main question:
How do I even know what to set the partition sizes to? I know that there are three partitions for the full image but I’m not sure what size they are uncompressed.
Thanks in advance!
@sebastian-roth Unfortunately it has been lower on my priority list right now, we are undergoing a lot of changes as a business right now. I’ll update ASAP.
@mwarner Any news on this?
@sebastian-roth I’ll try upgrading to 1.5 - I’m familiar with git and the upgrade process. I’ll post my findings after the upgrade is complete.
Are you familiar with upgrading to the latest version or how to use git at all? How did you go about when initially installing FOG? Well I assume you used git to checkout FOG 1.4.4 so those commands should get you to the latest working version:
cd /root/fogproject git checkout working git pull cd bin ./installfog.sh
Be warned, this is kind of a one way road. It’s not advised to go back to FOG 1.4.4 after you’ve moved forward. Though there are many people using FOG working branch on their productive server.
If you are afraid of going ahead I can offer to send you a patched
init.xzfile that you can use and stick to the stable FOG 1.4.4. Just let me know.
@mwarner I have done MAC cloning many times and I know others as well. I am fairly sure we can make this work! Just give it a bit more time. Might have some tonight…
@sebastian-roth No worries, I appreciate the effort. It’s not a top priority on my list and if it can’t be done then that’s fine, but I’d like to get to the bottom of it so I can get back to my boss about the status of the project.
@mwarner Sorry I didn’t find the time to look into this in detail and test yet. Will be sometime this week!
mwarner last edited by Sebastian Roth
label: gpt label-id: F648D791-9536-40F2-A0D3-3A25F0227609 device: /dev/sda unit: sectors first-lba: 34 last-lba: 1954210086 /dev/sda1 : start= 40, size= 409600, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=FCC1F955-3052-49AB-AE2C-ED013B75ADE9, name="EFI System Partition" /dev/sda2 : start= 409640, size= 1952530904, type=48465300-0000-11AA-AA11-00306543ECAC, uuid=A0816DEE-EEEA-40CD-BE23-14270C02A1D9, name="Macintosh HD" /dev/sda3 : start= 1952940544, size= 1269536, type=426F6F74-0000-11AA-AA11-00306543ECAC, uuid=1B0326DE-5FF2-40EE-B8DA-44645187605A, name="Recovery HD", attrs="GUID:49"
@mwarner Sorry, forgot to ask. Please post the contents of p1.partitions as well. This is a simple text file so you can just do
cat p1.partitionsto show its content on screen. Post a listing or picture please.
Here is a screen cap of my ls -la output.
@Sebastian-Roth Thanks for the heads up - I’ll still try to image it anyways but if it doesn’t work now I’ll know to stop trying.
@mwarner Be warned, Mac OS X major system updates don’t just consist of the data on disk but more often than not there is also an upgrade to the UEFI firmware which you wouldn’t be able to simply transfer to the other machine. FOG can’t do this!
On the other hand you should be able to deploy an image to a completely empty disk. As Wayne said, we need to know which version of FOG you run to see if it could be an issue with an older version.
On you FOG server console please run
ls -al /images/<IMAGE-NAME>and post a picture or full text output here! By the way, there is no need to mask the image name. It’s just making it harder for us to help you.
Wayne Workman last edited by
@mwarner What version of FOG is this?