Fog Imaging Issues

[Chris Garsee]

[Chris Garsee]

Don’t know if this is related or not, but here is another image.

[Tom Elliott]

What’s interesting it is states that it’s corrupt. Are you sure your image is working order?

[Chris Garsee]

@Tom-Elliott I thought about that and I tried another image that will work with that machine and still get the same thing.

[Wayne Workman]

When were these images created? What revision were you using when you created them?

[Chris Garsee]

@Wayne-Workman Are you taking about the version, which is 1.2.0? Forgive me but I am still learning Fog.

[Wayne Workman]

@Chris-Garsee

If you’re using pigz, then you’re not using 1.2.0.

If you look at the cloud in the top left corner of your web UI, it’ll have a number in it. That’s the revision number you’re using.

[Chris Garsee]

@Wayne-Workman We upgrade to 1.2.0 about 3 to 4 months. The images worked, but we were having issues with XP images. I upgraded 12 days ago to svn 3504 and thats when everything stopped working completely.

[Wayne Workman]

Are the old images set to partimage instead of partclone ?

[Chris Garsee]

@Wayne-Workman Partclone

[Wayne Workman]

@Chris-Garsee

Images created using .32 ish (around there and older) should be set to partimage. Somewhere in FOG Config -> Fog settings, you can enable selecting the image type.

Also, you might want to jump to the latest FOG Trunk (use ‘svn up’, then reinstall). See the SVN article for info on that.

[Chris Garsee]

@Wayne-Workman

[Wayne Workman]

These are really bizarre errors.

Could you try to uninstall pigz and then reinstall it?

[Tom Elliott]

The images, in fact, are in partclone format based on what I’m seeing.

What is the output of:
dmesg

[Junkhacker]

just a shot in the dark, but have you tried a different network cable?

[Chris Garsee]

@Junkhacker We have tried different cable and different ports.

[Tom Elliott]

@Chris-Garsee and I fixed this today.

He updated to 12.04, and we updated the rest of the system using:

sudo apt-get update;
sudo apt-get dist-upgrade;

Found that the nfs-kernel-server package wasn’t updated with the main OS. Once we updated and restarted the services and selected a proper image, the system went beyond the 20%.

I’m going to chalk it up to older data with the newer init’s methods of mounting causing the problems we were seeing.