• Content Count

  • Joined

Community Reputation

34 Good

About DoItMyselfToo

  • Rank

Recent Profile Visitors

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

  1. this morning SAB w/ wireguard would not connect even though it has been working fine for months. so then changed back to OVPN and worked flawlessly but slower. kept getting this error: "Unable to successfully download PIA json to generate token..." will retest tomorrow. suspect PIA was messing server side.
  2. Keep in mind that the E-2244G (and other Xeons in this class) have a limit of 16 pcie lanes. As for risks transferring to different chassis, basically every time one moves stuff around there is a risk of messing something up. Maybe inadvertent static discharge, or improperly seated cables, or a bad cable. Whatever. I have found that once my system is up and working, I do better to NOT tinker with it.
  3. That Xeon (E-2244G) is a 9th gen processor, which is 4c/8t. They sell for just under $300 and support ECC RAM. You could also get an i3-9100 (supports ECC and has Igpu for transcoding), which is 4c, so no hyper-threading. But the cost is about $120 on the eBay used market, but can also be purchased brand new for about $150. As for motherboards, I'm not familiar with the Asus board,. Some of us here use the ASRockRack E3C246D4U, which overall has been very good. See this forum post for more information. If you go this route, the board can be purchased separately from the eBay
  4. Heard back from WIlliam at Asrock, who said that there is no reason to change to the 2.34 bios if the 2.21a is running fine. Here is an exact quote: ”There is some minor modification in the BIOS to give little more support for a certain PCIe video card and there isn’t an additional feature added that would suit your need. If your system is current running fine with the current BIOS, you don’t need to use that beta BIOS. Thank you!”
  5. I really like these recommendations, which all have been previously implemented in my setup as a result of either watching SIO videos or various UnRAID forum posts. But having this security info in one thread really makes better sense than users having to assemble it on their own. Also, as another user posted in this thread, UnRAID should default to more secure settings out of the box. I’m not an IT professional, but my reading of the forums suggests that many if not most computer problems come from user error. I suspect security issues even more so.
  6. thank you. this makes sense. i seem to have tracked my problem down and the disk rebuild seems to be fine, though knowing more about this can only help in future. one "bad" thing about Unraid is that it works so well that when it doesn't i cannot remember how to fix anything. lol.
  7. so to do this looks like one would have to stop the array, remove the new disk. and replace with the old disk. and then use the "recipe" from Unraid 6/Storage Management to reset the array configuration in maintenance mode. anything else?
  8. i reseated the rear backplane connector, in both the backplane and hba then double checked all other connections. it's been nearly 7 hours since the rebuild started and so far so good. i am still interested to learn the answer to my original question if anyone knows more about parity syncing/rebuilding. thanks in advance.
  9. help please: my new to me Supermicro 36 bay chassis was running fine for a number of days; decided to upgrade the size of a disk; did the normal disk upgrade process: 1. stop array 2. unnassigne smaller disk 3 assign larger disk to same slot 4 start array (note: all dockers/vms off.) disk upgrade/rebuild started. everything seemed fine. then during the first hour a few UDMA CRC errors appeared on 6 disks that are in the rear backplane. prior to this there were no disk connection issues. so, i acknowleged the errors and watched if more would
  10. i've been running the 2.21a bios and 1.80 bmc since i got my E3C246D4U. seeing there is a 2.34 bios. anyone know what the changes are from 2.21a? anything critical? microcodes?
  11. had similar problems as others with Sonarr after updated SABnzbdvpn. added Unraid server to "ignore addresses" field in Sonarr (settings - general - proxy). then restarted SAB, NZBHydra2 and Sonarr. still wouldn't yield search results. so went into Sonarr indexer and downloader settings to "verify" them, though environment did not change, so settings were not changed. then clicked "test" for each. after testing both, now searches work.
  12. New - I was going to use in a second server build. Tested; work great. Four sticks available. Prefer to sell in multiples of two. $160 each, shipping included. Shipping: US lower lower 48; fast shipping. (Willing to ship to Canada if buyer pays shipping difference.) Paypal. Post here; or PM - questions, interest.
  13. Happy Birthday! Cheers!
  14. thank you for offering your input. i appreciate this. i always update all sas controllers to the latest ( firmware before running in my server. the cables are new. still problems with this disk as an UD. but i am currently preclearing this disk. did a full read of the disk and now at 20% zeroing without any hardware change. update: the disk pre-cleared without issues. but i did double check the firmware on my two LSI SAS HBA's. the 8i was updated to the latest ( but the 16e was not ( my bad. not sure how i missed that. but