FillDiskWithPartitions - SVN4730 - deploying an image



  • I am trying to image a lenovo x131e with an image that worked before - win7,single-resizable. Now I get this error even after updating to the latest svn. Any ideas? This also happens on an asus laptop that i have with a different image (same win7,single-resizable)

    0_1453994471470_IMG_5471.JPG
    0_1453994554228_Capture.PNG

    Thanks!



  • @Tom-Elliott
    they all went through with partclone after the latest update.

    Thanks!!


  • Senior Developer

    @GFm Can you update, I saw a similar issue last night and fixed it.



  • @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.

    0_1454069831281_IMG_5474.JPG

    So I tried partimage on an old-style image and it wouldnt even image… got this error.
    0_1454069905554_IMG_0969.JPG

    Any ideas?

    Thanks!


  • Moderator

    @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.


  • Testers

    @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



  • @Tom-Elliott
    It’s imaging now after the update. I did set the image to partimage too.

    Thanks!


  • Senior Developer

    @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.


  • Senior Developer

    Can you please update and let me know if this is still happening?



  • @ITSolutions
    Thanks… I will definitely update once it’s working, now knowing all of this (:


  • Testers

    @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
    It’s definitely all my images from the older style imaging. I tried a bunch and they all do the same thing



  • @ITSolutions
    Did not work. Anything else to try? Thanks for the help so far!


  • Testers

    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.


  • Testers

    @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.



  • 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?


  • Testers

    Can you try to image the Dell with the image that won’t work just to see if it will pull the image down? I know it might not boot correctly after imaging, I am just wanting to see if the dell will pull the image. This will get us a little closer to finding if it is the image or machine. If the Dell is able to get the image then I would try updating the BIOS on the Lenovos.



  • I tried 2 different computers, different images, both HDD instead of SSD. A third machine that I have (dell e5550) imaged fine (win10, single-resizeable) but it was an SSD. Could that affect it? Either way, these machines did image before a week or two ago on an older SVN (not sure which one)


  • Testers

    Is it only failing on this machine or do you have any others you can try? You could try to do a disk wipe task and then redeploy? This will wipe any existing odd partition table information off the drive.



  • fog in the cloud 6124
    svn is 4730


Log in to reply
 

457
Online

38746
Users

10572
Topics

100071
Posts

Looks like your connection to FOG Project was lost, please wait while we try to reconnect.