JulianB

Thank you very much @adam0. This is a really great guide.

To be honest: every single VM that I run with XPenology runs into the reboot problem. Sometimes it worked very well, but after an update (or even some time later), the VM stopped working. On the other site: I run an XPenology on bare metal since 2 years without any problem. It is just a backup PC that stores all my files. But it is working very well. And I start the PC once a month. I am surprised, that you have run xpenology on proxmox without any issues.

Hey @GreX, thanks for your note and great that you have fixed it. Maybe it depends on the System / Server ? I am running an old Intel® Xeon® CPU L3426.

Hey guys, I hope that my topic is placed in the correct corner of the community. I had several issues setting up Xpenology as a VM (also as a docker) in my latest Unraid server. It took me some nights to figure out, which is the correct setting and the correct Version of Xpenology. It should NOT be an discussion why users want to run an virtual NAS OS on an NAS OS... 😄 But for clarification, why I decided to get it run: I love Moments and Drive and also run an DVB Stick, which works very well on Xpenology. it is also not another post of "how to install Xpenology". There are tons of manuals in the web. I hope, that my configuration will help people getting it run on their servers. 1. To get everything you need, I am using the Xpenology Tools in Version 1.4.2. 2. Use the Template DS3617XS! All other Templates are not working (for me on Unraid!) 3. The Bootloader should be 1.03b for the DS3617XS 3.1. Set the correct MAC, that Unraid will tell you 3.2. comment out all boot options and just leave the ESX option enabled! 4. The VM Configuration: 4.1. Use Ubuntu as default Template 4.2. Set as Machine: Q35-5.1 4.3. Set the Bios to SeaBIOS 4.4. First HDD should be the Loader image 4.5 Second HDD should be a SATA disk. 4.6. Save the configuration WITHOUT starting the VM. 4.7. Go back to the edit page of the VM and switch to the XML view 4.7.1. Search the second HDD and change the Controller to 1. Example: <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/WHATEVER/vdisk2.img' index='1'/> <backingStore/> <target dev='hdd' bus='sata'/> <alias name='sata1-0-3'/> <address type='drive' controller='1' bus='0' target='0' unit='3'/> </disk> 4.7.2. Search the section for the ethernet and change the Type to "e1000-82545em" Example: <interface type='bridge'> <mac address='52:54:00:77:db:5f'/> <source bridge='br0'/> <target dev='vnet1'/> <model type='e1000-82545em'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </interface> 4.8. Save the configuration and start the VM. You should know be able to install the latest 6.2. DSM (For me it is "DSM_DS3617xs_23739.pat") It would be great, if somebody else could check this and report if it is also working for him! Thanks guys and take care.

+1

I installed some of them and found the bad program... it is/was nextcloud that prevented the spin down of my drives. I couldn't say enough thank you for the help guys! This helped me a lot. There is really much to learn about Unraid. But I really like it a lot.

OK, attached you will find my new diagnostic. When you will be able to find a wrong config, that would be great. If not I will try to throw away the dockers and set it up again. @itimpithe only problem i have is that the main drives will not spin down. It is good to know that there are many problems when tower will use ram. But hopefully it is only uising the ssd.

I copied the last files... better the Mover copied it for me. After starting the Dockers again, I noted in the settings of the vm and docker, that the default location is on the normal user share and not in the appdata... Do I also need to change it there? After I have started the dockers again, they are running all good. But the main drives still stay online (parity and disk1). You have any idea what to do? If the dockers might be a problem, i could delete them and re-create... some work but it could be done (It takes much time to import all photos and creating thumbs of them).

Hi Constructor, attached you will find the diagnostic file. What I did so far: 1. stopped the dockers (plex and NextCloud2) 2. stopped the array 3. added the new ssd as cache rive 4. created a btrfs partition on the cache drive 5. changed the share appdata to Cache only mode 6. started the array 7. moved (mv) the folder /mnt/disk1/appdata to /mnt/cache/. 8. now I made a mistake I think: I tried to move the folder under /mnt/user/appdata to /mnt/cache/appdata. After over 40 minutes I canceled the mv command. The folder was over 40 gb big in mnt/cache after that. However, I continued... 9. changed the docker App Config paths: 9.1 plex: from /mnt/user/appdata/binhex-plexpass/ to /mnt/cache/appdata/binhex-plexpass/ and 9.2 nextcloud2: from /mnt/user/appdata/nextcloud2/ to /mnt/cache/appdata/nextcloud2/ 10. started both dockers Current situation: Dockers are up and running. I could play all my music or watch my images in nextcloud. The ssd pushes it really forward! The speed increase was very good! I am not quite sure If my drives now spin down. mmmh.. Everytime when I am looking in the webgui, the drives are up. Thanks again for the help. And I really hope that I have not done too many mistakes

So, my Drive arrived and is now installed in the System. What / how should I Continue?

Ok, now i got it. As Said before i am new to unraid and don‘t got any configuration Tested by my own. I will give it a try with the Cache Drive and try to configure the dockers. Thanks again for the help.

I don‘t have that much Data that will be transferred to the Tower. Meaning that there May be some Images in the week and therefore i will Not Need the Cache. There is a bottlenec in the Drive capacity: i only habe 4 sata Ports on the Board and 1 PCI Slot. Yes, PCI and Not PCI-E. But it should work for one Cache Drive. so let‘s say that i will only Need a Drive Cache for Reading. is my Problem solved and the Hard drives will sleep? (Data Drive and parity Drive) if so, which config Could I use? Thanks again for Helping —— edit: After a Short Look on Amazon and searching for a ssd, i have noted the prices of ssds... 240 gb for 40 €. Will this be enough for e.g. 50 gb of Write Cache and 190 gb of read Cache?

Hi Constructor, thanks for the fast help and answer. I have missed to say, that I am currently having no cache drive. If a cache drive could help in this topic, I will buy one. So you say that the docker will keep the drives online. And when I will buy a ssd and put it into my tower, the docker could work on the ssd and the data array will completely spin down? If so, which config do I need to set in the config of the cache drive?

Hi @all, I am new to Unraid and really loves it! I have an Tower with 3 x 2 TB data drives and 1 x 2 TB parity drive. My main goals with this setup: save all my data, plex and NextCloud. After everything is setup and running really good, I mentioned that the parity drive and the first data drive will ever be online. Before installing NextCloud and plex I mentioned that ALL drives will spin down after some time. I guess that the docker's are preventing the array to spin down. Cause I don't find the exact problem in the documentation, I want to ask you to help. How could I spin down the array to save livetime of the disks (and some power) with active dockers? I tried to understand the cache drive topic and guess, that this could help here. Maybe somebody could explan it a bit for me? I found this post, but don't get it all all https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?page=2&tab=comments#comment-537383 Is cache only my option? Or do I need to manually copy files to cache drive?