Topics created by Fog_Newb

@Tom-Elliott All good with 1.5.10.1629

Thanks

@JJ-Fullmer @Tom-Elliott

I’ve found a work around. I now have /images on USB HDD passed through the to VM. When I run a standard back up of the VM via the VM software (Virtualization Station), it only back-ups the OS VM drive.

For the /images drive - I use a sync program to back-up the files, not the disk .

@Tom-Elliott

Yes, I even spun up a new FOG VM where the mount points were created before FOG was installed to makesure the FOG installer created all the files and set permissions.

edited - words

@Tom-Elliott

Ok thanks

@AUTH-IT-Center Should be addressed in the latest.

@Tom-Elliott

Thanks Tom, that fixed it right up. I guess I overlooked that file when copying everything from the original /images.

Yeah, that fdrive number… 🙂 It is the serial number of the drive.

The NVME drives initialize differently each time during boot. I guess that is a thing, so nvme0 would sometimes be nvme1. It was a mess. Then I learned drive size could be used to differentiate between drives under Host Primary Disk. Now that both of my NVME drives are the same size, I have to use the drive serial number.

@george1421

Thanks George. No but I will now that I have time machine back ups. Can I use mac-boot to create the stick then just update those 2 things?

@Sebastian-Roth Unfortunately the USB external drive wasn’t see by FOG, I tried the serial number listed in Windows but it backed up an NVMe drive Please disregard

@Sebastian-Roth Yes. Thanks

@george1421 Cool. Is the T2 Kernel known to address this specific issue?

@fog_newb said in Strange formatting when selecting host. Dev Branch1.5.9.207 Ubuntu 22.04.1 LTS:

I saw Partclone 3.20

Yes that is the version that contains the updated code for apfs support. So it should clone apple based computers beyond getting access for the T2 chip.

@sebastian-roth I just noticed .177 was out and updated. No errors at all during the update process.

@sebastian-roth I figured it was something like that. The good news is FOG is working for me under 22.04.1

@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