Hello everyone,

I am currently testing the FOG Project working-1.6 branch on a fresh installation of Debian 13 (Trixie) and encountered a fatal error during the installation script. I wanted to share the bug and a proposed fix.

The Issue

During the package installation phase, the installer fails with the following error:

Installing package: sysv-rc-conf............................Failed! (Will try later)
 ...
 sysv-rc-conf:amd64=0.99-10 is selected for install
 sysv-rc-conf:amd64 Depends on sysvinit-core

Because Debian 13 uses systemd, trying to install sysv-rc-conf forces the package manager to attempt installing sysvinit-core, which conflicts directly with systemd-sysv. The OS prevents this to avoid breaking the system, causing the FOG installation to halt.

The Cause

In /lib/ubuntu/config.sh, the variable sysvrcconf is hardcoded for all Debian versions:

bash
if [[ $linuxReleaseName_lower == +(*bian*) ]]; then
    sysvrcconf="sysv-rc-conf"

Proposed Fix

Since sysv-rc-conf is completely obsolete on modern Debian systems, we should exclude it for Debian 13 (and newer). I modified /lib/ubuntu/config.sh on my machine as follows, which allowed the installation to finish successfully:

if [[ $linuxReleaseName_lower == +(*bian*) ]]; then
    # Exclude sysv-rc-conf for Debian 13 and newer
    if [[ "$OSVersion" -ge 13 ]] 2>/dev/null; then
        sysvrcconf=""
    else
        sysvrcconf="sysv-rc-conf"
    fi
elif [[ $linuxReleaseName_lower == +(*ubuntu*|*mint*) ]]; then

I hope this helps anyone else trying to deploy FOG on the upcoming Debian releases, and perhaps this check could be merged into the repository for future compatibility.

Thanks for all the great work on FOG!

Hello everyone,

I am facing an issue with image capturing after performing an upgrade on my FOG server from 1.5.10 to 1.5.10.1886. Before the update, everything worked fine for me. The images were stored directly on the Synology NAS.

My Setup:

FOG Server: IP 192.168.10.220 (Debian 13)

Storage: External Synology NAS with multiple virtual IPs (192.168.109.220 and 192.168.110.220).

Storage Configuration: The Synology NAS is configured in FOG web UI as the Master Node for its storage group. The local Default storage node is NOT the master.

Clients: Multiple clients on different subnets (e.g., 192.168.109.23 and 192.168.110.23).

The Problem:
The Partclone phase finishes successfully on the client machine. The image files are correctly uploaded via NFS directly to the Synology NAS into the /images/dev/[MAC_ADDRESS] folder.

However, right after Partclone reaches 100%, the task gets stuck in the FOG Web UI (at around 70%), and the client screen shows the following PHP FTP error:

Error returned: Type: 2, File: /var/www/html/fog/lib/fog/fogftp.class.php, Line: 709, Message: ftp_put(/images/dev/[MAC]): Failed to open stream: No such file or directory, Host: 192.168.110.220, Username: foguser

What I have verified:

I tested the FTP connection manually via CMD/PowerShell from a PC using the same foguser credentials. I am able to log in, mkdir, rename, and rmdir inside the /images and /images/dev directories on the NAS without any permission errors.

If I move and rename the MAC folder manually inside Synology File Station from /images/dev/[MAC] to /images/[Image_Name], the image works fine.

This setup worked flawlessly before the FOG server upgrade. The /images directory is NOT mounted locally on the FOG server itself (and never had to be).

Verified FTP username and password on NAS and FOG. It's same.

It seems that fogftp.class.php is incorrectly triggering ftp_put (trying to read a local file from the FOG server) instead of doing a remote ftp_rename directly on the NAS storage node.

Has anyone encountered this bug after a recent upgrade, or is there a specific setting in the new version that I missed?

Thank you for any help.

Storage Node for NAS

Error on PC

Has anyone tried this? It would be very useful for my organization. Any guidance on what files to manually replace/edit?

Czech language code cs-CZ

### SHUTDOWN PROMPT ###
{company} je vyžadována údržba tohoto počítače.
Uložte prosím Vaši práci a ukončete všechny programy.
Zrušit
Skrýt
Odložit
Restartovat nyní
Vypnout nyní
Odložit o
X hodin Y minut Z sekund

### NOTIFICATIONS ###
Vypnutí přerušeno
Vypnutí bylo přerušeno
Vypnutí odloženo
Vypnutí bylo odloženo o {time}
K vypnutí dojde v {time}

Chystáte se odhlásit
Pokud zůstanete neaktivní, budete odhlášeni

Instaluje se {snapin name}
Prosím nevypínejte počítač dokud nebude dokončeno.

{snapin name} byl instalován
Instalace byla dokončena a je nyní připravena k použití

@Sebastian-Roth Thank you very much. It worked. Now everything is ok.

Hi,

i have this issue. After upgrade from Fog 1.5.5 to 1.5.6 not work rEFInd.

In 1.5.5 works all fine. HP workstation boot from UEFI PXE, FOG did not task and then normaly load Windows 10.

In 1.5.6 HP workstation boot from UEFI PXE ok, FOG did not task and then freeze on line “rEFInd - Initializing…” and nothing happens. I wait 5 minutes. Keyboard not response. Only powerbutton on pc case power off computer.

I tried change in /var/www/fog/service/ipxe/refind.conf config to “scanfor internal”. The same problem remains.

I dont know what to do next.

Hello,

FOG work ok. Capture and deploy works fine.

My BIOS (UEFI) boot order:

1. PXE IPv4 Intel
2. SSD M.2 Windows loader

After deploy Windows 10 Pro x64 to PC (HP Z2 Tower G4 Workstation), change BIOS boot order to:

1. SSD M.2 Windows loader
2. PXE IPv4 Intel

How to prevent change BIOS boot order after deploy?

Thank you for your advice

I would also be interested. You have tried this tutorial?

Include any ISO in the FOG Bootmenu - Hirens

Solution my problem:

1. tips of Sebastian Roth:

mkdir /home/fogbackup/
chown fogbackup:fogbackup /home/fogbackup/

2. change config file /etc/vsftpd/vsftpd.conf

vsftpd_log_file=/var/log/vsftpd.log
log_ftp_protocol=YES
allow_writeable_chroot=YES
chroot_local_user=YES
chroot_list_enable=YES
chroot_list_file=/etc/vsftpd.chroot_list
rsa_cert_file=/etc/ssl/private/vsftpd.pem
rsa_private_key_file=/etc/ssl/private/vsftpd.pem
ssl_enable=YES
force_local_data_ssl=NO
force_local_logins_ssl=NO

Hello,

I would like to create a new FTP user ‘fogbackup’. Lock (jail) on own home directory.

Install: Debian 9 + FOG Project 1.5.4

I use:

useradd fogbackup 
passwd fogbackup
usermod -d /home/fogbackup/ fogbackup
service vsftp restart

Use FTP client (WinSCP from MS Windows) and can’t login: authentication error.
I read wiki: https://wiki.fogproject.org/wiki/index.php/Troubleshoot_FTP
And as FOG user i can login successful.

What am I doing wrong?

Thanks for help