@x23piracy Mark as solved is only available for moderators and developers and such, to prevent people from solving too early and what not.

@Sebastian-Roth
Gr8 news. Thx a lot

Tom has fixed the issues and I am 100% up and functioning

@Tom-Elliott helped out, it was a bug in replication. It should be fixed in the current.

@Wayne-Workman sure! Thanks for your help!

@mimi1255 If your current issues are not related to the original problem in this thread, please start a new thread - and we will gladly help you there.

@tlehrian It would be really great if you could test this fairly soon so we have a little bit of time in case it needs further work. The earlier we know the better! We can’t guarantee a quick fix some time in January when you really need it.

@Sebastian-Roth

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

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

@george1421 I was able to edit the Grub.cfg and add our Fog server IP in and then boot with USB and register and capture and deploy. Thank you again for all the help.

The known good systems were extremely slow as well just like the new one using 3.12

I would like to have a link

Well Congratz lol!

That did work!! Hallelujah! Thanks vinyard and Tom!! I ran the following commands and now its uploading that first image:

systemctl status nfs-server
systemctl enable nfs-server
systemctl start nfs-server

Thanks guys, success at last!

@Uncle-Frank You’re amazing! What you posted is very similar to what I came up with in a thread, but I haven’t gotten around to testing it.

If you get dnsmasq to work with co-existence then you’re like… everyone’s hero… for real. Because if we can get a rock-solid dnsmasq config for all types of booting - then for 95% of fog setups out there, we’ve eliminated the need to change DHCP. Fog can then come with dnsmasq setup by default and it JUST WORK without further setup.

In my opinion, Linux DHCP is far superior to Windows DHCP… but dnsmasq would be the ultimate solution if we could just get it to work.

@Pascal-Gazaille Does this mean all the symptoms of not being able to deploy to the new disks disappeared?? Scratching my head… Will mark this solved for now anyway.

Thanks, Wayne!

Any other scripts I an run or ideas to get some usable info towards troubleshooting?

@sebastian-roth

Hi sorry, I couldn’t answer any sooner.
“Nevertheless we ought to try out using the SNP binary (debug enabled - DEBUG=snp:3,nii:3 to start with). So find 01_snp.efi here. Just give it a try and post pictures or video. Make sure when you take those to place the camera or phone on a stack of books in front of the screen so we have a good picture.”

Here you go, not much to say from my side but here goes: video

Thanks!

@lebrun78 Just be aware there is no way back to the 1.5.x version of FOG if you switched to working-1.6 now other than very messy manual manipulations in the database. We are working towards 1.6 and hope to have most users upgrade at some point. So I am not saying you shouldn’t. Just want to make sure you understand the consequences.

@Sebastian-Roth Sadly I am out of surface go’s to test at this time. Gotta get the ones we have in production.