Posts made by pixomondo

@Joe-Schmitt
Thank you Joe. Following the steps as described in the wiki worked and fixed it. At first I wrongly assumed that I only temporarily disabled the service and it fixed the issue. Turned out the service needed to be started again after sysprep.

I’ve tried it the suggestion posted but changed it a little bit. In the past I used to deactivate the fog client to prevent it from rebooting the machine while sysprep was running and this seemed to have fixed it again. No other steps were necessary in my case.

Thanks

As the legacy client is having issues at the moment (HostnameChanger globally disabled), I’ve upgraded to the latest version of the client on my master image. Install worked well but as soon as the fog prep VM reboots after sysprepping, I get the 'The Computer Restarted unexpectedly or encountered an unexpected error" error.
This is the same for the fog prep VM as well as all nodes imaged with the newly created image.

I went back to snapshot prior to the install of 0.11.8 client and it works well, reinstalled the new client and created a new image and it fails again.

Any insight to why this is happening?

Felix

I created a new group and it worked.
Can be marked solved.

Thank you

@Tom-Elliott
Uploading works now. Thank you.
I will check group deploy tomorrow once all downloads have finished.

Any other ideas?
I’m getting the same problem when trying to upload an image.

Failed to start tasking type Capture
Could not find any nodes containing this image

http://i.imgur.com/JE9uG0n.png

I mean hosts=servers in my case. Sorry for the confusion. I am imaging computers that are running on server hardware, that’s how it was meant.

Hello,

I can image single servers the way I always used to do. I basically queued up 180 servers one by one and that works well. Just the imaging of the group (no multicast) causes problems.

Random question for you, my transfers times of the image used to be around 22-25 minutes per workstation/server, since version 1.3 it went down to 5 minutes. Do you know why it’s that much faster now?

Thanks

Removing the wake on lan option solves the problem that I have with single nodes. I can manually image all of them now.

I have a few servers where I get this message: “Could not find any nodes containing this image” that are part of that group

I can’t post to bug reports, so sorry for my multiple posts.
Just created a group with two servers in them and have the same issue.

Server

• FOG Version: 1.3.0-RC-23
• OS: Centos 6.8

Client

• Service Version: ?
• OS: Windows 7

Description

When I try to image a group I created in 1.2 then I get “Theres no image definitions available on any node for the hosts in this group”. Imaging a single node works fine. All members in the group have the same image associated.

This is after upgrading from 1.2 to 1.3.
I am trying to image 120 servers so the group option is the only option viable.

Thank you

Seems like the vmdk-flat is failing when I try to copy it. Never had a storage device fail so selectively. I am copying it from an older backup now to a new hard drive.

Thanks for your help.

Hello,

I have moved my ESXi guest image to a new host with an SSD. Since then my image starts to fail to upload with a read DMA error at 95%. I’ve setup a new server with the latest version of FOG but I still get the same error. Has the image been corrupted during transfer? Is the SSD at fault?

Here is a screenshot of the error (this is from version 0.32):
http://imgur.com/hHStgPX

Thanks,
Felix

The latest stable build does not seem to be affected. Only Rev 5020 from the SVN repo showed this behavior.

Same problem here. The folder exists but no content and install won’t continue.
I am not upgrading though, it’s a new install on a new server. Centos 6.7.