Gragorg

Your going to need to post your diagnostic for the gurus to look at.

I currently have a sata Mx500 240GB SSD as a cache drive. I have never had an issue with the drive but it is now too small. I have read in the past that people have had issues with MX500s. Is this still the case? I am trying to avoid Samsung because their RMA policy is absolute garbage in Canada from what I have experienced.

Tried powerdown but it crashed server. I did a hard reboot and docker came back. How worried should I be regarding corruption on server cache now?

Last night server downloaded too many files and filled my cache drive which crashed docker. I cleared a bunch of space and disabled docker. When I enable docker it says it will be available after a reboot. So to be safe hit stop array first before reboot and the bottom left corner says Array Stopping•Retry unmounting disk share(s)... I have attached my diagnostics right before I tried the shutdown. My log is currently spamming Sep 9 09:14:56 Tower emhttpd: Unmounting disks... Sep 9 09:14:56 Tower emhttpd: shcmd (2787153): /usr/sbin/zpool export cache Sep 9 09:14:56 Tower root: cannot unmount '/mnt/cache/system': pool or dataset is busy Sep 9 09:14:56 Tower emhttpd: shcmd (2787153): exit status: 1 Sep 9 09:14:56 Tower emhttpd: Retry unmounting disk share(s)... Sep 9 09:15:01 Tower emhttpd: Unmounting disks... tower-diagnostics-20230909-0903.zip

I think you will find most on here have used XFS for array drives as it is more robust against corruption. It does however lack some of the modern features of other newer file systems. BTRFS can detect bitrot but can't really do much too much to fix it.

Hit advanced view on the docker tab and see if you have any orphaned images. Also posting your diagnostics would be good.

You could run an extended SMART test on disk 2. You will likely have to disable spin down while doing it.

Read through this parity swap procedure. This will allow you to upgrade your parity and your failing drive at the same time.

I had a similar issue with my flash going corrupt and having to repair it in a windows pc. I formatted my flash (not quick format) and restored from my backup and my usb has been good for years.

Spaceinvader has a great video on this here.

Thanks @JorgeB you've helped me out many times. Time for an appearance on UNCAST! Thanks again

Update went as expected!

What you looking to do is use the new 18TB to replace your parity drive and use your exsisting 8TB parity drive to rebuild your bad data drive. This procedure is called The parity Swap procedure.

So shutdown both my pc and my server. But the desktop is spamming errors in my syslog after I reboot both. The ones in red are what I’m referring to. Not sure how to proceed

Could anyone let me know what the nginx errors and networking issues are in my syslog. 192.168.1.8 is a desktop computer on my network. tower-diagnostics-20230623-0546.zip

I recently changed my domain name on Vaultwarden. I logged into the admin panel and changed it in the "domain URL" box to the new one. After is saved the settings and logged out I restarted vaultwarden but the WEBUI option on the docker still goes to the old domain. I logged back into Vaultwarden and confirmed that the new domain was saved. The new domain is working fine.

Thanks for this. Got it all setup and working like a charm with my domain proxied.

Ok so I had to change my cloudflare to dns only to renew. Is there a way to renew them while they are proxied in cloudflare?

Here they are. Disk 5 was showing in unassigned devices. Replaced the cable with a new one. tower-diagnostics-20230613-1120.zip

Was in process of upgrading parity to a larger drive. Disk 5 has read errors. How should I proceed? tower-diagnostics-20230613-1044.zip

My certs are not renewing not sure what changed here is a snippet from the log [app ] [6/11/2023] [9:09:56 AM] [SSL ] › ✖ error Error: Command failed: certbot renew --non-interactive --quiet --config "/etc/letsencrypt.ini" --preferred-challenges "dns,http" --disable-hook-validation [app ] Failed to renew certificate npm-1 with error: Some challenges have failed. [app ] Failed to renew certificate npm-10 with error: Some challenges have failed. [app ] Failed to renew certificate npm-11 with error: Some challenges have failed. [app ] Failed to renew certificate npm-13 with error: Some challenges have failed. [app ] Failed to renew certificate npm-2 with error: Some challenges have failed. [app ] Failed to renew certificate npm-3 with error: Some challenges have failed. [app ] Failed to renew certificate npm-4 with error: Some challenges have failed. [app ] Failed to renew certificate npm-5 with error: Some challenges have failed. [app ] Failed to renew certificate npm-6 with error: Some challenges have failed. [app ] Failed to renew certificate npm-7 with error: Some challenges have failed. [app ] Failed to renew certificate npm-8 with error: Some challenges have failed. [app ] Failed to renew certificate npm-9 with error: Some challenges have failed. [app ] All renewals failed. The following certificates could not be renewed:

I have seen some have problems if all your drives are powered on the same cable from the power supply.

Cable looked like it wasn't fitting the sata port right. I moved it to another port and rebooted. It came up with "array turned good" message. I'm hoping thats all it was.

Some read errors just appeared. Is this a cable or drive issue? tower-diagnostics-20230610-1620.zip

Your CPU wasn't the bottleneck for parity rebuilds. 170 MB/s is about all you will get with any CPU