daddygrant

Still crashing a few hours after the parity check is complete. I see this is the logs. Any idea what's happening here. Jun 26 01:06:56 Level1 kernel: Plex Media Scan[31375]: segfault at 0 ip 0000152d93efdb8d sp 00007ffc00f16840 error 4 in libavcodec.so.59[152d93d87000+3e0000] likely on CPU 4 (core 5, socket 0) Jun 26 01:06:56 Level1 kernel: Code: 41 56 41 54 53 0f 57 c0 0f 11 46 20 0f 11 46 10 0f 11 06 48 c7 46 30 00 00 00 00 8b 6f 10 48 8b 17 89 e9 48 89 e8 48 c1 e8 03 <8b> 04 02 0f c8 80 e1 07 d3 e0 8d 4d 10 8b 57 18 c1 e8 f0 39 ca 0f Jun 26 01:08:33 Level1 kernel: pcieport 0000:00:01.1: AER: Corrected error message received from 0000:00:01.1 Jun 26 01:08:33 Level1 kernel: pcieport 0000:00:01.1: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID) Jun 26 01:08:33 Level1 kernel: pcieport 0000:00:01.1: device [1022:1483] error status/mask=00000040/00006000 Jun 26 01:08:33 Level1 kernel: pcieport 0000:00:01.1: [ 6] BadTLP

I bought some on Amazon and waiting for them to come in. I'll report back.

Swapped with new power supply and ram. The server still crashes and reboots after the parity check. 😔

I bought a new power supply. From what I read on the forums it may be the culprit.

A few months ago, my Unraid server went offline and was stuck at the power-on message stating "DXE—CPU Initialization.." I rebooted the Server, and it started. Now, on the restart, it does a parity check, and near/close to 100%, it cycles again. This has been happening since. I'm not sure what to do next. I did swap out the USB drive. Any help would be appreciated. level1-diagnostics-20240606-1851.zip

I found the problem. Oddly enough, the local endpoint information went blank. I re-entered the information and now I'm rocking with LAN access client profile. The client profile for server only access is still not showing traffic.

Interesting thing. I got it working last night from the phone without issue. Easy as pie. But, This morning I added a few more clients and none can connect including my phone that worked fine last night. The clients say connected but that isn't reflected on the server and traffic is not passing. Firewall ports and DDNS are good. Any thoughts?

I turned off the QNAP OpenVPN service and everything is working now. Thank you.

OK. Thank you for confirming my suspicions. I'll disable it and use an openvpn docker for the same duties.

That is correct. The built in one from Qnap.

I'm experiencing something very similar with my QNAP. I moved from unraid and it was working then it was not. I looked at /etc/daemon_mgr.conf but only found "DAEMON53 = openvpn, start, QNAP_QPKG=QVPN /usr/sbin/openvpn --config /etc/openvpn/server.conf --daemon ovpn-server" and not the "stop" other have removed to solve the problem. My logs look good on the container but access is a no go. I'm receiving the error: 192.168.1.54 took too long to respond. Try: Checking the connection Checking the proxy and the firewall ERR_CONNECTION_TIMED_OUT

Yep... Thanks. Worked for me.

I'm having an issue where the unbalance webUI is not coming up despite the fact the plugin is running. Can anyone point me in the right direction?

As I was cycling through adding and removing the remote share at times it would show me a value under size. It was always 8.? GBs. During this period the share didn't actually mount. The used and free columns had no value.

@dlandon and @itimpi Thanks for the quick reply guys. I appreciate your time. @dlandon I did notice it was not mounted but sometimes it showed me 8ish under the size. Which striked me as odd. @itimpi I hear what you're saying. I did attempt to browse, unsuccessfully, from the Linux kernel side before associating the mount point with the Krusdar docker. I just didn't want to accept the truth... Good News.. I just got it to mount!!! I bounced between the CIFS and NFS share for a while like a crazy person. "The definition of insanity" Then I had the great idea to leave the unmounted config and reboot. After reboot I saw the same thing but when I started the array the share mounted. YAY! Now I wonder what protocol would be best, NFS or CIFS ?

I've used this plugin for a few years now with great success but I would like a little help on this issue. I have a ReadyNas sharing about 17TBs of Data and I'll like to share the media with my Dockers. I am able to load and mount the share via CIFS and NFS but I have run into anomalies. 1. The Size is show as 0 or incorrect Size (Not that important to me) 2. I can't see any contents of the share when browsing via docker or unraid share browser. Its just show nothing. Where am I going wrong? Thanks again for the great plugin.