Invalid Storage Group (may be related to image import)
-
I set up a new FOG server and exported/imported the images from the old one. I put the image folders into /images and successfully deployed an image. so far so good.
I now try to capture the same image from the just deployed PC and get the dreaded “Invalid Storage Group” message after the capture is finished. I also see, that there is a folder with a seemingly random name in /images/dev (name is: 20cf302bd905) with the captured image.
please advise.
-
@perler said in Invalid Storage Group (may be related to image import):
I also see, that there is a folder with a seemingly random name in /images/dev (name is: 20cf302bd905) with the captured image.
That’s just because it can’t finish moving the captured image over because of the “Invalid Storage Group” error.
Tom pushed a fix that should address the issue to the
dev-branchnot long ago (ref). Can you please update and see if that fixes the problem for you? -
Is there an easy way to switch branches?
-
@perler You can switch between branches but while moving from master (currently official 1.5.7) to dev-branch works well you should not switch back to master if you don’t know exactly what you do or one of us developers guides you. So it’s a bit of a one way road. On the other hand it’s possible to switch to dev-branch now and go back to master when the next official version is being released (because at that point master and dev-branch are equal for a short time).
sudo -i git clone https://github.com/FOGproject/fogproject cd fogproject git checkout dev-branch git pull cd bin ./installfog.sh -
ok, sorry, this took a while but I finally managed to witch to the dev branch. now the capturing stops earlier, when trying to capture the big “main” partition of the test machine it exits with error 139 and it asks me to check the space on the server (which is fine).
# df Filesystem 1K-blocks Used Available Use% Mounted on udev 977344 0 977344 0% /dev tmpfs 201784 848 200936 1% /run /dev/mapper/fog--vg-root 60655460 27545672 29998876 48% / tmpfs 1008900 0 1008900 0% /dev/shm tmpfs 5120 0 5120 0% /run/lock tmpfs 1008900 0 1008900 0% /sys/fs/cgroup tmpfs 201780 0 201780 0% /run/user/0 -
Ok, a server reboot fixed the error 139 (so there may be a small issue with the updater) and I can confirm that the original bug is fixed in the dev branch.
-
@perler said in Invalid Storage Group (may be related to image import):
error 139
Did you take a picture of the error on screen? I am not sure what exactly this referes to.
-
sorry, I didn’t. but I think you can easily recreate this by following your instructions and immediately after the upgrade is finished try to capture a machine.