UnRaid Incompatibility with Threadripper Build?

[LadyRosalyn]

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. After an hour or so decided to hard restart and then got the same error mentioned above shown in the image below:

[ji-q]

Just experienced something similar with a very different system. Dual Xeon on a Z10PE-D16/4L. Using unRAID 6.8.0 too. This system has been working fine but when I last turned it off from the webGUI (which I've done many times without any issues) it seems to have had an unclean shutdown. The webGUI went away but the machine was still on for about 30 minutes, so I did a forced shutdown with the power button. Other than that and maybe the core/thread count, I can't see how these are related.

 

Will look at the unRAID Flash USB drive contents and try diffing it with a new installation. 

[TPNuts]

Any progress with this as I have a 3970x on master aorus trx40 board with a VM+you pass through of 980ti. It has given me some serious issues. I rebuild the unraid profile and copied over the config file. It works for a bit but I see some serious issues in stability now. You would think that multiple generations would have some clarity. I can't even pull diagnostics due to the system freezing up and requiring a hard reset. Any guidance would be greatly appreciated!

 

[trurl]

3 hours ago, TPNuts said:

Any guidance would be greatly appreciated!

 

[meep]

Also, try reducing memory speed and removing all but 1 or 2 sticks.

 

I added some memory to my TR 2950x system recently and had constant fallovers. Removing the new dimms solved the problem immediately.

 

 

 

[TPNuts]

SO i got the system up and running here is what i did

Pulled the flash drive, backing up the drive on my laptop

wiped and reran the OS with 6.8.2 vs 6.8.3 it was on before. 

Also moved the flash drive to a USB 2.0 port (new motherboard so i didnt realize i had placed it on a 3.0 port

Booted up perfectly.

I think that the issue is related to either the OS itseld as I did try to do a rebuild before and it was a hit or miss every reboot, or it was the usb 2.0 which very well could be as it is always wise to run it on a stable legacy port.