Topics created by Fog_Newb

@sebastian-roth That is on the list of things to do next.

@george1421 Awesome - this worked. It booted from the stick fine and I was able to perform a quick registration. I started to capture the drive and it worked up until it came to the APFS portion. I ran into the apfsclone.c: bitmap error, like with the hackintosh.

@george1421 Not much but… I did a little testing at home. 4 different machines, HP Laptop hackintoshed (all drives, non resizable, Other OS) (one SSD NTFS the other APFS), 2 gaming PCs (win 10 single drive all partitions resizable), A 2018 mac mini all boot security turned off.

And… and !!! I finally migrated, well actually, I made a new FOG server from scratch using only the ltsc.conf from the previous FOG server . I installed Ubuntu Server 22.04.1 fresh in Virtual Station on a NAS, (QNAP TS-451+), latest dev branch with the new inits built in, and was able to capture and deploy from/to 4 home computers no problem. I wish I still had older images and more things to test with.

I love this NAS especially since it was given to me. I dropped in 16GB of RAM (from 2) and got cray stupid -configuring all the drives in a RAID 0 stripe, hey I live on the edge😂 , I can’t believe this thing is running a couple VMs no problem on that Celeron CPU.

@george1421

Hello,

Any luck with incorporating the 0.3.20 into FOG? Also, is there something I can check or turn on the debug/partclone logs? Nothing ever shows up in /var/logs

Thanks

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