Rabbithacker921

Members
  • Posts

    11
  • Joined

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Rabbithacker921's Achievements

Noob

Noob (1/14)

0

Reputation

1

Community Answers

  1. replaced cabled, seems to be working much better now. Thanks again unraidtower-diagnostics-20231011-2053.zip
  2. I bought new cables cause i thought that might be the case. Thanks for the quick reply. Will try that as soon as they come in.
  3. Hi all, I've been running an unRAID server for about a year now. In the past few months I've noticed a small number of parity check errors popping up, but this last parity check showed a very large number of errors. Two months ago, one of my hard drives failed and I had to rebuild it. I tracked the issue down to a loose SATA cable connected to that drive. I made sure to securely connect the new replacement drive. However, this most recent parity check on October 6, 2023 showed over 175,000 errors. I've attached diagnostics from the server and a screenshot showing the history of parity checks and errors. I'm concerned that these errors indicate a serious issue, perhaps with the parity drive itself or another disk. Has anyone experienced something similar or have any ideas on how I can track down the source of the errors? I want to identify and fix the problem before I lose any data. Any insights or advice would be greatly appreciated! I've been loving unRAID so far and want to make sure my server stays stable. Please let me know if any other details would be helpful. Thanks! Ps. I had the correct errors box selected. Is this recommended or should i have that turned off. unraidtower-diagnostics-20231006-2130.zip
  4. i dont know if you figured out the answer yet, but for me it was just to add this before location in the advanced config in NPM port_in_redirect off; It will look like this # Increase buffer size for large headers # This is needed only if you get 'upstream sent too big header while reading response # header from upstream' error when trying to access an application protected by goauthentik proxy_buffers 8 16k; proxy_buffer_size 32k; port_in_redirect off; location / { # Put your proxy_pass to your application here proxy_pass $forward_scheme://$server:$port; # authentik-specific config auth_request /outpost.goauthentik.io/auth/nginx; error_page 401 = @goauthentik_proxy_signin; auth_request_set $auth_cookie $upstream_http_set_cookie; add_header Set-Cookie $auth_cookie; # translate headers from the outposts back to the actual upstream auth_request_set $authentik_username $upstream_http_x_authentik_username; auth_request_set $authentik_groups $upstream_http_x_authentik_groups; auth_request_set $authentik_email $upstream_http_x_authentik_email; auth_request_set $authentik_name $upstream_http_x_authentik_name; auth_request_set $authentik_uid $upstream_http_x_authentik_uid; proxy_set_header X-authentik-username $authentik_username; proxy_set_header X-authentik-groups $authentik_groups; proxy_set_header X-authentik-email $authentik_email; proxy_set_header X-authentik-name $authentik_name; proxy_set_header X-authentik-uid $authentik_uid; } # all requests to /outpost.goauthentik.io must be accessible without authentication location /outpost.goauthentik.io { proxy_pass http://outpost.company:9000/outpost.goauthentik.io; # ensure the host of this vserver matches your external URL you've configured # in authentik proxy_set_header Host $host; proxy_set_header X-Original-URL $scheme://$http_host$request_uri; add_header Set-Cookie $auth_cookie; auth_request_set $auth_cookie $upstream_http_set_cookie; # required for POST requests to work proxy_pass_request_body off; proxy_set_header Content-Length ""; } # Special location for when the /auth endpoint returns a 401, # redirect to the /start URL which initiates SSO location @goauthentik_proxy_signin { internal; add_header Set-Cookie $auth_cookie; return 302 /outpost.goauthentik.io/start?rd=$request_uri; # For domain level, use the below error_page to redirect to your authentik server with the full redirect path # return 302 https://authentik.company/outpost.goauthentik.io/start?rd=$scheme://$http_host$request_uri; }
  5. I fixed it, it was either the power supply, or the other setting for C States that i found buried in the Advanced settings of the motherboard.
  6. just to update, i found another setting in the bios about c states so i disabled that, previously i disabled a c6 setting. Hopefully it will make a difference. Its been on for about 20 hours now so fingers crossed.
  7. I replaced the power supply, and i replaced the Cmos battery. We will see if that makes any difference. If not, i do have a 10700k that is currently in a prebuilt HP Omen 30L. I could buy a new motherboard and use that for my server if need be.
  8. Ive attached syslog. it looks like it crashed after about 3 hours last night. I noticed clock unsynchronized so i'm going to buy a replacement cmos battery today. syslog
  9. just set it up and then rebooted. as soon as i have my next crash i will upload. Thank you very much.
  10. Thank you for the link. i will check it out, i will post diagnostics now. If i need to wait for a crash just let me know unraidtower-diagnostics-20220607-2319.zip
  11. I build a unraid server with older hardware. I have really enjoyed the whole experience. I created a few shares and started transferring some media files over. Im waiting for some larger hdds to arrive and a new case, so I've just been tinkering around with learning how to set up VMs, and Dockers to gain experience for when i built the permanent server. The next day i noticed the server doing another pairty check. I learned that happens as a result of unclean shutdown and determined that to be the case. I think i've narrowed it down to either my cpu, a Ryzen 3 1200, or my power supply. Most recently I ran prime 95 on the server. oddly enough it ran fine for about 15 minutes, and it wasn't until i canceled the stress test that it rebooted about a minute later. I've included some of the syslog, I had it building a file for over a week and didnt want to share a 4mb log. Hopefully it has some information that is useful. If theres something better i can provide please let me know. I want to rule out any software issues before i order any replacement parts. Thank you all for your dedication. Ps. If you believe it to be the cpu, do you recon i should order a new one, or scrap the idea of using the AM4 motherboard and just move to an intel based system? Thanks again for taking the time. CPU: Ryzen 3 1200 14nm Motherboard: ASRock AB350 Pro4 ATX AM4 Ram:2x8gb XPG Z1 DDR4 3200MHz PSU: coolermaster MVE bronze 500 GPU: Zotac 1070 mini (could be removed, i just used it for the initial install and left it in) syslog.txt