Drivers requests for DSM 5.2


Recommended Posts

Have You read this thread?

viewtopic.php?f=2&t=2028

 

Hi, Trantor!

 

I builded recently a new hardware configuration for my xpenology - based on lsi 9211-8i with 8 hdd-s on it. So I had to try beta 6 hba version. Everything is fine except of one minor issue.

 

Here is something strange in dmesg output:

XPEnologyU> dmesg | grep -i pata
[    1.447614] scsi0 : pata_legacy
[    1.447724] ata1: PATA max PIO4 cmd 0x1f0 ctl 0x3f6 irq 14
[    1.599757] scsi1 : pata_legacy
[    1.599858] ata2: PATA max PIO4 cmd 0x170 ctl 0x376 irq 15

You see here two positions reserved for pata drives... What shall it mean??? I have asus P8Z77-I Deluxe mobo without any pata at all. It has sata controller, but I turned it off completely in bios.

 

As the result I have my 8 hdd-s as:

XPEnologyU> fdisk -l |grep Disk |sort
Disk /dev/sdc: 2000.3 GB, 2000398934016 bytes
Disk /dev/sdd: 2000.3 GB, 2000398934016 bytes
Disk /dev/sde: 2000.3 GB, 2000398934016 bytes
Disk /dev/sdf: 2000.3 GB, 2000398934016 bytes
Disk /dev/sdg: 2000.3 GB, 2000398934016 bytes
Disk /dev/sdh: 2000.3 GB, 2000398934016 bytes
Disk /dev/sdi: 2000.3 GB, 2000398934016 bytes
Disk /dev/sdj: 2000.3 GB, 2000398934016 bytes
Disk /dev/sdu: 8004 MB, 8004304896 bytes

And also in syno-web-interface they are enumerated as disks 3-10 (without disks 1 and 2).

 

Are there any solution to get rid of those two invisible pata drives?

Link to post
Share on other sites
Have You read this thread?

viewtopic.php?f=2&t=2028

Yes, I have. My problem is not discussed there. And the problems discussed there are not present in my configuration ('cause of less number of hdd's and more recent synoboot used).

Furthermore my question is quite concrete - why pata_legacy module is automatically loaded in my configuration with no pata at all?.. And moreover - what for do we need this module in hba oriented version of synoboot?..

Link to post
Share on other sites
Have You read this thread?

viewtopic.php?f=2&t=2028

Yes, I have. My problem is not discussed there. And the problems discussed there are not present in my configuration ('cause of less number of hdd's and more recent synoboot used).

Furthermore my question is quite concrete - why pata_legacy module is automatically loaded in my configuration with no pata at all?.. And moreover - what for do we need this module in hba oriented version of synoboot?..

 

Is your bios set to use SATA compatability mode for the SATA controller?

 

.

Link to post
Share on other sites
Have You read this thread?

viewtopic.php?f=2&t=2028

Yes, I have. My problem is not discussed there. And the problems discussed there are not present in my configuration ('cause of less number of hdd's and more recent synoboot used).

Furthermore my question is quite concrete - why pata_legacy module is automatically loaded in my configuration with no pata at all?.. And moreover - what for do we need this module in hba oriented version of synoboot?..

 

Is your bios set to use SATA compatability mode for the SATA controller?

As I have already mentioned two posts ago, I set sata controller to be completely off in bios. I mean "SATA Mode Selection" = "Disabled".

 

Anyway you give me an idea for a new test. I reenabled SATA (in AHCI mode) and here is a result:

XPEnologyU> dmesg |grep -i scsi
[    0.432944] SCSI subsystem initialized
[    1.413825] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
[    1.441825] Loading iSCSI transport class v2.0-870.
[    1.456193] scsi0 : ahci
[    1.456310] scsi1 : ahci
[    1.456414] scsi2 : ahci
[    1.456514] scsi3 : ahci
[    1.456616] scsi4 : ahci
[    1.456718] scsi5 : ahci
[    2.066316] scsi6 : pata_legacy
[    2.370390] scsi7 : pata_legacy
[    4.263541] scsi8 : Fusion MPT SAS Host

So there are 6 ahci ports - it is absolutely correct (4 internal sata and 2 e-sata). And also - surprise... Those two "pata legacy" ports from the dark side of the moon.

So my question remaines the same.

Link to post
Share on other sites

And some additional info on pata_legacy:

https://ata.wiki.kernel.org/index.php/Pata_legacy

ISA and other devices offering an ST416 style ATA interface.

There is specific controller support for:

HT6560A/B VLB

Opti 82C465MV VLB

Opti 82C611A VLB

Promise 20230C

Promise 20630

QDI 6500/6580/6580DP

Winbond W83759A

So I believe there is no any reason to include it even as a module. For example in openSuse 13.1 it is not included in binary kernel build by default.

 

I have no idea why it is found on my mobo... But it may be a problem with some class of hardware - for example 1155 mobos from asus, or with Z77 chipset, or with onboard wifi, or with something else. So it's better to remove this module in future versions or to build it as a module.

Link to post
Share on other sites
And some additional info on pata_legacy:

https://ata.wiki.kernel.org/index.php/Pata_legacy

ISA and other devices offering an ST416 style ATA interface.

There is specific controller support for:

HT6560A/B VLB

Opti 82C465MV VLB

Opti 82C611A VLB

Promise 20230C

Promise 20630

QDI 6500/6580/6580DP

Winbond W83759A

So I believe there is no any reason to include it even as a module. For example in openSuse 13.1 it is not included in binary kernel build by default.

 

I have no idea why it is found on my mobo... But it may be a problem with some class of hardware - for example 1155 mobos from asus, or with Z77 chipset, or with onboard wifi, or with something else. So it's better to remove this module in future versions or to build it as a module.

 

Since pata_legacy is a generic driver, it maybe have been able to detect your raid controller. All distributions no longer include this kernel by default.

Link to post
Share on other sites

A week ago, I was running DSM4.3-3810 v1 but then I got that stupid 'lolz' virus (similar to the PWNED virus).

I've successfully removed it and have updated my DS to DSM4.3-3810 v4.

 

The security fix is only available in 4.3-3827, or not?

Is there already a trantor 4.3-3827 version for my XPEnology NAS?

Link to post
Share on other sites

Hi Everyone - I think my previous post got lost among the noise. I'm running an HP N40L microserver with a Silicon Image sil3132 eSATA PCI card. When I boot to ubuntu, all of my drives on my eSata port multiplier bay show up and are available for use, but when I boot Xpenology (Trantor) v 4.1, 4.2, or 4.3 (even the betas) only 1 out of 4 of my drives in my eSATA port multiplier box show up. Again - Ubuntu shows all drives fine, Xpenology only shows first of four drives, others aren't shown at all.

 

Any help or suggestions?

 

Thanks

Link to post
Share on other sites
Hi Everyone - I think my previous post got lost among the noise. I'm running an HP N40L microserver with a Silicon Image sil3132 eSATA PCI card. When I boot to ubuntu, all of my drives on my eSata port multiplier bay show up and are available for use, but when I boot Xpenology (Trantor) v 4.1, 4.2, or 4.3 (even the betas) only 1 out of 4 of my drives in my eSATA port multiplier box show up. Again - Ubuntu shows all drives fine, Xpenology only shows first of four drives, others aren't shown at all.

 

Any help or suggestions?

 

Thanks

 

Instead of booting from Ubuntu, can you try Debian Wheezy which has same kernel base (3.2.54+)?

Link to post
Share on other sites
Hi Everyone - I think my previous post got lost among the noise. I'm running an HP N40L microserver with a Silicon Image sil3132 eSATA PCI card. When I boot to ubuntu, all of my drives on my eSata port multiplier bay show up and are available for use, but when I boot Xpenology (Trantor) v 4.1, 4.2, or 4.3 (even the betas) only 1 out of 4 of my drives in my eSATA port multiplier box show up. Again - Ubuntu shows all drives fine, Xpenology only shows first of four drives, others aren't shown at all.

 

Any help or suggestions?

 

Thanks

 

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?

Link to post
Share on other sites

Since pata_legacy is a generic driver, it maybe have been able to detect your raid controller. All distributions no longer include this kernel by default.

 

Ok, I will remove it in future build.

 

Hi Everyone - I think my previous post got lost among the noise. I'm running an HP N40L microserver with a Silicon Image sil3132 eSATA PCI card. When I boot to ubuntu, all of my drives on my eSata port multiplier bay show up and are available for use, but when I boot Xpenology (Trantor) v 4.1, 4.2, or 4.3 (even the betas) only 1 out of 4 of my drives in my eSATA port multiplier box show up. Again - Ubuntu shows all drives fine, Xpenology only shows first of four drives, others aren't shown at all.

 

Any help or suggestions?

 

Thanks

 

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^^

Link to post
Share on other sites
Hi Everyone - I think my previous post got lost among the noise. I'm running an HP N40L microserver with a Silicon Image sil3132 eSATA PCI card. When I boot to ubuntu, all of my drives on my eSata port multiplier bay show up and are available for use, but when I boot Xpenology (Trantor) v 4.1, 4.2, or 4.3 (even the betas) only 1 out of 4 of my drives in my eSATA port multiplier box show up. Again - Ubuntu shows all drives fine, Xpenology only shows first of four drives, others aren't shown at all.

 

Any help or suggestions?

 

Thanks

 

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^^

 

Hi Trantor -

 

Thanks for your help with this. I am running an HP Proliant Microserver N40L with 8GB ram and have a Monoprice (rebranded?) SATAII PCIe eSATA SIL3132 card installed. It is doubtful that an fdisk command would show the missing disks, because the eSata port multiplier enclosure doesn't light up the missing drives (no activity lights for missing drives). When I boot to Ubunto/Debian Wheezy, the missing drives' activity lights are all lit up and the drives are viewable. In Xpenology, only the drive in the first bay has an activity light lit up and only that drive is viewed by Xpenology. I will run an fdisk command later today at home, but it is very unlikely that the missing disks will be displayed as the enclosure itself doesn't show the disks are being recognized.

 

This is the eSATA Sil3132 card: http://www.monoprice.com/Product?c_id=104&cp_id=10407&cs_id=1040702&p_id=3581&seq=1&format=2&utm_expid=58369800-11.R-enhtUGRrSdHz5vzpVS2g.0&utm_referrer=http%3A%2F%2Fwww.monoprice.com%2FSearch%2FIndex%3Fkeyword%3D3132

Link to post
Share on other sites
Hi, Trantor!

Thank for such great work on DSM! :smile:

Can you add drivers for IBM_ServeRAID-7k_Ultra320_SCSI_controller (IBM eSeries x346)?

Drivers: https://drive.google.com/file/d/0Bzs_u2 ... sp=sharing

I try Beta 6 (both standard and hba), but it don`t see any of my disks.

 

Don't spam the forum it is useless.

Please give more informations about your card/controller :wink:

Link to post
Share on other sites
Don't spam the forum it is useless.

Please give more informations about your card/controller :wink:

Sorry for spaming...

What can I say about this controller? I see it only in IBM X346 server. It's ultra-320 scsi raid controller with bbu. There https://docs.google.com/file/d/0Bzs_u27 ... edit?pli=1 you can find drivers and readme for RHEL and SLES from original IBM disk . If I have to give you some special info - write me please how I can get it. XPEnology is really needed on this machine.

Link to post
Share on other sites
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 :sad:

 

Ok I would like to try your kernel above, but I am not experienced enough with Linux to know how to patch in a new kernel. Could you provide me either a .img/.pat file with that kernel in it, or link me to instructions with how to patch in your kernel from above to your already built DSM package? Sorry I'm just too new to know what to do.

 

Thanks

Link to post
Share on other sites
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 :sad:

Hi, Trantor!

 

Thank you for this quick fix. As for my problem with disk enumeration on asus mobo with lsi 9211 - the problem is gone with this kernel. Now my hdd's are unumerated as disks 1 to 8.

 

As for sil24 - I'll try this variant later. Now I have three different xpenology configurations without external enclosures. So I need to build a fourth one with sil3132 and dx510. It will take some time to find several unused hdd-s for the test.

Link to post
Share on other sites

@vasiiy_gr, I'm not sure why your mobo has problems or what it does with the pata_legacy module, but I requested Trantor to include that driver.

 

I have been using (and needing) that driver because it is the ONLY one that works with an Intel 945GZ chipset (not exactly new, but not ancient like the ones listed on wikipedia) that reside in the Intel ss4200 NAS. This system is designed to boot off an on-board DOM in the PATA port. It's a custom NAS that the bios is crippled and doesn't really cater to other boot media options.

 

@gnoboot, Ubuntu 13.10 does include the pata_legacy by default as well as Wheezy, but I do have to load it when my sata controller is configured in "enhanced" mode which is needed to enable the pata port, sata ports, and e-sata ports.

 

So Trantor, do you have any advice or instructions that I can include the pata_legacy module for my boot image?

 

Thanks again for all your time and efforts.

Link to post
Share on other sites
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 :sad:

Hi, Trantor!

 

Thank you for this quick fix. As for my problem with disk enumeration on asus mobo with lsi 9211 - the problem is gone with this kernel. Now my hdd's are unumerated as disks 1 to 8.

 

As for sil24 - I'll try this variant later. Now I have three different xpenology configurations without external enclosures. So I need to build a fourth one with sil3132 and dx510. It will take some time to find several unused hdd-s for the test.

Ok - quick test. Used hardware: 1155 gigabyte mobo, sil3132 and dx510.

 

1. dx510 is off. Boot from beta6_hba plus new kernel. Install beta5.pat. Everything ok.

 

2. At this stage I turn on dx510 with two hdd-s in it. The result:

[spoiler=][ 195.041597] ata7: exception Emask 0x10 SAct 0x0 SErr 0x0 action 0xe frozen

[ 195.041671] ata7: irq_stat 0x00b40090, PHY RDY changed

[ 195.041726] ata7: hard resetting link

[ 197.169939] ata7: SATA link up 3.0 Gbps (SStatus 123 SControl 0)

[ 198.194047] BUG: unable to handle kernel NULL pointer dereference at 0000000000000008

[ 198.194176] IP: [] syno_pmp_ports_num+0x45/0x75

[ 198.194263] PGD 0

[ 198.194338] Oops: 0000 [#1] SMP

[ 198.194445] CPU 0

[ 198.194478] Modules linked in: cifs udf isofs loop usbhid hid usblp usb_storage uhci_hcd etxhci_hcd xhci_hcd ohci_hcd ehci_hcd bromolow_synobios(P) synoacl_ext4(P) synoacl_vfs(P) btrfs zlib_deflate libcrc32c hfsplus md4 hmac ixgbe be2net igb(O) i2c_algo_bit dca fuse vfat fat cryptd ecryptfs sha512_generic sha256_generic sha1_generic ecb aes_x86_64 authenc chainiv des_generic crc32c eseqiv krng ansi_cprng cts rng aes_generic md5 cbc cryptomgr pcompress aead crypto_hash crypto_blkcipher crypto_wq crypto_algapi cpufreq_conservative cpufreq_powersave cpufreq_performance cpufreq_ondemand acpi_cpufreq mperf processor thermal_sys cpufreq_stats freq_table dm_snapshot crc_itu_t crc_ccitt quota_v2 quota_tree usbcore psnap p8022 llc usb_common ipv6 sg mvsas hpsa arcmsr aic94xx aic79xx aic7xxx 3w_xxxx 3w_sas 3w_9xxx atp870u ipr stex hptiop aacraid megaraid_sas(O) mpt2sas(O) sk98lin(O) r8169 r8168(O) bnx2(O) tg3(O) e1000e(O) alx(O) mdio compat(O) [last unloaded: bromolow_synobios]

[ 198.197973]

[ 198.198018] Pid: 1108, comm: scsi_eh_6 Tainted: P O 3.2.40 #62 Gigabyte Technology Co., Ltd. H61N-USB3/H61N-USB3

[ 198.198179] RIP: 0010:[] [] syno_pmp_ports_num+0x45/0x75

[ 198.198278] RSP: 0000:ffff880212e3bab0 EFLAGS: 00010202

[ 198.198329] RAX: 0000000000000001 RBX: ffff880212dfc000 RCX: 0000000000000001

[ 198.198382] RDX: 0000000000000001 RSI: 0000000000003726 RDI: 0000000000001095

[ 198.198436] RBP: 0000000000000006 R08: 000000007de47b4c R09: ffffffff8165b780

[ 198.198490] R10: ffffffff81028163 R11: ffff880212dfc000 R12: 0000000000000000

[ 198.198543] R13: ffff880212dfc000 R14: 0000000000000001 R15: ffff880212dfdc88

[ 198.198597] FS: 0000000000000000(0000) GS:ffff88021fa00000(0000) knlGS:0000000000000000

[ 198.198664] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b

[ 198.198715] CR2: 0000000000000008 CR3: 0000000001609000 CR4: 00000000000406f0

[ 198.198769] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000

[ 198.198823] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400

[ 198.198877] Process scsi_eh_6 (pid: 1108, threadinfo ffff880212e3a000, task ffff880212dfacb0)

[ 198.198943] Stack:

[ 198.198988] ffff880212dfdf98 ffff880212dfc000 0000000037261095 ffffffff812354e0

[ 198.199173] ffffffff81234e38 000000038102d3c9 0000008200000068 ffffffff81234e82

[ 198.199357] 0000000181234e38 0000000000000007 ffff880212dfe1e0 ffff880212dfdf98

[ 198.199541] Call Trace:

[ 198.199588] [] ? sata_pmp_configure+0x2a/0x1ca

[ 198.199641] [] ? ata_sff_data_xfer_noirq+0xf/0xf

[ 198.199695] [] ? SIMG3xxx_gpio_decode+0x4a/0x4a

[ 198.199748] [] ? sata_pmp_attach+0x2e6/0x6ae

[ 198.199801] [] ? ata_eh_recover+0x7b2/0x1248

[ 198.199854] [] ? sata_print_link_status+0xa6/0xa6

[ 198.199908] [] ? sil24_freeze+0x25/0x25

[ 198.199960] [] ? sil24_qc_fill_rtf+0x1e/0x1e

[ 198.200013] [] ? sata_link_resume+0x135/0x135

[ 198.200066] [] ? sata_pmp_error_handler+0xbc/0x8cd

[ 198.200121] [] ? find_worker_executing_work+0xe/0x1c

[ 198.200175] [] ? wait_on_work+0xab/0xc5

[ 198.200228] [] ? need_resched+0x1e/0x28

[ 198.200280] [] ? ata_deadline+0xb/0x10

[ 198.200331] [] ? ata_wait_register+0x3a/0x79

[ 198.200384] [] ? sil24_error_handler+0x29/0x34

[ 198.200437] [] ? ata_scsi_port_error_handler+0x306/0x9b0

[ 198.200493] [] ? scsi_block_when_processing_errors+0xa8/0xa8

[ 198.200559] [] ? ata_scsi_error+0x87/0xaf

[ 198.200611] [] ? scsi_error_handler+0xcf/0x3db

[ 198.202033] [] ? __wake_up_common+0x46/0x75

[ 198.202086] [] ? scsi_block_when_processing_errors+0xa8/0xa8

[ 198.202153] [] ? kthread+0x6a/0x72

[ 198.202205] [] ? kernel_thread_helper+0x4/0x10

[ 198.202258] [] ? kthread_bind+0x5c/0x5c

[ 198.202309] [] ? gs_change+0xb/0xb

[ 198.202359] Code: 01 00 00 00 74 4e 48 89 df 8b ab e8 21 00 00 e8 1c ff ff ff 84 c0 75 13 48 89 df e8 60 ff ff ff 84 c0 75 2b 89 ea 83 e2 0f eb 29 <41> 83 7c 24 08 00 79 1c 48 c7 c2 36 ec 51 81 48 c7 c6 32 b4 4e

[ 198.204386] RIP [] syno_pmp_ports_num+0x45/0x75

[ 198.204470] RSP

[ 198.204517] CR2: 0000000000000008

[ 198.204567] ---[ end trace a875502cce91b1dd ]---

 

Controller is unresponsive now.

 

3. Reboot with dx510 turned off. Then I turn it on with one hdd. The result is the same as the previous one.

 

4. Reboot with dx510 turned on with one hdd. Result - lockup at second 8 of boot process with similar crash trace.

 

5. Reboot with dx510 turned on without hdd-s. The same as previous.

 

So - nothing changed. sil3132 does not working with dx510 on all current xpenology synoboot versions for 4.3 and 5.0. But it is working with 4.2-3211-r1.2 and opensuse 13.1.

 

I can check this configuration with any linux version on your advise. I mean - with the most close kernel version.

Link to post
Share on other sites

 

Ok I would like to try your kernel above, but I am not experienced enough with Linux to know how to patch in a new kernel. Could you provide me either a .img/.pat file with that kernel in it, or link me to instructions with how to patch in your kernel from above to your already built DSM package? Sorry I'm just too new to know what to do.

 

Thanks

 

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 ?

Link to post
Share on other sites
@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 ?

3211 works nearly like my previous ds1511+ - yes in general but with absence of some details.

 

It do understand that there are 5 hdd-s in one enclosure (so all of them named as "Disk 7" and other 5 hdd's from the second dx510 named "Disk 8"). But it do not know the dx510 as a device in control panel. I do not remember exactly where it was there situated on ds1511+, but there was a configuration screen for dx510 with my two devices mentioned and some settings on its cooling policy.

 

Also 3211 turns off dx510 in case of shutdown as an original syno dsm. But it do not turn it on during startup.

 

Both differences mostly look like conditional compilation in kernel or/and dsm. So I am not surprised that ds3612xs based software does not support dx510 from top to bottom. For full support dsm for ds15xx, ds18xx or ds7xx is needed - I think so.

 

As for 4.3 and non-pmp devices on sil3132 - retried this experiment right now. I connected hdd in esata box. No problems - no crash, device is visible in gui.

Link to post
Share on other sites

Hello everybody,

 

I'm new to this project, but i would like to know if it is possible to add the driver for Highpoint Rocketraid 2680/2680SGL/2684 into the next repack.

The drivers can be found here: http://www.highpoint-tech.com/USA_new/r ... wnload.htm

 

I tried the synoboot-3810-pre-v1.1_v6_hba but this doesn't work for me.

 

Or is it possible to install the driver on the usb boot disk, so it will load on boot.

If so could anybody tell me how?

 

Thanks in advance

Link to post
Share on other sites

 

Ok I would like to try your kernel above, but I am not experienced enough with Linux to know how to patch in a new kernel. Could you provide me either a .img/.pat file with that kernel in it, or link me to instructions with how to patch in your kernel from above to your already built DSM package? Sorry I'm just too new to know what to do.

 

Thanks

 

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 ?

 

Trantor-

 

I have tried your kernel you posted above for the SIl3132 but the results are the same. Only the first drive is enumerated in DSM and Fdisk. The other drives in the port multiplier do not even spin up or show their activity lights. DSM cannot view them. However, both Ubuntu and Debian can see all drives in the port multiplier box

Link to post
Share on other sites

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

Link to post
Share on other sites
Guest
This topic is now closed to further replies.