FillDiskWithPartitions - SVN4730 - deploying an image
-
Same error.
My image for the x131 is from an older version of FOG… but it was working before. I see the image has a rec.img.000 and sys.img.000 and I think the newer way it captures, they look different. Anything else to try?
-
@GFm I think know what is wrong now, I missed that part. You need to go on the FOG server to FOG Configuration>FOG Settings>General Settings and check the box for FOG_FORMAT_FLAG_IN_GUI and save. Then go into your image and change it to Partimage in the "Image Manager"drop down. This will switch that image to the legacy style from .3x and allow you to image the machine.
-
I would recommend if that works that you pull the image down to a machine and then change to Partclone and re-upload. That will convert the image and keep it more in sync with the trunk and future releases. Partclone is much better and faster.
-
@ITSolutions
Did not work. Anything else to try? Thanks for the help so far! -
@ITSolutions
It’s definitely all my images from the older style imaging. I tried a bunch and they all do the same thing -
@GFm I think we are going to have to defer this to the @Developers and @Tom-Elliot in particular. We at least have a place for them to start at as it appears the legacy images are the issue and your new images are fine. The only work around that I can think of in the mean time would be to roll back to an earlier build and use it, until a fix is figured out.
As I mentioned before that I would highly recommend getting those images converted over as the benefits are great and the there is no real draw back other than the few min it takes to pull switch and push back up.
-
@ITSolutions
Thanks… I will definitely update once it’s working, now knowing all of this
-
Can you please update and let me know if this is still happening?
-
@Tom-Elliott just adding that I don’t expect this to be a fox, though if it is it will be awesome. It’s a hope of it fails that the edits I made help me find it quicker.
-
@Tom-Elliott
It’s imaging now after the update. I did set the image to partimage too.Thanks!
-
@GFm Now to carve out the time to update those over to Partclone. Just a quick FYI in case you are not aware of this. To convert them you don’t have to have the actual machine they go on. I found a spare machine and pulled the image down, and shut off the machine (DO NOT LET IT BOOT AFTER IMAGING) then changed the type in FOG and re-uploaded to the server. Doesn’t matter what hardware you put it on as it never boots into windows.
But on the same token if you have the correct hardware for them it is a perfect time to update the images, I am sure windows updates are way behind. lol
-
@ITSolutions said:
@GFm Now to carve out the time to update those over to Partclone. Just a quick FYI in case you are not aware of this. To convert them you don’t have to have the actual machine they go on. I found a spare machine and pulled the image down, and shut off the machine (DO NOT LET IT BOOT AFTER IMAGING) then changed the type in FOG and re-uploaded to the server. Doesn’t matter what hardware you put it on as it never boots into windows.
But on the same token if you have the correct hardware for them it is a perfect time to update the images, I am sure windows updates are way behind. lol
Very nice.
There is a new snapin that allows editing of the tasks, and custom task creation.
I think changing the end from a reboot to a shutdown would make this a lot easier.
-
@Tom-Elliott @ITSolutions
So, I left as it was imaging yesterday (using partclone on those old style images). When I came back, I re-imaged it because windows wasn’t booting and I saw this on multiple different machines with the old style images.
So I tried partimage on an old-style image and it wouldnt even image… got this error.
Any ideas?
Thanks!
-
@GFm Can you update, I saw a similar issue last night and fixed it.
-
@Tom-Elliott
they all went through with partclone after the latest update.Thanks!!