Image file does not "expand" the full size of the drive it is being deployed to
-
@rboan Bump…
-
@rboan Bumping again…
-
@sebastian-roth I work with Robyn. This looks good. We are now able to boot and capture images. We are just having trouble restoring them back to drives of a larger size. I don’t see that covered in your guide anywhere unless I missed it. We are still continuing to test… But don’t don’t really have a resolution yet.
-
@caw001 said in Image file does not "expand" the full size of the drive it is being deployed to:
We are just having trouble restoring them back to drives of a larger size. I don’t see that covered in your guide anywhere unless I missed it.
Well I don’t have a ready solution for you guys yet. We are in the process of helping you to find and fix this issue. Last @rboan posted was a screenshot with the error message “Invalid OS ID (0) (determineOS)” and so I answered:
Why do we see the “Invalid OS ID” now? Why 0 (zero)? Please check the image settings in the FOG web UI. As well please run fdisk -l in a debug task and hopefully we’ll see what disk you have.
I still want to help you guys and need more information to be able to do so.
-
@sebastian-roth Sorry, just spoke to her. (She’s working on trying our Mac capture at the moment). The issue she was experiencing at that moment was because she had no selected the OS type when setting up the capture. Once she did that we were able to successfully capture and image. That’s when we ran into the issue of restoring the image back to a larger disk and it not expanding to the full size.
-