Hi. I am running TrueNAS Scale on a Proxmox VE 8.1.10. 6.5.13-5
32GiB RAM non ECC
4 Processors
QEMU i440fx
64GiB Boot Disk
2X2TB SSD in RAID mirror PCIe passthrough with unique disk ID
Regular updates have been running without issues, 23.10.1, 23.10.2, 24.04.0, but:
While trying to update from 24.04.0 to 24.04.1.1 or 24.04.2 I am constantly running into a Kernel Panic and a checksum error while rebooting. System hangs on startup, but starts up regularly if I select 24.04.0 on the boot menu.
Loading Linux 6.6.32-production+truenas …
Loading initial ramdisk …
error: checksum verification failed.
Press any key to continue ,
Checksum err may indicate a corrupt update file, but twice?
Kernel Panic - not syncing: VFS: Unable to mount fs on unknown block (0,0)
CPU: 0 PID: 1 Comm: swapper/0 Not tainted 6.6.32-production
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996) BIOS rel-116.2-0-gea1b7a073390-prebuilt.qemu.org 04/01/2014
…
end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
No idea what it could be. Should I retry with a manual update file? Should I upgrade Proxmox first? Do I really need ECC RAM? Change something on the QEMU?
I am also experiencing a Kernel panic. From what I understand, this typically occurs when disk passthrough is utilized. However, I have consistently employed a dedicated controller for disk management, as evidenced by the image. Would it be possible to receive some advice on how to resolve this issue?
Do you have a source for that theory for me, that I can look-up? Because I believe that the error: „Unable to mount file system“ in the Kernel Panic rather points to the boot drive, and not to the data pool.
In the second link you yourself posted Christian Lempa first shows how to passthrough the controller (recommended), he then shows hows to passthrough individual disks (not recommended).
I understand his recommendation rather in a context of having a setup with large amounts of disks, and consequently stable I/O in ZFS. My issue seems different: after it worked smoothly, also updated smoothly, suddenly with the latest updates the system does not even boot no more. As far as I understand, mounting of storage should be far later in the boot up process, but my system panics right after the start. Should be rather boot disk related, if it is disk related anyway, but I am lost.
I’m having the same issue, and I’m on bare metal. I tried to upgrade to 24.04.2.2, but I get the same output as above. I finally figured out how to go back and 24.04.0 is working fine. I have no idea how to fix this.
Welcome to the club then. Still no solution found I am afraid. Can you give some details about your HW setup? Processor, drives, board, ram, … Maybe we could help each other. Do you use a dedicated controller?
Have a look at this, too: [NAS-131189] - iXsystems TrueNAS Jira. Indications there go versus the boot disk used or the GUI upgrade feature. This seems more logical to this kind of issue than the mentioned passthrough root cause here.
I also have the Same problem, when upgrading from Truenas 24.04.2 to everything above, but your solution did not help unfortunately. I also have it Virtualized in Proxmox but I have 64GB ECC, 100GB boot disk, uefi, q35, passed through hbas and also bare disks with ID.
I dont know if it is a good move and try to switch to the Electric Eel Train, as many have reported issues with the conversion scripts, and i mainly use Immich and Nextcloud. Both of which have many reported errors after conversion.
Yes it is. What i did is in grub select the old version, enter the command and checked the state of the pool, which was okay. after that i restarted and chose the new Version and still i got the error.
I had a similar issue upgrading from 24.04.2.2 to 24.04.2.5 (and then 24.10 after it failed), and that command didn’t work for me. In the end I managed to get it working by removing the two broken boot environments, downloading the .update file for 24.10 and using the “Install Manual Update File” button.
The kernel panic was apparently caused by a missing a missing initramfs.
