3.13 that comes on the latest dev-branch as of today has issues with APFS on my laptop.

3.20 x64 does not

@george1421 .The problem is with partclone 3.13

Version 3.20 appears to work.

I am using CloneZilla Live to get the mac drive copied to an external. Can you guys add partclone 3.20 for FOG?

@george1421 I guess it may be a while until partclone gets sorted. It looks like

Should I capture as a raw image? Clonezilla live 3.0 claims to support apfs and at one time I was able to capture both drives on the laptop sort of recently. IDK

@george1421 Hello George,

I was running a debug prior to posting this thread.

This is the error (from OP) when trying to capture the APFS partition on the mac OS SSD, which is /dev/sdb.

The Microsoft EFI boot files as well as the mac OS bootloader are located within the EFI partition on /dev/sdb, the mac OS drive.

Here are the results of the fdisk on both sda and sdb

Green blocks - blocking my face in the reflection.

Task - debug - host primary disk set to capture /dev/sdb. Image type is the following

I also tried “Apple Mac Os” as the operating system instead of “Other” but got the same results.

It captures the EFI on /dev/sdb fine

But same error when it tries to capture the APFS partition

For whatever reason there isn’t a partclone.log in /var/log/ this time either.

@george1421 Thanks, okay got it.

I’m running into trouble capturing the mac OS SSD on my laptop. Hackintosh.

diskutility doesn’t see any problems with the mac OS SSD, no problems with the drive on the FOG server. If I set FOG to capture All drives, all partitions, not resizable it will capture the Windows SSD fine and the EFI partition on the mac OS SSD, but fails when backing up the APFS partition(s) So to save time, I just tried backing up the mac SSD. Same problem. EFI fine, APFS fails.

Here are some pics if it helps.

Latest dev-branch version: 1.5.9.154 on Ubuntu 21.10

I looked for /var/log/partclone.log on the FOG box but it was not there.

Pics linked below

https://imgur.com/a/b2PgLvO

Thanks

edit:typo

@sebastian-roth - Ubuntu, 21.10 - I saw 1.5.9.138 was out. I installed that over 137, no error messages during the install and was able to capture!

@sebastian-roth The error during the FOG install on 21.10 is related to installing php 8.0 mysql

If I try to manually install php8.0-mysql it appears to be installed already

The GUI works fine and capturing an image goes smoothly until the end where the database needs to be updated

Wow, so I ran the FOG installer again, this time there wasn’t an error when it came to the mysql install.

Going to try capturing an image now.

Hmm. It still fails to update the database.

@sebastian-roth Going through the process again. Now with the FOG 1.5.9.137. Will take screen caps and can upload log files if you’d like. Just let me know which files to upload.

@sebastian-roth Unfortunately I didn’t pay much attention as it was the same error as usual when running the installer under 21.10. Error updating dating base. Then the same thing after capturing. If I get a chance to test again I will and take screen caps.

@sebastian-roth I updated to the latest dev-branch (on Ubuntu 21,04) and was able to access the GUI. However, right after the update, when going to the FOG web interface it was no longer able to contact the server to determine the current version. I didn’t go any further, instead I made a snapshot and am updating to 21.10 to see if that works.

Update:

21.04 with the latest dev branch appears to work fine so far for capturing a win 10 image. 21.10 - GUI is now working if you install the latest dev branch after updating ( if you have the latest dev branch and upgrade to 21.10 no GUI). But error with updating the data-base during the install and after capture are present. But I am sure you guys knew that cause that part hasn’t been updated.

@george1421

Thanks. Setting it to 7 did the trick. Was the default always 5 or… ?

Hello,

I have been capturing images of my OS drive every few days for a while now. The last capture was on the 14th. Two days ago I updated the dev branch to1.5.9.122 and when I tried to capture from the OS drive,a few minutes ago and got an error. chkdsk shows the drives is clean. The error was …Not enough MFT space. I so I did a debug and captured. I have no idea where the debug log is located, I just see the usual FOG Linux Service Logs which don’t have any info about the error I could find.

I have some pics though.

The system has 2 NVMe drives so the host primary disk is set to the drive size (250059350016)

I’ve since run Privazer on the Win 10 drive and cleaned the MFT and $Logfile but the same error occurs. Although it does notate a different New Volume size

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

@quazz

OH! Okay cool cool. Thanks

@quazz

The PHP 8 portion of the FOG upgrade / update went fine. It was when it came to the database.

@wayne-workman Thanks I do run it in a VM and took a snap-shot prior to the upgrade. It’s just I have other services and things running on the box too so it’s not just FOG I would have to migrate.

Hello,

I am wondering how to resolve this problem. After updating from 04 to 10 I rerun the fog installer and run into problems updating the database and the web interface never shows up. I thought about doing a fresh install but… IDK,

If you explain how to get logs and whatever else you need I can.

Thanks

Notifications no longer load. It just spins and I have to choose See all notifications.

https://imgur.com/OaaF1Xn.jpg

I disabled all my browser extensions, disabled shields up (Brave), cleared cookies and cache and bypassed pi-hole but the problem still persists. Nothing has changed on my end. I have been away from the site for a few month and noticed it when I came back a few days ago. Anybody else have this problem.

I am using Version 1.33.106 Chromium: 96.0.4664.110 (Official Build) (64-bit)