Hi

I just tried to upgrade from 7.2.3 to 7.3.1 and lost half my drives.
Boot took forever and I saw this error message:

I then downgraded to 7.2.3 and tried to upgrade to 7.2.7. Same issue!

Has HW support for one of my SATA Controllers been removed?

I have the following:

• an M.2 Controller from DeLock based on JMicron JM585 ( https://www.delock.com/produkt/64051/merkmale.html?f=s):
  

• the onboard controller of my Asrock X870 Taichi Lite:
  
  

I did not change any HW and this Server never had issues since I built it over 1.5 years ago. Back then it was running on Unraid 6.x.

I have once more downgraded to 7.2.3. and all is running perfectly stable again.

What is going on and can I fix this somehow?

Edited June 5Jun 5 by fae_76

I have JMB585 in my backup server, no problems on any version

That is good to know. Thank you.

However on my side this is reproducible. Working perfectly fine on 7.2.3 and prior releases, no errors, no SMART issues. As soon as I upgrade the issue is there and Unraid refuses to see the drives attached to this controller. No config changes, no BIOS changes! Just upgrade and reboot. After a downgrade all is fine again. Something has changed that much is for sure.
I can also boot form a Live-Ubuntu 26.04 USB Stick and I can see all the drives just fine. I don't see any errors there. Therefore I have a hard time to believe that it's anything HW related. All points to Unraid.

I can also not find anything related to this in my diagnostics (I'm a Linux noob though)

blackbox-diagnostics-20260606-0044.zip

Edited June 5Jun 5 by fae_76

I cant really offer any advice other than I do not exhibit those symptoms (it's a JBM585 in nvme form factor)

9 hours ago, fae_76 said:

Has HW support for one of my SATA Controllers been removed?

Nope, I also have some, look for a BIOS update.

7 minutes ago, JorgeB said:

Nope, I also have some, look for a BIOS update.

I would rather not. Here is the reason: https://www.youtube.com/watch?v=STWvlCefL4Q. This is most likely due to RowHammer. I'm running 5600MHz ECC and since my daily driver as well as my gaming VM are running on this machine too I would really like to avoid a BIOS Update, especially since my system is running stable. As mentioned, Ubuntu 26.04 LTS running of a USB has no issue correctly detecting the controller and disks. It's only Unraid that seems to have an issue.

In that case, my suggestion would be to wait for a new Unraid release with a newer kernel and retest.

I'm an idiot. My live Ubuntu was 24LTS not 26LTS and with 26 my drives do also not show up. I did an BIOS Update but not to the newest AGESA. With that 26LTS sees the drives. However for some reason I cannot boot from the Unraind USB Stick anymore. Ventoi with Ubuntu works in the same Port though. I even created a brand new Unraid stick installing 7.3.1 with the Unraid USB creator and even that does not boot. My BIOS seems to ignore Unraid based USB sticks. No clue why my Ventoy stick works but not Unraid.
I did load BIOS default settings, Secure Boot is disabled.

Finally I have all up and running again and this time with Unraid 7.3.1 and 5600MT on my ECC Memory 😊

I had to install that latest BIOS with an AGESA <1.3 and switch to internal boot. In order to get there I first had to upgrade to the newest BIOS which as suspected limits my RAM to 5200MT. Then I had to switch to internal boot and finally I could downgrade my BIOS again to the latest version that still supports 5600MT.

I have no clue why my ASROCK board refuses to boot from the Unraid USB stick with the BIOS I use now. This does not make sense to me.

Anyway I'm happy my server is up-to-date now and running again. Thanks everbody for your suggestions and support!

I was too early celebrating. Now all my VMs through kernel panic withnin the first 5min they are running.

VMs I create from scratch with the same HW passthrough as the ones that crash seem to work fine. I installed 26LTS Deskotp twice, once with iGPU passthrough, once with dGPU passthrough and an USB controller for each. Seems to be stable so far. The only difference, my legacy VMs that have worked since I installed Unraid use i440 (updating this did not resolve the crash) and my newly created VMs use q35. The rest is identical as far as I can tell. Legacy VMs run on 24LTS the newly intalled ones 26LTS.

This update was and is painful. The first part i can understand Kernel Bios interaction. This has nothing to do with Unraid. But what I'm experiencing now is very wired.

Edited June 6Jun 6 by fae_76

18 hours ago, fae_76 said:

I have no clue why my ASROCK board refuses to boot from the Unraid USB stick with the BIOS I use now.

There's a known issue with the stock Syslinux UEFI bootloader and newer AGESA, you can use the Limine bootlçader if you want to boot from a flash drive; internal boot is not affected since it uses the Grub bootloader. https://forums.unraid.net/topic/196349-black-screen-after-usb-boot-msi-x870e-carbon-ryzen-9950x-rtx-4070-ti-super/#findComment-1607672