atlatonin

I have reverted to 7.0.0 and so far no issues

Yep pulled the cable out and put it back in around that time

Attached new diagnostics - this is after the issue occurred and after I deleted the network config and rebooted (so bonding is enabled again as far as I can tell, I can try disabling it again) unraid-diagnostics-20250812-2119.zip

Alright, appreciate the context. I unfortunately gotta re-open this topic, issue appeared today again.

Turned it off and so far no disconnects, thanks! Will mark as solve and re-open if needed. However, why is this happening now? Is this something that got introduced in an update between 7.0.0 and 7.1.4?

Hello, I did some mainteance a short while ago on my NAS, and since then I have frequent issues where the server is not reachable anymore from the outside (so neither from the internet via Cloudflare Tunnel, nor from other local devices on the same network). It usually fixes itself after a while, it's a bit random. I'm pretty sure it is a network/DNS problem, because disconnecting and re-connecting the LAN cable on the physical server immediately fixes it. My problem is, I did quite a few things during said mainteance (not making that mistake again!) so I have a hard time narrowing it down where the issue lies: I installed a new HDD and switched over my parity disk (aka rebuilt parity on the new HDD and setup the old one as a normal drive) I updated Unraid from 7.0.0 to 7.1.4 I installed Fan Auto Control and uninstalled it again after testing it out I set Power Mode to "Best power efficiency" and set it back to "Best performance" after discovering the issues Updated plugins and docker containers, altough I do that frequently so I doubt thats where the issue comes from Attached is my diagnostics dump, roughly 5 hours after a reboot and directly after experiencing the issues again. Thanks a lot in advance! unraid-diagnostics-20250806-1440.zip

Just did that with a newly bought usb stick. I'm gonna run a memtest when I get to it, otherwise I'll mark this as solved for now and update when the issue occurs again (hopefully this time with a working diagnostics command...)

I made a picture of the screen: https://i.imgur.com/nSJxZ92.jpeg (not very helpful I know but just so you guys know its not a typo haha). The crond messages in there arent occuring because of any input, they would just pop up every couple of seconds.

Hmm I've run a standard memtest when building the NAS without problems, I can run another later overnight. Could this maybe also happen because of the boot USB stick somehow? That one is already pretty old.

Unfortunately I have to re-open this thread, since the problem occurred again today. I tried to run diagnostics with a keyboard and monitor connected to the NAS but I just got a "diagnostics: command not found". I've then tried to copy at least the syslog manually with cp /var/log/syslog /boot/syslog.txt which failed with a "cannot create regular file /boot/syslog.txt": Input/output error" (these errors in general were popping up a lot, even when running the shutdown command). Any advice on how to get any kind of diagnostics in this situation? I have the syslog server running, unfortunately there is a big gap in the log from when I last used the server until I restarted the server. There is just one single line at 3:40am (when the mover ran I assume) which has shfs copy_file fail copying a file from cache to disk because the filename is too long. This happens apparently everytime the mover is running though so I don't think its the culprit (I'm gonna fix it anyway of course).

Ok so far 48h without the issue appearing, thank you! I'm gonna monitor for a little while longer before I mark it solved though. If you don't mind me asking what does adding this do, and whats the underlying problem here?

@bmartino1 thank you for the quick answer. It's strange since the SSD is brand new (along with everything else). The go file line is from when I was trying to get Intel QuickSync to work, I removed it. I've run Check Filesystem Status - no errors: [1/7] checking root items [2/7] checking extents [3/7] checking free space tree [4/7] checking fs roots [5/7] checking only csums items (without verifying data) [6/7] checking root refs [7/7] checking quota groups skipped (not enabled on this FS) Opening filesystem to check... Checking filesystem on /dev/nvme0n1p1 UUID: 73696a74-c953-4034-a51e-ec08d71305c7 found 100921585664 bytes used, no error found total csum bytes: 72548668 total tree bytes: 129875968 total fs tree bytes: 25231360 total extent tree bytes: 9207808 btree space waste bytes: 28074520 file data blocks allocated: 1955216793600 referenced 96725143552 I've run scrubbing - no errors: UUID: 73696a74-c953-4034-a51e-ec08d71305c7 Scrub started: Wed May 29 09:11:51 2024 Status: finished Duration: 0:00:30 Total to scrub: 94.10GiB Rate: 3.14GiB/s Error summary: no errors found And I've run an extended SMART test, results are attached (again, no errors) Anything else I should check or run? CT1000P3PSSD8_234544DB96F6-20240529-0909.txt

Hello, so my newly built NAS has been running perfectly fine for about a month or so. However, since 3 days ago I've started getting random "crashes" about once per day. It's in quotation mark because it's not really a crash, but I usually have to hard shutdown and reboot the server. Basically it seems like the networking goes down, but only part of it? So for example the Unraid web gui is inaccessible and the docker containers can't communicate with each other anymore, but I can access some of the docker containers web ui's individually. Today for some reason the web gui was working (but only under the xxx.local domain, not the actual IP weirdly enough) but none of the docker containers were accessible, so I finally managed to get diagnostics, they are attached (crash is roughly 2-3 hours before reboot, around 20:00 if my notifications are working correctly). I'm running Unraid 6.12.10. Also today after I rebooted the server the SSD cache drive was missing. After another shutdown + hard start it showed up again, still I'm kinda worried now. mausflix-diagnostics-20240528-2244.zip