Jump to content
XPEnology Community

MrEze

Transition Member
  • Posts

    19
  • Joined

  • Last visited

Everything posted by MrEze

  1. I made a mistake it is the DS920+, but I also tried using the DS1520+ and I get the same issue. Not sure if it has something to do with the loader I was using (tinycore-redpill.v0.9.5.0.m-shell.img). I had to use this loader because it was the only one that would install the DSM on my computer. I tried using arc-23.8.30.img and arpl-i18n-23.8.11.img, but neither of them would install the DSM.
  2. Ok, I think I discovered part of the problem. The script I am using doesn't pass in --device to the docker container, so it can't transcode using HW acceleration. However when I add --device, I get an error saying that "Container Manager API has failed", and "Error gathering device information while adding custom device "/dev/dri/renderD128" no such file or directory". Here is the script I am using, but doesn't work because there is no /dev/dri directory on my system. docker run -d --name=jellyfin \ -v /volume1/docker/jellyfin/config:/config \ -v /volume1/docker/jellyfin/cache:/cache \ -v /volume1/MEDIA:/media \ --user 1026:100 \ --net=host \ --restart=unless-stopped \ --device /dev/dri/renderD128:/dev/dri/renderD128 \ --device /dev/dri/card0:/dev/dri/card0 \ jellyfin/jellyfin:latest If I remove the two "--device " then it will work without transcoding. I am using the DS923+ which I thought was able to transcode 4kstreams. Does anyone know how to fix this?
  3. When I try to check using ssh ls /dev/dri, it says "no such file or directory". So not sure how to do this. I am using DSM 7.2-64570, CPU is AMD Ryzen 5700X and GPU is Nvidia T400.
  4. I am having problems with media playback when using Jellyfin on Synology DSM 7.2. I get a "Playback Error: This client isn't compatible with the media and the server isn't sending a compatible media format." It seems to be something with the transcoding. If I turn off transcoding then my media will play. Previously, I did not have this problem. I was able to play with transcoding turned on, so I don't know what changed. Can anyone help me with this?
  5. My understanding was that it was not possible to perform a manual upgrade from within DSM for 7.2-64561 to 7.2-64570 and that the loader had to be updated first. I am just unsure how to do this.
  6. I am a new user to this forum and to arpl and DSM. I was wondering if anyone could provide me with a detailed guide on how to upgrade from DSM 7.2-64561 to 7.2-64570? I have been successfully running DSM 7.2-64561 for some time and am hoping to be able to upgrade my DSM without losing any of my data or having to copy it from a backup. Is there a way to upgrade the DSM so that I don't have to copy back all my data once the upgrade is completed? Any help would be greatly appreciated. Also, I was wondering which is best to use: arpl-i18n 23.7.4 or Arc build 23.7.34?
  7. I was able to get DSM 7.2 installed using the M SHELL for TCRP loader, "tinycore-redpill.v0.9.4.3-2.m-shell.img.gz" (from https://github.com/PeterSuh-Q3/tinycore-redpill)
  8. After installing arpl and loading DS920+ or DS918+, I cannot connect to the DSM. It says "Detected 2 network cards, but only 0 MACs were customized, the rest will use the original MACs." It shows: eth0: ERROR.. eth1: Access http://10.0.0.195:5000 to connect the DSM via web. and "This interface will not be operational. Please use the http://finds.synology.com/ find DSM and connect" I have tried to use the find.synology.com and the Synology assistant, neither can find the NAS. I don't know what to do. Please help. I tried using both ARPL-i18n v23.5.8 and arpl-1.1-beta2a and got the same error. I am installing on baremetal.
  9. Moved to General Installation Questions/Discussions (non-hardware specific)
  10. Is it possible to install something like DS920+ (a 4 bay drive) using redpill, on a system that has more than 4 harddrives? Will DSM 7.x see all the drives? I was originally planning on using DS3622xs+, but was informed that it does not support hardware transcoding. I need something that can support more drives (up to 8) and still use hardware transcoding.
  11. Maybe someone would be so kind as to even put up a video on how to install this, showing all the steps necessary that would be helpful to us newbies.
  12. Would be great if someone posted a "how to" to show complete newbies like myself on how to install/run this on Proxmox. And I do mean complete newbie to dockers and containers and Proxmox. If that is beyond the scope of this conversation, then maybe just a good reference on how to get started with dockers and containers that could assist with how to install this. Sorry if this is too much to ask here.
  13. - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 7.1.1-42962 Update 4 - Loader version and model: ARPL v1.1-beta2a (DS920+) - Using custom extra.lzma: no - Installation type: vmware Workstation 17.0.1 on top of Ryzen 7 5700X - Additional comments: Manual update from the DSM GUI
  14. I found the answer; "synology_geminilake_920+.pat" is the correct file to use for this update.
  15. I was considering upgrading from "DSM 7.1.1-42962-4" to "DSM 7.1.1-42962-5". I was trying to find the correct file to download for a DS920+ from the Synology archives. All I could find was "synology_geminilake_920+.pat". Is this the correct .pat file I would use for the DS920+? Sorry, if this seems like a obvious question, but I am very new to all this.
  16. Changed the model to DS920+ (from DS918+) and changed the configuration of the hardrive to 1:0 (from 0:1). That seems to have fixed this issue. Not sure which one or both of these changes made the difference.
  17. Just tried to install DSM 7 using Redpill on VMWare Player. Everything went well until I got to opening the DSM installer page on the web. I got an error that said... "Failed to install DSM...Failed to format the drive" The hardrive size I used was 25GB. What could be wrong? How do I fix this? I have tried several times and always get the same error.
×
×
  • Create New...