[24.10.0.2] Unable to mount root fs on unknown-block(0,0)

Hi,
On HP Z440 workstation I’ve installed latest version of TrueNAS Scale (24.10.0.2).

Everything was normal and I have set everything up but after reboot I got this “Kernel panic” issue.

First of, i get the message: “truenas checksum validation errors”, and than this:

[  0.482987] Key type encrypted registered
[  0.483006] apparmor: AppArmor sha1 policy hashing enabled
[  0.483074] integrity: Loading X.509 certificate: UEFI:db
[  0.483077] integrity: Loaded X.509 cert 'Hewlett-Packard Company: HP UEFI Secure Boot 2013 DB Key: 1---------------------------------------------7'
[  0.483141] integrity: Loading X.509 certificate: UEFI:db
[  0.483143] integrity: Loaded X.509 cert 'Hewlett-Packard Company: HP UEFI Secure Boot DB Key: e---------------------------------------------9'
[  0.483208] integrity: Loading X.509 certificate: UEFI:db
[  0.483210] integrity: Loaded X.509 cert 'Microsoft Windows Production PCA 2011: a---------------------------------------------3'
[  0.527351] ima: No architecture policies found
[  0.527635] evm: security.selinux
[  0.527637] evm: security.SMACK64
[  0.527638] evm: security.SMACK64EXEC
[  0.527639] evm: security.SMACK64TRANSMUTE
[  0.527639] evm: security.SMACK64MMAP
[  0.527640] evm: security.apparmor
[  0.527641] evm: security.ima
[  0.527642] evm: security.capability
[  0.531260] ima: Allocated hash algorithm: sha256
[  0.531635] evm: HMAC attrs: 0x1
[  0.600274] RAS: Correctable Errors collector initialized.
[  0.677530] Freeing unused decrypted memory: 2036K
[  0.678032] Freeing unused kernel memory: 2704K
[  0.678187] Write protecting the kernel read-only data: 32768k
[  0.679016] Freeing unused kernel memory: 2028K
[  0.679451] Freeing unused kernel memory: 1684K
[  0.730255] x86/mm: Checked W+X mappings: passed, no W+X pages found.
[  0.730256] x86/mm: Checking user space page tables
[  0.781081] ZFS: Cannot open root device "ZFS-boot-pool/ROOT/24.10.0.2" or unknown-block(0,0): error -6
[  0.781083] Please append a correct "root=" boot option; here are the available partitions:
[  0.781085] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[  0.781115] CPU: 27 PID: 1 Comm: swapper/0 Not tainted 6.6.0-truenas #1
[  0.781116] Hardware name: Hewlett-Packard HP Z440 Workstation/212B, BIOS M60 v02.62 01/04/2024
[  0.781116] Call Trace:
[  0.781117]   <task_stack+0x4720/0x4720>
[  0.781118]   panic+0x345/0x360
[  0.781119]   mount_root_generic+0x1ce/0x3a0
[  0.781120]   prepare_namespace+0x10c/0x160
[  0.781121]   kernel_init_freeable+0x1c0/0x3e0
[  0.781122]   ? rest_init+0xb0/0xb0
[  0.781123]   kernel_init+0x1a/0x1d0
[  0.781123]   ret_from_fork+0x2c/0x50
[  0.781126] Kernel Offset: disabled
[  0.781127] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]---

I have managed to reinstall the system and have set everything back up again, but the issue persists - now I’m back at this screen again…

Can someone help me with this?

My first guesses are bad installation disk or bad RAM.

So ways to test that is to try to install TN on a different device and memtest your RAM.

I have run memory and disk tests via HP’s BIOS tool(s), and everything is passing

I have exactly the same behaviour after an upgrade from 24.10.0 to 24.10.0.2. Before the system was working fine. Server: IBM x3550 M3

1 Like

It does appear to be an issue with the 24.10.0.1+, I have installed the 24.10.0, and it is working as of now, hopefully issue is fixed in future release.

Have you raised a bug ticket? If not please do so to allow investigation,

Hi ABain, I just did. it is created in Jira under: NAS-132689

1 Like

As soon as the ticket is closed with no changes I suppose that upgrading from 24.10 (which works fine) to 24.10.1 will lead to the same inability to boot. Did anybody having this issue try to do the upgrade?

Yes, that is correct, the ticket is closed probably because I did not attach the logs from the system (which are inaccessible after the system failure). I am trying to find time to do a clean system install on a separate drive to do tests and export logs - but haven’t got around it as of now.

In the meantime, I encourage anyone with the same issue to jump in if they can.

Hi everyone, this issue has been solved for me, the underlying problem was a faulty SATA cable. After replacement, the upgrade was successful.

For more info see: [NAS-133926 Unable to update from 24.10 to 24.10+]