pigr8

and if it's working, it's obsolete [cit.]

why would they do such a thing, to speed the release up? they dont get paid for the efforts so no rush is required.

nice, a lot of new feature <3

no problem here, bios corruption can be easilly fixed saving to defaut all the needed stuff, running since months with no issues whatsoever

i have a similar setup, couchpotato sickrage and transmission installed on dsm as packages. after i created an user "droid" and placed a folder in /volume1/share/downloadz i give him permission to read and write in that folder. then i changed all the startup user of the 3 packages to user droid (instead of having 1 user individually for each package) and the relative target folder in @appstore. now all the packages runs as a single user and all can read and write in the specific folder, postprocessing is handled correctly and the movies/series folder is shared over the local network using NFS (to a raspi2). it doesnt really make sense to have 3 specific users for cp sr and trans and create then a 4 one to read those folders, just handle all with 1 dedicated user.

option 1

6 cores each, 12 threads each, 24 total. for a Synology Bare Metal setup? like andyf said go for a EXSi server and give only 8 of them to Synology VM and the rest to other stuff.

nope

sorry for bumping this up, i tried to poke around and set the values to esataportcfg=0x10 internalportcft=0x2F usbportcfg=0x1FC0 (biosmod to have all 6 port to ahci) but in the end even if port 4th (the physical rear esata) is set to be esata it shows up in DSM as empty slot in storage manager.. can this not be hidden?

docker is working

updated without issues on HP N40L, reboot is required after upgrade

i don't think the problem needs another rebase of xpenology, the genuine ds3615xs is probably working fine with btrfs like benji30's ds1813+ out of the box with some modification at the *.conf and i think with the next big update Synology will bring btrfs to all latest gen NAS.

excellent maybe next release of xpenology could bring us a fix

i think btrfs is fully included in 5.2 it only needs to be enabled by default and xpenology has to fix everything to use is properly

support_btrfs="yes" support_dr_snap="yes" support_share_snapshot="yes" supportraidgroup="yes" i added the first 3 and set "yes" to the last one that was "no"

i managed to get the same results but it's not fully working.. here is my recap: 1. first thing, upgrading 5.2-5592 to update3 brings some new stuff to btrfs.ko i think 2. volume creation works but mount is crashing at boot, manually mount makes volume online again. 3. shr expansion works adding a disk and btrfs filesystem grows so handlig here is ok 4. data protection is enabled while creating a new share in the volume (i suppose it's snapshot ability) 5. folder is visible as it should in file manager and #snapshot is here too 6. data protection manager handles the share snapshots and let you manually snap or schedule it 7. creating the first snapshot gives error to all users (even SYSTEM) i wanted to try to make via ssh a manual snapshot and see if DPM handles it but i'm stuck with it :\

the gui is the same for managing the snapshots. i added the lines in synoinfo.conf but it keeps crashing when i try to create a new volume and disk group, how did you manage to create it?

yes ofc you can, i have volume1 as data raid and volume2 that is used only for time machine backup and surveillance station.

working here too on 5.2-5592.3 thank you!

you have to use DSM 5.2-5565 pat file, after that you can flash update1 and then update2.. upgraded just today from 5.0-xxxx to the latest version 5565 and everything is perfect

http://xpenology.com/forum/viewtopic.php?f=2&t=3052&p=20337&hilit=PID#p20337 done that was easy, thank you!

just configured my new (used) N40L with nanoboot and 4528, 2x 3TB Barracudas, USB3 Nec pci-ex card, wifi backup dongle and everything is working great. integration with sickrage and transmission is working flawless, and time machine backups are fine too just a question, i'm reading back some pages but i didn't find yet a solution: is there a way to hide the system boot drive (usb key) completly from DSM? this is the last thing i need to fix