testdasi

Reboot is the reason. The device can't be reset so a reboot resets it. I vaguely remember reading somewhere about some FLR fix for Starship/Matisse devices in kernel 5.8+ but even Unraid 6.9.0-beta25 is only 5.7 IIRC.

Ryzen should have 1 USB controller that can be passed through.

Reboot is the best way but you can try this. Also from command line go to /var/log and delete the old syslog.1 and 2 and so on. echo "$(date "+%d.%m.%Y %T") Log was cleared." > /var/log/syslog You should post a separate bug report with Diagnostics. Also perhaps try Q35 machine type (but I doubt it would help). And ask SpaceInvader One if he has any tips.

Known issue. "unexpected GSO type" issue flooding your syslog. Read the release note (search for virtio-net). Also read my post here for some alternative fixes.

I received notification in my case (and a red box on the GUI saying fail) so I think you should check your notifications settings. You have to have all devices connected during scrub for correction to happen (i.e. you will have to reboot). If a drive truly died, I would suggest to post on here with diagnostics and wait for Johnnie to respond for next step.

Settings -> Docker -> untick "Host access to custom networks"

Because LT has a small team and other features are way higher on the priority list. You will have to out-scream the [Include graphics card driver] crowd, the [Include Wifi] crowd and the [ZFS] crowd.

Some pointers: That is typical symptom of a drive dropping offline and then reconnected it back. That is typically a cable problem. Check your power and data cable. You misunderstand a few things. A disconnected device from the pool will not be automatically re-added (because trying to do it blindly risks corrupting your data beyond repair). A reboot is the easiest way for the dropped device to be automatically added back (assuming you haven't wiped the "unassigned" one). There is no such thing as "just a hiccup". If a drive drops offline, the pool is degraded. It's kinda similar to the array, if a drive drops offline, you can't just add it back but have to rebuild it. The list of devices in a pool is a configuration list and not a connected device list. Unraid will alert you something is wrong with the pool but won't just remove the device from the list. Functioning is different from repairing. You seem to lump both into "auto-correct". A RAID-5 pool will function (i.e. all data is readable and writable, including data written after the failure) with a single failed device but in a degraded state. It can't repair while in degraded state (because there is insufficient data to repair). Scrub = repair. My tried-and-tested procedure when a disk drops offline from the pool is as followed. I have had to do this several times now due to a bad power cable and it has always worked. Shut down as soon as possible to reduce risk of additional failure Check cable and reboot Once booted, check that the dropped device is no longer unassigned but in the pool i.e. online (e.g. easiest way is to see if temperature shows up) Run scrub (with correction) Beside what Johnnie linked above, you can also have a look at my post here which I added a few more tips. Before you run any balance, make sure scrub has completed successfully first.

Why are you running raidz1 with 2 devices? Did a disk drop offline? I highly recommend using BTRFS RAID-5 instead of ZFS RAIDZ1 for a SSD pool in Unraid. Integration with the OS is something you take for granted until for instance a disk drop from a ZFS pool without your realising it. (PS: ZFS also completely ignores isolcpus so don't be surprised when things lag terribly under heavy IO)

Some Bluetooth USB dongles don't like libvirit connection so you need to pass through a USB controller for it to work. Keep that in mind.

Don't bother. Proper nested virtualisation doesn't work.

What you see is all that is available (with the kernel) so if it's not the right one then you just have to wait for the next kernel release to see if it improves anything. This probably is very true with 3rd gen Ryzen (and 10th gen Intel etc.). Even my 2nd gen Threadripper didn't have the right sensors. Perhaps try 6.9.0-beta25 which has 5.x kernel with better support. My TR4 now has the right sensors. PS: read the release notes very carefully so you understand the implication of using beta. There's more than just stability (which it is very stable).

Start with attaching Diagnostics. (Tools -> Diagnostics -> attach full zip file).

What I do is to map disk and not user share just to be 100% sure there can be no wrong. So let's say I have /mnt/user/other that is on the array and /mnt/user/appdata/PlexMediaServer on cache. Then cd /mnt/cache/appdata/PlexMediaServer ln -s /mnt/disk1/other other You get the picture. Obviously appdata is set to Cache = Only so that there won't be any mover action. The map /config to /mnt/cache/appdata/PlexMediaServer Then anything written to /config/other => /mnt/cache/appdata/PlexMediaServer/other => /mnt/disk1/other It's overly cautious but I rather err on the safe side.

Can't tell clearly from the pic but I don't think the 1st PCIe x8 slot is open-ended so it won't fit a x16 length card. The 2nd PCIe x8 slot could be open-ended but need a better closer picture to tell. In terms of transcoding, the popular Quadro P2000 is single-slot width and not that long so could fit on the 2nd x8 slot (assuming it's open-ended).

Neither. USB stick only affects boot time and nothing afterwards. RAM speed has zero impact on the page load. That is sounding increasingly like it's a browser problem.

Did you leave the page open overnight? The slow loading could be browser related. That page loads information from the docker image so 32GB isn't enough to load the entire image, not that I think doing that would resolve that speed issue.

I don't think that's an iso. Try following SpaceInvader One guide instead

Yes, revert the problematic parameters and reinstall Plex docker and it will come back. How comfortable are you with network setup? (with array stopped) Settings -> Network Settings -> choose both IPv4 and IPv6 in Network protocol and make the appropriate setup to give your server an IPv6 (assuming your router supports v6) Set your Plex docker in "Bridge" network type i.e. it will use the same IP as your server. Then in port-forwarding config of your router, point a certain port x to your server IP + 32400. The in Plex settings, look for Remote Access, enable and test (would be best to use the port x in the step above in the "Manually specify public port" to make it test faster). If that still doesn't work then your ISP doesn't allow access. To be honest, don't see why you need ipv6 for that.

Go to Docker -> Add Container -> pick the template from the drop-down list. It will have your last parameters If you have problems with a docker, ask question in that particular docker support topic for more targeted answer. I saw your other post in the other topic in a [DEPRECATED] forum. What are you trying to do with the Plex docker?

Multiple cache pools can be created manually (in conjunction with Unassigned Devices). See quoted post from Johnnie below. 6.9.0 (currently beta25) has multi-pool functionality built into the GUI so if you don't mind running beta then that will be more user-friendly. Note that any SSD formatted in 6.9.0 will NOT be backward-compatible to 6.8.x. Major point: avoid RAID-0 with HDD. That is strictly in the "do it if you know exactly what you are doing" category or you are asking for troubles. Also avoid BTRFS RAID-5/6 with HDD as well (ZFS RAID-Z1/2 is a better option for HDD). FAQ link

Re-extract diagnostics and attach in your next post. Not clear what you did from your description.

There is no limit (e.g. I'm running 32 at the moment). Copy-paste your xml on your next post. Use the forum code functionality (the </> button next to the smiley button) so the code is formatted correctly. Also if possible, attach diagnostics (Tools -> Diagnostics --> attach full zip file) but I suspect just the xml is sufficient.

Raise a bug report but I have seen this quirk many times. I think it's timing diff i.e. when temp is read on the various pages.

I don't think it would work with a parent + a sub. Why don't you just map /other instead of /config/other? Usually simpler is better. Otherwise an alternative is to create symlinks in the host which I try to avoid doing in /mnt/user because of potential issues with Unraid own shfs process.