Trantor

No sorry, can you repost me the driver link. When I found some time I will look for this. Both correct I think most people just use the SATA ports on the motherboard and don't need SCSI/SAS drivers. And yes HBA version is less tested and this is not a original synology feature.

No sorry no idea Just forget to edit synoinfo.cfg ^^ This is the default value for DS3612xs.

DSM 4.3-3827 v1.1 Beta7 is available : viewtopic.php?f=2&t=1361&p=12750#p12750

This is an updated beta which include several updates/fixes. Before doing anything, backup your data. No warranty for any damages, loss of data or anything else. Link : http://xpenology.trantor.be/beta/ Update DSM to 4.3-3827 build, please update your system to fix security issues in previous version. Two versions of synoboot : standard and hba (with scsi/sas drivers - only use this if you have a storage controller) Known issues: It will take 10 minutes or longer before it writes the configuration files, you can either cancel the installation or wait for it to finish. If you cancel, run assistant again and right click setup. Changelog: v7 (24/02/2014) - Update to 4.3-3827 build - Synology DX510 is properly detected - Temporarily removed pata_legacy v6 (09/02/2014) - Fix grub error 17 (introduced in beta5) - Add Mellanox Technologies 10Gbit Ethernet support - Add QLOGIC QLCNIC 1/10Gb Converged Ethernet support - Add RocketRAID 2640x4 support (rr26xx driver) v5 (20/01/2014) - Add VIA CPU support (CENTAUR) - Update synobios.ko (by k3dt ; fix "buzzer stop button pressed" warning) - Add Brocade 1010/1020 10Gb support - iSCSI (block level) works in IET mode (change lio to iet in synoinfo.cfg) - iSCSI (regular) works in LIO mode - NFS working - CIFS mount point working - Include bootstrap ipkg setup script (/root.profile is already modified) : after setup just log to ssh and type : sh syno-i686-bootstrap_1.2-7_i686.xsh reboot, log again to ssh and type ipkg update v4 (29/12/2013) - You can now install DSM on drives connected to a SCSI/SAS controller - Fix the volume "broken" issue when DSM is installed on a SCSI/SAS controller - Fix NFS support - Update megaraid_sas driver to the latest version - Modify the way XPEnology's modules are loaded in ramdisk - Include modules from previous beta - Add PS2 keyboard support v3 (21/12/2013) - Add more drivers for KVM / virtio / virtualization support - Add patched r8169 driver (realtek chips which are not working with the r8168 driver will work with this one) - Add latest version of sk98lin driver (Marvell Yukon / SysKonnect SK-98xx/SK-95xx support) - Update Broadcom bnx2 driver to latest version v2 (05/12/2013) - AX88179 Gigabit Ethernet USB 3.0 - Latest driver version for RocketRAID 3xxx/4xxx Controller - Latest (aacraid) driver version for Adaptec - Support XFS filesystem (no idea if DSM will automount this) v1 - Update synobios.ko (by k3dt ; fix "buzzer stop button pressed" warning) SCSI ---- Highpoint Rocketraid 2720SGL LSI mpt2sas v17 Adaptec aacraid Intel C600 Series Chipset SAS NETWORK ------- 3Com 3c590/3c900, 3cr990 Alteon AceNIC/3Com 3C985/NetGear GA620 QLogic QLA3XXX SiS 900/7016 SiS190/SiS191 USB --- USB to serial / Prolific 2303 driver PATA ---- ATI PATA (PATA_ATIIXP) AMD/NVidia PATA (PATA_AMD) CMD64x PATA (PATA_CMD64X) JMicron PATA (PATA_JMICRON) Marvell PATA (PATA_MARVELL) Promise PATA 2027x (PATA_PDC2027X) Intel SCH PATA (PATA_SCH) CMD / Silicon Image 680 PATA (PATA_SIL680) SiS PATA (PATA_SIS) VIA PATA (PATA_VIA) Winbond SL82C105 PATA (PATA_WINBOND) Legacy PATA support (PATA_LEGACY)

Thank you for this. I think I will buy a cheap esata box to run some tests...

Can you post the full error : failed to configure port multiplier (...... Use dmesg command, and post output about port multiplier Yes this is the good way.

Thank you for the tip If I remove the vender file and add sn=xxx in grub, Synology Assistant show empty sn Any idea ?

Try with this : http://xpenology.trantor.be/beta/zImage-sil_v4.7z I just coment out the check (noob style ^^). I doubt it solves the problem but give it a try

Download links are only valid 60sec. Refresh the page and click again

I patched the sources to *properly detect* non-synology esata box http://xpenology.trantor.be/beta/zImage-sil_v3.7z @vasiliy_gr : Can you try with this one if it still detect your DX510 @kyleday : Can you try it to see if all your drives are detected.

YES!!! Now it is working properly. So what is already tested? I turned on dx510 with a mix of 5 different hdd and ssd. All of them are now visible in web-gui. Then I builded SHR volume on those 5 hdds plus the sixth one that was used for booting. Next experiment - restart. Nothing suspicious. Volume survived the reboot. System volume on enclosure's part of raid1 is undamaged. But still I do not understand why the original 4.3 code is not working... My ds1511+ died in last November. It had the latest version of DSM. So it should be 3810 I believe. And there were no problems between its onboard sil3132 and dx510... Coool Synology add some check in 4.3 source code. Did your DX510 poweron and/or poweroff when xpenology boot/shutdown ? What about performance ? Next step patch source code to properly detect other esata enclosure.

Ask k3dt, he patch my 3827 synobios

Can you help me with that ?

I will look about this. The best will be that xpenology only use real mac adresses, so no headaches ^^

I recompiled the kernel with libata-pmp from 4.2 build: http://xpenology.trantor.be/beta/zImage-sil_v2.7z Your DX510 *should* works with this. Also found that syno_pmp_ports_num return 1 when a non synology esata device is connected. I think this why you (kyleday) only get one drive on your esata box. I will try to patch sources to enable both (synology and others) esata devices to be properly detected.

Just found this in syno_pmp_ports_num function: /* Block sata 6Gbps host + sata 3Gbps expansion unit case*/ if (syno_pm_is_synology_3xxx(ap) && (hpriv->flags & AHCI_HFLAG_YES_MV9235_FIX)) { ata_port_printk(ap, KERN_ERR, "This expansion unit is unsupported\n"); ret = 0; } I will build the kernel with original libata-pmp source

Boot your xpenology, browse xpenology's share, go in usbshare1, put the new kernel. @vasiliy_gr : I will look about syno_pmp_port With 4.2-3211 you can use the DX510 like "normal" synology ? With 4.3 build what if you connect other esata device than your DX510 on the sil controller ? Did it works ? DSM can detect drives ?

Don't spam the forum it is useless. Please give more informations about your card/controller

Try with this kernel ; http://xpenology.trantor.be/beta/zImage-sil.7z - Removed pata_legacy - Build kernel with official sil.c, sil24.c and enclosure.c files (not the synology's patched one). Unfortunately I don't have any sil based card nor any esata box

Ok, I will remove it in future build. Instead of booting from Ubuntu, can you try Debian Wheezy which has same kernel base (3.2.54+)? So I've tried Debian Wheezy like you recommended, and similar to Ununtu, all drives in esata port multiplier drive show up. But only the first drive shows up in Xpenology. What's wrong? Failing to load the sil3132 driver? Other users reported issues with sil3132 chip: viewtopic.php?f=2&t=2272 viewtopic.php?f=2&t=2269 viewtopic.php?f=14&t=1700&p=10358&hilit=dx510#p10358 Does fdisk command "shows" all your disks ? Can you give us more informations about your setup ? We must investigate deeper this issues^^

Only centaur CPU are supported, I think only your C7 will work.

I hope to have enough time to release 3827 beta7 this week-end

This is what the patch does by including marvell 9230 id to ahci.c When you type : # echo 1b4b 9230 > /sys/bus/pci/drivers/ahci/new_id you manually add marvell 9230 id to the ahci stack so dsm can detect drives, but it's not "reboot proof" ^^

This is what the patch does by including marvell 9230 id to ahci.c When you type : # echo 1b4b 9230 > /sys/bus/pci/drivers/ahci/new_id you manually add marvell 9230 id to the ahci stack so dsm can detect drives, but it's not "reboot proof" ^^

Just found this for your controller: http://ubuntu.5.x6.nabble.com/3-8-y-z-e ... 50287.html http://www.spinics.net/lists/linux-ide/msg46859.html I will patch the kernel with their informations in order to handle Marvell 9230 chip.