Multicasting -- Image Fails After Completion
-
The same processes, as far as partitioning and resizing happen identically regardless of imaging medium (Uni/Multi cast) The only time there’s a difference in how partclone receives the image. You’re 100% sure the same machine and same image works with unicast but fails with multicast?
-
@Tom-Elliott said in Multicasting -- Image Fails After Completion:
You’re 100% sure the same machine and same image works with unicast but fails with multicast?
I’m 100% Positive! In fact I Uni-casted to one of the 5 that failed last night and verified it was working this morning. Then this morning I tried multicasting just to 1 of the 5 test machines and it failed with the screenshot posted here.
Are their any other logs you might need?
-
Any ideas on this one?
-
@Tom-Elliott
@Developers
Just updated to FOG 1.4.2…Re-ran multicast on machine that bombed earlier… Same problem.
I created a new image on a different machine type and thought I’d try and push it… Got a new issue…
How do we resolve this one? Maybe they are connected… Ugh…
-
I figured out that issue… Going to retry the new image and see if the other issue comes back.
-
@Tom-Elliott
@Developers
@george1421Apparently yesterday I made two images that were empty. The GUI shows that one has data and the other has nothing in it. Everything appeared to finish normal. I’m at a loss on this one.
I’m going to try and capture a new image and see what the heck is going on.
The other images pushes fine from uni-cast just not fine on multi-cast… don’t know what the heck is going on.
Any advice is appreciated as I’m dead in the water.
-
I did check the /images directory from the terminal and it shows no directory created. Just a file with the images name…
-
@Joe-Gill look in /images/dev to see if there are any directories in there titled by the mac address of the target computer.
-
@george1421
The MAC address from my captured target machine is there.The images seem to push fine via unicast. I’m still having problems with MultiCast.
I have tried pushing to multiple labs, just to make sure their isn’t any underlying problem with a switch, and I’m still having the same issue. The image appears to push, but when you start the machine, you get the message below.
Any ideas of what to try would be helpful… Thanks!
-
@Joe-Gill Multicast ALWAYS comes from the Master node. Unicast can vary and change which node the image is pulling from. If unicast works, can you try to get it to image from either of your nodes to determine if it is specific to multicast or the master node doesn’t have the full image information for some reason?
-
@Tom-Elliott
So I can see it’s pulling the image from the Master Node on at least one occasion that was successful. Let me see if I can push an image from the node. -
@Tom-Elliott
So I created a new storage group with my storage node on it and nothing else. I set the image that I was having issue with multicasting to that storage group. Then I pushed the image via UniCast and things worked fine from the storage node.I will re-push this same image and change the storage group back to the server and see what happens…
Joe
-
Well, the image I pushed via the server works just fine unicast.
Now, that said, I make a pre-sysprep image (one prior to running sysprep when it’s in audit stage) and one post-sysprep prior to reboot. The pre-sysprep image is stable and pushes via multicast. The post-sysprep image fails. SO… I’m going to re-capture my image and try again. Ugh… Glad to hopefully resolve this one.
Thanks for making me think, as usual.
Cheers,
Joe
-
The resolution here was the following…
My image WAS corrupt. It DID image just fine with UniCast. I remade my image and all is happy. I also made an adjustment to the resize option on my image. I set it to be resizeable.
I’m all going good now. All is happy.
Just in time for my server upgrade!! I’ll be installing Debian here in the next couple days…
Cheers!!!
Joe Gill
Townsend K-12 Schools
