Jump to content

testdasi

Members
  • Content Count

    2449
  • Joined

  • Last visited

  • Days Won

    9

testdasi last won the day on May 7

testdasi had the most liked content!

Community Reputation

355 Very Good

4 Followers

About testdasi

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

2520 profile views
  1. It depends on whether the card reader has a unique GUID or not. Impossible to know without actually owning the product. You probably are better off assume "No".
  2. There are 2 ways to do it. If your media server upports multiple folder per library then you can just add 2 folders to the same library. Alternatively, you can use a pooling software like mergerfs / unionfs to combine 2 folders together to the same mount point. If you follow DZMM's guide, it's somewhat trivial to add another folder to the mergerfs list. Guide:
  3. Updating driver to Nvidia 450.51 fixed the Plex transcoding problem. Ya'll just need to be patient for Unraid Nvidia 6.9.0 beta 24 to come out.
  4. Then I suspect it could be due to your sound card e.g. connection, power, incompatability etc. Typically a passed through controller works is 99.99% of cases.
  5. I don't think those GSO relate to the VM. Those errors started after the appdata backup job kicked off, which presumably stopped the dockers. I also see Restarting PiHole / Hydra. Could be related to the docker custom network issue?
  6. Are you passing through the controller as a PCIe device? Or are you plugging the devices to the USB controller and then attach those devices to the VM via libvirt (hence nec XHCI / qmu XHCI relevance).
  7. Yes it can be due to the controller but quite unusual. The most common cause is bad cable / connector. Try a different port.
  8. The only way to ensure minimum issue with USB devices is to get a dedicated USB PCIe controller (i.e. card) and poss it through to the VM. Libvirt usb mostly works but when it doesn't there is no possible fix unfortunately. Some headsets just don't like it.
  9. Hi guys, Are you guys experiencing issues with Plex transcoding with 6.9.0-beta22? Symtoms: File takes forever to load. Checking nvidia-smi shows "Plex Media Server" process using the GPU, instead of the usual "Plex Transcoder" process. The PMS process would drop in and out. Every now and then, the Plex Transcoder process is launched after about 1-2 minute wait then the video is transcoded. In most cases though, I can wait an hour and the video stays on the loading screen at 00:00. Checking Plex log, it seems to suggest the PMS process is used to check capabilities of the GPU but it fails and ends up in a loop of trying to check and failing. I didn't change Plex config prior to seeing this, which happened right after updating reboot. I have tested with all combinations of config that I can think of, including changing GPU between my 1070 and P2000 and nothing fixed it, except for downgrading to 6.8.3. Tested custom kernel with ".100" Nvidia driver and exactly the same issue. Unfortunately can't get the kernel to compile with the old Nvidia driver. Only Plex has this problem (I use the LSIO docker for max compatibility). Jellyfin, Handbrake, F@H are all fine with the GPU. I have exactly the same problem with the P2000. Transcoding is back to normal simply by downgrading to 6.8.3 Unraid Nvidia. My suspicion is something to do with the Nvidia driver and/or kernel incompatibility. I have been thinking about having a backup media server solution because Plex has gone quite bloated lately. I'm now setting Plex to software transcode and Jellyfin to hardware transcode just to see how things go. Maybe will move permanently away from Plex.
  10. First thing, turn C State back on. Global C States Control is no longer a fix for freezes while causing severe lags on Threadripper. Beside idle current to normal as jerky_san said, you should also turn off Precision Boost Overdrive. Normal PB is fine but PBO in recent BIOS has been unstable due to AMD cutting the voltage too low. That could be the cause of your random freezing. And please use the forum code functionality (the </> button next to the smiley button) when copy-paste text from Unraid e.g. config / xml etc. That will format and section the text correctly to make it easier to track things in your post. Otherwise everything is just the same blob of text of the same format, making it very hard to read. You are also better off having each problem on its own topic with only the relevant information. Unraid Nvidia issue is best asked in the LSIO dedicated support topic for the plugin.
  11. OVMF with Q35, SeaBIOS with i440fx. Haven't thought of that but could very well be.
  12. Moving between i440fx and Q35 isn't quite simple if you use SeaBIOS. I would say try i440fx-5.0 + virtio and test to see if you get any performance improvement + whether there's any GSO. I don't have any GSO error with Q35-5.0 and i440fx-5.0 for days already; hence, worth a try.
  13. Note that I found a performance penalty with virtio-net. I can't get above 200MB/s over the network between VM and disk share. That's ok with SATA SSD but is rather slow compared to the usual GB/s I get with my NVMe. Instead of using virtio-net, I keep the type as virtio but change the machine type to Q35-5.0 (which is available with 6.9.0 beta). Haven't had those GSO error since while still doing GB/s to cache.
  14. You misunderstood backup and RAID concepts. RAID is about the method that is used to store data. e.g. RAID-0: stripe data across multiple drives RAID-1: mirror data across multiple drives RAID-5: stripe data + 1 parity block RAID-6: stripe data + 2 parity blocks Unraid: no striping, parity block is on a dedicated drive etc. A backup is a redundant independent copy of your data i.e. it's about the nature of the data. Redundant means you don't access (i.e. use) the backup data as part of your business-as-usual activities, outside of the window which you restore from / update the backup. Independent means the backup can be used on its own without needing all or part of the original data Copy means there are multiple instances of the data (i.e. the backup is NOT the original). You can store a backup on a RAID array, just as you can store the original version of the data on a RAID-array. RAID provides resilience to failure but on its own is not a backup because none of the RAID implementation, including non-standard RAID (e.g. Unraid) can satisfy all 3 criteria of being a backup. RAID-0: fail all 3 RAID-1: fail (1) RAID-5: fail (2), (3) RAID-6: fail (2), (3) So RAID is like having a spare wheel for your car; a backup is like having another car all together.
  15. @limetech is there any way to repeatably trigger the unexpected GSO error for testing purposes? I found running <model type='virtio'/> + machine='pc-q35-5.0' also stop the errors for VM use without the performance penalty of virtio-net. I have been dumping a few TB of data from VM to a share in my backup job so I reckon I should receive plenty of errors by now but I haven't. Hence, wondering if there's anyway to trigger the error manually just to be sure that it's not coincidental.