Topics created by Fog_Newb

@george1421 said in Error capturing Win 10 image after updating to the latest dev version - Resize Test fails:

Would it just create a larger disk image?

Yes exactly.

If yes then 7 or 8 might be a good start if size is the only penalty.

Ok, will 7 do for now.

@wayne-workman

The FOG server is running at home and I forget exactly what else is running on it. KMS emulator, and some other things that are easy to migrate. It’s just… I suck at Linux and I remember making lots of tweaks here and there and the idea of doing that all over again is a PITA to me.

The more I think about it, it wouldn’t be a big deal to start fresh.

@Fog_Newb Notification loads for me in Firefox 95.0.

@sebastian-roth

I used the latest inits and I was able to capture the mac OS drive. I forgot about needing the debug option to get the partclone log.

I didn’t know the dev inits were using the disk size option. I try to keep up on that by going here.
https://github.com/FOGProject/fogproject/compare/dev-branch

Thanks for your time.

@junkhacker

Thank you

@kibade

My memory I really bad but IIRC I ended up having to upgrade to Ubuntu I was on 20.04 at the time

@george1421 said in dnsmasq won't start automatically. [SOLVED]:

@fog_newb Well there are really two commands you need to use.

Enable the service to start every reboot systemctl enable dnsmasq To start the service now systemctl start dnsmasq

These are two distinct actions and one doesn’t depend on the other.

@george1421

Thanks. I have used both of those commands before trying to get it to autostart on boot. I haven’t used them since running sudo systemctl enable dnsmasq , which was the one that got dnsmasq starting on boot for me. Perhaps since I used those commands prior it is all good?

I went through my bash history and saw I almost used sudo systemctl enable dnsmasq I had the syntax messed up though. I used sudo systemctl dnsmasq enable

I am really starting to like Linux. I digress, I am mostly a casual so I doubt I will ever have it on my daily driver but I am thinking about trying it on a laptop. I don’t know though, sometimes, I just like to point and click. 🙂

@sebastian-roth

It was just a hiccup. Running the installer again without git pull there weren’t any errors.

foginstall.log

@sebastian-roth I need to get back into those docs. Things have been just so crazy lately. When you have something working let me know and we’ll get it documented.

@george1421

I figured it out. /dev/nvme1n1

I wasn’t sure how Linux named NVMe’s.

@Fog_Newb said in Odd issue with Win 10 UEFI images after updating from 1.5.9-RC2.15 to 1.5.9-RC2.17:

Nobody else has access to either FOG server and the only change made was the update from RC2.15 to 1.5.9-RC2.17

And automated Updates…

RC2.19 is not much of a difference. Just preparing for the actual release to come very soon!

@Fog_Newb Yes.

@Sebastian-Roth

Thanks.

I see. I decided to just uninstall the fog client and reinstall the latest and point it to the current fog server.

@Sebastian-Roth

Hell yeah dude, that cleared it right up.

I am facing the some problem.
I Got it working …
i Changed the Indle Power Savings to Normal , under Powe Section in Bios

It is not happening anymore. The VM is only 18GB. It takes less than 10 minutes to capture and less than 10 minutes to update FOG. Or visa versa.

The only weird thing I have since noticed is during the install process, when are asked to go to fog/management and hit update database, that page no longer shows up. It just displays the fog login screen. So I just go back to the installer and hit ENTER. It seems to work fine.

Thank you guys. I have now got the latest RC 1.3 and found a problem. I made another thread about it.

@Fog_Newb I am still not convinced you need the acpi=off kernel parameter as you said that it does register properly. Both registration and deploy use the same Linux environment…

The error messages were in the links to the others posts.

This is not of much help. Often error messages seem to be “the same as” but actually are not if you look closely. To be able to help we need a picture of the error on the screen of your machines!