Michael_P

Members
  • Posts

    668
  • Joined

  • Last visited

Everything posted by Michael_P

  1. Then why the ginormous sign-in icon in the header? I'm already signed in to the server. It smacks of future intentions, and us tin-foil hat wearers default to nefarious, unfounded or not. Just rubs me the wrong way. Same with M$ - I have a Microsoft account, personally and professionally. They already have my "data". But still, requiring an unrelated account and nagging me when I don't want to associate them just to login to MY MACHINE to use software I PAY FOR, just annoys me - especially when it provides absolutely no benefit to me. Seriously, the sign-in nag in the header is huge. If it's not necessary, it should be smaller or better yet, on the admin page.
  2. I'm against it, too. I don't want a forum account tied to my server, just 'cause (reasonable or not, rubs me the wrong way). Won't give in to M$, either. Seems unnecessary, so I'll just stick on 6.8.3, I suppose.
  3. Here's my rig: https://forums.unraid.net/topic/86712-compact-rack-setup/ - more hard drives, and some of the smaller ones upgraded to 8TBs but more or less the same. Almost all movies, tv shows, concerts et al - I have a digital hoarding problem for sure lol. Yeah, that's what I keep telling myself, too lol
  4. Oracle, and in regards to this question Unraid, has no obligation to the 3rd party purchaser to provide replacement keys (or anything else) - doubly so if they don't have operations in the EU (who would you sue?). Oracle let the cat out of that particular bag by taking action against a company within the jurisdiction of the EU court, here you'd just be pissin' up a rope.
  5. No https://unraid.net/policies No Key Transfers Lime Technology does not support the transfer of an Unraid Server OS Registration Key to a 3rd party for any reason whatsoever.
  6. You should also update the firmware on the HBA, 07.15.08.00 is really old
  7. Same here, as soon as I restarted the container this morning, won't finish connecting to https://privateinternetaccess.com/gtoken/generateToken
  8. Looks like the same issue this person has with their 980
  9. You need to post in the support thread for that docker container as mentioned in your other now closed thread...
  10. 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).
  11. I'd just use the iGPU, should have more than enough horsepower
  12. I ended up adding passthru punch down connectors to my PSU's unused SATA power lines, worked great. Cost me 5 bux on ebay
  13. 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
  14. 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).
  15. Looks like they call it "Network Inspector". Run another scan and see if it shows up in your logs again
  16. 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)
  17. 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
  18. 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
  19. 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