Invalid Operating System (D5) Capone & Windows 7

[Jaymes Driver]

Try a few different ones, just go thru the list, keep track of what they say, I’m sure Chad will be able to sort it out XD.

I know that the problem is stemming from the Image and the OS selected.

[Ian C]

Okay i just finished trying all of them. Same problem just with different numbers.
I also tried deleteing the image and host and re-registering with re image upload and no avail.

[Ian C]

Still having no luck with this. If anyone can help that would be great. Doing these machines one by one is a real pain

[chad-bisd]

I’m not as familiar with Capone as the rest of FOG, but try changing the image name to something without spaces or special characters and see if that helps. Just a guess, but the bash script that is processing your request may error out on the name, but display a misleading error message.

[Matt.Collins]

Is this your original fog server? We had an issue in another district when migrating certain images off to another fog server and when manually recreating the image definitions, it would error out with the same message. We ended up having to migrate the entire /images directory versus just the select images that were used at that site.

[cholt]

Did anyone ever find a solution to this issue? We are having the same problem here with a new install.
Fog .32, Ubuntu 12.04.4 Windows 7 Pro images coming from identical model machines.
Error is "Invalid Operating System id (i5)

[jbsclm]

It is a problem with the fog.capone script. It has been fixed in 0.33 however the 0.32 problem is documented here with a fix.
[url]http://fogproject.org/forum/threads/capone-and-fog-0-32-not-working-errors.192/#post-762[/url]

essentially.
copy init.gz (just in case it all goes wrong)
uncompress init.gz
mount it
edit /bin/fog.capone as per the instructions
unmount init.gz
compress init.gz

Hope this helps.

PS
the modified fog.capone is in the link above, which will save you editing it.

[cholt]

Thank you for the link.

I followed all the steps and now the capone module shuts the machine down after displaying
…
Starting network…
ip: RTRNETLINK answers: File exists
/etc/init.d/S99fog: line 72: /bin/fog.capone: Permission denied
The system is going down NOW!
Sent SIGTERM to all processes
…

So it just shuts down in a huff.
I just copied the file over after using the Boot Image Editor utility. (had tried editing using the manual method but figured I was screwing something up that way)
Do I need to change permissions on the fog.capone file in the zip? If so, what should they be changed to?

Sorry, my UNIX classes were 1986 or so and I may be a little rusty.

Chris

[jbsclm]

Hi Chris
That rings a bell.

If you copied the file in you’ll need to chmod the file, as it probably got dos permissions, which don’t come across into unix ones.

If you go to the folder and do
ls -l
it will tell you what the others are

ls -l fog.capone will give something like
-rw-rw-r–
which is 664, ignore the initial “-”, it is the sticky bit.
it will tell you what the others are, fog.capone needs to be the same.
At a guess they will be either 755 or 777

to set them you do

chmod 755 fog.capone

also check the ownership, and change as necessary with

chown <username> fog.capone.

at the end it should look the same as the others.

[cholt]

755 matched them all up. Owner/group of all files was “root root” already.

Okay, some progress?

Now I get:
/etc/init.d/S99fog: line 72: /bin/fog.capone: not found

I looked and line 72 is:
$run;

Which appears to be the result of else if on line 56-57:
elif [ “$mode” == “capone” ]; then
run=“/bin/fog.capone”;

Which looks peachy to me. Thanks for sticking with me on this. I’m going to get it one way or another!

.<
Chris

[jbsclm]

It sounds like the name is wrong, but it looks right.
I’ll grab a copy of my working init.gz for you later today, and stick it on google drive for you.

[jbsclm]

My init.gz fixes the problem for 0.32, if anyone else needs a copy send me a message.