jgh0927

I think it was a power issue. I ended up replacing the power supply completely and no more issues!

Okay, I've done a fresh install on a vanilla USB drive, and that seems to have worked. I'll start the process of sliding things over a couple items at a time to see what the culprit was. Thanks so much!

Thanks for your help so far. Booting up in safe mode GUI has the same result. Locally on the server I can access the internet, but I can't access the server via the assigned IP. The IP is assigned by my opnsense router, and the network config (ipv4 address and DNS assignments) on unraid is automatic.

Ok, that seemed to have worked...sort of. From the display, I can now get to the internet, but I can't log in to the server from my laptop via the IP directly. Nothing has changed on my firewall rules. I can, however, log in to the server via my tailscale IP.

With my server shut off, I removed the USB, found the realtek8125 under config/plugins, and changed "r8125-driver.png" to "r8125-driver.png.bak". No change, still can't access the server other than via display. Also, I still spotted the eth0 not found error mentioned earlier during the bootup scroll, however when I boot into GUI safe mode, under System Devices (via Tools) I see "Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125 2.5 GbE Controller (rev 05)" under IOMMU group 12.

Hello all- I'm currently running 7.0.1, and I have had a flawless experience with Unraid for over a year and a half. I have been dealing with a drive error issue(https://forums.unraid.net/topic/191160-ata-errors-701/) , and I tried first to stop the array and then shut the system down to replace the SATA and power cables as recommended in another support thread, but the system locked up when I tried to stop the array. I was able to get it to gracefully shut down by tapping the power button, turned it back on, and then tried to shut it down, but it wouldn't. It hung on the web GUI for over an hour, and the server never powered down. I had to do a hard reboot, and once the system came back up, I did some googling and found that some culprits for now allowing a shutdown could be an open SSH session (not me), open terminal (possible, but after subsequent testing unlikely), or a docker container or VM preventing it from shutting down. I had been able to stop all my Docker containers, but when I tried to stop my single VM, a Home Assistant instance, the system completely locked up again. I've also tried stopping the VM service from the settings page, and selecting "safe mode" when rebooting, all with the same lockup. When the system locks up, I can't ping the server anymore. Now, I cannot log into the server web interface anymore; the browser just times out. My router sees the system with an active network connection. I cannot ping the server, it times out. I plugged in a monitor, keyboard, and mouse, and the system booted, on the display, and I can log in, but I don't know enough to know where to start troubleshooting from the command line. I did download diagnostics and will attach them. I've tried to get it to boot into safe mode via the display, and it does boot, but I still cannot access it via IP or ping the IP. I also tried to boot it into the GUI and GUI safe mode, but all I get is a blinking cursor on the display. I've also plugged in my laptop to the Ethernet cable, and all seemed to work fine network-wise on my laptop. As my last-ditch attempt before submitting this, I've pulled all my USB "extras" (Coral, Z-Wave and Zigbee controllers, Bluetooth dongle), and my Nvidia RTX video card. I was able to boot into the GUI under safe mode (huzzah!). However, I'm still unable to access the server remotely via IP, nor am I able to pull up (any) website via my browser on the server display. I also happened to notice a message during bootup along the lines of "Eth0 - Device not found". I'm at the end of my initial diagnostic efforts and not sure where to go next. Has the onboard NIC on the motherboard (ASRock - Z790 Pro RS/D4) failed...how would I test that? What should I look into next? Thanks for the assistance. howardfile-diagnostics-20250615-2059.zip

Ok, I'll check into that. But at the moment it seems I may have a bigger problem....posting a new support request.

I have an “older” thermaltake power supply, (SPD- 0600P) and used one of these (https://a.co/d/2Qkye2q) that I clipped the power to pin 3 on. That was about 18 months ago, but could that be a factor as well?

Good afternoon- Yesterday, when I was looking at my log file, I saw the errors copied below repeated multiple times. Today I got a message that one of my disks, the 16 GB Exos, had read errors, but I don't see them reflected in the SMART log. I assume that this is indicative of a drive going down, but I wanted to confirm. Thanks very much! Jun 13 04:32:02 HowardFile kernel: ata3.00: exception Emask 0x10 SAct 0x7f010 SErr 0x4490100 action 0xe frozen Jun 13 04:32:02 HowardFile kernel: ata3.00: irq_stat 0x08000000, interface fatal error Jun 13 04:32:02 HowardFile kernel: ata3: SError: { UnrecovData PHYRdyChg 10B8B Handshk DevExch } Jun 13 04:32:02 HowardFile kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jun 13 04:32:02 HowardFile kernel: ata3.00: cmd 61/98:20:68:9f:71/01:00:00:00:00/40 tag 4 ncq dma 208896 out Jun 13 04:32:02 HowardFile kernel: res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x10 (ATA bus error) Jun 13 04:32:02 HowardFile kernel: ata3.00: status: { DRDY } Jun 13 04:32:02 HowardFile kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jun 13 04:32:02 HowardFile kernel: ata3.00: cmd 61/40:60:78:f4:fd/05:00:00:07:00/40 tag 12 ncq dma 688128 out Jun 13 04:32:02 HowardFile kernel: res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x10 (ATA bus error) Jun 13 04:32:02 HowardFile kernel: ata3.00: status: { DRDY } Jun 13 04:32:02 HowardFile kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jun 13 04:32:02 HowardFile kernel: ata3.00: cmd 61/30:68:b8:f9:fd/04:00:00:07:00/40 tag 13 ncq dma 548864 out Jun 13 04:32:02 HowardFile kernel: res 40/00:01:01:4f:c2/00:00:00:00:00/00 Emask 0x10 (ATA bus error) Jun 13 04:32:02 HowardFile kernel: ata3.00: status: { DRDY } Jun 13 04:32:02 HowardFile kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jun 13 04:32:02 HowardFile kernel: ata3.00: cmd 61/a8:70:e8:fd:fd/02:00:00:07:00/40 tag 14 ncq dma 348160 out Jun 13 04:32:02 HowardFile kernel: res 40/00:ff:ff:00:00/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Jun 13 04:32:02 HowardFile kernel: ata3.00: status: { DRDY } Jun 13 04:32:02 HowardFile kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jun 13 04:32:02 HowardFile kernel: ata3.00: cmd 61/98:78:00:a1:71/02:00:00:00:00/40 tag 15 ncq dma 339968 out Jun 13 04:32:02 HowardFile kernel: res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x10 (ATA bus error) Jun 13 04:32:02 HowardFile kernel: ata3.00: status: { DRDY } Jun 13 04:32:02 HowardFile kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jun 13 04:32:02 HowardFile kernel: ata3.00: cmd 61/f0:80:98:a3:71/03:00:00:00:00/40 tag 16 ncq dma 516096 out Jun 13 04:32:02 HowardFile kernel: res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x10 (ATA bus error) Jun 13 04:32:02 HowardFile kernel: ata3.00: status: { DRDY } Jun 13 04:32:02 HowardFile kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jun 13 04:32:02 HowardFile kernel: ata3.00: cmd 61/48:88:88:a7:71/01:00:00:00:00/40 tag 17 ncq dma 167936 out Jun 13 04:32:02 HowardFile kernel: res 40/00:01:01:4f:c2/00:00:00:00:00/00 Emask 0x10 (ATA bus error) Jun 13 04:32:02 HowardFile kernel: ata3.00: status: { DRDY } Jun 13 04:32:02 HowardFile kernel: ata3.00: failed command: WRITE FPDMA QUEUED Jun 13 04:32:02 HowardFile kernel: ata3.00: cmd 61/40:90:d0:a8:71/05:00:00:00:00/40 tag 18 ncq dma 688128 out Jun 13 04:32:02 HowardFile kernel: res 40/00:01:01:4f:c2/00:00:00:00:00/00 Emask 0x10 (ATA bus error) Jun 13 04:32:02 HowardFile kernel: ata3.00: status: { DRDY } Jun 13 04:32:02 HowardFile kernel: ata3: hard resetting link Jun 13 04:32:03 HowardFile kernel: ata3: SATA link down (SStatus 0 SControl 310) Jun 13 04:32:03 HowardFile kernel: ata3: hard resetting link Jun 13 04:32:08 HowardFile kernel: ata3: link is slow to respond, please be patient (ready=0) Jun 13 04:32:13 HowardFile kernel: ata3: COMRESET failed (errno=-16) Jun 13 04:32:13 HowardFile kernel: ata3: hard resetting link Jun 13 04:32:18 HowardFile kernel: ata3: link is slow to respond, please be patient (ready=0) Jun 13 04:32:23 HowardFile kernel: ata3: COMRESET failed (errno=-16) Jun 13 04:32:23 HowardFile kernel: ata3: hard resetting link Jun 13 04:32:28 HowardFile kernel: ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Jun 13 04:32:28 HowardFile kernel: ata3.00: configured for UDMA/33 Jun 13 04:32:28 HowardFile kernel: ata3: EH complete howardfile-diagnostics-20250613-1438.zip

Hello all, first off thanks for taking a moment to read this and I hope is able to help or guide me. I was out of town the past week helping chaperon/lead a youth mission trip from my church to repair houses in the mountains and came home yesterday. Logged into Unraid today and saw that a Parity check appears to have been started 6 days ago, but is currently paused, and I have a disk 5 error. All the popup notifications also say the same. The Fix Common Problems menu says that disk 5 is disabled and that it has read errors and to look at the SMART attributes. I tried to look, but none were available, and I can't run a smart tet (possibly because the drive is disabled?) I've attached a copy of the logs...this is my first drive issue, so I'm not sure where to begin. I'm also still a little sleep-deprived. Disk 5 (an Ultrstar 12GB) was my parity drive until about a month-ish ago when I got the 18TB drives and added them. Thanks! ~Jeff howardfile-diagnostics-20240811-1529.zip