-
Xpenology VM any one running this ?
Just a quick FYI for anyone getting the error 13 failed to install. I was able to fix it by changing my primary vdisk bus type to USB.
-
Running Xpenology 6.2 on Unraid 6.9.2 in 2021
I got the failed to install error 13 as well. tried numerous configurations of loaders and pat files centOS vs Ubuntu. The issue was my primary vdisk bus was set to vritIO. changed to bus type USB and the install proceeded. in the end followed the exact guide above, set primary vdisk bus to USB and used DS3615xs 1.02b with DSM_DS3615xs_15047.pat to work on my machine.
-
coldhammer started following Critical Help Needed ASAP , Parity schedule being ignored , Parity Corrections and 7 others
-
[Support] Djoss - HandBrake
*Solved* there were two issues. 1) I had output set to a sub directory within the storage path. Seeing the post above by Djoss that storage was readonly it made me think that the read only permissions were applying to the subdirectory as well. Moved the output folder to a level above the storage folder allowed it to write the output file. 2) within the GUI the destination directory shows as being set to a "folder" named output. it is not clear that this folder name is actually just a pointer to the folder selected in the output path of the docker. Showing the name of the user selected output folder within the GUI would be a good improvement to the UX of the docker.
-
[Support] Djoss - HandBrake
I installed the docker and ran a test and it wrote a file to the selected directory. I then created a new directory for output files, edited the output path in the docker and got "unable to write" to directory error. I have reset permissions on the directories and that did not make a difference. I uninstalled and reinstalled several times and set the path during initial and post installation and that has not fixed the issue. I can also no longer write to the directory that it was successful writing to on the first install.
-
Container for No-IP dynamic DNS updates
ahh i see. i thought the command line instructions predated the docker template. so if im understanding this correctly i need to execute the command line portion first then install the docker from the template?
-
Container for No-IP dynamic DNS updates
I think im missing something here. when i install the docker from the template i map the container volume: /config to the host path: /mnt/user/appdata/noIp/config/ the install process runs. everything seems fine. after about 15 minutes the docker is stopped and the log says "Could not find /config/noip2.conf" It appears i have not set something up correctly. Any suggestions?
coldhammer
Members
-
Joined
-
Last visited