Search the Community

Thank you for your replies... In my case, both virtual/real options will fit in the same server (HP Proliant N40L with 4x3TB drives + 64GB SSD), so power consumption difference it's not the issue. It will be running 24/7. The SSD drive came from my HTPC, the GOAL was to generate as less noise as possible, but the HTPC crashed, so I reused SSD for OS in the server since 64GB is not enough to store almost anything Any comment is welcome in this thread, but my goal was to discuss what environment would be "better" for home use (storage movies and photos) and if anyone finds more PROs/CONs for each scenario. My biggest concern is how can I restore the information from SHR raid if the hardware (server) fails. Assuming that HDDs are OK, It be easier to move them to a different Server if it's virtualized, but I still have some doubts about the performance and failure points, too many layers (Debian >> VirtualBox >> XPEnology >> Data). On the other hand if it was installed as main system, I don't know if the recovery process to different hardware would be factible. For now, looks like virtualization has more advantages, but I always like to have third users opinions I appreciate your performance feedback.

This is old question in IT field ... virtual vs real ... I'd say it's really up to your environment. I have a real synology 712+ at home and a major PRO for me is the power consumption. It uses like 15W. Most PC hardware uses around 100W and in some cases even more (in my gaming PC, only VGA card needs around 275W). That can add up on your monthly bill. Other thing is availability. If it is virtual on a home machine that tends to be rebooted - the synology goes offline too. So at my home i'd go for a real BOX running xpenology on it. In my company that has existing VMWare platform that is based on 5 clustered hosts i'd go for VMWare image of xpenology because the platform is already there and anyway needs to be up 24/7 (and company pays the electrical bill). Ideal home platform would consist of mobo with dual core atom, 4Gb ram, and 2x or 4x 2Tb drives spinning at 5400 RPM. My synology ds712+ has 1Gb ram and singe core atom 1.8GHz. It is behind 50/5mbit line. I use pptp vpn, download station, file server, media server, video station, ... CPU hits 100% only when i add new pics to photo station (because they are 12mpix, roughly 6Mb average in size). Video station streams flawlessly without any hickups, while my downloads run in background. So my normal scenario consists of my son watching movies at PS3 over syno media server(LAN), my download station downloading torrents(WAN), my wife watching tv show over cifs share(LAN), my friend downloading my stuff over file station(LAN) and me watching a movie over video station(WAN). My 1.8Ghz cpu is at 7% and memory usage is at 21% ... so i think having a strong cpu like i3/i5/i7 is waste of money and a massive overkill (for home users, not ones that will put syno in gigabit LAN enviroment with >50 users accessing it). Also one thing i noticed is people wanting to use SSD for OS. People - it is not a gaming machine that needs to load BF3 map within seconds. Any 5400/7200rpm sata HDD will do. My first synology ds107 is today up and running with 250Gb samsung sata2 drive. It is running 24/7 without hibernation or standby and it works like a charm.

After boot you also can eject USB drive with software, while keeping it physically plugged in for future reboots. Configuration is not saved on it and written not to synoboot, but to the system partition on the hard drives.

..some information http://forum.synology.com/wiki/index.php/What_kind_of_CPU_does_my_NAS_have What kind of CPU does my NAS have Notes: For the installation of ipkg (via a bootstrap) you need to know the model of your CPU as detailed below. Be sure to refer to the General Disclaimer before modifying the Synology DiskStation. The GPL Source Code of the Synology DiskStation Manager and ToolChains can be downloaded from here. Refer to the Modification Contents to see other mods which can be performed on the Synology DiskStation. x13 Series System Model CPU Model CPU Speed (GHz) Cores Threads FPU Package Arch RAM Notes DS213air Marvell Kirkwood mv6282 ARM 1.6 1 1 no 6281 6282 16-bit@DDR3 256MB DS213 Marvell Kirkwood mv6282 ARM 2.0 1 1 no 6281 6282 16-bit@DDR3 512MB DS213+ Freescale QorIQ P1022 PPC 1.067 2 2 yes qoriq 64-bit@DDR3 512MB DS413j Marvell Kirkwood mv6282 ARM 1.6 1 1 no 6281 6282 16-bit@DDR3 512MB DS413 Freescale QorIQ P1022 PPC 1.067 2 2 yes qoriq 64-bit@DDR3 1GB DS713+ Intel Atom D2700 x86_64 2.13 2 4 yes x86 cedarview 64-bit@DDR3 1GB DS2413+ Intel Atom D2700 x86_64 2.13 2 4 yes x86 cedarview 64-bit@DDR3 2GB RAM expandable up to 4GB x12 Series System Model Processor Type Notes DS112+ Marvell Kirkwood mv6282 2.0Ghz ARM (Marvell ARMADA 300) 16-bit@DDR3, 512MB of RAM DS112j Marvell Kirkwood mv6281 1.0Ghz ARM (Marvell ARMADA 300) 128MB of RAM DS11 2 Marvell Kirkwood mv6282 1.6Ghz ARM (Marvell ARMADA 300) 256MB of RAM DS212j Marvell Kirkwood mv6281 1.2Ghz ARM (Marvell ARMADA 300) 16-bit@DDR2, 256MB of RAM DS212 Marvell Kirkwood mv6282 1.6Ghz ARM (Marvell ARMADA 300) 16-bit@DDR3, 256MB of RAM DS212+ Marvell Kirkwood mv6282 2.0Ghz ARM (Marvell ARMADA 300) 16-bit@DDR3, 512MB of RAM DS412+ Intel Atom D2700 Dualcore (2C/4T) 2.13GHz x86 Processor 64-bit@DDR3, 1GB of RAM DS712+ Intel Atom D425 Monocore (1C/2T) 1.8GHz x86 Processor 64-bit@DDR3, 1GB of RAM DS1512+ Intel Atom D2700 Dualcore (2C/4T) 2.13GHz x86 Processor 64-bit@DDR3, 1GB of RAM DS1812+ Intel Atom D2700 Dualcore (2C/4T) 2.13GHz x86 Processor 64-bit@DDR3, 1GB of RAM DS3612xs Intel Core i3 Dualcore (2C/4T) 3.1GHz x86 Processor 64-bit@DDR3, 2GB of ECC RAM (6GB Max), scalable to 36-drives with DX1211 (12+12+12 drives total) RS212 Marvell Kirkwood mv6282 1.6Ghz ARM (Marvell ARMADA 300) 16-bit@DDR3, 256MB of RAM RS812 Marvell Kirkwood mv6282 1.6Ghz ARM (Marvell ARMADA 300) 16-bit@DDR3, 256MB of RAM, scalable to 8 drives with RX410 (4+4 drives total) RS812+/RS812RP+ Intel Atom D2700 Dualcore (2C/4T) 2.13GHz x86 Processor 64-bit@DDR3, 1GB of RAM, scalable to 8 drives with RX410 (4+4 drives total) RS2212+/RS2212RP+ Intel Atom D2700 Dualcore (2C/4T) 2.13GHz x86 Processor 64-bit@DDR3, 1GB of RAM, scalable to 22 drives with RX1211 or RX1211RP (10+12 drives total) RS3412xs/RS3412RPxs Intel Core i3 Dualcore (2C/4T) 3.1GHz x86 Processor 64-bit@DDR3, 2GB of ECC RAM (6GB Max), scalable to 34-drives with RX1211 or RX1211RP (10+12+12 drives total) x11 Series System Model Processor Type Notes DS111 Marvell Kirkwood mv6282 1.6Ghz ARM (Marvell ARMADA 300) 16-bit@DDR3, 256MB of RAM DS211j Marvell Kirkwood mv6281 1.2Ghz ARM 16-bit@DDR2, 128MB of RAM DS211 Marvell Kirkwood mv6282 1.6Ghz ARM (Marvell ARMADA 300) 16-bit@DDR3, 256MB of RAM DS211+ Marvell Kirkwood mv6282 1.6Ghz ARM (Marvell ARMADA 300) 16-bit@DDR3, 512MB of RAM DS411 Marvell Kirkwood mv6282 1.6Ghz ARM (Marvell ARMADA 300) 16-bit@DDR3, 512MB of RAM DS411j Marvell Kirkwood mv6281 1.2Ghz ARM 16-bit@DDR2, 128MB of RAM DS411slim Marvell Kirkwood mv6282 1.6Ghz ARM (Marvell ARMADA 300) 16-bit@DDR3, 256MB of RAM DS411+ Intel Atom D510 Dualcore (2C/4T) 1.67GHz x86 Processor 64-bit@DDR2, 1GB of RAM DS411+ II Intel Atom D525 Dualcore (2C/4T) 1.8GHz x86 Processor 64-bit@DDR2, 1GB of RAM DS1511+ Intel Atom D525 Dualcore (2C/4T) 1.8GHz x86 Processor 64-bit@DDR2, 1GB of RAM (3GB Max), scalable to 15-drives w/DX510, (5+5+5 drives total) DS2411+ Intel Atom D525 Dualcore (2C/4T) 1.8GHz x86 Processor 64-bit@DDR2, 1GB of RAM (3GB Max), scalable to 24-drives with DX1211 (12+12 drives total) DS3611xs Intel Core i3 Dualcore (2C/4T) 3.1GHz x86 Processor 64-bit@DDR3, 2GB of ECC RAM (8GB Max), scalable to 36-drives with DX1211 (12+12+12 drives total) RS411 Marvell Kirkwood mv6282 1.6Ghz ARM (Marvell ARMADA 300) 16-bit@DDR3, 256MB of RAM RS2211+/RS2211RP+ Intel Atom D525 Dualcore (2C/4T) 1.8GHz x86 Processor 64-bit@DDR2, 1GB of RAM (3GB Max), scalable to 22-drives with RX1211 or RX1211RP (10+12 drives total) RS3411xs/RS3411RPxs Intel Core i3 Dualcore (2C/4T) 3.1GHz x86 Processor 64-bit@DDR3, 2GB of ECC RAM (8GB Max), scalable to 34-drives with RX1211 or RX1211RP (10+12+12 drives total) x10 Series System Model Processor Type Notes DS110j Marvell Kirkwood mv6281 ARM SATA, 16-bit Memory Bus, 128MB of RAM DS110+ Freescale PowerQUICC III MPC8533E PPC SATA, 64-bit Memory Bus, 512MB of RAM DS210j Marvell Kirkwood mv6281 ARM SATA, 16-bit Memory Bus, 128MB of RAM DS210+ Freescale PowerQUICC III MPC8533E PPC SATA, 64-bit Memory Bus, 512MB of RAM DS410j Marvell Kirkwood mv6281 ARM SATA, 16-bit Memory Bus, 128MB of RAM DS410 Freescale PowerQUICC III MPC8533E PPC SATA, 64-bit Memory Bus, 512MB of RAM DS710+ Intel Atom D410 Monocore (1C/2T) 1.67GHz x86 Processor SATA, 64-bit Memory Bus, 1GB of RAM DS1010+ Intel Atom D510 Dualcore (2C/4T) 1.67GHz x86 Processor SATA, 64-bit Memory Bus, 1GB of RAM (expandable to 3GB), Scalable to 10-drives RS810+/RS810RP+ Intel Atom D510 Dualcore (2C/4T) 1.67GHz x86 Processor SATA, 64-bit Memory Bus, 1GB of RAM (expandable to 3GB), Scalable to 8-drives, x09 Series System Model Processor Type Notes DS109j Freescale PowerQUICC II MPC8241 PPC SATA, 32-bit Memory Bus, 32MB of RAM DS109 Marvell Kirkwood mv6281 ARM SATA, 16-bit Memory Bus, 128MB of RAM DS109+ Freescale PowerQUICC III MPC8533 PPC SATA, 64-bit Memory Bus, 512MB of RAM DS209j Freescale PowerQUICC II MPC8241 PPC SATA, 32-bit Memory Bus, 64MB of RAM DS209 Marvell Kirkwood mv6281 ARM SATA, 16-bit Memory Bus, 256MB of RAM DS209+ Freescale PowerQUICC III MPC8533 PPC SATA, 64-bit Memory Bus, 512MB of RAM DS209+II Freescale PowerQUICC III MPC8533 PPC SATA, 64-bit Memory Bus, 512MB of RAM DS409 Marvell Kirkwood mv6281 ARM SATA, 16-bit Memory Bus, 256MB of RAM DS409Slim Marvell Kirkwood mv6281 ARM 2.5" SATA, 16-bit Memory Bus, 128MB of RAM DS409+ Freescale PowerQUICC III MPC8533 PPC SATA, 64-bit Memory Bus, 512MB of RAM DS509+ Freescale PowerQUICC III MPC8533 PPC SATA, 64-bit Memory Bus, 1GB of RAM RS409 Marvell Kirkwood mv6281 ARM SATA, 16-bit Memory Bus, 256MB of RAM RS409+ Freescale PowerQUICC III MPC8533 PPC SATA, 64-bit Memory Bus, 1GB of RAM RS409RP+ Freescale PowerQUICC III MPC8533 PPC SATA, 64-bit Memory Bus, 1GB of RAM, Redundant Power Supplies x08 Series System Model Processor Type Notes DS108j Freescale PowerQUICC II MPC8241 PPC SATA, 32-bit Memory Bus, 32MB of RAM DS408 Freescale PowerQUICC III MPC8543 PPC SATA, 64-bit Memory Bus, 512MB of RAM DS508 Freescale PowerQUICC III MPC8543 PPC SATA, 64-bit Memory Bus, 512MB of RAM RS408 Freescale PowerQUICC III MPC8543 PPC SATA, 64-bit Memory Bus, 512MB of RAM RS408-RP Freescale PowerQUICC III MPC8543 PPC SATA, 64-bit Memory Bus, 512MB of RAM, Redundant Power Supplies x07 Series System Model Processor Type Notes DS107e Freescale PowerQUICC II MPC8241 PPC SATA, 32-bit Memory Bus, 32MB of RAM DS107 Freescale PowerQUICC II MPC8241 PPC SATA, 64-bit Memory Bus, 64MB of RAM DS107+ Marvell Orion mv5281 ARM SATA, 32-bit Memory Bus, 64 or 128MB of RAM DS207 Freescale PowerQUICC II MPC8241 PPC SATA, 64-bit Memory Bus, 32MB, 64MB or 128MB of RAM, (128MB variant has limited availability) DS207+ Marvell Orion mv5281 ARM SATA, 32-bit Memory Bus, 128MB of RAM CS407e Freescale PowerQUICC II MPC8241 PPC SATA, 64-bit Memory Bus, 64MB of RAM CS407 Marvell Orion mv5281 ARM SATA, 32-bit Memory Bus, 128MB of RAM RS407 Marvell Orion mv5281 ARM SATA, 32-bit Memory Bus, 128MB of RAM x06 Series System Model Processor Type Notes DS-106e Freescale PowerQUICC II MPC8241 PPC SATA, 32-bit Memory Bus, 32MB of RAM DS-106 Freescale PowerQUICC II MPC8241 PPC SATA, 64-bit Memory Bus, 64MB of RAM DS-106x Freescale PowerQUICC II MPC8241 PPC SATA, 64-bit Memory Bus, 128MB of RAM, Limited Availability DS-106j Freescale PowerQUICC II MPC8241 PPC PATA, 32-bit Memory Bus, 32MB of RAM CS-406e Freescale PowerQUICC II MPC8241 PPC SATA, 64-bit Memory Bus, 64MB of RAM CS-406 Freescale PowerQUICC II MPC8245 PPC SATA, 64-bit Memory Bus, 128MB of RAM RS-406 Freescale PowerQUICC II MPC8245 PPC SATA, 64-bit Memory Bus, 128MB of RAM x01 Series System Model Processor Type Notes DS-101 Intel XScale FWIXP420BB ARM PATA, 32-bit Memory Bus, 64MB of RAM DS-101j Intel XScale FWIXP420BB ARM PATA, 32-bit Memory Bus, 32MB of RAM DS-101g+ Freescale PowerQUICC II MPC8241 PPC SATA, 32-bit Memory Bus, 64MB of RAM

Thank you so much! Very good. Does this not support USB drives? or USB sticks?

Hi, I want to move to XPEnology but I have some doubts... Which setup do you think it's better? Hardware: N40L with 8GB RAM ECC + 4x3TB HDs + 1xSSD 64GB for OS **Note: Please consider that I might be wrong in some of these statements Scenario 1) Virtualized PROS: ===== - NO USB flashdrive needed to boot. - Hardware independent: If the server motherboard crashes, you can port it to a different hardware as long as you have the same HDs. - Can use both SOFTWARE / HARDWARE RAID as long as Hypervisor is compatible. - Snapshots - Possibility to install other Virtual Machines. - I can install the MainOS (such a Debian + Headless Vbox or VMWare ESXi) in 64GB SSD drive. CONS: ===== - Virtualized HDs are really Files stored in other filesystems. Slower. ** Edit: Reported 50MB/s in VMWare even with RAW DEVICE MAPPING. It's 50% performance of a standalone installation. - No USBs??? (not sure about this). ** Edit: VirtualBox has some instructions to link USBs to hosted machines. - More failure points, the need to have XPEnology hosted in another OS, makes it less reliable as both systems + virtualization soft (in VirtualBox case) may have bugs. Scenario 2) Standalone PROS: ===== - SHR RAID. - Performance should be sightly better. Again, feedback is appreciated. ** Edit: Reported transfers up to 100MB/s limited by Gigabit network card. - USB (updating the modules for N40L). CONS: ===== - USB flashdrive required - If HW crashes... little mess to bring everything back online. **Edit: XPEH explained that Synology O.S. is stored in all hard drives, and even using different synoboot images to boot, it worked OK. - Adding SSD drive, would provide no beneffit unless I create as a different volume - (Maybe using it as SSD cache?). This is all I can think about, but I'm sure that you know more PROs/CONs. My Needs (if anyone asks): - PLEX Media Server - Transmission (or another BT Client). - Emule client - Sickbeard - Samba sharing - AFS sharing - (Planned) Fog Clone server (will install in Debian-Chroot) or nClone. - OwnCloud - Photostation - DynDNS Thank you in advance!!

I am currently running XPEnology native on my N40L however I stumbled on the issue that the drives will not go in hibernation. The /var/log/messages file is full with this line: scemd: smartctl_ata_command_interface.c:117 ata ioctl HDIO_DRIVE_CMD error I am 2 of these drives: Western Digital WD30EZRX All services are down, disconnected the internet cable from the NIC. Does anyone have an idea how to fix this? Thanks.

Trying to determine whether there are any gotchas with setting up systems with more than 10 disks? I have a DS412+, and I've really enjoyed the ease of use - my main NAS/SAN currently runs OpenFiler, and I'd love to move it over to xpenology. Boots just fine on the main board (Intel S5000PSL), and detects the SAS controller (IBM M1015), but I have that attached to 3 Chenbro SAS expanders (16 drives each). I know Linux itself will most definitely work, but was wondering if there were any artificial limitations in the Synology interface that would make this combination unusable? The largest con figs on the Synology gear support 36 disks, so short of dismantling my existing setup, does anyone know if this will work? Thanks!

В самом начале тестирования XPEnology на HP Microserver N36L делал много переустановок и почему-то довольно часто затирался загрузочный USB диск, несмотря на принимаемые меры. Неопытный, однако... Меня это достало и вроде нашел нормальное решение этой проблемы. Загрузочный диск делается на карте SD либо microSD но(!) с переходником. После создания диска его нужно просто механически заблокировать на запись (там рычажок Lock есть такой) и готово. В комп карта вставляется с помощью любого подходящего картридера, лучше миниатюрного типа обычной USB флешки. Кроме того встречаются (редко) USB флешки с механическим блокиратором записи. На некоторых моделях (если вскрыть корпус) иногда сам переключатель не распаян, но место под него и контакты предусмотрены. Остается аккуратно присобачить свой простейший замыкатель контактов. Я нашел одну такую (нераспаянную) флешку - Transcend на 8ГБ, сейчас испытываю её после проведения паяльных работ. Некоторые флешки, кроме того, требуют, чтобы в Микросервере в БИОСе режим эмуляции для USB дисков стоял не в положении Auto, а именно в Hard Drive. В Аuto некоторые флешки дают сообщение GRUB Error при попытке загрузиться, либо загружаются через раз, сбивая с толку таким поведением. Заблокирован ли загрузочный USB диск от записи проверяется и выводится на монитор при загрузке системе в общей куче. Предполагаю, что на родных Synology загрузочный диск заблокирован от записи по умолчанию.

you could take two identical usb sticks (as hard drives) and boot from sd boot please test

Hi together, I would like to know what you would do in my situation: I have XPE running on a HP MicroSerer N40L running VMWare ESXi 5.0 The reason why vmware is that I have to run another small machine on it. Now my question is how would you set up the data storage if you were me? I have three Hard Disks dedicated for NAS data storage, 2TB, 2TB, 3TB A fourth HDD of 1 TB is used as vmware datastore for placing the system containers on. I could now use three ways to create a storage: Option 1: Semi-HW-RAID Use the onboard RAID Controller (HP) and create a RAID5 over all three disks and give the resulting logical disc as a raw device over to XPE which will then detect one data-disc connected. Advantages: RAID is done before any OS sees the drive. So vmware only has to deal with one drive. Disatvantages: a) If my board crashes I probably might not find a replace... oh! It's HP You know what I mean... b) If I decide to move to another device anytime I will need to backup and restore all data. Option 2: SW-RAID5 Pass all three discs to XPE and let the DSM create a software raid Adv: I can pull the discs out and put them into a DiskStation any time without forcefully having to backup and restore. Dadv: vmware has to deal with three discs Option 3: Container Create SEMI-HW-RAID but do not pass the RAW "device" to XPE but use it as ESX datastore. Then create a big vHD for XPE. Additional to Advs and Diss of Option 1 there is the positive point that I could also use the storage for vHDs. Another negative point is that I have one more layer between the software and effectively writing the block... What way would you use?

Hello, I am running the XPEnology_DS3612xs_2668 on a Intel D2700MUD motherboard. Everything is working perfect. The only issue I have is when I do a reboot from the GUI. The http://ip-nas:5000/webman/... Is not accessible. I can still login with SSH but when I give a reboot command nothing happens. Does anyone know what this problem can be and how to fix it. At the moment a manual hard reset is the only option. For the rest keep up the good work Cheers Burner1977

Thank you very much for the VMware img. I have it running on ESXi 5.1. Is PVSCSI supported? I can only add 2 more RDM drives as IDE. I have 3 other drives to add. Is this possible? Thanks!

thanks for this great build. Anyone try to install on PC? It's seems doesn't support hard drive hibernation. I have enable the HD hibernation on DSM control panel. But never enter hibernation mode.

У меня есть старый PATA Disk. Можно ли его использовать как загрузочный вместо USB Drive? На материнке поддержка PATA присутствует. И еще вопрос. Сейчас когда я подключаю внешний USB диск они не виден в разделе Exsternal Drives, а добавляется в список внутренних. Можно ли это поправить?

It would be nice if you post witch driver you need so we can make a list for the next build and maybe someone can compile then the next build . I will Update the list . THE WISH LIST Controller : Adaptec RAID ASR-6805 http://www.adaptec.com/en-us/downloads/linux_source/linux_source_code/productid=sas-6805&dn=adaptec+raid+6805.html Promise FastTrak TX4310 http://firstweb.promise.com/upload/Support/Driver/1_ft-tx4310-linux-partial-src-v2.6.1.0321.tgz Chipsets: SSD Drives: Other stuff:

ok... For the NIC I will use a intel gigabit desktop adapter with just a single port. The power consumption is much less than the dual port server adapter. But I'm going crazy on the hibernation / standby problem with the HDDs. I just tried to use a WD20EARS. I reinstalled XPEnology on just a single drive. I can't get it to sleep. The DSM says "Failed to setup WOL" using hdparm -Y the drive just enters sleep mode for some seconds... I'll try to test with a Samsung HDD... Maybe I'll also try to use a different NIC as mentioned above... Maybe WOL will work and the drives will suspend?!

Hmm... After some more investigation on hhd sleep: hdparm -S 60 /dev/sd... is accepted but the disk does not spin down. hdparm -Y /dev/sd... is successful but the disk spins up again after a few seconds. REMARK: a fresh installation of DSM is done before. There are NO data partitions except the DSM OS... It seems to be an issue with my WD10EADS drives. I found several threads with the same problem. They suggest to use hd-idle... Any experience on hd-idle on XPEnology? Bernd

Just use "syno_hibernate_debug_tool --enable 10" and see "/var/log/messages" to find out, which applications uses uour drives. I just try..and no message it's clean....i try --enable-force and same...no went go to standby mode.. I will try my second NL40...

Hi All, Finally got around to test, and truly enough, it works. You test that the nic is detected with "Synology Assistant" but installing means wiping the first disk... . Prepared a USB key with the img written on it. didn't modded it with the mac address . Connected it and went in the bios to but the usb key first in the disk boot sequence . Booted from it then removed it after it has booted . Used synology assistant to install the *.pat DSM_DS3612xs_2668.pat . after install, put back the USB key, booted and voila Added afterwards the usb2 modules and while the camera still worked, it now showed my USB Stick. I tried the logitech orbit webcam, but two playstation eye fail to work, complaining about no serial number... I tried two usb tuners, but they failed to capt anything under video station and no tuner detected under TVHeadEnd

Just use "syno_hibernate_debug_tool --enable 10" and see "/var/log/messages" to find out, which applications uses uour drives.

Since you are in this thread, i will thank you as well. I found few things after installing under VMware thanks to the ++version with more hardware compiled... This therefore might interest you: Module drivers included the same way controller driver and network was done: . List of supported USB speakers/soundcard: http://forum.synology.com/wiki/index.ph ... B_Speakers . List of supported USB printers: http://www.synology.com/support/faq_sho ... 6〈=enu . List of supported USB DVB-T (DTV) dongles by VideoStation http://www.synology.com/support/faq_sho ... u&q_id=532 . List of Supported USB webcam (UVC compatible): http://www.ideasonboard.org/uvc/#devices By the USB Camera module (actually not compiled in kernel) Repository: http://e-remonty.info/spkrepo/packages . TVHeadEnd (cannot be running concurrently to VideoStation), add repository: http://www.synocommunity.com/packages Webcam ======== I tried an intel atom package for USB webcam: https://dl.dropbox.com/s/4qludm9rf5k079j/webcam-intel-41.zip?dl=1 Source: http://forum.synology.com/enu/viewtopic.php?f=190&t=49790&start=150, repository/download: http://e-remonty.info/spkrepo/packages I needed to reboot, time out half the time when launching the webcam module, but can show the video using webcam application. USB device not detected in "external devices" but that's normal. Go into surveillance station, put the following to have surveillance station work: CODE: SELECT ALL . IP Address: 127.0.0.1 . Port: 5000 . Brand: [user Define] . Path: /webman/3rdparty/webcam/webcam.cgi . Login: admin . Password: your admin password PS: Playstation eye could work, but missing serial make them non supported with webcam 1.0 app Synology Download Station Search Modules:http://sourceforge.net/projects/synoboost/?source=dlp ========================================= ThеPirateBaу RuTrасker NNM-Сlub RuТоr Megatorrents TorrentDownloads Demonoid TorrentReactor TVTorrents KickAssTorrents TorrentLeech XSpeeds FastTorrent HDClub What.CD TorrentHound HD-Space YouTube iLoveTorrents HDME.eu HD-Torrents Dreambox OpenPli [record with dreambox on NFS share on synology nas] ================= DSM > File station > create dreambox folder DSM > Control panel > shared folders > select folder > Privileges > NFS privileges > *, read/write, Mapped to admin, Yes Use the Dreambox web interface > settings > Mount Manager Filetype: 0 (NFS) Client directory: /media/hdd Server Directory: /volume1/dreambox Remote IP: 192.168.0.2 Username: admin Pass word: your admin password Ticked boxes: rw, nolock, intr, soft, tcp

what about Hyper-v support? I tried to boot from converted .VDI file to .VHD, but synology is not detected from SynoAssistant. I also converted .IMG file to .VHD but also not detected... Probably the problem is in the network cards available in Hyper-v. I tried both (normal and legacy card) Regards

Hi All, since i'm not good at recompiling drivers (USB webcam driver for monitoring station please ?) i can at least document my trials to share (a little) something... Also logged separatly the errors encountered, to avoid newbie questions VMWare Player 5.0.1 install with XPEnology DS3612xs DSM 4.1 build 2668++: . Enabled "Virtualization support" in BIOS, otherwise no 64 bit support for the VM . Installed "VMWARE Player" . In VMWare Player VM settings, removed CD, Floppy, Added serial port . In VMWare Player VM settings, added USB 2.0 controller (could be fun to test USB 3.0 is such a port is present, and to test performance) . In VMWare Player VM settings, ticked in Settings > Processor "Virtualize Intel VT-s/EPT or AMD-V/RVI" and "Virtualize CPU Performance Counters" (Have i5 processor) . In VMWare Player VM settings, Configured NIC as bridge mode or HostOnly + Configured DNS for virtual NIC as the NIC IP (192.168.206.1 by default) and use Mac address: 00:11:32:08:D6:2A . In VMWare Player VM Folder "C:\Users\Admin\Documents\Virtual Machines\XPEnology" i have added in file "XPEnology.vmx" the entry: ethernet0.virtualDev = "e1000e" and you will have gigabit speed instead of 100MB detected as 0 in control panel > network > Netowrk Interface : network status . In VMWare Player VM settings, created an IDE disk 2TB size (64GB is too small, SCSI Fails formating) but my SSD size was 64GB, no pb there . Used "StarWind V2V Image Converter" to convert IMG to VMDK and did a copy of the vmdk (usefull if getting error 22 on boot after failed install, always keep a good backup file) . Loaded VMDK file as IDE . Used "Synology Assistant" (doesn't work with XPEnology web interface directly despite the possibility to load *.pat file) scanned, then right-click>install, and loaded xpenology *.pat file, and got Error 22 at re-boot as expected . restored VMDK from backup, installation continued . Install Finished, and it is working. Thanks again for this great package Tips, errors encountered + Fix: . The IDE 200MB VMDK disk will be recognised as well, so the raid won't be automatically created . After install attempt, error 22 at the console after boot-up. restore VMDK from backup keeping a good backup still . Went http://192.168.206.128:5000 and selected to "install DSM from my computer or installation disk" but got an error "An error occurred during installation. The telnet service of Diskstation is turned ON for error determination. Please configure your router to forward port 23 to Diskstation, and then contact synology online support. (21)". AND "Synology Assistant" gave partition format error and Error 22 at re-boot. Disk size was too small (used 64GB. 2000GB was subsequently ok). . Originally, I didn't put the MAC address "00113208D62A"in "VMWare Player" and it still worked. Apparently, it's only needed if you have more than one instance of a synology OS on the network . Try to use IDE disk format, it's not recognised for the HSR raid as expected...[/code] [EDIT]Bonus!!!! I tried an intel atom package for USB webcam: https://dl.dropbox.com/s/4qludm9rf5k079j/webcam-intel-41.zip?dl=1 Source: http://forum.synology.com/enu/viewtopic.php?f=190&t=49790&start=150 I needed to reboot, time out half the time when launching the webcam module, but can show the video using webcam application. USB device not detected in "external devices" but that's normal. Go into surveillance station, put the following to have surveillance station work: . IP Address: 127.0.0.1 . Port: 5000 . Brand: [user Define] . Path: /webman/3rdparty/webcam/webcam.cgi . Login: admin . Password: your admin password Module drivers included the same way controller driver and network was done: . List of supported USB speakers/soundcard: http://forum.synology.com/wiki/index.php/User_Reported_Compatible_USB_Speakers . List of supported USB printers: http://www.synology.com/support/faq_show.php?q_id=116〈=enu . List of supported USB DVB-T (DTV) dongles by VideoStation http://www.synology.com/support/faq_show.php?lang=enu&q_id=532 . List of Supported USB webcam (UVC compatible): http://www.ideasonboard.org/uvc/#devices By the USB Camera module (actually not compiled in kernel) Repository: http://e-remonty.info/spkrepo/packages . TVHeadEnd (cannot be running concurrently to VideoStation), add repository: http://www.synocommunity.com/packages . Pay to use product: DVBLogic http://dvblogic.com/en/products/synology-x86-intel

IDE drives are seen as md devices, that is why it will fail on esx 5 (or workstation 9) The firmware image will be overwritten during install. I managed to get it to work by restoring the firmware image after install. Would be better if ide devices would not be mapped into md devices. If i have time i will look into it this weekend. Cheers