brantje

OpenVPN works fine here.

Enjoy this year =D. Lets make xpenology big!

As far i know, HA never worked with xpenology.

Afaik there are some xpenology AMD build, so it looks like it works.

And you are sure that the bios battery's are not empty?

First of all, welcome! 1) You can use ESXi or another hypervisor, or just run bare metal. If you choose to run bare metal, make sure the chipsets are supported by xpenology. 2) Hardware requirements depends of what you want to do with it. A powerfull, but still basic build can be found in my signature. 3) SSD Caching is not supported afaik. Therefore, i should add an extra disk to the Surveillance so you can have redundancy. 4) I have that board too, however, when i tried 16GB RAM it wouldn't boot. Not sure if that is a problem with this one or a general problem. 5) Still busy with this site.. but you can have a look https://dev.myxpenology.com/tutorials

You should downgrade to 5592. Their are driver issues with 5644.

Dsm 5.1 and higher is X64

5592 update 2?

DSM 5.2 5565 is running here for about 2 months. Rock solid ^_^. But true, don't fix it if it ain't broken.

If QTS used mdam raid, then it *might* be compatible. Best shot is creating a backup before you try.

Nice, good job! Did you try DSM 5.2 5565? That has docker in it ^_^

Tutorial here: viewtopic.php?p=6494#p6494

I think there are some drivers missing for the motherboard, you can ask the devvers to add them here

No, I was wrong, it is a Synology issue. Secure erase locks the drives. http://forum.synology.com/enu/viewtopic.php?f=7&t=93103 Good topic, will write a tutorial for that =)

DISCLAIMER! I’ll take no responsibility for any loss of data or any other problem caused by following this tutorial. Reinstall DSM (eg 5.2-5592) without losing the data on Volume: 01. Enable SSH if it`s not & connect to SYNOLOGY 02. Open & edit the file \etc.defaults\VERSION 03. Exchange the data with one of previous ver.: majorversion="5" minorversion="2" buildphase="0" buildnumber="5565" builddate="2012/12/05" 04. Save & Exit 05. Restart Synology 06. Launch Synology Assistant 07. Click 'Search' 08. If you've done everything correctly you'll see a new 'DiskStation' has been found. 09. Disconnect the USB flash drive from the computer for this next step 10. Right-click the new 'DiskStation' and choose 'Install' 11. Browse and select the same version (5.2-5592.pat) which U already running 12. Choose a Name for the DiskStation, a new default admin password and IP configuration 13. After installation is complete the DiskStation will reboot automatically. 14. Power it OFF manually now 15. Isert the same USB Flash drive (5.2-5592.img) back into PC 16. Power on PC & DSM will boot normally 17. In Synology Assistant click 'Search' again 18. Depending on the name and network config you chose during installation you will see now a DiskStation has been found with the NAME you chose.

Afaik serials / mac do not matter since the licenses are transferable. Looks like they do a simple check: GET /license_activation.php?cipherText=75FzMfuFSNq%2FwZagH3MYwoxc7VBy9L7N7szG4m6FJjhnna8W7VWaNRu%2Bafb0EzBOi4RnM6YKFJcILalWpoNkx0aEVIrY1OuXgFveKAjppPVEqgi2TRM%2FRW9Re2AZJLItG600DMYyU8HYgufzB1ZNFfYIDI22%2BCd3cZ7eJRR3pvQ%3D&dsSN=XXXXXXXXXX&dsModel=XXXXX&seed=275599814

The a bug in 5644 its currently not possible to create volumes.

Downgrading to 5592, create volume will also work i think. Have to try this on a Virtual Machine.

Thanks. Will add those parts to the list.

You got more info about that?

You got a serial / model for the RAM? What manufacturer and model is the ram?

This is for bare metal installations only! I'm gathering information so i can build a nice database of supported hardware by Xpenology Requirements: Provide me with the following details Type Supported hardware types for now: - CPU - Motherboard - RAM - SATA Card - SAS Card - SCSI Card - Network card - Harddrive - USB Wifi Manufacturer and model Thanks in advance =)

For future reference, what steps did you do to downgrade xpenology?

Try to reinstall download station, sounds like messed up configuration.