@Sebastian-Roth Interesting. I’ll keep that in mind. Thanks.

@Sebastian-Roth Yes. This mine was set up a couple of years before I became in charge of it. The other motherboards I have all have resizable images and they work fine. Does the regular non-resizable image take up less space than the sector-by-sector image?

@Sebastian-Roth Awesome, thank you. I have actually deleted the existing image because it was fubar anyway. I have created the new image as “sector by sector” and it is currently capturing right now. I’ll post back whether it works or not.

Thanks again! I hope this works. It took another two hours for me to get the rig to mine again. Windows is so damn finicky with drivers, I hate it.

EDIT: It worked. Thank you!

It’s not really a non-standard Windows install. It’s really just Windows with a few mining apps installed. There are only the regular partitions that Windows creates when you install it. I have two other types of motherboards I use for mining that I can image and capture all day and they work fine.

Someone on the reddit did actually comment and they suggested the same thing, doing the raw capture without the resizing. I will certainly give that a shot. However, I’ve just spent the last 20 minutes looking around in the webGUI and I can’t find how to make it do the capture without resizing. How do I do that?

Thanks.

Hi guys. I posted this on the reddit as well but I noticed it seems to be pretty dead there and it says that this is the place where everything happens so…here I am.

I am running a crypto mine and I use FOG to image my rigs. I have a particular type of motherboard that I have to fight with to make it work. Getting it to mine in the first place is an exercise in frustration but that is neither here or nor there. The problem I’m having is, after all the fighting and hair-pulling to make the rig mine, FOG ends up breaking it.

I had this one rig mining all day to make sure it would work before I captured the image to deploy to the rest of the boards of the same type that I have. However, once the capture task had completed and the rig rebooted, it would no longer boot into Windows and kept boot-looping until it started auto-repair and then just shut down. It has done this at least twice already and each time I make it work and try to capture an image…well, we all know Einstein’s definition of insanity, right?

It is my understanding that the only change FOG makes to the drive from which it captures an image is to resize the partition to the amount of used space to make the image as small as possible. Why then does capturing an image off this rig break the Windows installation and cause it to boot-loop? What is going on and how do I prevent it? I’m ready to throw things through windows, here.

Help, please.