Please forgive if there is a more appropriate forum for this question/discussion. Feel free to move it there if applicable.

 

Disclosure: I'm not a Linux guru by any means so my lack of accuracy may be a contributor.

 

I recently moved my UR server to newer hardware in a new chassis consolidating another server running some Docker containers (Plex, Tdarr) on bare metal.

 

I went with an AMD R5 8500G on an m-atx B650 board and a new SAS controller.

 

Everything went fine with the transfer. All the drives were mounted and the array is working fine. However, the APU in the AMD CPU cannot be used in the current UR V6.12.14 because of the kernel version 6.1.118. I've done some searching around and from what I can see, these CPUs were first supported under kernel v6.7 albeit using open-source drivers. It was not supported until v6.11rc2 with the latest stable kernel version being v6.12 that addressed random reboots when using virtualization -a significant issue with use in an UR scenario.

 

Which brings us to UR v7 rc1. I see in the release notes that UR7 is based on the kernel v6.6.62. That would lead me to understand that these CPUs are still not going to work properly with the latest version of UR until the kernel version gets up to and beyond kernel v6.12.

 

 

 

TLDR:

Why the choice to use kernel v6.6.62 in UR7 when that version is significantly behind the currently available releases?

5 minutes ago, aglyons said:

Please forgive if there is a more appropriate forum for this question/discussion. Feel free to move it there if applicable.

 

Disclosure: I'm not a Linux guru by any means so my lack of accuracy may be a contributor.

 

I recently moved my UR server to newer hardware in a new chassis consolidating another server running some Docker containers (Plex, Tdarr) on bare metal.

 

I went with an AMD R5 8500G on an m-atx B650 board and a new SAS controller.

 

Everything went fine with the transfer. All the drives were mounted and the array is working fine. However, the APU in the AMD CPU cannot be used in the current UR V6.12.14 because of the kernel version 6.1.118. I've done some searching around and from what I can see, these CPUs were first supported under kernel v6.7 albeit using open-source drivers. It was not supported until v6.11rc2 with the latest stable kernel version being v6.12 that addressed random reboots when using virtualization -a significant issue with use in an UR scenario.

 

Which brings us to UR v7 rc1. I see in the release notes that UR7 is based on the kernel v6.6.62. That would lead me to understand that these CPUs are still not going to work properly with the latest version of UR until the kernel version gets up to and beyond kernel v6.12.

 

 

 

TLDR:

Why the choice to use kernel v6.6.62 in UR7 when that version is significantly behind the currently available releases?

Lack of support for zfs on 6.12 and is the current lts kernel.

I see ZFS 2.3.0-rc3 has been aligned for Linux v6.12.1. Just waiting for one commit test to complete for freebsd13-4r.

 

Fingers crossed that ZFS 2.3.0 is released in time for URv7 to jump up to Linux 6.12.x which has been marked as LTS.

Since rc1 was released with kernel 6.6, I would expect it would remain with that kernel for the future, it would be risky to make a kernel change during the rc phase, Unraid 7.1 should then go to kernel 6.12

6 hours ago, JorgeB said:

Since rc1 was released with kernel 6.6, I would expect it would remain with that kernel for the future, it would be risky to make a kernel change during the rc phase, Unraid 7.1 should then go to kernel 6.12

So we'll get there eventually. It's just a little bummer that I'll have to wait a little longer before I can use the iGPU in the 8500G. I'm stuck with the 1050ti, which is stuck in a PCIE16 slot running on 1 lane, so transcodes are crawling at CPU speeds!