The server crashes every few days/every day. I am a new Unraid user and I cannot deal with server issues.

The server crashes from time to time (sometimes every day, sometimes every few days) and cannot be connected to. I am attaching the logs.

I started the log server because when the server crashes, it is impossible to connect to it via the GUI or Windows SMB. I searched Google for error messages from the logs, read about them, and looked for solutions, but still without success. The NAS is mainly used for Plex and as data storage.

What I have tried:

-I replaced the SATA cables because I thought they were faulty.

-I replaced the PSU, it is currently connected, but the problem has still not been fixed.

-I ran Memtest, and it came back OK.

-I am currently trying the server with a change from macvlan to ipvlan (somewhere it was mentioned that this could also be the cause).

I ordered a new motherboard, but I have to wait for it. What else can I do?

server-diagnostics-20251121-1034.zip

2 hours ago, chronosik said:

I am currently trying the server with a change from macvlan to ipvlan

This has not been an issue since 6.12.11

Enable the syslog server and post that after a crash.

@JorgeB

Last lanes in syslog before crash is:
Nov 21 04:52:53 DMAR: DRHD: handling fault status reg 3

Nov 21 04:52:53 [DMA Write NO_PASID] Request device [00:17.0] fault addr 0x40178535000 [fault reason 0x04] Access beyond MGAW

syslog-192.168.100.4.txt

Those and the other call traces may indicate a hadrware issue, like bad RAM, but there is also a problem with the flash drive:

Nov 20 09:24:43 xfect-server kernel: SQUASHFS error: Unable to read fragment cache entry [ac385dc]
Nov 20 09:24:43 xfect-server kernel: SQUASHFS error: Unable to read page, block ac385dc, size 8e50
Nov 20 09:24:43 xfect-server kernel: I/O error, dev loop0, sector 776368 op 0x0:(READ) flags 0x800 phys_seg 14 prio class 2
Nov 20 09:24:43 xfect-server kernel: SQUASHFS error: Failed to read block 0x17b16c30: -5
Nov 20 09:24:43 xfect-server kernel: I/O error, dev loop0, sector 776368 op 0x0:(READ) flags 0x800 phys_seg 14 prio class 2
Nov 20 09:24:43 xfect-server kernel: SQUASHFS error: Failed to read block 0x17b16c30: -5
Nov 20 09:24:43 xfect-server unassigned.devices: Mounting partition 'sde1' at mountpoint '/mnt/disks/UNRAID'...
Nov 20 09:24:43 xfect-server unassigned.devices: Error: Cannot mount device '/dev/sde1' with label 'UNRAID'.
Nov 20 09:25:01 xfect-server kernel: fat__get_entry: 118 callbacks suppressed
Nov 20 09:25:01 xfect-server kernel: FAT-fs (sda1): Directory bread(block 30720) failed
Nov 20 09:25:01 xfect-server kernel: FAT-fs (sda1): Directory bread(block 30721) failed
Nov 20 09:25:01 xfect-server kernel: FAT-fs (sda1): Directory bread(block 30722) failed
Nov 20 09:25:01 xfect-server kernel: FAT-fs (sda1): Directory bread(block 30723) failed

So I would start there, try using a different USB port, if it still happens, replace it.

The problem with the flash drive occurred after the crash. The thing is, at that time it was possible to enter the GUI, but it did not detect the flash drive—it said that it was blacklisted, but after restarting everything was fine.

To be sure, I will do as you say.

I removed one RAM chip and changed the USB port for the flash drive.

I deleted the old system logs. After the next crash, it will be easier to see what caused it.

I think I'll be back here soon :/

Update:

- I changed the PSU.

- I read the motherboard manual and it recommended inserting RAM into slots A2 and B2 (previously I had A1 and B1).

- I changed the USB port from the flash drive with the unRAID installation.

So far, no errors have appeared.

I'm back :/

I'm getting a lot of errors again that I've had before. I replaced the motherboard and it's exactly the same, so it's not the motherboard's fault.
I changed the cables again, switched the ATA ports, but it's still the same.

Sometimes it's parity, sometimes it's the second drive. I don't think both drives are bad, they're new.

Any ideas?

Dec  3 09:11:04 xfect-server kernel: ata7.00: exception Emask 0x0 SAct 0x3f003ffc SErr 0x50000 action 0x6 frozen
Dec  3 09:11:04 xfect-server kernel: ata7: SError: { PHYRdyChg CommWake }
Dec  3 09:11:04 xfect-server kernel: ata7.00: failed command: READ FPDMA QUEUED
Dec  3 09:11:04 xfect-server kernel: ata7.00: cmd 60/b8:10:18:b5:e3/01:00:b6:00:00/40 tag 2 ncq dma 225280 in
Dec  3 09:11:04 xfect-server kernel:         res 40/00:01:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Dec  3 09:11:04 xfect-server kernel: ata7.00: status: { DRDY }
Dec  3 09:11:04 xfect-server kernel: ata7.00: failed command: READ FPDMA QUEUED
Dec  3 09:11:04 xfect-server kernel: ata7.00: cmd 60/60:18:d0:b6:e3/00:00:b6:00:00/40 tag 3 ncq dma 49152 in
Dec  3 09:11:04 xfect-server kernel:         res 40/00:01:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Dec  3 09:11:04 xfect-server kernel: ata7.00: status: { DRDY }

Dec  3 22:03:45 xfect-server kernel: ata6.00: exception Emask 0x0 SAct 0xffffffff SErr 0x50000 action 0x6 frozen
Dec  3 22:03:46 xfect-server kernel: ata6: SError: { PHYRdyChg CommWake }
Dec  3 22:03:46 xfect-server kernel: ata6.00: failed command: READ FPDMA QUEUED
Dec  3 22:03:46 xfect-server kernel: ata6.00: cmd 60/68:00:a8:c6:2d/01:00:cc:00:00/40 tag 0 ncq dma 184320 in
Dec  3 22:03:46 xfect-server kernel:         res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Dec  3 22:03:46 xfect-server kernel: ata6.00: status: { DRDY }
Dec  3 22:03:46 xfect-server kernel: ata6.00: failed command: READ FPDMA QUEUED
Dec  3 22:03:46 xfect-server kernel: ata6.00: cmd 60/58:08:10:c8:2d/00:00:cc:00:00/40 tag 1 ncq dma 45056 in
Dec  3 22:03:46 xfect-server kernel:         res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Dec  3 22:03:46 xfect-server kernel: ata6.00: status: { DRDY }
Dec  3 22:03:46 xfect-server kernel: ata6.00: failed command: READ FPDMA QUEUED
Dec  3 22:03:46 xfect-server kernel: ata6.00: cmd 60/40:10:68:c8:2d/00:00:cc:00:00/40 tag 2 ncq dma 32768 in
Dec  3 22:03:46 xfect-server kernel:         res 40/00:01:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Dec  3 22:03:46 xfect-server kernel: ata6.00: status: { DRDY }

server-diagnostics-20251204-0924.zip

Any power splitters in use? It's also worth trying with a different PSU if you have one.

No power splitters. I tried a second PSU, Pure Power 12 550w 80plus gold - it did the same thing. Of course, the PSU was new.

Edited December 4, 2025Dec 4 by chronosik

If everything else has been replaced, it could be the actual disks. They don't have a brand. Were these refurbished/remanufactured drives?

These are SEAGATE EXOS 24TB Refurbished by the manufacturer- ST24000NM000C.

I would recommend trying a different disk, I've had terrible experiences with refurbished disks, so much so that I wouldn't take them for free.

I will probably order new disks soon and check it out, but it takes a lot of time to rebuild the array. I treat it as a last resort.

I noticed that when I turn on Mover and transfer data from disk1 to disk2, after a short time these errors pop up and Mover stops working. The bar shows that Mover is running, but it does nothing at all. The percentages remain unchanged (I checked for several hours and % did not moved).

For now, I've played around in the BIOS and turned off all the energy-saving options, ASPM, etc., and so far it's working. I'm transferring data from disk1 to disk2 and I don't see any errors for now.

I think its a 7.2 issue, I had the same problem with crashes, pretty sure its linked to the intel iGPU

https://forums.unraid.net/bug-reports/prereleases/69x-611x-intel-i915-module-causing-system-hangs-with-no-report-in-syslog-not-alder-lake-r1674/page/14/?tab=comments#comment-36452

I wanted to update the thread.

I removed Autotweak and turned off energy saving modes – it now consumes about 45W, compared to about 42W previously.

I swapped the drives around. I put the Toshiba drive as parity and the two recertified Seagate drives as an array.

I've been testing it for a week and the problem has not occurred.