Hoopster

I had to put Kapton tape on a couple of pins to get a 9211-8i equivalent to work in my server.

Batteries in my APC UPS units have usually lasted 4-5 years. YMMV.

From your motherboard manual, the PCIe slots on the board are the following: It is usually the X16 slot that supports bifurcation on most motherboards. Ideally, it would support X4/X4/X4/X4 to utilize all four M.2 SSDs in your expansion card each with 4 PCIe lanes. Unfortunately, your motherboard does not appear to support bifurcation in any PCIe slot. It does not appear that anything other than one M.2 SSD will ever be recognized in your expansion card. Because of CPU and chipset limitations on the total number of supported PCIe lanes, often the X16 slot is reduced to X8 if a card is in the X8 (slot 3 in your board). It is rare with Intel desktop motherboards that you can populate all available PCIe slots on a motherboard with their full PCIe lane width. A lot of people like AMD Threadripper CPUs as they support a lot more PCIe lanes than Intel (unless you go with server-grade CPUs). I found this in the specifications section of the MPG Z590 GAMING FORCE manual: 3x PCIe x16 slots ▪ Support x16/x0/x4, x8/x8/x4, x8/x4+x4/x4 ▪ PCI_E1 & PCI_E3 slots (From CPU) ▫ Support PCIe 4.0 for 11th Gen Intel® CPU ▫ Support PCIe 3.0 for 10th Gen Intel® CPU ▪ PCI_E5 slot (From Z590 Chipset) ▫ Supports PCIe 3.0 ∙ 2x PCIe 3.0 x1 slots (From Z590 Chipset) Bifurcation is not mentioned but check your BIOS to see if you can designate PCIe lane splitting in an x16 slot. The above likely just refers to the speeds at which the 3 PCIe x16 slots can be run and not the bifurcation of a single slot to these speeds.

Does your motherboard support PCIe slot bifurcation? Without it, your system will see only the first M.2 card and assign all PCIe lanes to it From the description of the card you referenced: "Only support Bifurcation Motherboard" Here is a good explanation of the need for bifurcation to support multiple M.2 cards in the same slot. The best my motherboard allows is X8/X4/X4 so I could use a maximum of three M.2 SSDs in the device you referenced.

I have This HP 2.0 Flash drive in one of my Unraid servers. When I had issues with a prior flash drive no longer being able to boot Unraid, I went through 5-6 others which also would not work. I bought the linked flash drive at a local Office Depot (it's only $6). It has a unique GUID and has been booting that Unraid server for a couple of years now.

Tailscale is not shared with anyone else. "Good stuff" is on drive 3 from lots of shares but no one but me has access and I was not doing anything with Tailscale. However, there are several devices in my Tailscale network and most of them were connected even if no Tailscale access was taking place. Perhaps there is some housekeeping Tailscale does between connected devices, although, I still don't know what that would have to do with Drive 3 in particular and no other drives. Eventually, I will re-enable Tailscale on the serer because I need it and we'll see if any more UDMA CRC errors result from that. I really don't see the relationship, but, since I disabled Tailscale there have been no more UDMA CRC errors. Just a strange coincidence, I think.

Perhaps unrelated but I was able to eliminate UDMA CRC errors on drive 3 by disabling Tailscale. Top showed Tailscale activity when errors were occurring. Since disabling Tailscale, it has been five days since the last CRC error on drive 3 with other activity on the disk. Again, there may be no correlation and perhaps it is just coincidence as I don't know why Tailscale would be accessing a particular array drive.

Yes. Building parity will still take some time (depends on size of parity drive), but with the parity tuning plugin, you can have it run in segments during the night when the array is not used much over multiple days. For example, my 12TB parity drive takes a little over 24 hours to do a parity check. I split this up over three midnight to ~8am sessions. Before that I had an 8TB drive that took about 16-17 hours for a parity build done in two nightly sessions. A 6TB drive (parity drives must be as larger or larger than largest data drive in array) will probably take around 12-13 hours for a full parity build.

It is recommended for initial data transfer to not have parity drives configured in the array as this will slow down data transfer as it must simultaneously do parity calculation. Move the data first, then add parity to the array and let the system do the parity calculation after data transfer.

By the way, Unraid (as its name suggests) does not support traditional RAID levels like 0, 1, 2, 5, etc. From the manual: Does Unraid support various RAID types such as RAID1/5/6/10? Unraid manages storage in two separate buckets: the array and the cache. The array itself uses dedicated parity device(s) similar to a MAID. The array cannot be configured into traditional RAID methods such as RAID 1/5/6/10. The cache is created using btrfs. When more than one disk is present, the cache is called a "pool" and is by default configured to use btrfs RAID1, which is a slightly different take than a traditional RAID1. The cache can optionally be configured to use btrfs RAID 5/6/10, but RAID 5/6 on btrfs is still considered unstable, so it isn't recommended for production use.

Parity (single or dual parity) is not required. However, it does protect against the loss of one or two data drives. It is not a backup, just a protection against drive failure. The parity drive contains a calculation derived by examining all the data drives. If the parity drive dies, it can be replaced and rebuilt as long as all the data drives are in good working order. If a data drive dies, it can be replaced and rebuilt from the parity drive and all the other data drives. This is correct. Unraid stores a file completely on one drive, it does not stripe data across multiple drives. How it determines where to store the drive is a combination of the chosen allocation method, split level and minimum free space for each user share.

The fix is for docker containers in general running host mode with Tailscale and not Plex specific. See the 7.0.1 release notes for more details. With respect to running Plex in a mode other than Host, I have done it two ways; Custom: br0 with a static IP address on same subnet as the host and on a VLAN I created for docker containers on a different subnet than the host (this showed up as Custom: br0.3 as it was on a xxx.xxx.3.xxx subnet. Both worked fine with no problems with direct and remote streaming. The only problem I had with Custom: br0 was macvlan call traces. These would crash my server every few days to a couple of weeks. This used to be a big issue and one of the reasons ipvlan was implemented. Because of the macvlan call traces on br0, I created a VLAN (br0.3) and all my problems went away. This was years ago. I have not tried going back to br0 although I did switch to ipvlan. Having Plex on a VLAN with Unraid host and the content on a different subnet was not a problem because my router automatically passes traffic between "corporate" subnets.

@Triplerinse Unraid 7.0.1 was just released and contains this note: "This resolves a security issue when the Tailscale integration is enabled on a container running in Host mode and then shared with other users. "

FYI - Marvell controllers are known to have problems with Unraid (Linux in general). This does not mean that you are guaranteed to have problems; just that you may have issues such as disks attached to Marvell controllers dropping offline. Here is a controller discussion thread started by @JorgeB with recommended controllers should the Marvell cause you problems.

I had an Unraid server on which I had to replace the motherboard under warranty when the BMC/IPMI chip failed. The same flash drive I had been using to boot Unraid for a couple of years on that system (and its predecessor before that) would not boot with the new motherboard. It was the same model and had the same BIOS/UEFI version as the prior board but it would simply not boot Unraid from the flash drive I had always used. I tried that same flash drive on other Unraid systems with no problem; it booted fine. I went through every flash drive I had and none of them would boot Unraid on the new motherboard. Finally, I bought a new USB flash drive (HP brand) at the local Office Depot on a sale and it booted Unraid without issue. It is still booting that system now. I have no idea what happened, but that motherboard was extremely picky about what flash drive it would accept to boot Unraid.

A SATA SSD will work fine, but I do have a 512GB NVMe in mine for cache purposes. In your case, the best reason for a "cache" pool is to store appdata (Docker applications) and Plex database files. NVMe speed is not a must in either case and a SATA SSD will work just as well. One thing to keep in mind that new Unraid users sometimes don't realize is that Unraid does not support WiFi (even though the H510M-ITX/ac does). You need to connect it to your network with an Ethernet cable.

It looks fine for me on Firefox. That's what it often looks like for me when I view the forum in Safari on my phone with a poor cell signal or filtered WiFi. Maybe clearing cache will help?

Unraid works with almost any hardware. Any mini-ITX or mATX board that supports your CPU should work. i would look for a board that has the needed SATA ports. I have two ASRock boards (Main and Backup servers) that support 8 SATA devices on the motherboard; one mini-ITX and one mATX (see my signature). Even though the Jonsbo N4 supports mini-ITX and mATX, I would personally look for a mini-ITX as there is not a lot of room in these small cases and every little bit helps. The motherboard I have in my Spare/Test Unraid server (see signature) is the ASRock H510M-ITX/ac which supports both 10th generation and 11th generation Intel CPUs. I have the i5-11600 in mine and it works great with Unraid. You will need a SATA expansion card for four additional SATA ports as it only has four on the motherboard. It also has an M.2 slot. Again, any board that meets your needs and supports your CPU should work well with Unraid.

Does your BIOS say [UEFI]:{name of flash drive} or USB:{name of flash drive}? if UEFI, Unraid flash drive needs to be set to boot UEFI or you may get a black screen and blinking cursor or a return to BIOS. EFI- folder on Unraid flash drive must be renamed to EFI (remove the - ) to boot UEFI To boot legacy/BIOS it should be EFI-

Understandable. But, if it boots and runs fine with no GUI or IP issues with a generic trial install and DHCP, that would indicate a problem somewhere on you current licensed boot flash drive with either Unraid files or the configuration. If it has the same problems with even a trial generic install, the issue is likely with your network. Frankly, I am just shooting in the dark hoping to at least help you narrow down the problem.

Isn't what you want in Network type br0? That or a Docker VLAN is the way I do it.

Have you tried booting with a new Unraid 7.0.0 vanilla installation on a trial key just to rule out that something is borked with your current Unraid setup?

There is nothing inherently wrong with Unraid 7.0.0 networking and UniFi routers/gateways in combination. I have a UniFi Cloud Gateway Ultra at two different locations managing three different Unraid servers which are all running version 7.0.0 since it came out. I have zero issues with IP address and login in or navigating the Unraid GUI in any of the three servers. I can also hit the IPMI/BMC or PiKVM address on each one of them for remote management. I set a static IP address in both Unraid network settings for the server and in UniFi client settings. This is overkill, but I want to make sure I am dealing with a known IP address for Unraid servers. I have also used them all successfully with DHCP. I can also hit the IPMI/BMC or PiKVM NICs for remote or out-of-band management. Obviously, this is no help to you in resolving your issue, but it is not a general problem with incompatibilities. Are you perhaps experiencing IP address conflicts with multiple clients somehow getting the same IP address assignment?

I have the X570 Steel Legend (Ryzen AM4) in my desktop PC. It has been very solid. You should like it.

My motherboard choice always comes down to: Supports my chosen CPU Has the connectors I need for things like, NVMe SSDs, SATA HDs/SSDs, PCIe cards, USB port expansion, etc. Doesn't break the bank If the ASRock boards you have found meet your needs, get one of those. I have ASRock/ASRock Rack motherboards in all three of my Unraid servers and my desktop PC. They have all been great.