Piteball

Yeah, make sure you don't have any "?" or other special characters in your password as that's going to f*ck up passing auth through URL. Skickat från min LE2113 via Tapatalk

No problem, just open an Incognito/InPrivate webbrowser and then run this command to get an authentication cookie. https://IP-address-of-NAS:5001/webapi/auth.cgi?api=SYNO.API.Auth&version=3&method=login&account=ADMIN-USERNAME&passwd=ADMIN-PASSWORD&format=cookie Expected respons {"success":true} In same Incognito/InPrivate session, run the following commands to active each function. Active Backup https://IP-address-of-NAS:5001/webapi/entry.cgi?api=SYNO.ActiveBackup.Activation&method=set&version=1&activated=true&serial_number="DeviceSN" Expected respons {"success":true} Active Backup 365 https://IP-Address-of-NAS:5001/webapi/entry.cgi?api=SYNO.ActiveBackupOffice365&method=set_activation&version=1&serial_number="DeviceSN" Expected respons {"success":true} Active Backup Google G-Suite https://IP-Adress-of-NAS:5001/webapi/entry.cgi?api=SYNO.ActiveBackupGSuite&method=set_activation&version=1&serial_number="DeviceSN" Expected respons {"success":true} Then you should have all functions activated, just make sure not to accidentally create new device serial number when upgrading as it will deactivate Active Backup suite. Skickat från min LE2113 via Tapatalk

This is what worked for me. Replace ADDRESS, DEVICESERIALNUMBER and port number if you use non default ports. Authentication https://ADDRESS:5001/webapi/auth.cgi?api=SYNO.API.Auth&version=3&method=login&account=USERNAME&passwd=PASSWORD&format=cookie Activate Active Backup 365 https://ADDRESS:5001/webapi/entry.cgi?api=SYNO.ActiveBackupOffice365&method=set_activation&version=1&serial_number="DEVICESERIALNUMBER" Activate Active Backup G-Suite https://ADDRESS:5001/webapi/entry.cgi?api=SYNO.ActiveBackupGSuite&method=set_activation&version=1&serial_number="DEVICESERIALNUMBER" Skickat från min LE2113 via Tapatalk

Your best bet would be to ask pocopico nicelly if he can compile drivers for the missing devices and to his rp-ext tree. In Linux drivers are bound to the Linux kernel so you need to recompile using kernel sources used in the specific DSM version and emulated Synology hardware. Skickat från min LE2113 via Tapatalk

It's quite impossible to give any assurances in current state. I'm actually trying it out using Tinycore Loader, however not so much luck getting the drives on the LSI 9211-8i to show up, even though mpt3sas was detected and me running rploader satamap, so I will probably have to either play around with satamap settings or connect to serialport using IPMI on the Supermicro mainboard to see what's not happening.

Go ahead and try it out, it's completely experimental and unsupported. However as you have noticed some people have actually gotten it to work mostly, except for some instability using docker containers.

If running under VirtualBox, make sure you change the network card from default NAT to bridged mode on primary LAN/WLAN Interface, then you will see the NAS in your network instead of behind NAT through you primary machines connection. That's probably why you got a strange NAT IP address by DHCP. Skickat från min LE2113 via Tapatalk

You can read about it in this thread, look at last page for some info on doing it this way. https://xpenology.com/forum/topic/13342-nvme-cache-support/ The simpler way is of course running DSM under Hypervisor/virtualized and then just setup a virtual disk on the NVMe storage as DSM will then just see this as a normal SATA or SAS SSD. Skickat från min LE2113 via Tapatalk

That's because it only supports official Synology NVMe cache out of the box, you will have to hex edit the driver to replace device ID with the one of your NVMe device. Skickat från min LE2113 via Tapatalk

The DS3615xs doesn't have a physical NVMe port, this was introduced in the DS918+, and therefore the utilities for managing NVMe disk cache is not available. Note that DS918+ also needs an Intel 6th gen CPU to boot because of the Intel atom extensions being used in that platform wasn't available in normal Intel CPU before that. Also as you may note, NVMe cannot be used for storage, only as cache. Skickat från min LE2113 via Tapatalk

There's no complete instructions as it's not ready for use by other then developers/programmers as of now. Don't be fooled by all posts here, people are just grasping for anything right now as this is our only hope of getting newer DSM working, but it's not finished and we don't know if we still have anyone working on solving all possible issues like support for drives larger then 2TB on SCSI/LSI controllers and many more. Skickat från min GM1913 via Tapatalk

You don't, you will have to make it yourself on a Linux machine or using WSL under Windows. Skickat från min GM1913 via Tapatalk

As the builds are version specific you have to use the exact PAT file which the loader was built for/using. Simplest way to ensure you use the correct PAT is by copying it from the build cache. Skickat från min GM1913 via Tapatalk

I've included the PCI hardware info of an RS2418RP+ 12-drive Atom C3538 based Synology NAS if it could be of any help. PCI-Hardware-Info-RS2418RP+.txt

I would not recommend anyone to use an in development proof of concept release like this in any way other than for the pure fun of testing it. I know some are actually storing they´re personal data at their own risk. Also, as we are standing right now we don't even know if the project is still alive, it's all just speculations bitcoin-style.