Michael_P

You should also update the firmware on the HBA, 07.15.08.00 is really old

Same here, as soon as I restarted the container this morning, won't finish connecting to https://privateinternetaccess.com/gtoken/generateToken

Looks like the same issue this person has with their 980

You need to post in the support thread for that docker container as mentioned in your other now closed thread...

I use Nextcloud

Put a heatsink on it

That's the great part about Unraid (and RAID, too) - uptime resilience AKA the R(redundant) in RAID. Your system stays up during the rebuild and nobody is the wiser as far as end users are concerned (it's still not a replacement for an actual proven backup routine for irreplaceable files).

I'd just use the iGPU, should have more than enough horsepower

Here's one https://www.ebay.com/itm/251295075570

I ended up adding passthru punch down connectors to my PSU's unused SATA power lines, worked great. Cost me 5 bux on ebay

Pulled my hair out for a long time, too. Hell, for almost 2 years I just didn't do parity checks because I was tired of drives dropping

Looks like you rebooted - but entries like this are what you're looking for in the future Oct 16 19:49:42 T-800 sshd[31255]: Invalid user 666666 from 192.168.87.104 port 54106 Oct 16 19:49:42 T-800 sshd[31255]: pam_unix(sshd:auth): check pass; user unknown Oct 16 19:49:42 T-800 sshd[31255]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.168.87.104 Oct 16 19:49:44 T-800 sshd[31255]: Failed password for invalid user 666666 from 192.168.87.104 port 54106 ssh2 Oct 16 19:49:44 T-800 sshd[31255]: Received disconnect from 192.168.87.104 port 54106:11: [preauth] Oct 16 19:49:44 T-800 sshd[31255]: Disconnected from invalid user 666666 192.168.87.104 port 54106 [preauth] Oct 16 19:49:44 T-800 sshd[31340]: Connection from 192.168.87.104 port 59203 on 192.168.87.26 port 22 rdomain "" Oct 16 19:49:44 T-800 sshd[31340]: Invalid user 888888 from 192.168.87.104 port 59203 Oct 16 19:49:44 T-800 sshd[31340]: pam_unix(sshd:auth): check pass; user unknown Oct 16 19:49:44 T-800 sshd[31340]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.168.87.104 Oct 16 19:49:47 T-800 sshd[31340]: Failed password for invalid user 888888 from 192.168.87.104 port 59203 ssh2 Oct 16 19:49:47 T-800 sshd[31340]: Received disconnect from 192.168.87.104 port 59203:11: [preauth] Oct 16 19:49:47 T-800 sshd[31340]: Disconnected from invalid user 888888 192.168.87.104 port 59203 [preauth] It's pretty common to get these "security" scans from antivirus and other security software like Bitdefender (commonly found in Netgear routers these days, too).

Looks like they call it "Network Inspector". Run another scan and see if it shows up in your logs again

If the "attacks" are still coming from your LAN PC (as it appears from your log), then you may have a network scanner installed (antivirus probably)

You likely have too many drives hanging off of 1 connector/line to the PSU causing the drives to brown out from sagging power. Try eliminating the splitters

Indeed, but I can say that I've done pre-clears on a half dozen drives or so and not once has unraid allowed them to be added to the array without clearing them again. I just basically use the plugin as a stress test at this point, but if anyone has any insight as to what exactly I'm doing wrong, I'm all ears

In my experience, when I pre-clear new drives and add to the array, no formats, no changes just straight from pre-clear to the array - every time it starts clearing again. I've never had a "cleared" drive add to the array without having to clear again. From cold spares to drives that dropped for one reason or another and I've pre-cleared to make sure they're good, each time it's needed to clear them again when adding to the array

FWIW - pre-clearing never works right for me either, always clears again when I add a drive

Looks like it's on its way out. (I would not use that drive) ATTRIBUTE INITIAL NOW STATUS Reallocated_Sector_Ct 0 8 Up 8 Current_Pending_Sector 0 16 Up 16 Offline_Uncorrectable 0 16 Up 16

Tried UrBackup?

You could just create a separate DB and save come complexity. If it's all running on the same hardware, there's no performance gain to have 2 docker instances running, just my opinion

Just curious, why 2 DB servers?

Short answer, yes - if it's not an encrypted array, it should start by itself and begin providing services. If you assign a static IP to the server, you won't need routing to get to it so you'd be able to access it from the LAN should you need to (you'd need to assign a static IP to your client machine too).

Take whatever disk you're using in your W10 machine and move it into your Unraid server as an unassigned device, then assign that to the VM and it should boot like it never left (assuming it was your boot drive and the boot manager is set up correctly).

Yep, you can either move the whole disk, or do an image backup and restore into the VM.