Cristian Sava

I own several licenses and wanted to move some of them to newer hardware. Tried both unRaid 6.11.5 & 6.12.0-rc4 on this combo and none seem to work on a usb vanilla install. It just hangs at some point in the boot process never reaching mounting the os root. The last lines i see on the screen seem to be related to bluetooth initialization process (confirmed with Windows 10 install and run for a month that there's no hardware issue). The newer hardware is : - B760 AORUS ELITE AX DDR4 mainboard from Gigabyte - Intel Raptor Lake i9-13900 - 4 sticks of DDR4 Kingston Fury 3200 MT/s Is there a known problem with the Intel Wi-Fi 6E AX211 ? Is there a way to tell Unraid to stop loading modules for the wifi/bluetooth hardware combo with kernel parameters as i am using wired conectivity anyways with Unraid ?

i've determined that having less then one line of text in the parity check log is the cause of the problem with the screen above and should be corrected if possible in a new release cause it wasn't a problem before. The other issues i am having are related to the unasigned devices plugin. i will reach the author on their forum page.

Hi all, I have 6 hosts licensed now (5 basic and 1 pro). All have various number of disks attached either in array or unasigned devices. I mainly use host for virtualization purposes. Before 6.11.x versions I was using 6.9.x and the startup process went smooth all the time and all of the web components loaded just fine. Now I have random issues where something does not load properly, loads incomplete, the array starts but its web view (array components, parity status and last check and unasigned devices) are not available in the view or even worse, some of the samba shared disks (unasigned devices ones) are not showing up anymore on the network. Has anybody encountered this issue ? Any quickfixes ?

corrupt data. reinstalled from scratch and resolved.

Changed Status to Solved Changed Priority to Minor

Changed Status to Open Changed Priority to Urgent

Hi, I have invested in 4 licenses for all my hosts and I have issues I want solved. I want to be able to move past 6.9.0-beta25 in order to use my windows vm's which have all 2 nvidia gpus and 1 nvme passed through. They work just fine on the named version and not at all on any newer beta or stable version. Moreover I don't get any meaningful logs but just a screen freeze when loading windows 10 at the spinner stage and one ore more cpu cores assigned to the vm gets stuck to 100% usage. Any other vm's that I have with just a nvme passed through without a gpu or with nothing passed through are linux and work just fine on any version. Anybody else having the same issue ? unraid4-diagnostics-20210627-0651.zip unraid3-diagnostics-20210627-0651.zip unraid1-diagnostics-20210627-0651.zip unraid2-diagnostics-20210627-0650.zip

I have the same error with 6.9.1 / 6.9.2. The most recent version that works for me (and i tested them all) is 6.9.0-beta25. I already own two licenses and was thinking buying a 3rd one - till i saw that coming out of beta's has no effect. In my case the vm's i'm using are win10 with nvme and gpu passthrough. I really wish this was solved.

Just tried beta-30. Exibits the same behaviour. The only difference is that now the screen goes black and it even won't get to the phase where the win10 circles spin and then freeze on the intel machine. And the same thing with the amd machine still working just fine. So for now sticking with beta-25 until further developments.

How is this an issue with disk passthrough if i already said that i got the another vm working and that the only difference is the gpu passthrough missing in the one that works ?

passthrough an entire samsung evo 500 gb nvme disk.

Yes I have 3 monitors. One is for the onboard gfx. The other two are for the nvidia cards. They are all connected simultaneously.

I think that i may have found the issue. It seems that my first graphics card is jumping from one id to the other (01 and 02). When the first card's id is 01 it seems to display "(rev a1)" and when id is 02 it shows as "(rev ff)". The second card seems to be stable at id 04 with "(rev a1)". I managed just once to boot both vm's when they displayed different revisions. This is very strange. q1 : is this an issue cause the cards are suposed to be idendical (should i just put in two different cards)? q2 : can i make their id's "sticky" somehow if i were to have them both identical ?