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

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.

@Sebastian-Roth

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

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

@Wayne-Workman sure! Thanks for your help!

@sebastian-roth It’s beautiful!
Thanks for figuring that out!

@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.

@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.

bonsoir george, stp excuse moi de venir ce soir te poser ce problème,

je veux déployer mon image sur une machine physique mais cela ne fonctionne pas. voici l’erreur que je reçois.

la marque de mon ordinateur c’est un dell latitude et en passant, mon serveur est sur une machine virtuel et j’ai connecté ma machine cible directement sur la machine physique qui abrite mon serveur fog sur virtual box. par quelle moyen savoir que ma machine physique est bien connecté à mon serveur virtuel???

@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.

@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.

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

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

Well Congratz lol!

@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!

Thanks, Wayne!

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

@marted Just want to keep this topic up as it might be very helpful for others. Not sure if you have time and access to systems right now though.

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!