Broken BIOS?

[jwong858]

Hi,

I'm running Truenas Scale 22-12-RC1 with motherboard ASRock X570M Pro4. Truenas Scale crashes many time a day with the broken BIOS message. Please see below?

Nov 28 04:28:51 truenas kernel: ccp 0000:0d:00.1: ccp: unable to access the device: you might be running a broken BIOS.
Nov 28 04:43:26 truenas kernel: ccp 0000:0d:00.1: ccp: unable to access the device: you might be running a broken BIOS.
Nov 28 04:57:03 truenas kernel: ccp 0000:0d:00.1: ccp: unable to access the device: you might be running a broken BIOS.
Nov 28 09:23:53 truenas kernel: ccp 0000:0d:00.1: ccp: unable to access the device: you might be running a broken BIOS.
Nov 28 16:58:59 truenas kernel: ccp 0000:0d:00.1: ccp: unable to access the device: you might be running a broken BIOS.
Nov 28 21:45:01 truenas kernel: ccp 0000:0d:00.1: ccp: unable to access the device: you might be running a broken BIOS.
Nov 29 02:10:25 truenas kernel: ccp 0000:0d:00.1: ccp: unable to access the device: you might be running a broken BIOS.
Nov 29 02:26:05 truenas kernel: ccp 0000:0d:00.1: ccp: unable to access the device: you might be running a broken BIOS.
Nov 29 02:32:26 truenas kernel: ccp 0000:0d:00.1: ccp: unable to access the device: you might be running a broken BIOS.
Nov 29 02:38:16 truenas kernel: ccp 0000:0d:00.1: ccp: unable to access the device: you might be running a broken BIOS.
Nov 29 02:44:10 truenas kernel: ccp 0000:0d:00.1: ccp: unable to access the device: you might be running a broken BIOS.
Nov 29 02:58:29 truenas kernel: ccp 0000:0d:00.1: ccp: unable to access the device: you might be running a broken BIOS.
Nov 29 03:04:26 truenas kernel: ccp 0000:0d:00.1: ccp: unable to access the device: you might be running a broken BIOS
Nov 29 03:10:12 truenas kernel: ccp 0000:0d:00.1: ccp: unable to access the device: you might be running a broken BIOS.
Nov 29 03:16:01 truenas kernel: ccp 0000:0d:00.1: ccp: unable to access the device: you might be running a broken BIOS.
Nov 29 03:31:38 truenas kernel: ccp 0000:0d:00.1: ccp: unable to access the device: you might be running a broken BIOS.
Nov 29 03:49:20 truenas kernel: ccp 0000:0d:00.1: ccp: unable to access the device: you might be running a broken BIOS.
Nov 29 04:03:55 truenas kernel: ccp 0000:0d:00.1: ccp: unable to access the device: you might be running a broken BIOS
Nov 29 04:09:49 truenas kernel: ccp 0000:0d:00.1: ccp: unable to access the device: you might be running a broken BIOS.
Nov 29 04:26:19 truenas kernel: ccp 0000:0d:00.1: ccp: unable to access the device: you might be running a broken BIOS.
Nov 29 04:32:23 truenas kernel: ccp 0000:0d:00.1: ccp: unable to access the device: you might be running a broken BIOS
Nov 29 04:46:07 truenas kernel: ccp 0000:0d:00.1: ccp: unable to access the device: you might be running a broken BIOS.

The hardware in question is as follow:

*-generic:1
description: Encryption controller
product: Starship/Matisse Cryptographic Coprocessor PSPCPP
vendor: Advanced Micro Devices, Inc. [AMD]
physical id: 0.1
bus info: pci@0000:0d:00.1
version: 00
width: 32 bits
clock: 33MHz
capabilities: pm pciexpress msi msix bus_master cap_list
configuration: driver=ccp latency=0
resources: irq:144 memory:fc300000-fc3fffff memory:fc408000-fc409fff

I have reapplied the firmware but I'm still getting the error message. Is the BIOS truely broken or is it something else? Please advise?

Thanks,

James

 

[WN1X]

Have you triede disabling the encryption controller? The option is usually found under Advanced > AMD CBS.

 

[jwong858]

No, I don't see the encryption controller under Advanced > AMD CBS. I'm running Truenas Scale 12-12-RC1.

 

[joeschmuck]

@WN1X is talking about a BIOS setting, not a TrueNAS setting.

 

[jwong858]

Ok, I see it, but it seems only SMEE (Secure Memory Encryption Enable) and CC6 Memory region encryption options are available for use of encryption. Should I disable both?

 

[WN1X]

Not having this (or any other) AMD motherboard, I can only guess here. I would try disabling the SMEE setting and see if that resolves your issue. If anything "bad" happens, you should be able to to re-enable it.

 

[joeschmuck]

I'm not familiar with these BIOS options so I can't really help other than to say, take one change at a time.

 

[jwong858]

When I disabled SMEE (Secure Memory Encryption Enable) or/and CC6 Memory region encryption, Plex can't see the GPUs. By the default SMEE (Secure Memory Encryption Enable) and CC6 Memory region encryption are automatic (not enabled or disabled). Once I set SMEE (Secure Memory Encryption Enable) and CC6 Memory region encryption as enabled, Plex works with the GPUs and Truenas Scale does not crash. Thanks, @WN1X!

 

[jwong858]

Never mind. I spoke too early. It just crashed.

 

[jwong858]

I think I know what the real problem is now. Whenever Plex scans library files, it crashes. I have thousands of media files. I see this in the Plex logs.

Dec 05, 2022 21:02:39.495 [0x7f85330d6b38] DEBUG - Pre-processed minidump directory: /config/Library/Application Support/Plex Media Server/Crash Reports/1.30.0.6442-5070ad484
Dec 05, 2022 21:02:39.495 [0x7f85330d6b38] DEBUG - Post-processed minidump directory: /tmp
Dec 05, 2022 21:02:39.495 [0x7f8534d7b808] ERROR - Too many crashdumps detected / retries disallowed!

This may not have anything to do with the BIOS. Anybody any idea?

 

[jwong858]

Actually it only crashes when scanning photo files. I have a lot of Sony raw photo files. Does Plex support Sony raw photo files?