-MacGyver-

One thing to take note of, as you said "original" USB. If that was the USB key you transfered your license from,and not the one transfered to, be mindful of OS updates. In a future update that prior key will be blacklisted and the array won't start. If you meant the USB key that you transfered to and recreating it worked that one won't have the blacklist issue.

6.11 array drives are XFS or BTRFS. 6.12 array drives are those and can also be ZFS. Any of these can be popped into a machine with Linux, or even a live CD/USB, and you can recover your data. For ZFS you would need to be sure to use a distro that has openzfs included. There is no lockin with unRAID.

The "Critical: libusb_init failed" isn't an issue and can be safely ignored. I'm using LSIO plex container and for many years have had that same message. Hasn't cause any problems. What device is dev/sdb? If that is where appdata resides then that disk looks to be RO (read-only) from the I/O error. If it is that is most likely why plex gui isn't working. Check the filesystem on that drive, the gui help or DOCUMENTATION link at the bottom of the forums can help. I'm not a checkdisk guru, aapologies for not giving you more discrete guideance there.

You are on the right track with the unRAID trial. However, you don't have to reconfigure anything if you copy over the config folder from the current setup, which you would do for the new registered USB anyways. The only cavet with the trial is internet access is required to validate the trial.

Should work and start as you outline. Few changes though. Disable auto start of the array, as well as disable auto start for docker and vm if you use those. Do a non-correcting parity check. Manually shutdown to ensure you have a clean shutdown. Perform your swap then power back on. Depending if/how you reserve the ip to your server some network setting updates may be needed, unless you use same nic or static config setup in unraid. If you updated network settings reboot again. Start array, do another non-correcting parity check. Start Dockers/VM's and then reboot again. This is to ensure clean shutdowns on new hardware as well as checking auto starts work.

The OP used Tom's words from the announcement 🤣

Disable auto start for array, docker and VM's (if you have any). Be sure to have a clean shutdown. For good measure make a copy of config folder, found on your unRAID USB. This way if something happens you have a backup already prepared. Swap over to the new, then start. I've done this a few times over the 10+ years with unRAID, it's a treat it works this way. If you want to be a little more sure you could: Verify the new motherboard can boot ok from USB before you migrate over. Maybe start with an Ubuntu, or other distro, live USB. Then you can use a trial version of unRAID to verify that boots. This could save you before you transfer everything over. Also from trial unRAID can verify if your network card/onboard works too.

You wouldn't have an unRAID array. With only the ZFS pool you want the setting at "only". Without the array the idea of unRAID cache no longer exists, hence the reason itimpi started what he did.

Welcome Justin!

You mentioned the unRAID webgui and docker restarts are slow in your initial post. These are internal and your internet connection has no impact on. The iperf test is to test your internal network. Still suggest you test the network. If this was after a power cut restart all of your network equipment. Some part may not have come online properly. With all network equipment turned off, turn back on in the order of modem, router and then any switches. Wait until each has stabilized before continuing to the next.

What you describe in your initial post sounds like network issues. At the very bottom of your screenshot are very slow bond0 inbound/outbound speeds. Have you done an iperf test, both directions, to rule out network issues ( Full disclosure - I haven't used that tool, can't help on setup, operation )

Correct media location is where movies, music, tv ( I have photos too ) are. Haven't heard of anyone setting up a DVR media location. There is no place I see to configure the DVR to place content in another location. You'd probably have to Google, or ask on the Plex forums, if DVR content can go in its own media library.

Plex DVR recordings would go to your configured media location(s). If that is cache enabled the initial write is to the cache. Then mover moves to array. If not cache enabled recordings go to the array. My hdhomerun is the 4 tuner (currently all ATSC 1.0) and I can record from all 4 at the same time to the SSD cache.

This isn't a quiet support channel when the issue pertains to unRAID itself. You're looking for Docker support in General unRAID space. I don't have one of the screenshos the mods have, but click on Emby on the Docker tab and then click on Support. That will take you to the support thread for Emby. You ask your question in the continuous thread.

An email should have been sent, not just an announcement post, about forum security updates. The 12 character password has completely ruined my password management process. Also, when force logged out on my Android device unread posts never showed as all posts were unread. That's backwards to me. Meaning I didn't see the announcement post until *AFTER* resetting my PW and logging in. Very frustrating.