Dase

I don't know how many DIMMs you're using, but I'd suggest trying to boot with just one to help rule out any RAM compatibility or slot issues. Also, for me it took around five minutes to do the initial memory training. Be patient on those first boots. Good luck, it's a great board once everything is up and running.

I have a Norco 4220. Last month I added these items and it's working great. I did have to tape off some pins on the 14 GB refurb drives I bought to make them work, but that was also the case with the MV8. This is with unraid version 7.0.0. Tape power mod: https://imgur.com/a/3-3v-pin-reset-BFdmB 16 port SAS card: https://www.ebay.com/itm/326266070704 Cables (the MV8 cables won't work with the newer SAS card): https://www.amazon.com/dp/B086TVKKNX?ref=ppx_yo2ov_dt_b_fed_asin_title

I'll be curious to to see the results of the original author's web UI revamp. He's done some commits recently. https://github.com/bitmagnet-io/bitmagnet/pull/280

By the way, here's the call trace on on my system on the active core during a spike. You can see it trying to do some display-related work: Call Trace: [ 967.656630] <NMI> [ 967.656631] ? nmi_cpu_backtrace+0xd3/0x104 [ 967.656633] ? nmi_cpu_backtrace_handler+0xd/0x15 [ 967.656635] ? nmi_handle+0x54/0x131 [ 967.656637] ? do_raw_spin_lock+0xb/0x1a [ 967.656638] ? default_do_nmi+0x66/0x15b [ 967.656640] ? exc_nmi+0xbf/0x130 [ 967.656642] ? end_repeat_nmi+0x16/0x67 [ 967.656644] ? do_raw_spin_lock+0xb/0x1a [ 967.656645] ? do_raw_spin_lock+0xb/0x1a [ 967.656647] ? do_raw_spin_lock+0xb/0x1a [ 967.656647] </NMI> [ 967.656648] <TASK> [ 967.656648] _raw_spin_lock_irqsave+0x2c/0x37 [ 967.656650] fwtable_read32+0x2c/0xb8 [i915] [ 967.656723] get_data+0x54/0x63 [i915] [ 967.656796] bit_xfer+0x252/0x3e1 [i2c_algo_bit] [ 967.656800] gmbus_xfer+0x44/0x92 [i915] [ 967.656909] __i2c_transfer+0x2af/0x39b [i2c_core] [ 967.656917] i2c_transfer+0xa2/0xc6 [i2c_core] [ 967.656923] drm_do_probe_ddc_edid+0xc6/0x130 [drm] [ 967.656950] ? drm_get_override_edid+0x53/0x53 [drm] [ 967.656973] edid_block_read+0x3a/0xc1 [drm] [ 967.656996] _drm_do_get_edid+0x83/0x2ec [drm] [ 967.657018] ? drm_get_override_edid+0x53/0x53 [drm] [ 967.657041] drm_get_edid+0x34/0x5c [drm] [ 967.657063] intel_hdmi_set_edid+0x9d/0x271 [i915] [ 967.657136] intel_hdmi_detect+0xc7/0x101 [i915] [ 967.657207] drm_helper_probe_detect_ctx+0x81/0xf4 [drm_kms_helper] [ 967.657219] output_poll_execute+0x10e/0x1fb [drm_kms_helper] [ 967.657231] process_one_work+0x1a8/0x295 [ 967.657233] worker_thread+0x18b/0x244 [ 967.657235] ? rescuer_thread+0x281/0x281 [ 967.657237] kthread+0xe4/0xef [ 967.657239] ? kthread_complete_and_exit+0x1b/0x1b [ 967.657241] ret_from_fork+0x1f/0x30 [ 967.657243] </TASK>

I have this same problem on my board, an ASRockRack E3C246D4U. Took me forever to track down. It appeared in the 6.11 series. Blacklisting the GPU i915 module fixed it. Now I can't use hardware transcoding, but the CPU not spiking every 30 seconds was worth the tradeoff for me.

A setting that noticeably improved my Windows 11 VM performance was disabling the Windows "Memory integrity" option. From the Windows Start menu, search for "Core isolation" and open that page. I'm curious if this is enabled and if disabling it helps you at all.

"Memory integrity" Is the option you should try disabling to see if it makes a difference. Leave the driver blocklist enabled.

Just open the Windows Start menu and type "core isolation". It'll take you to that settings page. Make sure "Memory integrity" is disabled. That definitely slowed down my Windows 11 VM.

6.10.3 and earlier work fine. 6.11+ including 6.12 maxes a CPU core for about 5 seconds every 30 seconds. This process shown in HTOP accumulates about 3 seconds of CPU time after each spike: /usr/bin/php -q /usr/local/emhttp/webGui/nchan/device list Any idea what might have changed here 6.11+? This recurring spike happens even in safe mode with the array stopped. I'm not positive it's this process causing my problem, but its behavior seems suspect. It's making newer releases of unraid unusable for me, because the spike seems to eventually land on a CPU core assigned to a VM, making the VM unresponsive while the spike is happening. Safe mode 6.12.0 diagnostics attached. System: ASRockRack E3C246D4U Motherboard Intel® Xeon® E-2288G CPU @ 3.70GHz Dell PERC H310 8-Port 6Gb/s SAS Adapter RAID Controller 11 Drives and 1 Parity Drive

Seeing this same issue in my 6.11.0 final install. I too use an integrated GPU for Plex transcode.

Mine gives the same 1006 error. Thanks for letting us know the UnraidServerName version of the URL works. I was able to get it in that way.

I idle at 65 watts, but that's with two drives always spun up, a parity drive and a torrent/download drive, and 13 more on standby. I also have two drive controllers, a Dell Perc H310 and a Supermicro AOC-SASLP-MV8. Each of these draws around 10 watts on its own I've noticed. System specs: M/B: ASRockRack E3C246D4U CPU: Intel® Xeon® E-2288G CPU @ 3.70GHz Memory: 32 GiB DDR4 Single-bit ECC

If it won't boot with one stick, try pulling the battery for 5 min so the CMOS can clear and try it with one stick again. After I got it to boot, I went into the CMOS and flashed the BIOS that allows hardware transcoding. After that I didn't have problems, other than having to flash the BMC separately so sensors would work.

As I recall I had this problem too. I got past it by using only one stick of RAM, and then once it posted successfully I spent some time figuring out which pair of slots worked correctly. Board has been rock-solid ever since.