rawfuls

Ah, that's what I feared. I removed the low profile mount and never bought a full size mount, but do recall reseating the board cleanly. Since my time is limited, I think having a replacement on hand is probably smarter than trying something and having it fail again in a week. Thanks!

Woke up this morning to a plethora of issues in the email notification system. Had a similar instance in which disk1/disk3 also had the same failures. I ran SMART long test and it all passed. Assuming it was a bad cable connection, I unplugged and replugged, then rebuilt the drive (set drive as NA, started array. Stopped, set drive as identifier, started array. Rebuilt). However, this time around it seems disk1/2/5 are seeing issues. However, I also noticed when I logged into the WebGUI this morning, only disk1 was showing disabled on the dashboard. I tried stopping the array, it wouldn't; so about 45mins later, I rebooted. It's never come up since (server is at my parent's house). (can't ping server IP via VPN). I do plan on stopping by sometime this upcoming week to take a look, but want to see if anybody had some insight. Should I start shopping for a new controller? Controller: SAS9201-8I LSI **** disk1 (ST4000LM024-2AN17V_WFF0FXMF) is disabled **** **** parity (WDC_WD100EMAZ-00WJTA0_JEKU74UZ) has read errors **** **** disk1 (ST4000LM024-2AN17V_WFF0FXMF) has read errors **** **** disk2 (ST4000LM024-2AN17V_WCK2F91N) has read errors **** **** disk3 (ST4000LM024-2AN17V_WCK2SVE2) has read errors **** **** disk4 (ST4000LM024-2AN17V_WCK2SV4V) has read errors **** **** disk5 (WDC_WD50EZRX-00MVLB1_WD-WX31D15P76C3) has read errors **** **** parity2 (WDC_WD100EMAZ-00WJTA0_JEKTZ10Z) has read errors **** **** /var/log is getting full (currently 84 % used) **** **** Unable to write to disk1 **** **** Unable to write to disk2 **** **** Unable to write to disk5 **** hoangserver-diagnostics-20200913-0836.zip

This was it, thanks a ton @alturismo!

Seeing a variety of different issues, the latest being a 400 Bad Request The plain HTTP request was sent to HTTPS port. This happens when trying to access via https://192.168.1.180:444, too. Just prior I had a 502 Bad Gateway. Pulling my hair out trying to figure this out, I've got Sonarr/Radarr/Bazarr services working through LetsEncrypt with no issues. If anybody sees where I'm missing a variable, it'd be appreciated LetsEncrypt console can ping 'nextcloud' with no issues Docker Config: https://imgur.com/a/xzLs6x5 nginx default config: https://pastebin.com/hdd3YeZp subdomain config: https://pastebin.com/Vq1LGHbS nextcloud config: https://pastebin.com/xvvJCeCj Error: 400 Bad Request The plain HTTP request was sent to HTTPS port nginx/1.16.1

I love how easy it is to setup, first time docker and server user and it was a (relatively) easy process! Would love to see multiple drive pools & native back-up options