@Tom-Elliott said in Version 1.6.0-beta.3187 ipxe 2.0.0.x problems:

secureboot/snponly.efi

Nice work! I had exactly the same problem (see the other thread), and adding “secureboot” to the boot file fixed the issue (even though Secure Boot is actually disabled in the clients’ BIOS)

Hello, I’m taking the liberty of jumping into this conversation because I’ve been having a similar issue for the past few days: everything was working fine a month ago, but I’ve updated FOG several times since then (currently on 2218) and I’ve realized I can no longer deploy images; I get an error message:

No filesystem could mount root, tried ext4
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)

I modified the “Kernel Ramdisk Size” value to 512000, tested various EFI/iPXE boot files (snp, snponly, intel), and tried rolling back to the master or stable versions (running “git pull” followed by “./installfog.sh -Y” each time), but I encounter this message in every case.
I had to restore my Veeam backup (dev-branch version 1894) to get it working again (I didn’t test other intermediate versions).