Image with OEM Recovery Partition
-
Going to type out what I am done so far, tell me what I am missing. if anything.
Hardware: Panasonic CF-31S
I am assuming one HDD as I do not see room for more.
HDD: 500GB
[LIST]
[]Part 1: Recovery | 12GB
[]Part 2: 100mb
[*]Part 3: Windows 7 | Rest of the Disk
[/LIST]
Coworker finished installing custom applications on what is labeled Drive C, Partition 3 (Technically 2 for Win7 case)
Keeping First partition intact for time being, it is the OEMs Recovery Partition.No SysPrep (For the time being, higher ups want to keep it that way)
No FogPrep (Am I reading this wrong or is it already implemented into 0.32 upon imaging?)
Taking an image: First trying Single Disk, Multi Part, NonResize.
Image get saved, pushed down to another.
Endless Startup Repair.Go back into master hardware, do a defrag and error check.
Everything comes up fine.Retake image, same problems.
Decide to use Windows 7 Backup to test other options.
I was able to clone another from using Backup. Works fine from what I can tell.I am now going back to the master and re-uploading the image as a Mutli Disk, Multi Part, NonResize.
Let’s see where this leads me if anywhere.Worse case: If nothing else, wiping disk, fresh Windows 7 install.
Am I missing something?
-
I think you’ll have the best luck on multipart versus single disk resize. Resize seems to only work for sysprepped win 7.
-
First one I tried was a Multi Part, Single Disk, NonResie.
Wouldn’t even let me try a Single part, Single Disk, Resize.3 more minutes and I can try the Multi Part, Multi Disk I mentioned.
I apologize if my wall was hard to read.
EDIT: Now to wait until morning if it works.
-
Normally,
Windows 7, fresh install, works by creating two partitions. Partition 1 is the 100MB partition. Partition 2 is the one that typically has all the main software and things needed by the os. (C:\Windows C:\Users etc…)
In your case, it sounds like your Partition 1 is the OS Recovery that comes with the laptop, Partition 2 is the 100MB and Partition 3 is the main stuff.
You may not have to change the image stuff from the GUI. My understanding is that it did copy over all three partitions, but the order it’s writing the data is not correct.
The fog scripts only create two partitions normally.
Partition 1 is usually created, again, with that 100MB stuff, but in your case d1p1.img is actually your OS Recovery stuff. It’s amount of data is probably larger than the 100MB we’re so used to seeing. So it writes the data, until the space is completely used, then fails, but starts the Partition 2 imaging (In this case your actual 100MB Partition) from d1p2.img file, but it’s using the rest of the disk. Then d1p3.img (Your main
stuff) tries to copy, but there’s no partition created for that to be uploaded.This would explain why you’re having the issue with deploying the image properly and getting such a weird error message.
Maybe try renaming the files in the proper order?
Change d1p2.img to d1p2.img.orig
[code]mv /images/<imagefilename>/d1p2.img /images/<imagefilename>/d1p2.img.orig
mv /images/<imagefilename>/d1p3.img /images/<imagefilename>/d1p2.img
mv /images/<imagefilename>/d1p1.img /images/<imagefilename>/d1p3.img
mv /images/<imagefilename>/d1p2.img.orig /images/<imagefilename>/d1p1.img
[/code]This method should work for either Single Disk - Multi Partition or Multi Disk - Multi Partition for your case.
-
My small test failed.
[QUOTE]
This is first findings, before changing d#p#.img files around
It looked like it copied the partition correctly how they showed up in Disk Management.
Which was Recovery -> 100mb -> OS
sda1 took a while getting 12GB
sda2 breezes past
sda3 Takes longer being around 40GB+ anyway[/QUOTE]Following your steps, I do not think that will work without changing other things. (Which I am not sure how)
What is now sda1 flys by too quickly. Almost failing (300mb if I saw it flash correctly?)
What is now sda2 tries to put what was in the 400GB+ part into 12GB
What is now sda3 tries to put the recovery partition into what is left over 400GB+
This leads to not even attempting to boot into Windows. Can’t find anything. -
Then I guess the best option for your particular scenario is to do a fresh install, leaving out the OS Recovery Partition.
Another check would be to do the steps I stated above, in reverse order so:
[code]mv /images/<imagefilename>/d1p1.img /images/<imagefilename>/d1p2.img.orig
mv /images/<imagefilename>/d1p2.img /images/<imagefilename>/d1p3.img
mv /images/<imagefilename>/d1p3.img /images/<imagefilename>/d1p1.img
mv /images/<imagefilename>/d1p2.img.orig /images/<imagefilename>/d1p2.img[/code]This should put all the files back in the same order they originally where in.
Then, do the deploy task, but use deploy debug, rather than the basic deploy.
This will cause the system to boot where you have command line access before the task actually runs.
When the prompt is ready, type fog and hit enter.
It should go thru and reimage just like before.
When it’s complete, it will say it’s restarting the system, but will drop back to command line.
Run the command:
[code]fdisk -l[/code]Output the results here. I have a sneaky suspicion that the Boot partition is being flagged on /dev/sda1 but should be set on /dev/sda2 in this case.
-
Quick report
Was about to wipe a spare CF31S clean with an install and this was an odd sighting.
Still straight from OEMWhere do you want to install Windows?
Name | Total Size | Free Space | Type
Disk 0 Partition 1: Recovery | 17.7 GB | 3.3 GB | OEM (Reserved)
Disk 0 Partition 2: System | 300.0 MB | 258.0 MB | System
Disk 0 Partition 3 | 29.3 GB | 15.6 GB | Primary
Disk 0 Unallocated Space | 423.5 GB | 423.5 GB |EDIT: For research sake, I will fdisk.
EDIT 2: Heard from coworker who started the image; they may have used a partition merging program to combo 2 partitions. This may be one of the issues with getting the image. -
Stopped mid way.
Cannot read file d1p3.img.001
Going to try again with a backup of the first attempt ever tried.
-
sda2 has * boot marked.
sda2 is the 300mb part.
