Sundune

Members
  • Posts

    10
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Sundune's Achievements

Noob

Noob (1/14)

1

Reputation

  1. 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!
  2. 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
  3. 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
  4. 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
  5. 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
  6. some of the Containers are from LinuxServer.io but it seems more like it is random what containers are affected by it.
  7. Sorry, my bad. unRAID 6.7.2 (32TB) | Intel Xeon E3-1245 v6 3.70GHz | Supermicro X11SSH-LN4F | Intel SSD 760p 512GB NVMe Cache | 2x Kingston ValueRAM 8GB 2400MHz CK17-17-17 ECC RAM | 5x Seagate IronWolf 8TB | Seagate Exos 7E8 8TB (unmounted) Diagnostics are in the Attachments. I found a post with a similar Problem, but there was no solution mentioned unraid-diagnostics-20190905-1929.zip
  8. Hello Community, this weekend i changed my Network IP-range from 192.168.178.0/ to 10.10.20.0/23. Everything seems to be working perfectly, except that multiple docker containers now say they have an update available. I did update them manually through the WebUI, without success. Deleting the Containers including the Images and recreating the container using the saved template don't seem to fix the problem either. Many greetings
  9. 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
  10. 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!