@Tom-Elliott Tom, looks like everything has been resolved after going from 2144 to 1.5.10.2218! No errors and I was able to capture no problem. Thanks

@Tom-Elliott Hello Tom, I had posted a pic of the RAM0 error. Since I reverted to a backup of 2144. I no longer get any errors so I can’t take a new pic but here is the original pic with 2191 installed - (see below). I will try 1.5.10.2213 as soon as I can. Perhaps tomorrow evening?

The laptop is booting UEFI. It runs windows 11 with secure boot disabled and TPM requirements disabled during install.

Here is a text translation of the error in case you are unable to view attached photo.

RDSEED32 is broken. Disabling the corresponding CPUID bit.
ACPI BIOS Error (bug): Failure creating named object [_SB.PCI0.GPP5.WLAN._PRR],
AE_ALREADY_EXISTS (20250807/dswload2-326)
ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20250807/psobject-220
)
pcieport 0000:01:00.0: Unable to change power state from D3cold to D0, device in
accessible
pcieport 0000:02:00.0: Unable to change power state from D3cold to D0, device in
accessible
Kernel panic - not syncing: VFS: Unable to mount root fs on “/dev/ram0” or unknown-block(1,0)
Kernel Offset: disabled
—[ end Kernel panic - not syncing: VFS: Unable to mount root fs on “/dev/ram0” or unknown-block(1,
0) ]—

“2144 good, 2191 bad”

Yes, that is the kind of in-depth analysis I am known for.

@Tom-Elliott I’m sorry. I restored a previous version of the FOG server and no longer have any error logs from when all this happened. I can go to 1.6… IIRC there is a change that needs to be made to SSHD conf or something. The last time I went to 1.6 FOG was unable to see the default storage node.

Everything working fine until this latest FOG update. Using a Strix Point laptop with a USB Ethernet adaptor. Also trying to install different kernels through the web UI no longer works. HTTP ERROR 500

I tried installing master branch. Failed, couldn’t even boot to memtest. I restored the FOG VM from a back up made a few days ago. 1.5.10.2144 - everything is working as normal now. Afraid to update

Just thinking, sometime between the 1.5.10.2144 backup, there were tons of dev updates, and one time when I did a git pull on FOG, it deleted a bunch of things. But since the gui worked, I assumed it was okay

FOG 1.5.10.1734

Ubuntu 24.04.3

Booting from the default FOG menu to a Windows host isn’t a problem but Linux… I get errors.

Fresh install of Ubuntu Desktop (EFI). It was installed on a host that was running Win 10 and was able to get from the Fog menu to booti Windows

With Ubuntu and Pop OS I can not boot PXE to the Fog menu to the OS using the stock refind.conf and even this custom one

This error with stock refind.conf and a custom one

Tried making a custom refind.conf

I’m editing the refind.conf on the FOG server /var/www/html/fog/service/ipxe/

Any ideas?

If I wipe linux and install Win 10/11 it has no problem PXE boot to FOG menu to OS

@mmoore5553
Assuming you’ve tried setting the VM to BIOS and UEFI and still no go… Do you have the VM set to use a bridged network connection? Also you have to make sure the boot order on the VM is set for network boot first.

@Sebastian-Roth Can I bother you with this quick question ^^^

All my hosts are registered in DNS accordingly, Usually after doing this FOG is able to see which OS the host is running. Almost in real time. Like when FOG is capturing an image from the host, the hosts section of the UI will show a Linux icon, then after it completes and boots back into Windows, it will show a windows icon. But this new laptop running Win 11 with a USB to Ethernet PXE adapter ,the OS Icon is just an exclamation point that says unknown. I disabled the firewall and refreshed the FOG UI but it still shows unknown. When an image is being captured from it, it shows Linux as the OS What do?

Thanks

I have a Win 11 install that isn’t using bitlocker and the TPM and secure boot requirements bypassed but it is using Windows Hello biometrics to log in (fingerprint). Are there any caveats when it comes to basic capture and deploy?

Thanks

@Tom-Elliott Thank you. Logging out with 1.5.10.1730 works properly.

When Logging out of the Web UI I get a “This page isn’t working
10.1.1.100 is currently unable to handle this request.
HTTP ERROR 500”

To duplicate
Click Log Out Of Fog, which directs to this URL http://[ipaddressoffogserver/fog/management/index.php?node=logout

Gives HTTP ERROR 500

Tried on Brave and Firefox

@Tom-Elliott Yes, everything is working as expected. For the longest time, FOG would always show UTC time for when an image was captured or deployed, now it is correctly showing local time and no more zombie processes! Thanks

@Tom-Elliott No worries, thanks for adding that in. I’m going to update in a few to .26 and see what happens. Oh it looks like it is now showing the correct local time on captured images. I’m not sure if this started with .21, .25 or .26. Nothing changed on the system other than updating FOG. This is also excellent!

It’s this http://forums.fogproject.org/post/157404 again.

Thanks all

@Floppyrub said in Wrong target device:

@Tom-Elliott Thanks for your detailed response. I can understand the problem well. On desktops, you can simply disconnect the HDDs if necessary. However, the day before yesterday, I had a laptop with two NVMe drives,

I’ve run into this problem on a PC that had 2 NVME’s, It’s my understanding the reason is, sometimes one NVME initializes first, so /nvme0n is sometimes /nvme1n. If the drives are different sizes, you can specify the size of the target drive / Host Primary Disk (or at least you could). Currently I have 2 NVME’s the same size so I use the serial number of the drive as Host Primary Disk. It works.

Fresh Ubuntu 24.04.3 LTS install running 1.5.10.1721 (started on 1.5.10.1698)

This is what is happening

What to do?

Thank you

UPDATE

I think I may have fixed it. Chat GPT may be a lot of things but it seems to be really good helping with pedestrian level Linux things.

I added this to the Multicast Manager Script under

@error_reporting(0);

// Prevent zombie (defunct) php children
if (function_exists('pcntl_signal')) {
    pcntl_signal(SIGCHLD, SIG_IGN);
}

Then restarted the service. So far it is working. I don’t use Multicast at all so I am not sure if this will impact the way it functions. Does anyone know? @Tom-Elliott

@Tom-Elliott Thanks, going to switch back to 1.6 very soon.