Best posts made by ty900000

Hey guys, since PartClone got updated in 1.5.7.86 I can no longer take images.

@george1421

I added a Cisco switch in the mix, but I couldn’t get it to pass any traffic, even from the switch itself. I don’t know if adding a layer 3 switch into the mix confused everything?

Anyway, I’ll wait until we get new equipment and then debug it from there, like you suggested. We’re going to be reimaging multiple machines at a time before we get new network equipment anyway, so I most likely need to get a RAID 10 set up.

Once we get new equipment in, I’ll give the Multicast a shot and then reply back to this thread. But, that’s way in the future. Probably several months or more.

I appreciate all the help you guys have put in to this! Thanks a bunch!

I am having a few issues and I don’t know how to resolve them. And they are making me wonder if this configuration is even viable for general usage.

One of the issues I am having is if I enable the Apache rewrite to HTTPS, when I try to inventory a machine or deploy an image and when FOS adds/checks the MAC address, I get an error that states “No viable mac to use.” If I disable HTTPS rewrite, it works first time, every time. I don’t know if a FOG URI needs to be excluded from the rewrite, like I had to do for iPXE to boot. I have a hunch this might be an easy fix?

The second major issue I am having is even if I disable HTTPS rewrite and the SSL certificate checks, I get the error in the attached image. I even just did a base Debian install using 1.5.7.88, none of my extra code, and I still got the error. Don’t know if I am doing something wrong? I know all the Linux installs I have been testing with have more than enough space to captures images, even a full disk, non-resized image. And it’s typically the ‘raw’ partition or the ‘ntfs’ partition of a Windows Server image. It’s all very strange…

@Sebastian-Roth

I think I managed to do it properly. Let me know if I need to change anything. Thanks!

@Sebastian-Roth

I’m sorry! I had to backtrace this information, if you still want it: FOS 112 had the segmentation fault, FOS 113 had the segmentation fault (also tried the debug with this one), FOS 114 captured without the segmentation fault and introduced the unset_name [OPTIONS] error during capture and subsequently the /dev/sda3 error during deployment, and FOS 115 reintroduced the segmentation error.

I can redownload FOS 114 files and test with those again, if need be.

@Sebastian-Roth

Yes, sir! My apologies for not doing this sooner.

https://forums.fogproject.org/topic/14116/development-fog-not-capturing-image-partclone-update