Problem laying image on a virtual machine
-
@Sebastian-Roth I’m wondering if there is some way to trap this error prior to image deployment? I know we can capture the lsblk output with
lsblk -d |awk '{print $1 " " $4}'(note this command was a quick hack to solve a problem in another thread) to return the target disk size. Is there some way to build the minimum space needed from the metadata collected during image capture? -
@george1421 said in Problem laying image on a virtual machine:
Is there some way to build the minimum space needed from the metadata collected during image capture?
I am sure there is. Something like
tail -1 d1.partitions | awk '{print $4+$6}'(ord1.minimum.partitionsif that exists) would get the minimum sector count of the destination disk needed. And for sector count of the disk in question I’d runblockdev --getsz $disk -
The image was deployed, but when I booted the virtual machine, there isn’t a valid boot file at SCSI 0,0 found. I should probably start a new thread?
-
@davemccracken @george1421 @Sebastian-Roth
This is the current screen I get when I try to boot the target VM
-
@davemccracken Understand we are still testing here, but if you run the recovery tools can you fix the problem with boot?
Its still not clear if its something wrong with your image or the way FOG has deployed to this target computer. If you can fix the issue with the recovery tools we will know that FOG has deployed the image intact.
Another question, did you sysprep this image before it was captured?
-
Yes, I syspreped before capture.
I will try the recovery tools. One question which comes to mind though, although since the partition tables are recreated I doubt this is the case, but does that target drive have to have had a working operating system on it prior to the FOG deployment?
Thank you,
Dave -
@davemccracken said in Problem laying image on a virtual machine:
does that target drive have to have had a working operating system on it prior to the FOG deployment?
No FOG doesn’t care what was there before to deploy it. The point being you can deploy to bare metal or a previous OS, FOG doesn’t care because it destroys the partition table and creates a new one. This error kind of tells me the boot partition is not in a sane state.
-
@george1421 Okay, but the gold image VM boots fine, and so, I am somewhat unsure what would cause a block by block copy of it to have a bad boot partition.
Interestingly, once I booted from a Win10 ISO file, it then says the registry is missing or has errors. This has me wondering if I should just try to deploy again, as maybe something got lost or corrupted between the image and the target.
What do you think? Can this be a possibility?
Dave
-
@davemccracken said in Problem laying image on a virtual machine:
I am somewhat unsure what would cause a block by block copy of it to have a bad boot partition.
Using image type MPS (Multiple Partitions Single Disk) is not really a block by block copy. Although it is pretty save to properly deploy to another system fine! As you didn’t use the resizable image type (as we see in the picture you posted) partition problems are not very likely. My guess is this has something to do with how you sysprep.
-
I agree with you that something must be wrong with the image. It has done the same thing on 3 virtual machines so far. I originally had done a multicast for the first 2 and a single machine deploy for the last.
I am going to go back to the VM with the gold image, and re-sysprep and capture it. Then try the deploy again. Do you have recommended sysprep parameters? I was using /oobe /shutdown
-
@davemccracken Here is my unattend.xml file and the sysprep command I use: https://forums.fogproject.org/topic/11920/windows-10-1803-sysprep-problem/7
Make sure you put the unattend.xml file in c:\windows\panther only.
-
@george1421 @Sebastian-Roth @Quazz
Thanks George, I tried to use your unattend file, but it kept bluescreening on the host once imaged, so I tried creating a new one today and it worked fine. I probably didn’t change enough things in it, and missed something important, but I got around it now.
I greatly appreciate all the help you kind folks have provided. It is very much appreciated. I couldn’t have gotten to this point without it,
Dave
