Hey gang,

newbie here that's struggling with my first Unraid build.

Specs below and diagnostics attached. Long and short is, new build similar to a great pal of mines, he's had nothing but great success - I'm struggling with random shutdowns, occasional cache drive disappearing, felt like a plex problem until shutdowns overnight so then thought mover, then parity disappeared and then came back, lost the flash drive, reboot brought most things back so I'm wondering if I'm staring in the face of a faulty MOBO...

Love Unraid and have had a blast getting it up and running. My goal is to be self hosting to relinquish myself of the subscription services along with custody over my own files. I travel a huge amount for work and being able to access my NAS from the other part of the world has been fulfilling my inner nerd quite heavily not to mention my plex / hue / home assistant integration which scratches my tech itch beautifully!

I currently can't rely on this setup to use it for all my work file's infrastructure and I'm finally giving up the attempt to fix this myself as I'm at a loss and hoping one of you, my fellow computer lovers, to get this setup cruising like the server it has the potential to be!

Here to answer any more questions you may have about my setup!

Thanks in advance!

Best

Chris

Unraid server Starter, version 7.1.4
Model:	JonsboN3
Motherboard:	ASUSTeK COMPUTER INC. ROG STRIX B760-I GAMING WIFI, Version: Rev 1.xx,
Processor:	Intel® Core™ i3-14100 @ 4455 MHz
HVM:	Enabled
IOMMU:	Enabled
Cache:	L1 Cache = 192 KiB (max. capacity 192 KiB)
	L1 Cache = 128 KiB (max. capacity 128 KiB)
	L2 Cache = 5 MiB (max. capacity 5 MiB)
	L3 Cache = 12 MiB (max. capacity 12 MiB)
Memory:	16 GiB DDR5 (max. installable capacity 128 GiB)
	Controller0-DIMM0: Corsair CMH16GX5M2B5200C40, 8 GiB DDR5 @ 4800 MT/s
	Controller1-DIMM0: Corsair CMH16GX5M2B5200C40, 8 GiB DDR5 @ 4800 MT/s
Network:	bond0: fault-tolerance (active-backup)
	eth0: 2500 Mbps, full duplex, mtu 1500

Parity	ST20000NE000 - 20 TB (sdb)	39 °C	0.0 B/s	0.0 B/s	0
Disk 1	ST12000NE0008- - 12 TB (sdc)	42 °C	0.0 B/s	0.0 B/s	0	xfs	12 TB	6.03 TB	5.97 TB
Disk 2	ST12000NE0008- - 12 TB (sdd)	41 °C	0.0 B/s	0.0 B/s	0	xfs	12 TB	1.65 TB	10.3 TB
Disk 3	ST12000NE0008- 12 TB (sde)	36 °C	0.0 B/s	0.0 B/s	0	xfs	12 TB	230 GB	11.8 TB
	Array of four devices	40 °C	0.0 B/s	0.0 B/s	0		36 TB	7.90 TB	28.1 TB

Pool Devices

DEVICE	IDENTIFICATION	TEMP	READS	WRITES	ERRORS	FS	SIZE	USED	FREE
Cache	Samsung_SSD_990_PRO_2TB - 2 TB (nvme0n1)	40 °C	0.0 B/s	0.0 B/s	0	btrfs	2 TB	306 GB	1.69 TB

Boot Device

DEVICE	IDENTIFICATION	TEMP	READS	WRITES	ERRORS	FS	SIZE	USED	FREE
Flash	SanDisk_3.2Gen1 - 30.8 GB (sda)

csnas-diagnostics-20250722-1055.zip

En

1 hour ago, crispeedee said:

I'm struggling with random shutdowns

Do you mean the server is powering off by itself?

5 minutes ago, JorgeB said:

En

Do you mean the server is powering off by itself?

It isn't powering itself completely off but the machine is unresponsive and the attached monitor (kept attached because so many issues) looks like ;

your screenshot lets me think of a serious memory problem... Did you already run memtest?

Just now, MAM59 said:

your screenshot lets me think of a serious memory problem... Did you already run memtest?

Multiple memtests all with flawless results each time !

hmm, but this pattern implies that there are addressing problems for (at least) the video ram, or the gpu is seriously broken...

strange.

2 minutes ago, MAM59 said:

hmm, but this pattern implies that there are addressing problems for (at least) the video ram, or the gpu is seriously broken...

strange.

I understand, I’ll run another memtest and report back…

I found this in you diagnostics:

Jul 22 10:47:41 CSNas kernel: system 00:03: [mem 0xfeda0000-0xfeda0fff] has been reserved

Jul 22 10:47:41 CSNas kernel: system 00:03: [mem 0xfeda1000-0xfeda1fff] has been reserved

Jul 22 10:47:41 CSNas kernel: system 00:03: [mem 0xfed20000-0xfed7ffff] could not be reserved

Jul 22 10:47:41 CSNas kernel: system 00:03: [mem 0xfed90000-0xfed93fff] could not be reserved

Jul 22 10:47:41 CSNas kernel: system 00:03: [mem 0xfed45000-0xfed8ffff] could not be reserved

Jul 22 10:47:41 CSNas kernel: system 00:03: [mem 0xfee00000-0xfeefffff] could not be reserved

Jul 22 10:47:41 CSNas kernel: system 00:04: [io 0x2000-0x20fe] has been reserved

But I dont know if it is important, I am no INTEL Guy, so I am not used what is "normal" during that boot phase.

My AMD Boxes can reserve all the blocks they are asking for, so maybe some Intel Specialist can clear this up?

46 minutes ago, MAM59 said:

I found this in you diagnostics:

Jul 22 10:47:41 CSNas kernel: system 00:03: [mem 0xfeda0000-0xfeda0fff] has been reserved

Jul 22 10:47:41 CSNas kernel: system 00:03: [mem 0xfeda1000-0xfeda1fff] has been reserved

Jul 22 10:47:41 CSNas kernel: system 00:03: [mem 0xfed20000-0xfed7ffff] could not be reserved

Jul 22 10:47:41 CSNas kernel: system 00:03: [mem 0xfed90000-0xfed93fff] could not be reserved

Jul 22 10:47:41 CSNas kernel: system 00:03: [mem 0xfed45000-0xfed8ffff] could not be reserved

Jul 22 10:47:41 CSNas kernel: system 00:03: [mem 0xfee00000-0xfeefffff] could not be reserved

Jul 22 10:47:41 CSNas kernel: system 00:04: [io 0x2000-0x20fe] has been reserved

But I dont know if it is important, I am no INTEL Guy, so I am not used what is "normal" during that boot phase.

My AMD Boxes can reserve all the blocks they are asking for, so maybe some Intel Specialist can clear this up?

1 hour ago, crispeedee said:

I understand, I’ll run another memtest and report back…

Memtest came up all good here…

Mayber silly question but do you have the latest BIOS installed on your mobo?

https://www.asus.com/supportonly/rog%20strix%20b760-i%20gaming%20wifi/helpdesk_bios/

Version 1820

12.76 MB

2025/05/27

SHA-256 ：2A4144081C8A52D91FDE5C3FA5BBFF42C511F4731881CE9CE1B08BBE9869D353

"Update the Intel microcode to version 0x12F to further improve system conditions that may contribute to Vmin Shift instability in Intel 13th and 14th Gen

Version 1805

12.75 MB

2024/11/12

"1. Updated with Intel microcode 0x12B to address elevated voltage requests during idle or light activity, further mitigating Vmin Shift instability issues.

Version 1663

12.79 MB

2024/08/15

"1.The new BIOS includes Intel microcode 0x129 to enhance the stability of Intel Core 13th and 14th Gen processors.

Edited July 23, 2025Jul 23 by googleg

11 minutes ago, googleg said:

Mayber silly question but do you have the latest BIOS installed on your mobo?

https://www.asus.com/supportonly/rog%20strix%20b760-i%20gaming%20wifi/helpdesk_bios/

Version 1820

12.76 MB

2025/05/27

SHA-256 ：2A4144081C8A52D91FDE5C3FA5BBFF42C511F4731881CE9CE1B08BBE9869D353

"Update the Intel microcode to version 0x12F to further improve system conditions that may contribute to Vmin Shift instability in Intel 13th and 14th Gen

Version 1805

12.75 MB

2024/11/12

"1. Updated with Intel microcode 0x12B to address elevated voltage requests during idle or light activity, further mitigating Vmin Shift instability issues.

Version 1663

12.79 MB

2024/08/15

"1.The new BIOS includes Intel microcode 0x129 to enhance the stability of Intel Core 13th and 14th Gen processors.

Mate! Stunning suggestion - this update wasn't out when I built the NAS - I'm on 1805 - will update immediately and report back!

Also keep in mind that Intel 14th Gen are notorious for developping stability issues. You may need to RMA your CPU.

https://www.tomshardware.com/pc-components/cpus/firefox-dev-says-intel-raptor-lake-crashes-are-increasing-with-rising-temperatures-in-record-european-heat-wave-mozilla-staffs-tracking-overwhelmed-by-intel-crash-reports-team-disables-the-function

Edited July 23, 2025Jul 23 by googleg

34 minutes ago, googleg said:

Also keep in mind that Intel 14th Gen are notorious for developping stability issues. You may need to RMA your CPU.

https://www.tomshardware.com/pc-components/cpus/firefox-dev-says-intel-raptor-lake-crashes-are-increasing-with-rising-temperatures-in-record-european-heat-wave-mozilla-staffs-tracking-overwhelmed-by-intel-crash-reports-team-disables-the-function

Thanks for the info there @googleg , it's in a relatively stable temperature room but will keep an eye on the temps.

Bios updated and will keep you all in the loop - It turns out I built this on the 24th May and the updated Bios came out on the 27th and I had only just flashed it with the "latest" so figured id be waiting a minute before a new Bios...little did I know!

Just wanted to chime in and say that a simple memtest is not enough to identify a memory issue, you need to run it for 12-24 hours on a continuous loop to catch deeper instabilities.

I doubt its related to the raptor lake instability issues as the 14100 is not a true raptor lake part, it's a refreshed alder lake core, effectively a slightly clocked up 12100/13100, which as far as anyone can tell were unaffected.

I'd be doing some testing with the bios starting at default settings, all gaming options off, xmp off, power limits back to default intel spec etc.

Some gaming motherboards have "enhancements" enabled out of the box that could push some cpus too far. Then I'd reseat the cpu and memory, remount the cooler etc. usual hardware checks.

Thanks I did not know about the specific case of the 14100. That said according to Gemini it is still potentially affected by the degradation problem:

1. Affected SKUs: While the most severe and widely reported cases of degradation have been with the high-end K/KF/KS SKUs (i7 and i9) due to their higher default clock speeds and power limits, Intel has widened the potential at-risk processors to include 65W SKUs and even Raptor Lake laptop models. Since the i3-14100 is a 65W part, it falls into this broader category.

2. Die Reuse and Shared Microcode: Even though the i3-14100 uses an Alder Lake die, it still shares the same microcode and BIOS power management algorithms with the rest of the 14th Gen lineup. These are the elements that were reportedly flawed in requesting excessive voltages. So, while the physical silicon might be older, the control mechanisms are part of the newer generations affected by this issue.

Gemini isn't a person and is just repeating words that make sense with zero fact checking, what it is saying is based on a much older Intel comment that warned all 65w chips may be affected.
That has been further clarified to a definitive list of chips starting at the 14600K and up (14600 non-K is unaffected). Evidence of chips outside of the 14600K and up are not significantly higher than baseline failure.

The Raptor lake flaw does not apply to the 14100 as it uses the 12th gen IA power delivery silicon which has shown no firm evidence of degradation above the baseline for the 12100 and 13100.

Thanks for all the details and shame on Gemini for propagating fake newss :-)

6 minutes ago, googleg said:

shame on Gemini for propagating fake news

Never trust a hyped AI...

On 7/24/2025 at 12:29 AM, Faceman said:

Just wanted to chime in and say that a simple memtest is not enough to identify a memory issue, you need to run it for 12-24 hours on a continuous loop to catch deeper instabilities.

I doubt its related to the raptor lake instability issues as the 14100 is not a true raptor lake part, it's a refreshed alder lake core, effectively a slightly clocked up 12100/13100, which as far as anyone can tell were unaffected.

I'd be doing some testing with the bios starting at default settings, all gaming options off, xmp off, power limits back to default intel spec etc.

Some gaming motherboards have "enhancements" enabled out of the box that could push some cpus too far. Then I'd reseat the cpu and memory, remount the cooler etc. usual hardware checks.

Unfortunately gang, we’re back into Trouble, had a good couple of days and then two crashes in less than 24 hours.

I’ve run a memtest86+ for over 17 hours now and we still have 33 passes, 0 errors… posting this from my phone - will reboot and post diagnostics.

Notes are that I disabled XMP as mentioned previously as a problem and where I can, everything to default spec (I believe )

memtest is only definitive if it finds errors, since you have multiple RAM sticks, try using the server with just one, if the same try with the other one, that will basically rule out bad RAM.

hey gang,

so tried the ram individually, one was seemingly less reliable than the other. swapped them out for some brand new ram, all been fine for the last 4 days then today the cache drive has gone missing....any help hugely appreciated...

diagnostics below

csnas-diagnostics-20250811-0148.zip

Aug 10 20:25:31 CSNas kernel: nvme nvme0: Device not ready; aborting reset, CSTS=0x1

Aug 10 20:25:31 CSNas kernel: nvme nvme0: Abort status: 0x371

### [PREVIOUS LINE REPEATED 7 TIMES] ###

Aug 10 20:25:51 CSNas kernel: nvme nvme0: Device not ready; aborting reset, CSTS=0x1

Aug 10 20:25:51 CSNas kernel: nvme nvme0: Disabling device after reset failure: -19

Nvme device dropped offline, try this: on the main GUI page click on the flash drive, scroll down to "Syslinux Configuration", make sure it's set to "menu view" (top right) and add this to your default boot option, after "append initrd=/bzroot"

nvme_core.default_ps_max_latency_us=0 pcie_aspm=off pcie_port_pm=off

e.g.:

append initrd=/bzroot nvme_core.default_ps_max_latency_us=0 pcie_aspm=off pcie_port_pm=off

Reboot and see if it makes a difference.

On 8/11/2025 at 8:01 AM, JorgeB said:

Aug 10 20:25:31 CSNas kernel: nvme nvme0: Device not ready; aborting reset, CSTS=0x1

Aug 10 20:25:31 CSNas kernel: nvme nvme0: Abort status: 0x371

### [PREVIOUS LINE REPEATED 7 TIMES] ###

Aug 10 20:25:51 CSNas kernel: nvme nvme0: Device not ready; aborting reset, CSTS=0x1

Aug 10 20:25:51 CSNas kernel: nvme nvme0: Disabling device after reset failure: -19

Nvme device dropped offline, try this: on the main GUI page click on the flash drive, scroll down to "Syslinux Configuration", make sure it's set to "menu view" (top right) and add this to your default boot option, after "append initrd=/bzroot"

nvme_core.default_ps_max_latency_us=0 pcie_aspm=off pcie_port_pm=off

e.g.:

append initrd=/bzroot nvme_core.default_ps_max_latency_us=0 pcie_aspm=off pcie_port_pm=off

Reboot and see if it makes a difference.

22 days update post your above fix - will keep you updated and THANK YOU!!!

On 8/11/2025 at 8:01 AM, JorgeB said:

Aug 10 20:25:31 CSNas kernel: nvme nvme0: Device not ready; aborting reset, CSTS=0x1

Aug 10 20:25:31 CSNas kernel: nvme nvme0: Abort status: 0x371

### [PREVIOUS LINE REPEATED 7 TIMES] ###

Aug 10 20:25:51 CSNas kernel: nvme nvme0: Device not ready; aborting reset, CSTS=0x1

Aug 10 20:25:51 CSNas kernel: nvme nvme0: Disabling device after reset failure: -19

Nvme device dropped offline, try this: on the main GUI page click on the flash drive, scroll down to "Syslinux Configuration", make sure it's set to "menu view" (top right) and add this to your default boot option, after "append initrd=/bzroot"

nvme_core.default_ps_max_latency_us=0 pcie_aspm=off pcie_port_pm=off

e.g.:

append initrd=/bzroot nvme_core.default_ps_max_latency_us=0 pcie_aspm=off pcie_port_pm=off

Reboot and see if it makes a difference.

Well, I've now got an uptime of 1 month, 7 days and counting. THANK YOU! This forum rocks!

Hi everyone,

Forgive me, but english is not my mother tongue.

I have a similar config, and similar issues.

My config :

Unraid system:	Unraid server Lifetime, version 7.2.0
Model:	JonsboN2
Motherboard:	ASUSTeK COMPUTER INC. ROG STRIX B760-I GAMING WIFI, Version: Rev 1.xx
Processor:	Intel® Core™ i5-14500 @ 4554 MHz
HVM:	Enabled
IOMMU:	Enabled
Cache:	L1 Cache = 288 KiB (max. capacity 288 KiB)
	L1 Cache = 192 KiB (max. capacity 192 KiB)
	L2 Cache = 7680 KiB (max. capacity 7680 KiB)
	L3 Cache = 24 MiB (max. capacity 24 MiB)
	L1 Cache = 256 KiB (max. capacity 256 KiB)
	L1 Cache = 512 KiB (max. capacity 512 KiB)
	L2 Cache = 4 MiB (max. capacity 4 MiB)
	L3 Cache = 24 MiB (max. capacity 24 MiB)
Memory:	32 GiB DDR5 (max. installable capacity 128 GiB)
	Controller0-DIMM0: Corsair CMK32GX5M2B6000Z30, 16 GiB DDR5 @ 6000 MT/s
	Controller1-DIMM0: Corsair CMK32GX5M2B6000Z30, 16 GiB DDR5 @ 6000 MT/s
Network:	bond0: fault-tolerance (active-backup)
	eth0: 10000 Mbps, full duplex, mtu 1500
	eth1: 2500 Mbps, full duplex, mtu 1500

Device

Parity	Samsung_SSD_870_EVO_2TB_S754NX0X704321V - 2 TB (sdb)	25 °C	1612	1717	0
Disk 1	Samsung_SSD_870_EVO_2TB_S754NX0X704719M - 2 TB (sdc)	25 °C	1315	607	0	xfs	2 TB	1.10 TB	896 GB
Disk 2	Samsung_SSD_870_EVO_2TB_S754NX0X703871B - 2 TB (sdd)	25 °C	1,278,772	553	0	xfs	2 TB	892 GB	1.11 TB
Disk 3	Samsung_SSD_870_EVO_2TB_S754NX0X704324Y - 2 TB (sde)	24 °C	1284	557	0	xfs	2 TB	431 GB	1.57 TB
	Array of four devices	25 °C	1,282,983	3434	0		6 TB	2.43 TB	3.57 TB

Pool Devices

Device	Identification	Power / Temp	Reads	Writes	Errors	FS	Size	Used	Free
Cache	Samsung_SSD_980_PRO_1TB_S5GXNU0WC34019V - 1 TB (nvme0n1)	8.49 W / 52 °C	91,550	175,418	0	btrfs	1 TB	103 GB	893 GB

Boot Device

Device	Identification	Temp	Reads	Writes	Errors	FS	Size	Used	Free
Flash	Flash_Drive_FIT - 64.2 GB (sda)	*	12,785	171	0	vfat	64.1 GB	1.01 GB	63.1 GB

I've stability issues since the beginning, i've tried many things like basic BIOS update, microcode update, memtest, RAM with or without XMP, c-state disabling, etc.

I've tried the solution posted below, and after a reboot i've encountered a crash again. I'm clueless of what append on my system, and i hope someone here can have an answer.

Have a great day,

Gauthier

nas-diagnostics-20251110-1415.zip