pika

yes, the shutdown of the complete machine shuts down immediately when i do a quick button press. edit: while looking for the syslog server i landed in the "normal" syslog, where this error appears pretty often: Apr 22 20:33:06 DataTower kernel: pcieport 0000:00:01.2: AER: Corrected error received: 0000:00:01.0 Apr 22 20:33:06 DataTower kernel: pcieport 0000:00:01.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID) Apr 22 20:33:06 DataTower kernel: pcieport 0000:00:01.2: device [1022:15d3] error status/mask=00000040/00006000 Apr 22 20:33:06 DataTower kernel: pcieport 0000:00:01.2: [ 6] BadTLP

Hi! my system stopped/crashed twice in the last 9 days. can't reach webgui, can't ssh the system. after pushing (not pressing for a longer time) the system shut down completely. after new boot parity checks starts... didn't notice anything before the system stop... diagnostics attached! datatower-diagnostics-20240422-1954.zip

Hello! I have these two warnings: tried to search the internet but i wasn't able to solve the problems. any ideas? should i change to english and post the errors in english?

and it works again. and i had a hunch it had something todo with nordvpn - but i didn't find anything. Thanks, again!

Hello! Suddenly my openVPN docker stopped and won't start up correctly: ---Checking for optional scripts--- ---No optional script found, continuing--- ---Taking ownership of data...--- ---Starting...--- 2023-06-30 21:18:03 DEPRECATED OPTION: --cipher set to 'AES-256-CBC' but missing in --data-ciphers (AES-256-GCM:AES-128-GCM). Future OpenVPN version will ignore --cipher for cipher negotiations. Add 'AES-256-CBC' to --data-ciphers or change --cipher 'AES-256-CBC' to --data-ciphers-fallback 'AES-256-CBC' to silence this warning. 2023-06-30 21:18:03 WARNING: file '/vpn/vpn.auth' is group or others accessible 2023-06-30 21:18:03 OpenVPN 2.5.1 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on May 14 2021 2023-06-30 21:18:03 library versions: OpenSSL 1.1.1n 15 Mar 2022, LZO 2.10 2023-06-30 21:18:03 WARNING: --ping should normally be used with --ping-restart or --ping-exit 2023-06-30 21:18:03 Outgoing Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication 2023-06-30 21:18:03 Incoming Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication 2023-06-30 21:18:03 TCP/UDP: Preserving recently used remote address: [AF_INET]xxx:1194 2023-06-30 21:18:03 Socket Buffers: R=[212992->212992] S=[212992->212992] 2023-06-30 21:18:03 UDP link local: (not bound) 2023-06-30 21:18:03 UDP link remote: [AF_INET]xxx:1194 2023-06-30 21:18:03 TLS: Initial packet from [AF_INET]xxx:1194, sid=xx 2023-06-30 21:18:03 VERIFY OK: depth=2, C=PA, O=NordVPN, CN=NordVPN Root CA 2023-06-30 21:18:03 VERIFY OK: depth=1, O=NordVPN, CN=NordVPN CA8 2023-06-30 21:18:03 VERIFY KU OK 2023-06-30 21:18:03 Validating certificate extended key usage 2023-06-30 21:18:03 ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication 2023-06-30 21:18:03 VERIFY EKU OK 2023-06-30 21:18:03 VERIFY OK: depth=0, CN=xx.nordvpn.com 2023-06-30 21:18:03 Control Channel: TLSv1.3, cipher TLSv1.3 TLS_AES_256_GCM_SHA384, 4096 bit RSA 2023-06-30 21:18:03 [xx.nordvpn.com] Peer Connection Initiated with [AF_INET]xxx:1194 2023-06-30 21:18:04 SENT CONTROL [xx.nordvpn.com]: 'PUSH_REQUEST' (status=1) 2023-06-30 21:18:09 SENT CONTROL [xx.nordvpn.com]: 'PUSH_REQUEST' (status=1) 2023-06-30 21:18:09 AUTH: Received control message: AUTH_FAILED 2023-06-30 21:18:09 SIGTERM[soft,auth-failure] received, process exiting i haven't changed anything regarding my provider and haven't changed a thing on the docker... vpn.auth credentials are valid, account is active.

huh, tried the update. server didn't boot after "restart server now". had to press the power button... that shouldn't happen, right? edit: parity check runs again after manual boot. so i guess there was something wrong during the update? should i provice another diagnostics?

is it safe to update to 6.11.5 ? using the TBS-OpenSource package with my TBS-6902.

Hello! I'm on unraid 6.11.2 and my system went down 3 days ago (no idea why, no power shortage). after new start i saw parity check starting and i did not inquire further (no time atm). today i opened the dashboard and there are were several things missing: all the infos in the marked areas were missing (while i was typing the first lines of this post they came back)... i was not able to download diagnostics, also working again now. i saw these errors in the syslog: Jan 13 20:24:18 DataTower kernel: pcieport 0000:00:01.2: AER: Corrected error received: 0000:00:01.0 Jan 13 20:24:18 DataTower kernel: pcieport 0000:00:01.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID) Jan 13 20:24:18 DataTower kernel: pcieport 0000:00:01.2: device [1022:15d3] error status/mask=00000040/00006000 Jan 13 20:24:18 DataTower kernel: pcieport 0000:00:01.2: [ 6] BadTLP Jan 13 20:24:18 DataTower kernel: pcieport 0000:00:01.2: AER: Multiple Corrected error received: 0000:00:01.0 Jan 13 20:24:18 DataTower kernel: pcieport 0000:00:01.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID) Jan 13 20:24:18 DataTower kernel: pcieport 0000:00:01.2: device [1022:15d3] error status/mask=00001040/00006000 Jan 13 20:24:18 DataTower kernel: pcieport 0000:00:01.2: [ 6] BadTLP Jan 13 20:24:18 DataTower kernel: pcieport 0000:00:01.2: [12] Timeout Jan 13 20:24:18 DataTower kernel: pcieport 0000:00:01.2: AER: Corrected error received: 0000:00:01.0 Jan 13 20:24:18 DataTower kernel: pcieport 0000:00:01.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID) Jan 13 20:24:18 DataTower kernel: pcieport 0000:00:01.2: device [1022:15d3] error status/mask=00000040/00006000 Jan 13 20:24:18 DataTower kernel: pcieport 0000:00:01.2: [ 6] BadTLP Jan 13 20:24:48 DataTower kernel: pcieport 0000:00:01.2: AER: Corrected error received: 0000:00:01.0 Jan 13 20:24:48 DataTower kernel: pcieport 0000:00:01.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID) Jan 13 20:24:48 DataTower kernel: pcieport 0000:00:01.2: device [1022:15d3] error status/mask=00000040/00006000 Jan 13 20:24:48 DataTower kernel: pcieport 0000:00:01.2: [ 6] BadTLP Jan 13 20:24:51 DataTower kernel: pcieport 0000:00:01.2: AER: Corrected error received: 0000:00:01.0 Jan 13 20:24:51 DataTower kernel: pcieport 0000:00:01.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID) Jan 13 20:24:51 DataTower kernel: pcieport 0000:00:01.2: device [1022:15d3] error status/mask=00000040/00006000 Jan 13 20:24:51 DataTower kernel: pcieport 0000:00:01.2: [ 6] BadTLP no idea what this means. looks like everything is working for now but i think there is something wrong with my system... could somebody please take a look at my diagnostics? have a nice day! datatower-diagnostics-20230114-1024.zip

didn't find anything in syslog, Diagnostics via PM!

works for me! thanks haven't found the time to check for aem errors. i think i'll notice on sunday (tatort!).

uhm, where do i look? on my unraid server? or on the client?

Thanks! hopefully that will fix my little "freeze" problems (i have some very short freezes once or twice an hour).

did you figure this out? these logs (how do i read them?) occupy my whole cache drive (only for today there are 252 = 24,5GB)... yesterday i had to manually delete some files so i could enter mariaDB console to dump the logs older than a day...

swag showed nothing special. i don't understand why i can't duckdns.org (see screenshot above)...

i'm getting a wrong certificate when i'm trying to access my cloud (secured with swag/duckdns). had some problems in the past (duckdns gave back wrong ip address), so i tried to log into duckdns.org: am i missing something or is something wrong with duckdns?