@Clifford-Raymond I did pretty much what these guys are telling you as well. After I initially upgraded and got the errors, wayne told me to uninstall mysql and reinstall it so I did. Then he told me to update my OS, but I went a step further and went ahead and upgraded from 12.04 to 14.04. After all that finished I was still getting the problems so I re-ran the installer and it took me a couple of times to but it finally worked itself out. I can’t really point to any one thing in particular that fixed it. Even after I first got it to working it was a little buggy (couldn’t search hosts or use host menu), and if I restarted the machine I would get the errors again. So I pretty much did everything except uninstalling and reinstalling mysql a couple of times and so far it is all good. Not sure, but I hope that helps some.

@Wayne-Workman Ok it is now back to working just like it should. Thanks Wayne

Ok, nevermind. I was inadvertently installing a x86 kernel and I tried installing the x86_64 kernel and it solved the problem

I went and did a system diagnostic in my bios after you said this and it was my memory. I removed it from the slot that it was in and placed it into another slot on the MB and everything seems good to go now. Thanks for the tip.

@george1421 so could it just be that I need to edit a file that points the /image directory to the other drive? If so, which file do I need to edit?

@george1421 I’m just curious, but why do I need NFS if the storage is local to the fog server? It’s just a 2 TB hard drive installed on the server.

I updated my fog server yesterday. I was on Ubuntu 12.04 and had to do a fresh install of 18.04 and did a fresh install of fog 1.5.8. On my previous setup, I had my OS on a small SSD and my /images was on a 2TB HDD. After I set it up again, the /images folder was on my SSD so I had to move it back to my HDD. The images from my previous fog setup are still on the HDD, but I’m getting the error message "can’t mount /images folder (bin/fog.download). What am I missing?

@Tom-Elliott Yes

@george1421 Ok, figured it out. I didn’t pay close attention to the computer after running chkdsk. It would reboot and try to start, but it would just boot up normal. Tried it on second image and it did actually run the chkdsk on reboot an I was able to capture then. But your right, I couldn’t find much of anything on that error either. When I scanned the drive with chkdsk, I did see an error about incorrect bitmap for a volume so that’s what it was

@george1421 I ran chkdsk and no errors. I also ran diagnostics on the system and no errors. I sysprep’d it and used that shutdown command, still the same error. These are new to us, off lease machines with brand new SSDs installed. So far I’m 0 for 2. I have the same machine with windows 7 installed with HDDs and no problem. I am assuming that I should be using the OS id for windows 10 correct.

What are the file attachment size limits again?

First off it gets through a 900MB partition and just sits there for 5 mins, then it starts to go forward. It goes to reading super block and calculating bit map…please wait…ntfsclone-ng.c: used blocks count mismatch: 8232062 in header, 8232063 from readbitmap.

I haven’t run sysyprep on the machine yet, just wanted to run it through this first incase something messed up and I needed to have a backup. Anybody have any ideas on that error?