UnRaid Incompatibility with Threadripper Build?

LadyRosalyn · December 30, 2019

CPU	AMD Ryzen Threadripper 1920X (12-core/24-thread) Desktop Processor (YD192XA8AEWOF)
Motherboard	ASUS PRIME X399-A AMD Threadripper TR4 DDR4 M.2 U.2 X 399 EATX HEDT Motherboard with USB 3.1 Gen2, AURA Sync RGB Lighting and 3D Printing Mounts
Memory	Corsair Vengeance RGB Pro 64GB (8x8GB) DDR4 3600 (PC4-28800) C18 Desktop Memory – Black
Storage	4 of CORSAIR Force Series MP510 1920GB NVMe PCIe Gen3 x4 M.2 SSD Solid State Storage, Up to 3,480MB/s
Power Supply	CORSAIR RMx Series, RM1000x — 1000 Watt 80 PLUS® Gold Certified Fully Modular PSU
CPU Cooler	Corsair Hydro Series H150i PRO RGB AIO Liquid CPU Cooler,360mm,Triple ML120 PWM Fans, Intel 115x/2066, AMD AM4

12/28 -

Kernel Offset: disabled

end Kernel panic - not syncing: VPS: Unable to mount root fs on unknown - block (0,0) ] ----

Unexpected reschedule of offline CPU#0!

Trying to get unraid running on the above build. Had it working fine when I started out with unraid 6.7.2, after upgrading to 6.8 I started having an inconsistent kernel panic, that would only boot in safe mode, sometimes (Sometimes it would kernel panic even in safe mode) decided to try to remake my unraid image, and have now tried reinstalling with a fresh 6.8, and a fresh 6.7.2, but I keep getting the kernel panic. I have tried both versions with UEFI boot and legacy boot with no luck.

Is this just an issue with Unraid not supporting the hardware? I know I’ve read a fair amount of people having issues with threadripper, but not many people seem to be using it actively.

12/29 -

Ran a fresh copy of 6.7.2 in UEFI boot in Unraid OS mode and reboot it just to make sure that it wasn’t a fluke. Not sure why it would be working today since I followed the exact same process yesterday and got the kernel panic

¯\_(ツ)_/¯

Parity check is running and appeared to freeze at 19% Attempted to shut down the system and whatever error caused the parity check to freeze has been running a loop and is now preventing the system from shutting down (Said something about the CPU line being Tainted G D). After an hour or so decided to hard restart and then got the same error mentioned above shown in the image below:

Ralphred · December 30, 2019

Have you formatted the disks between installs?

The error you are getting can roughly be translated to "we booted the hardware, loaded the software needed to finish the boot, but couldn't find your system disk"

There are lots of questions to ask, like is LVM being used, is the system root fs part of a raid before suggesting a way forward, but if you can interrupt (I assume) grub2 and post a pic of the edit window we can all see how the bootloader is trying to load the OS and it should answer a lot of that.

The "worked in safe mode but not normal after an update" sounds like a dodgy initramfs or bootloader config error, but the unpredictability of the panic and the 19% stall on the parity check sounds more like hardware failure. Unplug and plug all the drives again, just for good measure.

This is my issue with these "make complicated things easy" OS's, if you were doing it yourself you'd know all the answers and the diagnosis could begin straight away.