Problems Deploying Image FOG 1.4
-
when entering fdisk and selecting ‘n’ command it tells me all space for primary partition in use at the top of the first image it cut off the command but i used ‘p’ to print the partition tables the rest of what I did is in the picture.
After running the ‘fog’ command it still fails with the same error I also rechecked the partitions using lsblk and it is how it was before the image deploy command.
-
@jeffj Well I think we are at a point in debugging where we need to ping the @Senior-Developers to see if they understand the issue.
The only other thing is if your source image is some how incomplete. But instead of me guessing at it, lets let them take a look .
-
@george1421 I would just thinking there is one more bit of info they will ask for.
On the fog server console, change to the images directory and the image name you are trying to deploy.
In there run the following command
cat d1.partitionsand post the results here. That file describes what fog should push to the target computer.Silly question too, what this image captured as single disk resizable?
-
-
@jeffj one of the devs are traveling right now but hit me on IM.
He’s saying it appears the image was captured as single disk non-resizable and the destination disk is smaller than the size of the original disk where the image was captured from. Is this possible? Your target disk is 298.1GB in size.
-
AH yeah it is a smaller drive than the original. I happen to have another one of those computers I can recreate an image using single disk resizable. If my memory serves me correctly I was having trouble getting it to create an image that way. I will update this when I run into problems.
-
Sorry I was driving. Yes your image was captured MPS (Multi-partition Single Disk non resizable).
The original disk was, what appears to me, 500GB disk, while the disk receiving this image and having the problem is 300GB (Maybe 320?)
Just taking the information thus far given.
-
@Tom-Elliott said in Problems Deploying Image FOG 1.4:
Sorry I was driving. Yes your image was captured MPS (Multi-partition Single Disk non resizable).
Ah that’s what
Imgtype mpsmeant. I just though you hit turbulence and that’s what I got.
-
Okay when creating a new image that was resizable I receive the dirty filesystem 0,0 error.
rebooted the system and turned fast startup off.
After doing so I was able to create the image successfully.
Tried to deploy the newly created image on the smaller HDD and so far so good we are writing the image now.Recap for marking the post solved.
Could not image HDD with known good image was getting a “No image file(s) found that would match the partition(s) to be restored (performRestore)”
Ran Debug mode to see what partitions were being created on the HDD.
Checked the partition table on the image on the server.
Noticed that the image was a MPS(Multiple Partition Single Disk) and HDD in host was smaller than the original used to create the image.
Disabled Fast booting on the host I need to re-create an image from.
Re-created an image using SDR (Single Disk Resizable).
Was then able to deploy the image to the host with the smaller HDD with no problems. -
@jeffj So it’s safe to solve the thread?
-
@Tom-Elliott yes
