hans_solo_dolo

This issue has plagued me for sometime even before 7.0.0. I also have this line in my logs tons of times. I am running an 11th Gen Intel® Core™ i5-11400 @ 2.60GHz. Doesn't seem to have any rhyme or reason. Eventually it will go away or my machine will become unresponsive. I have standard plex/arr/krusader/pihole/qbit dockers. I ssh in and stop docker service and restart and issue goes away for a while. I also have a Cloudflare url pointing to it but not sure if related. I have thought about going to a directory instead of an Img for docker.

@bmartino1 some developments. My plex and all other services were down again. I couldn't immediately connect to local IP so I thought disabling one of the NICs might at least let me access it. I was able to get onto the dashboard and pull diagnostics (CPU was pinned to 100% on the dashboard). Rather than reboot I tried HTOP and saw usage was mostly normal but still pinned on the dashboard. very odd (see pic). I tried stopping a couple dockers I thought might be the culprit like cloudflared but CF didn't stop. I then stopped docker and started again and it resolved the issue w/o a reboot. So there is either a docker or something in the docker service tying it up. Happy thanksgiving! unraid-server-diagnostics-20241128-AFTER DOCKER RESTART.zip unraid-server-diagnostics-20241128-BEFORE DOCKER RESTART.zip pics.zip

@bmartino1anything in the logs give you a clue? It will suck but I think I will shut down my cloudflare tunnels, maybe I'm getting DDOS'd?

@bmartino1it passed memtest 3 times

@bmartino1thank you. I thought I had waited long enough but might have been a little early to call it. My biggest concern is why it's going unresponsive to begin with. I'll check memtest.

Unsure where to go. Unraid dockers were unresponsive, but I was able to ssh in, although VERY slow. Nothing seemed out of the ordinary so I issued a reboot command. The reboot got hung up on "Starting diagnostic collection". Having felt defeated, I pressed the reboot button on the computer. It just gave me a black screen from HDMI. Tried again, same thing. It wasn't until I killed power to the outlet that I was finally able to get the server back up. Any ideas? Thanks! syslog-192.168.1.65.log unraid-server-diagnostics-20241121-1423.zip

LSI wasnt an issue but I swapped the CMOS battery at the same time (as suggested by ArtOfServer). Existing one was reading 2.89v and brand new was 3.3v I then put Dell back and have been running strong for a couple days. Wild if that little button battery could have been the issue all along. (also a CMOS reset by default so maybe that too)

I've tried a different PCI slot (swapped the 16e and 8i) and experienced the same issue. I then got another HBA and same thing. I tried it without the 16e and the problem seems to go away. It seems, for now at least, it only occurs when the second PCI slot is filled (keep in mind I have a 10g nic in the third slot and hasn't been an issue) I also tried it with just the 16e (using an internal to external adapter and SAS cable) and the issue was gone. So now I'm thinking maybe motherboard? PSU? Thoughts? I have an LSI card showing up to remove the possibility the Dell is causing compatibility issues Thanks!

Does the post read cycle verify it cleared successfully? I had an issue with a different hba card so I stopped the current operation on several drives to shutdown and troubleshoot. I have now solved that issue and continued from where I left off. I’m not sure if I trust it unless the post read checks that for me.

One other thing worth mentioning is when I reboot the server, the drives are gone from the system and I have to reboot a couple times for them to show back up and a couple times, two random drives were disabled and I had to resync. Shutting down and waiting doesn't seem to help so I'm not sure if a cooling issue. Right now I have a fan on it and running without the top on to help

All 8 of the drives attached to the HBA all of a sudden have read errors. I can resolve and be stable for a week or two but if I reboot or enough time passes, eventually get the read errors and end up rebooting two three times and the issues go away. Tried different BIOS settings and such. Almost thought I found the issue when I noticed a 4 pin power plug not plugged in on the motherboard for the CPU (thought maybe the CPU was stealing power from MB or something like that) I have a 850W psu, not sure if that could be an issue (using a calc it says i only need 500W) I have the 8i card and a 16e card and a 10GB NIC card attached. Would love your feedback, thanks! I am working on expanding my array and using a 16e card with an external enclosure. Would it be smart rather than getting another 8i to just use the two ports on the 16e I wont be using? So going from the breakout cable to a 8077-8088 adapter and a short 8088 cable to connect at the back of the case. Thanks again (and nevermind some of the file names you'll see in the logs, thats just how I name my taxes) This is the relevant line that starts the read errors Jun 18 11:40:46 UnRaid-Server kernel: mpt2sas_cm0: SAS host is non-operational !!!! unraid-server-diagnostics-20240618-1148.zip

Interesting that turning ASPM on seemed to make everything happy and work together. I also reseated the card for good measure. Thanks for the reply!

I have had a couple times this past week or so with major errors with my array where all disks attached to the SAS expander card would be unavailable. Woke up to an array that wasn't available and a full log file. This sort of happened when I replaced a 10GBaseT card with an SFP+ one. Not sure if related. A day or so later, it said one of my drives failed so I replaced and rebuilt the array. Then I had an unresponsive server. After some reboots and updating BIOS and ensuring BIOS settings are correct, I finally was able to get it booted and working when I pulled the GPU. So far so good. So not sure if related to the GPU or not, or maybe its some sort of PCI lane issue with the mobo or power management with PCI. Or it could be the SAS card failing. Some help is appreciated. I've attached logs from when it happened two times. At the end of the two logs are the read errors which continue almost infinitely. logs relevent #2.txt logs relevent.txt unraid-server-diagnostics-20240411-1209.zip

Thank you! I upgraded shortly after 6.11 released and made the change and havent had this issue again

I would except with the file permission issues I had with 6.10 all the way to 6.10.3. I saw quite a few others with the same problem.

I mean servers are supposed to be on 24/7 but you can use a smart plug like a kasa hs105 or something like that. And make sure there's a setting in bios to turn on after getting power restored. Then, when you want to turn it on, just reset the outlet.

I went ahead and turned off the pihole docker (it was a backup to my pi anyways) we'll see how long I can go with out a crash!

The only docker I have running in br0 with its own ip address is pihole. I had countless file permission issues with v6.10. Do you think just stopping pihole will resolve my issue? Thank you

syslog (2)I also posted the syslog file here. I had crashes at Sept 9 12:03p, Sept 4 7:43a, Sept 1 2:54p, Aug 22 2:58a. Thanks for the help

This is the result from df -h / Filesystem Size Used Avail Use% Mounted on rootfs 16G 1.7G 14G 11% / I had the larger docker image size just to avoid it filling up. I'm at 16gb now and I think I just went to 120 since I have plenty of space on my cache so didn't want to deal with it again.

I'm the OP, I posted the last few lines from syslog. I have it mirroring to usb

Bump

unraid-server-diagnostics-20220910-1004.zip Diagnostics attached. I have tried deleting some plugins not used and disabling igmp snooping and stp for the port on my switch and still have the issue.

I have had this issue for a while and can't quite nail it down. My server will randomly hang and become unresponsive, requiring me to reboot on the machine. Cannot access via webgui, ssh, or via monitor plugged in. Never any real info in the logs from what I can tell. Here are from the last time this happened. My server locked up later around 12:01pm or so but the logs stopped until I rebooted. The last line is concerning. Sep 9 11:53:12 UnRaid-Server kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth367ca58: link becomes ready Sep 9 11:53:12 UnRaid-Server kernel: docker0: port 18(veth367ca58) entered blocking state Sep 9 11:53:12 UnRaid-Server kernel: docker0: port 18(veth367ca58) entered forwarding state Sep 9 11:53:21 UnRaid-Server kernel: docker0: port 18(veth367ca58) entered disabled state Sep 9 11:53:21 UnRaid-Server kernel: vethd0ae93e: renamed from eth0 Sep 9 11:53:21 UnRaid-Server kernel: docker0: port 18(veth367ca58) entered disabled state Sep 9 11:53:21 UnRaid-Server kernel: device veth367ca58 left promiscuous mode Sep 9 11:53:21 UnRaid-Server kernel: docker0: port 18(veth367ca58) entered disabled state Sep 9 11:54:21 UnRaid-Server kernel: docker0: port 18(vethee550ee) entered blocking state Sep 9 11:54:21 UnRaid-Server kernel: docker0: port 18(vethee550ee) entered disabled state Sep 9 11:54:21 UnRaid-Server kernel: device vethee550ee entered promiscuous mode Sep 9 11:54:21 UnRaid-Server kernel: docker0: port 18(vethee550ee) entered blocking state Sep 9 11:54:21 UnRaid-Server kernel: docker0: port 18(vethee550ee) entered forwarding state Sep 9 11:54:21 UnRaid-Server kernel: docker0: port 18(vethee550ee) entered disabled state Sep 9 11:54:21 UnRaid-Server kernel: eth0: renamed from vethd3a5f8d Sep 9 11:54:21 UnRaid-Server kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethee550ee: link becomes ready Sep 9 11:54:21 UnRaid-Server kernel: docker0: port 18(vethee550ee) entered blocking state Sep 9 11:54:21 UnRaid-Server kernel: docker0: port 18(vethee550ee) entered forwarding state Sep 9 11:54:26 UnRaid-Server kernel: docker0: port 18(vethee550ee) entered disabled state Sep 9 11:54:26 UnRaid-Server kernel: vethd3a5f8d: renamed from eth0 Sep 9 11:54:26 UnRaid-Server kernel: docker0: port 18(vethee550ee) entered disabled state Sep 9 11:54:26 UnRaid-Server kernel: device vethee550ee left promiscuous mode Sep 9 11:54:26 UnRaid-Server kernel: docker0: port 18(vethee550ee) entered disabled state Sep 9 11:54:27 UnRaid-Server kernel: general protection fault, probably for non-canonical address 0x49e5ef1403d70: 0000 [#3] SMP NOPTI Sep 9 11:54:27 UnRaid-Server kernel: CPU: 0 PID: 8290 Comm: Disk Tainted: P D W O 5.10.28-Unraid #1 Sep 9 11:54:27 UnRaid-Server kernel: Hardware name: ASUS System Product Name/PRIME Z590-A, BIOS 1202 10/27/2021 Sep 9 11:54:27 UnRaid-Server kernel: RIP: 0010:page_vma_mapped_walk+0x209/0x4dc

One of the recent updates is causing my gpu to not go to a sleep state. Would go to P8 after a single login. Now it goes to sleep mode for a second or two and then goes back to P0. Not sure what caused it