'Target partition size(11 MB) is smaller than source(11 MB)' Sudden Issue


  • So we’ve deployed a few dozen of these machines. Today some of our technicians were messing around trying to get multicast to work unsuccessfully, which is fine. We’re pretty much all new to FOG.

    However, what’s not so fine is that when we did a group unicast, we started seeing the error above for our Recovery partition. The actual size should be 500 MB. The machines actually boot and run fine, I assume just because it’s the recovery partition only that’s broken. But for safety and consistency’s sake, we need this to be fixed.

    So my question since I and the team are very new to FOG: is there any setting in the FOG interface that could cause this problem? It’s like it’s resizing C:\ to be too big to have space for the final partitions. But we have deployed a couple dozen of these machines before today that worked fine, and we haven’t captured any images in days.

    Any help appreciated, and if there are any logs or anything else I can provide let me know. Thanks in advance.

  • Senior Developer

    @gbarron said in 'Target partition size(11 MB) is smaller than source(11 MB)' Sudden Issue:

    Thanks for the quick response and I 100% understand if we have to wait for logs to continue troubleshooting.

    Yeah sorry, can’t help you much without the partition layout files mentioned. Meanwhile can you take a picture of the error on screen and post that here. Just for reference. Sometimes there is something hidden in the screen that might help as well.

    You are right, it’s kinda strange this has worked before and now you get this error. Unfortunately my crystal ball runs out of energy… 😉

    I’m hoping to get access soon but technically I’m a temp right now so not sure.

    FOG is a hands on tool. Without access to the server via SSH your hands are pretty much tied up.


  • @sebastian-roth

    To attempt to answer these questions in sequence:

    The disk sizes theoretically are all the same, but we’re working with multiple models and we’d rather have it resizable just in case. The odd thing is that this has been working for a couple of days and just started failing today, when the image has been cemented for a while and locked.

    We’re using FOG 1.5.9.

    I’ll try to get the logs here soon. Unfortunately at my job we hired an outside consultant for hosting the FOG server so our access to it is a bit spotty. One person can ssh in but he’s work from home today and busy with some other stuff. I’m hoping to get access soon but technically I’m a temp right now so not sure.

    Thanks for the quick response and I 100% understand if we have to wait for logs to continue troubleshooting.

  • Senior Developer

    @gbarron said in 'Target partition size(11 MB) is smaller than source(11 MB)' Sudden Issue:

    So my question since I and the team are very new to FOG: is there any setting in the FOG interface that could cause this problem?

    No I would say. Well partly, by using resizable image type this is being caused. If you capture and deploy to same size disk (sector count needs to be equal!) then you want to use the non-resizable image type.

    FOG is trying to handle many different partition layouts and situations but sure there are setups out there it cannot handle. We have not seen this error in a long time and I had the feeling that we had it right for pretty much all setups. Which version of FOG do you use?

    Anyway, it’s interesting you see 11 MB smaller than 11 MB. That usually means the partition causing the error is just a few sectors smaller. So let’s dig into the details and see what’s going wrong.

    Please post the contents of the (text) files d1.partitions, d1.minimum.partitions and d1.fixed_size_partitions here in the forum (best as text, not picture). You find all those files in the subdirectory named after the image name in /images/... on your FOG server.

403
Online

8.8k
Users

15.5k
Topics

144.4k
Posts