Excellent news! I had tried various kernel and boot kernel combinations, but gave up and just used an older version of FOG. It’s nice to know we can avail ourselves of the new version and interface (and just switch boot kernels when needed). Thanks for the update!

Cool! I’m glad to hear that you got it working.

You may have to change (reset) the password in the host OS for the user fog. I had to do that after an upgrade, and that did fix the issue. You’ll need to make sure that it matches what you have set in Storage Management::All Storage Nodes::DefaultMember

Management Username
Management Password

Good luck

Okay - well, this has stopped working. I’m running v.32, but am running the kernel from .29. The machine will appear to begin imaging, the progress bar will move along but will stop somewhere between 50% and 80%. I’ve run top on the server to see what’s going on, and it doesn’t look like it’s really working. The load levels are low.

Anyone have any ideas of things to try? FWIW - these same machines can upload an image fine, even though that takes quite a long time (20 minutes). Could it be I/O related?

Also - the deployment stops while processing the first partition, and even though it’s stopped w/out completing, the display on the client computer reads: image restored

Thanks,

M

Okay - well, it’s worked with two machines now, and that’s all I have to test with for now. Thanks. I’ll have to double check my notes on which netbooks have been successfully imaged with v.32, and which ones with .29. It must be that I imaged this set before I upgraded that fog server (we have 4 throughout the district) to v.32.

Thanks again for your suggestion.

M

I restarted my server after the first failure, thinking that perhaps the v.29 boot image wnasn’t getting deployed. Now when I re-pushed it, it appears to have completed, and went to 100%. Awaiting reboot…

It worked! Wild! Okay - let me try it again with a few other machines…

Rats - crapped out at about 87% of restoring the first partition.

Any other ideas? I can’t tell whether the server is stalling the push, or the client is choking on it.

Is there a way to increase the capacity of the push, or at least to see whether the server is having a hard time keeping up with I/O?

M

I started that process, then realized I could probably just copy the init.gz from an existing install of v.29 to /tftboot/fog/images/ directory.

I’m trying a deploy now - let me know if there’s some other magic I need to do (I already renamed the previous init.gz to init.gz.32, as per your suggestion).

Thanks,

M

Perfect - I’ll try that now.

Thanks,

M

Yeah - I was thinking of trying that, except that I have been successful imaging these sorts of machines with v.32.

I’ll keep tinkering…

BTW - are you suggesting just using an older kernel, or actually converting down to v .29?

Thanks,

M