Nexal

I had just lost connectivity to the Unraid Web UI. Uncertain if this is the same issue as before because while I did also loose access to one of the two docker services I was running, my plex service was still able to load new video data into the buffer which seem to be different than previous times this has occurred. This is also the first time I have seen the following in the logs: Error: eth0 does not have a valid IP address Curious to get an outside perspective. Thanks! syslog

@JorgeB I will try this. To clarify the procedure: I turn on the Syslog server and set to save the files to USB. Once the disconnection occurs, I should use the command line to shut down the computer. After plugging in the USB stick into my client machine I should have a file somewhere that I need to upload? Will this look different from the diagnostic files? Thanks in advance for the guidance.

I don't believe so. In my pfsense router I have assigned a static IP to the virtual machine's mac address. Additionally, the two other VMs I have don't have any issues with connectivity. I would expect these issues to be occurring on both machines with duplicated IP addresses if this were the problem. But happy to hear an alternative perspective if that's not how these kinds of things work.

Hello everyone, I recently upgraded my Unraid server from a QNAP TS-873A to a custom built machine with significantly higher capabilities. However, ever since I have switched machines, I have had nothing but problems getting consistent access to Unraid. To clarify, the Web GUI, Samba, and docker web-based service are all available when the server first boots, but after what seems like a random amount of time (maybe 30-45 min on average) they all become unavailable simultaneously, often while I am actively using them. I am still able to access the server via the command line sitting at the server itself (not through the network) which shows me the server is still operational and has not frozen. From the CLI I can validate the network connection is still live and I can ping both my router and client computers successfully. The new specs are below (in case it helps diagnose the issue): - Intel Core i14700K CPU - Crucial Pro RAM 96GB Kit (2x48GB) DDR5 5600MT/s - GIGABYTE Z790 AERO G Motherboard - 10Gb SFP+ PCI-E Network Card NIC, with Broadcom BCM57810S Chip, Dual SFP+ Port - LSI SAS9300-16I 9300-16I 16-PORT 12GBPS PCIe HBA (for Unraid array) - 8x Seagate Exos X20 ST20000NM007D 20TB 7.2K RPM SATA 6Gb/s 3.5in Hard Drive - 3x TEAMGROUP MP34 4TB 3D NAND TLC NVMe (2x for cache drives, 1x for VMs) - 2x SAMSUNG 870 EVO SATA SSD 250GB 2.5” (for mirrored Proxmox install, unmapped in Unraid) - ZOTAC Gaming GeForce RTX 4080 Super (For Windows VMs) - EVGA Supernova 1000 P3, 80 Plus Platinum 1000W As both an experiment and also info gathering step, I have tried to run Unraid both on bare metal, and also as an Proxmox VM with PCIe passthrough for my HBA and NVMe drives. Unfortunately, I am experiencing the same issues both with and without Unraid being virtualized. What I have tried: - Currently running the memtest that comes with Unraid. After multiple hours the tests passed with 0 errors. - Turning off all VMs and Docker Containers - Using Tips and Tweaks plugin to disable NIC Flow Control and NIC Offload (per this post: https://forums.unraid.net/topic/133745-network-issue-server-sometimes-cant-be-reached-without-reseting-network-connection/?do=findComment&comment=1215477) I have gone through the logs and there was one line that stood out to me, but it's possible it could just be circumstantial: - Apr 1 13:58:46 NAS ntpd[1459]: no peer for too long, server running free now Diagnostics are attached below, some from when the Web GUI does briefly return, and others from running `diagnostics` from the command line before the Web GUI is available. Any support on what to do next would be greatly appreciated as I have now been unsuccessful in independently diagnosing the issue for nearly two weeks now. Thanks in advance. nas-diagnostics-20240401-1434.zip nas-diagnostics-20240401-1214.zip nas-diagnostics-20240402-0948.zip nas-diagnostics-20240403-0722.zip

Hello everyone, I have recently upgraded my server and in the process, have migrated my Unraid instance to run inside Proxmox as a VM (uses PCI passthrough for HBA and NVMe drives). My thinking is that this would still give me all of the functionality I love from unraid regarding data storage and access, but also allow me to have a much more robust hypervisor than what Unraid supports. When I first boot up the Unraid VM, everything appears to be working without issue. However, after some variable amount of time (typically 20-45 minutes), the network interface becomes unavailable. I am unable to load the web GUI or access any of the SMB shares. However, I am able to access the shell via the VM's video out. Using the shell, I can see that the eth0 interface is still up and still can be pinged. From the Unraid VM I can also successfully ping my router as well as see in my pfsense web gui that the static IP is still assigned, valid, and connected. During all of these steps, the Unraid web GUI remains unavailable. However, whenever I ping my client computer's IP address, the Unraid GUI becomes available moments after the ping successfully begins returning data. Possibly just a coincidence, but seems to be a surefire way to regain access at the moment. I have attached the logs. One line in particular that seems like it may be relevant is : Apr 1 13:58:46 NAS ntpd[1459]: no peer for too long, server running free now This line can be observed around the same time the web gui becomes inaccessible. I'd be curious if this has anything to do with the problem I'm experiencing. Thanks in advance for any support. nas-diagnostics-20240401-1434.zip