Sundune

Thank you for your post, as I was in the same or at least similar boat as my Server has been running for a couple of years and had a single FAT32 Partition. With your guide it was easy to fix and upgrade successfully. This really should be checked by the Update Process itself. My server was stuck in a bootloop without any error messages on screen, making diagnosis for most users really challenging if they don't know where to look. I also have a full Backup of the "broken" state of the Stick if any staff member wants to see it in detail.

It seems like the changes made to the Seagate drive have resolved the issue. At least so far there have been no more read errors. Honestly i am positively impressed that Seagate allows to change those settings. Thank you very much again for your help!

Thank you very much for the helpfull link! I will try that after the Parity Check is completed, so that will be tomorrow. There is actually a new BIOS Update available, so that will also be on the checklist. The issues with the SSD dropping started after i installed the HDDs, of course that could be coincidence. But i will also give the changes you I forgot to mention that i had to change the syslinux.cfg file to get the HDDs running in the first place, see below append initrd=/bzroot intel_iommu=on iommu=pt I will keep this Thread updated

Hello Forum, last week i installed 2 new Seagate 8TB drives in my server Expanded the array and everything worked fine. During the initialization there was a read error on one of the disks, which got resolved by Unraid itself. Didn't think much about it considering it is a onetime occurrence during a time of heavy load. But since then, it is a more common occurrence for the new disks to have read errors. Since then the NVME Cache Drive occasionally is also lost. What makes me guess it may not be related to the SATA/SAS Controller but maybe the Mainboard/CPU being overloaded? I checked the cables and made sure the SATA/SAS Connectors are dust free. As recommended in another Thread. As of writing this Thread there is a Parity Check going after losing the Cache Drive. The attached diagnostics are from right after the Cache Drive was lost and before the restart. PS: The drives are Brand new with warranty in case i need to return them. Here is a bit more Information about the Hardware in use: MB: SuperMicro X11SSH-LN4F CPU: XEON E3-1245 v6 RAM: Kingston 9965643-006.A01G 8GB RAID-Controller: LSI SAS2008 flashed in IT Mode anon-unraid-diagnostics-20220131-1752.zip

As long as you don't have the ports forwarded in your router and automatic port forwarding isn't enabled in your router, jellyfin shouldn't be accessible outside of your network. Glad you got it fixed

The config file is located under appdata/binhex-jellyfin/config/system.xml on your Unraid Server. Path my vary depending on your setup. And change this line from false to true <EnableRemoteAccess>true</EnableRemoteAccess> I hope this works, i didn't try myself

Just tested it and skipping to a specific time works now! Tested it with a 60Mbit video and transcoded it to 5Mbit. fixed in my book

Hey, Thank you for this container! I can confirm the behavior @tarkus_au mentioned above. It is a known bug and a downgrade to ffmpeg 4.0 would fix it. It would be great if the version could be downgraded until this issue is fixed. Many greetings!