Trantor

XPEnology DS3612xs DSM 4.3 build 3810++ (repack v1.0)

Recommended Posts

Hi,

 

this question might have been asked a number of times before, sorry for that.

What is the compatibility of the XPEnology releases with server HW like the HP Proliant DL160 G5, DL360 G5, ... As I'm interested to use an enclosure that can be easily rack mounted.

 

Any known issues or pitfalls? Things to consider when buying refurbished HW?

 

Regards,

 

Pieter

Share this post


Link to post
Share on other sites

Hello,

 

sorry for the double post but I think it was better to put my question in this post :???:

viewtopic.php?f=2&t=6&start=380

 

does someone notice that is impossible to properly reboot or shutdown N40L with xpenology ?

It seem that acpi is not fully supported ... When I launch a reboot or a shutdown of my N40L it say "system is halting/rebooting now ..." but it stay at this step, need to press the power button.

The system is properly halting as I can hear my harddisk spindown but not completely shutdown.

It's not really a problem in fact, but I have a UPS connected and when the power goes off, the UPS send the command to halt the computer and it was not completely halted ...

Is there a way to fix that ? Thanks.

Share this post


Link to post
Share on other sites

Hi,

 

I did the update to 4.3 synology software.

 

But now I'm getting the error on my NAS screen

Synobios: buzzer stop button pressed.

 

Sombody knows a solution for it?

 

I found this solution : viewtopic.php?f=14&t=1700&start=110

 

But how can I change the synobios.ko file?

 

Kind regards,

Share this post


Link to post
Share on other sites

I did the upgrade to 4.3-3810 Update 4 today and i'm facing an issue.

One of my USB HDDs is showing as initalizing. Also, sometimes it's not coming up after a reboot, i have to manually reset the machine.

It's a gen8 HP microserver.

Any ideas?

Thanks!

Share this post


Link to post
Share on other sites
on my new N54L (with patched BIOS/Settings, including e.g. SATA: up to 3GB, AHCI,...) with 4 SATA HDDs i installed DSM 4.2 initially and had Transfer rates at 80-100 MB/sec (over several 100 GB!)

Thereafter I upgraded to DSM 4.3 and now my Transfer rate is down to 40-50GB/sec (I didn´t Change nothing in the BIOS!)

 

Even after a complete reset/new Installation of DSM 4.2, the Transfer rate is still "only" 40-50GB/sec.....during boot process I now spotted the following messages for all SATA Ports: "SATA max UDMA/133" respectively "configured for UDMA/133"

 

Could anyone please support how to arrive back at the earlier Transfer rates?

Thanks in advance

msmn

 

unfortunately I could not get too much help on the above so far.

Hence, can someone please confirm/clarify, whether the above described configuration/setting for my N54LServer during Linux boot-process: "SATA max UDMA/133" respectively "configured for UDMA/133" is correct or (what I´d rather suspect) some Kind of safety Settings due to whatever other Problem I may have?

Thank you in advance

msmn

Edited by Guest

Share this post


Link to post
Share on other sites
The new iSCSI (LIO) currently is not enabled with Trantor's kernel build, but there's still a problem even if its enabled which I'm trying to figure out. To make iSCSI work, you have to change iscsi target type to IET in synoinfo.conf.

 

I tried "IET" (only Regular File, I can't try Block Level) and it works, but only with LUN's advanced features turned off.

 

ema

Share this post


Link to post
Share on other sites

I have two synology dx510 (they left orphan after ds1511+ death). I tried for several weeks to find a suitable e-sata controller for them. Most of them simply do not work with PM of dx510 not only in xpenology but in generic linux as well. For two weeks experimented with highpoint rocketraid 622. It seems to work but suffers resets on heavy disk load. So it is also not suitable for raid usage (and also it is not a problem of xpenology but of any linux). And as the last chance I decided to purchase sil3132 based card. It is very-very old... But it should work anywere. Moreover I disassembled my dead ds1511+ and find out that it has sil3132 chip on main board. So... It should work?......

 

For my big disappointment it is not working in this build with dx510. If I try to start with powered dx510 - it hangs on the early startup (something about 3 secs from start) with crash. If I start with unpowered dx510 everything is ok. But when I power them up - it crashes. Here is dmesg output:

[spoiler=][ 92.682849] ata7: device plugged sstatus 0x123

[ 92.682937] ata7: exception Emask 0x10 SAct 0x0 SErr 0x0 action 0xe frozen

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

[ 92.683050] ata7: hard resetting link

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

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

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

[ 95.837268] PGD 0

[ 95.837348] Oops: 0000 [#1] SMP

[ 95.837461] CPU 0

[ 95.837497] 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 r8101(O) r8168(O) tg3(O) e1000e(O) alx(O) mdio compat(O) [last unloaded: bromolow_synobios]

[ 95.840633]

[ 95.840680] Pid: 1192, comm: scsi_eh_6 Tainted: P O 3.2.40 #15 System manufacturer System Product Name/P8Z77-I DELUXE

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

[ 95.840955] RSP: 0000:ffff880216133ab0 EFLAGS: 00010202

[ 95.841008] RAX: 0000000000000001 RBX: ffff880216278000 RCX: 0000000000000001

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

[ 95.841119] RBP: 0000000000000006 R08: 00000000a08f9044 R09: ffffffff818594c0

[ 95.841175] R10: ffffffff81028163 R11: ffff880216278000 R12: 0000000000000000

[ 95.841231] R13: ffff880216278000 R14: 0000000000000001 R15: ffff880216279c88

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

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

[ 95.841410] CR2: 0000000000000008 CR3: 0000000001805000 CR4: 00000000000406f0

[ 95.841466] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000

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

[ 95.841578] Process scsi_eh_6 (pid: 1192, threadinfo ffff880216132000, task ffff88021ea3e6a0)

[ 95.841647] Stack:

[ 95.841694] ffff880216279f98 ffff880216278000 0000000037261095 ffffffff812b4774

[ 95.841890] ffffffff812b40cc 000000038102d3c9 0000008200000068 ffffffff812b4116

[ 95.842086] 00000001812b40cc 0000000000000007 ffff88021627a1e0 ffff880216279f98

[ 95.842282] Call Trace:

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[ 95.843791] 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 25 76 74 81 48 c7 c6 1f 92 6f

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

[ 95.846072] RSP

[ 95.846121] CR2: 0000000000000008

[ 95.846174] ---[ end trace b6306c69ed23fbfd ]---

 

I tried this on two systems: hp n54l and sandy-bridge based. Everything is the same. Also I tried synoboot-3810-pre-v1.1_v4 - nothing changed. If I connect a single hard drive (not a box with PM) it seems to work correctly.

 

As the last chance I tried "DSM 4.2 build 3211++ (repack v1.2)" - and a miracle - it works! The only problem is the necessity to rebuild system partition after reboot.

 

So for now I had to downgrade version of my xpenology. But it seems to me that it is something wrong with the version in topic. Because original dsm 4.3 works with sil3132 on dx510. I do know - I used it on ds1511+...

Share this post


Link to post
Share on other sites

I have this release up and running on my gigabyte G31M-S2L... It's ICH7. I thought that ICH7 wasn't supousted to work?

Share this post


Link to post
Share on other sites
And as the last chance I decided to purchase sil3132 based card. It is very-very old... But it should work anywere. Moreover I disassembled my dead ds1511+ and find out that it has sil3132 chip on main board. So... It should work?......

 

For my big disappointment it is not working in this build with dx510. If I try to start with powered dx510 - it hangs on the early startup (something about 3 secs from start) with crash. If I start with unpowered dx510 everything is ok. But when I power them up.

 

As the last chance I tried "DSM 4.2 build 3211++ (repack v1.2)" - and a miracle - it works! The only problem is the necessity to rebuild system partition after reboot.

 

So for now I had to downgrade version of my xpenology. But it seems to me that it is something wrong with the version in topic. Because original dsm 4.3 works with sil3132 on dx510. I do know - I used it on ds1511+...

 

Both 4.2 and 4.3 build have CONFIG_SATA_SIL24=y (This option enables support for Silicon Image 3124/3132 Serial ATA).

Can you try to power up the DX510 when 4.2 is booted and post mesages to see what's happend.

Also does your DX510 work with your sil3132 controller on standard linux distro like debian/ubuntu ?

If yes, can you provide logs/dmesg/module ?

Share this post


Link to post
Share on other sites

I have the similar problem with HP EX490 MediaSmart Server ...it has a sil3531 E-SATA

 

It does detect the enclosure, but only finds one of the 4 drives inside it ....

 

Ubuntu is no problem finding all 4 drives

 

.

Share this post


Link to post
Share on other sites
I have the similar problem with HP EX490 MediaSmart Server ...it has a sil3531 E-SATA

 

It does detect the enclosure, but only finds one of the 4 drives inside it ....

 

Ubuntu is no problem finding all 4 drives

 

Can you look what's the module loaded by ubuntu when you power up the device ?

After quick google search, it appear that sil3531 have some Power Management issue : http://patchwork.ozlabs.org/patch/151442/

 

EDIT:

 

I just compare sata_sil24.c between dsm 4.2 and 4.3:

 

<       link->uiStsFlags |= SYNO_STATUS_IS_SIL3132; - (4.3)
>       link->SynoIsSil3132 = 1; - (4.2)

<       link->uiStsFlags |= SYNO_STATUS_IS_SIL3132PM; - (4.3)
>       link->SynoIsSil3132PM = 1; -(4.2)

 

Not sure this is why dsm 4.3 crash when connecting your DX510, but as we can see in 4.2 the code force SynoIsSil3132 to be true.

I can try to compil kernel with sata_sil24.c file modified like in DSM 4.2.

Share this post


Link to post
Share on other sites
Both 4.2 and 4.3 build have CONFIG_SATA_SIL24=y (This option enables support for Silicon Image 3124/3132 Serial ATA).

Can you try to power up the DX510 when 4.2 is booted and post mesages to see what's happend.

Also does your DX510 work with your sil3132 controller on standard linux distro like debian/ubuntu ?

If yes, can you provide logs/dmesg/module ?

Ok. I rebooted xpenology 4.2 and collected results. Here is dmesg (lines related to sil3132, PM and dx510):

[spoiler=dmesg]<...>

[ 3.180729] sata_sil24 0000:02:00.0: version 1.1

[ 3.180746] sata_sil24 0000:02:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16

[ 3.180952] sata_sil24 0000:02:00.0: setting latency timer to 64

[ 3.181421] scsi6 : sata_sil24

[ 3.181855] scsi7 : sata_sil24

[ 3.182148] ata7: SATA max UDMA/100 host m128@0xfe8ffc00 port 0xfe8f8000 irq 16

[ 3.182296] ata8: SATA max UDMA/100 host m128@0xfe8ffc00 port 0xfe8fa000 irq 16

[ 3.182445] Enable Synology sata fast booting

[ 3.283101] ata7: controller in dubious state, performing PORT_RST

[ 3.406097] ata7: hardreset failed (PHY debouncing failed)

[ 3.486112] ata5: SATA link down (SStatus 0 SControl 300)

[ 3.507098] ata8: controller in dubious state, performing PORT_RST

[ 3.630102] ata8: hardreset failed (PHY debouncing failed)

<...>

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

[ 6.788164] ata7.15: Port Multiplier 1.1, 0x1095:0x3726 r23, 5 ports, feat 0x1/0x9

[ 6.791871] ata7: Apply Synology fast PMP boot

[ 8.327204] ata7.00: hard resetting link

[ 8.654296] ata7.00: SATA link up 3.0 Gbps (SStatus 123 SControl 320)

[ 8.654419] ata7.01: hard resetting link

[ 8.981298] ata7.01: SATA link up 3.0 Gbps (SStatus 123 SControl 320)

[ 8.981421] ata7.02: hard resetting link

[ 9.297294] ata7.02: SATA link up 3.0 Gbps (SStatus 123 SControl 320)

[ 9.297418] ata7.03: hard resetting link

[ 9.613297] ata7.03: SATA link up 3.0 Gbps (SStatus 123 SControl 320)

[ 9.613421] ata7.04: hard resetting link

[ 9.929298] ata7.04: SATA link up 3.0 Gbps (SStatus 123 SControl 320)

[ 9.933305] ata7.00: ATA-8: WDC WD20EARS-00MVWB0, 51.0AB51, max UDMA/133

[ 9.933406] ata7.00: 3907029168 sectors, multi 16: LBA48 NCQ (depth 31/32)

[ 9.937291] ata7.00: configured for UDMA/100

[ 9.941418] ata7.01: ATA-8: WDC WD20EARS-00MVWB0, 51.0AB51, max UDMA/133

[ 9.941513] ata7.01: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32)

[ 9.945230] ata7.01: configured for UDMA/100

[ 9.952016] ata7.02: ATA-8: WDC WD20EARX-00PASB0, 51.0AB51, max UDMA/133

[ 9.952111] ata7.02: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32)

[ 9.959025] ata7.02: configured for UDMA/100

[ 9.966745] ata7.03: ATA-8: WDC WD20EARX-00PASB0, 51.0AB51, max UDMA/133

[ 9.966841] ata7.03: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32)

[ 9.974751] ata7.03: configured for UDMA/100

[ 9.981934] ata7.04: ATA-8: WDC WD20EARX-00PASB0, 51.0AB51, max UDMA/133

[ 9.982038] ata7.04: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32)

[ 9.988900] ata7.04: configured for UDMA/100

[ 9.989078] ata7: EH complete

[ 9.989481] scsi 6:0:0:0: Direct-Access ATA WDC WD20EARS-00M 51.0 PQ: 0 ANSI: 5

[ 9.990396] sd 6:0:0:0: [sdga] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)

[ 9.990561] scsi 6:1:0:0: Direct-Access ATA WDC WD20EARS-00M 51.0 PQ: 0 ANSI: 5

[ 9.990748] sd 6:1:0:0: [sdgb] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)

[ 9.990772] sd 6:0:0:0: [sdga] Write Protect is off

[ 9.990775] sd 6:0:0:0: [sdga] Mode Sense: 00 3a 00 00

[ 9.990790] sd 6:0:0:0: [sdga] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA

[ 9.991378] sd 6:1:0:0: [sdgb] Write Protect is off

[ 9.991483] sd 6:1:0:0: [sdgb] Mode Sense: 00 3a 00 00

[ 9.991500] sd 6:1:0:0: [sdgb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA

[ 9.991787] scsi 6:2:0:0: Direct-Access ATA WDC WD20EARX-00P 51.0 PQ: 0 ANSI: 5

[ 9.992429] sd 6:2:0:0: [sdgc] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)

[ 9.992591] sd 6:2:0:0: [sdgc] 4096-byte physical blocks

[ 9.992725] sd 6:2:0:0: [sdgc] Write Protect is off

[ 9.992817] sd 6:2:0:0: [sdgc] Mode Sense: 00 3a 00 00

[ 9.992949] sd 6:2:0:0: [sdgc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA

[ 9.993030] scsi 6:3:0:0: Direct-Access ATA WDC WD20EARX-00P 51.0 PQ: 0 ANSI: 5

[ 9.993271] sd 6:3:0:0: [sdgd] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)

[ 9.993427] sd 6:3:0:0: [sdgd] 4096-byte physical blocks

[ 9.993571] sd 6:3:0:0: [sdgd] Write Protect is off

[ 9.993666] sd 6:3:0:0: [sdgd] Mode Sense: 00 3a 00 00

[ 9.993745] sd 6:3:0:0: [sdgd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA

[ 9.993751] scsi 6:4:0:0: Direct-Access ATA WDC WD20EARX-00P 51.0 PQ: 0 ANSI: 5

[ 9.994431] sd 6:4:0:0: [sdge] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)

[ 9.994581] sd 6:4:0:0: [sdge] 4096-byte physical blocks

[ 9.994708] sd 6:4:0:0: [sdge] Write Protect is off

[ 9.994800] sd 6:4:0:0: [sdge] Mode Sense: 00 3a 00 00

[ 9.994825] sd 6:4:0:0: [sdge] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA

[ 10.016120] sdgc: sdgc1 sdgc2 sdgc3 < sdgc5 >

[ 10.016829] sd 6:2:0:0: [sdgc] Attached SCSI disk

[ 10.020392] sdge: sdge1 sdge2 sdge3 < sdge5 >

[ 10.021116] sd 6:4:0:0: [sdge] Attached SCSI disk

[ 10.021249] sdgb: sdgb1 sdgb2 sdgb3 < sdgb5 >

[ 10.021967] sd 6:1:0:0: [sdgb] Attached SCSI disk

[ 10.028451] sdga: sdga1 sdga2 sdga3 < sdga5 >

[ 10.029129] sd 6:0:0:0: [sdga] Attached SCSI disk

[ 10.032410] sdgd: sdgd1 sdgd2 sdgd3 < sdgd5 >

[ 10.033856] sd 6:3:0:0: [sdgd] Attached SCSI disk

[ 12.127128] ata8: SATA link up 3.0 Gbps (SStatus 123 SControl 0)

[ 13.153215] ata8.15: Port Multiplier 1.1, 0x1095:0x3726 r23, 5 ports, feat 0x1/0x9

[ 13.156749] ata8: Apply Synology fast PMP boot

[ 14.691205] ata8.00: hard resetting link

[ 15.018294] ata8.00: SATA link up 3.0 Gbps (SStatus 123 SControl 320)

[ 15.018417] ata8.01: hard resetting link

[ 15.345296] ata8.01: SATA link up 3.0 Gbps (SStatus 123 SControl 320)

[ 15.345420] ata8.02: hard resetting link

[ 15.661294] ata8.02: SATA link up 3.0 Gbps (SStatus 123 SControl 320)

[ 15.661417] ata8.03: hard resetting link

[ 15.977296] ata8.03: SATA link up 3.0 Gbps (SStatus 123 SControl 320)

[ 15.977420] ata8.04: hard resetting link

[ 16.293290] ata8.04: SATA link up 3.0 Gbps (SStatus 123 SControl 320)

[ 16.297612] ata8.00: ATA-8: WDC WD20EARS-00MVWB0, 51.0AB51, max UDMA/133

[ 16.297708] ata8.00: 3907029168 sectors, multi 16: LBA48 NCQ (depth 31/32)

[ 16.302657] ata8.00: configured for UDMA/100

[ 16.307519] ata8.01: ATA-8: WDC WD20EARS-00MVWB0, 51.0AB51, max UDMA/133

[ 16.307614] ata8.01: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32)

[ 16.312524] ata8.01: configured for UDMA/100

[ 16.316414] ata8.02: ATA-8: WDC WD20EARS-00MVWB0, 51.0AB51, max UDMA/133

[ 16.316509] ata8.02: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32)

[ 16.320433] ata8.02: configured for UDMA/100

[ 16.325336] ata8.03: ATA-8: WDC WD20EARS-00MVWB0, 51.0AB51, max UDMA/133

[ 16.325432] ata8.03: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32)

[ 16.330343] ata8.03: configured for UDMA/100

[ 16.334449] ata8.04: ATA-8: WDC WD20EARS-00MVWB0, 51.0AB51, max UDMA/133

[ 16.334550] ata8.04: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32)

[ 16.339417] ata8.04: configured for UDMA/100

[ 16.339574] ata8: EH complete

[ 16.339885] scsi 7:0:0:0: Direct-Access ATA WDC WD20EARS-00M 51.0 PQ: 0 ANSI: 5

[ 16.340472] sd 7:0:0:0: [sdha] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)

[ 16.340748] sd 7:0:0:0: [sdha] Write Protect is off

[ 16.340841] sd 7:0:0:0: [sdha] Mode Sense: 00 3a 00 00

[ 16.340918] sd 7:0:0:0: [sdha] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA

[ 16.340932] scsi 7:1:0:0: Direct-Access ATA WDC WD20EARS-00M 51.0 PQ: 0 ANSI: 5

[ 16.341610] sd 7:1:0:0: [sdhb] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)

[ 16.341796] sd 7:1:0:0: [sdhb] Write Protect is off

[ 16.341888] sd 7:1:0:0: [sdhb] Mode Sense: 00 3a 00 00

[ 16.341912] sd 7:1:0:0: [sdhb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA

[ 16.342251] scsi 7:2:0:0: Direct-Access ATA WDC WD20EARS-00M 51.0 PQ: 0 ANSI: 5

[ 16.342802] sd 7:2:0:0: [sdhc] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)

[ 16.342896] scsi 7:3:0:0: Direct-Access ATA WDC WD20EARS-00M 51.0 PQ: 0 ANSI: 5

[ 16.343059] sd 7:3:0:0: [sdhd] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)

[ 16.343088] sd 7:3:0:0: [sdhd] Write Protect is off

[ 16.343090] sd 7:3:0:0: [sdhd] Mode Sense: 00 3a 00 00

[ 16.343103] sd 7:3:0:0: [sdhd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA

[ 16.343659] sd 7:2:0:0: [sdhc] Write Protect is off

[ 16.343763] sd 7:2:0:0: [sdhc] Mode Sense: 00 3a 00 00

[ 16.343847] sd 7:2:0:0: [sdhc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA

[ 16.344220] scsi 7:4:0:0: Direct-Access ATA WDC WD20EARS-00M 51.0 PQ: 0 ANSI: 5

[ 16.344748] sd 7:4:0:0: [sdhe] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)

[ 16.345088] sd 7:4:0:0: [sdhe] Write Protect is off

[ 16.345184] sd 7:4:0:0: [sdhe] Mode Sense: 00 3a 00 00

[ 16.345283] sd 7:4:0:0: [sdhe] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA

[ 16.361351] sdhd: sdhd1 sdhd2 sdhd3 < sdhd5 >

[ 16.362124] sd 7:3:0:0: [sdhd] Attached SCSI disk

[ 16.367076] sdha: sdha1 sdha2 sdha3 < sdha5 >

[ 16.367780] sd 7:0:0:0: [sdha] Attached SCSI disk

[ 16.375627] sdhc: sdhc1 sdhc2 sdhc3 < sdhc5 >

[ 16.377075] sd 7:2:0:0: [sdhc] Attached SCSI disk

[ 16.382713] sdhe: sdhe1 sdhe2 sdhe3 < sdhe5 >

[ 16.383709] sd 7:4:0:0: [sdhe] Attached SCSI disk

[ 16.386191] sdhb: sdhb1 sdhb2 sdhb3 < sdhb5 >

[ 16.386846] sd 7:1:0:0: [sdhb] Attached SCSI disk

<...>

[ 16.634046] md: deny sdga1.

[ 16.634147] md: export_rdev(sdga1)

[ 16.646336] md: deny sdga2.

[ 16.646429] md: export_rdev(sdga2)

[ 16.666622] md: invalid raid superblock magic on sdga5

[ 16.666717] md: sdga5 does not have a valid v0.90 superblock, not importing!

[ 16.682904] md: deny sdgb1.

[ 16.682997] md: export_rdev(sdgb1)

[ 16.692497] md: deny sdgb2.

[ 16.692595] md: export_rdev(sdgb2)

[ 16.711508] md: invalid raid superblock magic on sdgb5

[ 16.711603] md: sdgb5 does not have a valid v0.90 superblock, not importing!

[ 16.746438] md: deny sdgc1.

[ 16.746530] md: export_rdev(sdgc1)

[ 16.753173] md: deny sdgc2.

[ 16.753266] md: export_rdev(sdgc2)

[ 16.791769] md: invalid raid superblock magic on sdgc5

[ 16.791864] md: sdgc5 does not have a valid v0.90 superblock, not importing!

[ 16.816922] md: deny sdgd1.

[ 16.817022] md: export_rdev(sdgd1)

[ 16.825187] md: deny sdgd2.

[ 16.825279] md: export_rdev(sdgd2)

[ 16.850165] md: invalid raid superblock magic on sdgd5

[ 16.850260] md: sdgd5 does not have a valid v0.90 superblock, not importing!

[ 16.885394] md: deny sdge1.

[ 16.885487] md: export_rdev(sdge1)

[ 16.890694] md: deny sdge2.

[ 16.890794] md: export_rdev(sdge2)

[ 16.911021] md: invalid raid superblock magic on sdge5

[ 16.911115] md: sdge5 does not have a valid v0.90 superblock, not importing!

[ 16.923810] md: deny sdha1.

[ 16.923903] md: export_rdev(sdha1)

[ 16.930075] md: deny sdha2.

[ 16.930169] md: export_rdev(sdha2)

[ 16.947861] md: invalid raid superblock magic on sdha5

[ 16.947955] md: sdha5 does not have a valid v0.90 superblock, not importing!

[ 16.956423] md: deny sdhb1.

[ 16.956517] md: export_rdev(sdhb1)

[ 16.971226] md: deny sdhb2.

[ 16.971319] md: export_rdev(sdhb2)

[ 17.008393] md: invalid raid superblock magic on sdhb5

[ 17.008487] md: sdhb5 does not have a valid v0.90 superblock, not importing!

[ 17.018787] md: deny sdhc1.

[ 17.018886] md: export_rdev(sdhc1)

[ 17.027451] md: deny sdhc2.

[ 17.027544] md: export_rdev(sdhc2)

[ 17.047850] md: invalid raid superblock magic on sdhc5

[ 17.047944] md: sdhc5 does not have a valid v0.90 superblock, not importing!

[ 17.051050] md: deny sdhd1.

[ 17.051142] md: export_rdev(sdhd1)

[ 17.055989] md: deny sdhd2.

[ 17.056090] md: export_rdev(sdhd2)

[ 17.077187] md: invalid raid superblock magic on sdhd5

[ 17.077282] md: sdhd5 does not have a valid v0.90 superblock, not importing!

[ 17.080715] md: deny sdhe1.

[ 17.080808] md: export_rdev(sdhe1)

[ 17.094557] md: deny sdhe2.

[ 17.094650] md: export_rdev(sdhe2)

[ 17.123892] md: invalid raid superblock magic on sdhe5

[ 17.123987] md: sdhe5 does not have a valid v0.90 superblock, not importing!

[ 17.124098] md: Scanned 45 and added 10 devices.

<...>

[ 22.472303] md: md3 stopped.

[ 22.474897] md: bind

[ 22.475173] md: bind

[ 22.475409] md: bind

[ 22.475641] md: bind

[ 22.475900] md: bind

[ 22.476164] md: bind

[ 22.476402] md: bind

[ 22.476656] md: bind

[ 22.476907] md: bind

[ 22.477192] md: bind

[ 22.478680] md/raid:md3: device sdga5 operational as raid disk 0

[ 22.478817] md/raid:md3: device sdhe5 operational as raid disk 9

[ 22.478911] md/raid:md3: device sdhd5 operational as raid disk 8

[ 22.479014] md/raid:md3: device sdhc5 operational as raid disk 7

[ 22.479110] md/raid:md3: device sdhb5 operational as raid disk 6

[ 22.479205] md/raid:md3: device sdha5 operational as raid disk 5

[ 22.479301] md/raid:md3: device sdge5 operational as raid disk 4

[ 22.479397] md/raid:md3: device sdgd5 operational as raid disk 3

[ 22.479492] md/raid:md3: device sdgc5 operational as raid disk 2

[ 22.479590] md/raid:md3: device sdgb5 operational as raid disk 1

[ 22.480357] md/raid:md3: allocated 10594kB

[ 22.481171] md/raid:md3: raid level 5 active with 10 out of 10 devices, algorithm 2

[ 22.481359] RAID conf printout:

[ 22.481361] --- level:5 rd:10 wd:10

[ 22.481363] disk 0, o:1, dev:sdga5

[ 22.481365] disk 1, o:1, dev:sdgb5

[ 22.481367] disk 2, o:1, dev:sdgc5

[ 22.481369] disk 3, o:1, dev:sdgd5

[ 22.481370] disk 4, o:1, dev:sdge5

[ 22.481372] disk 5, o:1, dev:sdha5

[ 22.481374] disk 6, o:1, dev:sdhb5

[ 22.481376] disk 7, o:1, dev:sdhc5

[ 22.481378] disk 8, o:1, dev:sdhd5

[ 22.481380] disk 9, o:1, dev:sdhe5

[ 22.481427] md3: detected capacity change from 0 to 17959953235968

[ 22.482025] md3: unknown partition table

<...>

[ 74.370705] ata4.00: configured for UDMA/133

[ 74.370816] ata4: EH complete

[ 74.370920] ata6.00: configured for UDMA/133

[ 74.371030] ata6: EH complete

[ 74.371414] ata7.00: configured for UDMA/100

[ 74.371571] ata7: EH complete

[ 74.375241] ata1.00: configured for UDMA/133

[ 74.375351] ata1: EH complete

[ 74.375562] ata2.00: configured for UDMA/133

[ 74.375678] ata2: EH complete

[ 74.375879] ata3.00: configured for UDMA/133

[ 74.375972] ata3: EH complete

[ 74.380122] ata7.01: configured for UDMA/100

[ 74.380279] ata7: EH complete

[ 74.394855] ata7.02: configured for UDMA/100

[ 74.395024] ata7: EH complete

[ 74.411167] ata7.03: configured for UDMA/100

[ 74.411325] ata7: EH complete

[ 74.421400] ata8.00: configured for UDMA/100

[ 74.421556] ata8: EH complete

[ 74.426018] ata7.04: configured for UDMA/100

[ 74.426207] ata7: EH complete

[ 74.431795] ata8.01: configured for UDMA/100

[ 74.431952] ata8: EH complete

[ 74.440935] ata8.02: configured for UDMA/100

[ 74.441123] ata8: EH complete

[ 74.450209] ata8.03: configured for UDMA/100

[ 74.450366] ata8: EH complete

[ 74.460632] ata8.04: configured for UDMA/100

[ 74.460789] ata8: EH complete

 

Then I rebooted with opensuse 13.1. It has no problems with this configuration (it even can operate xpenology arrays). dmesg output is synonymously the same:[spoiler=dmesg on suse][ 5.560865] sata_sil24 0000:02:00.0: version 1.1

[ 5.573135] scsi6 : sata_sil24

[ 5.574217] scsi7 : sata_sil24

[ 5.574277] ata7: SATA max UDMA/100 host m128@0xfe8ffc00 port 0xfe8f8000 irq 16

[ 5.574281] ata8: SATA max UDMA/100 host m128@0xfe8ffc00 port 0xfe8fa000 irq 16

<...>

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

[ 7.775402] ata7.15: Port Multiplier 1.1, 0x1095:0x3726 r23, 6 ports, feat 0x1/0x9

[ 7.782954] ata7.00: hard resetting link

[ 8.103255] ata7.00: SATA link up 3.0 Gbps (SStatus 123 SControl 320)

[ 8.103288] ata7.01: hard resetting link

[ 8.423173] ata7.01: SATA link up 3.0 Gbps (SStatus 123 SControl 300)

[ 8.423206] ata7.02: hard resetting link

[ 8.746977] ata7.02: SATA link up 3.0 Gbps (SStatus 123 SControl 300)

[ 8.747017] ata7.03: hard resetting link

[ 9.066831] ata7.03: SATA link up 3.0 Gbps (SStatus 123 SControl 300)

[ 9.066865] ata7.04: hard resetting link

[ 9.088345] tg3 0000:03:00.0: irq 43 for MSI/MSI-X

[ 9.863080] IPv6: ADDRCONF(NETDEV_UP): enp3s0: link is not ready

[ 9.864963] NET: Registered protocol family 17

[ 9.970467] ata7.04: SATA link up 3.0 Gbps (SStatus 123 SControl 300)

[ 9.970507] ata7.05: hard resetting link

[ 10.290346] ata7.05: SATA link up 1.5 Gbps (SStatus 113 SControl 320)

[ 10.306866] ata7.00: ATA-8: WDC WD20EARS-00MVWB0, 51.0AB51, max UDMA/133

[ 10.306879] ata7.00: 3907029168 sectors, multi 16: LBA48 NCQ (depth 31/32)

[ 10.310394] ata7.00: configured for UDMA/100

[ 10.331276] ata7.01: ATA-8: WDC WD20EARS-00MVWB0, 51.0AB51, max UDMA/133

[ 10.331287] ata7.01: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32)

[ 10.334959] ata7.01: configured for UDMA/100

[ 10.350509] ata7.02: ATA-8: WDC WD20EARX-00PASB0, 51.0AB51, max UDMA/133

[ 10.350520] ata7.02: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32)

[ 10.356877] ata7.02: configured for UDMA/100

[ 10.370955] ata7.03: ATA-8: WDC WD20EARX-00PASB0, 51.0AB51, max UDMA/133

[ 10.370965] ata7.03: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32)

[ 10.378543] ata7.03: configured for UDMA/100

[ 10.391776] ata7.04: ATA-8: WDC WD20EARX-00PASB0, 51.0AB51, max UDMA/133

[ 10.391787] ata7.04: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32)

[ 10.398635] ata7.04: configured for UDMA/100

[ 10.398714] ata7: EH complete

[ 10.399009] scsi 6:0:0:0: Direct-Access ATA WDC WD20EARS-00M 51.0 PQ: 0 ANSI: 5

[ 10.399455] sd 6:0:0:0: [sdh] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)

[ 10.399546] sd 6:0:0:0: [sdh] Write Protect is off

[ 10.399553] sd 6:0:0:0: [sdh] Mode Sense: 00 3a 00 00

[ 10.399593] sd 6:0:0:0: [sdh] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA

[ 10.400083] sd 6:0:0:0: Attached scsi generic sg7 type 0

[ 10.400343] scsi 6:1:0:0: Direct-Access ATA WDC WD20EARS-00M 51.0 PQ: 0 ANSI: 5

[ 10.400746] sd 6:1:0:0: [sdi] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)

[ 10.400808] sd 6:1:0:0: [sdi] Write Protect is off

[ 10.400813] sd 6:1:0:0: [sdi] Mode Sense: 00 3a 00 00

[ 10.400838] sd 6:1:0:0: [sdi] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA

[ 10.401554] sd 6:1:0:0: Attached scsi generic sg8 type 0

[ 10.405729] scsi 6:2:0:0: Direct-Access ATA WDC WD20EARX-00P 51.0 PQ: 0 ANSI: 5

[ 10.406152] sd 6:2:0:0: Attached scsi generic sg9 type 0

 

Both logs above are from hp n54l. But previously I tried sil3132+dx510 on absolutely standard sandy bridge microITX device with no diffrences. And previously I tried hpt rr622+dx510 with 4.3/3810+/r1.0 on both of them and saw all my 10 hdds as in PM-boxes. But rr622 is a buggy piece of hardware no matter of version of DSM or linux.

 

Also I want to add some interesting things on 4.2 behaviour with sil3132+PM. My 10 hdds are not enumerated in order. They are "Disk 7" and "Disk 8" in synology gui (for five hdd's on both this numbers as they are situated per two dx510). As for linux view they are sdgx and sdhx, where 'x' is from a to e.

 

When I shutdown xpenology 4.2 it turns off both dx510 itself. So it works as the original ds1511+ on this. On the other hand ds1511+ turnes on dx510 on startup. But xpenology 4.2 misses this feature.

Share this post


Link to post
Share on other sites

Gday Trantor

 

I notice with the new beta v1.4, that CPU temps seem to be stuck at 40c

Normal Repack v1.0 temps change and read (I hope) properly :wink:

 

.

Share this post


Link to post
Share on other sites

Just made a clean install of v1.0 on my test computer (ASUS P5KPL-AM SE, Q8200, 4GB, 160GB 2.5", Intel PRO1000 PT Server) to test iSCSI.

After setup, I can create lun/target without error in DSM (few errors in the console about failed to mount boot device /dev/synoboot2/, I will try to fake it in the future).

I can connect it with my Win7 Pro computer, reboot XPEnology, windows autoreconnect iscsi drive and vis-versa, read/write are about 90-100MB/s :smile:

 

iSCSI works fine in lio mode after dsm setup without modifying anything. If someone can confirm on other hardware.

 

BUT iSCSI support is broken in betas (too many things added, like virtualization, xen, kvm...), and I can't successfully build working iscsi modules :sad:

I decide to restart from scratch with v1.0 config, and add things step by step to not break the iSCSI support.

 

 

I notice with the new beta v1.4, that CPU temps seem to be stuck at 40c

Normal Repack v1.0 temps change and read (I hope) properly :wink:

 

With my ASUS P5KPL-AM SE temp is alway (with v1.0 and beta v4) stuck at 40c...

Share this post


Link to post
Share on other sites
Just made a clean install of v1.0 on my test computer (ASUS P5KPL-AM SE, Q8200, 4GB, 160GB 2.5", Intel PRO1000 PT Server) to test iSCSI.

After setup, I can create lun/target without error in DSM (few errors in the console about failed to mount boot device /dev/synoboot2/, I will try to fake it in the future).

I can connect it with my Win7 Pro computer, reboot XPEnology, windows autoreconnect iscsi drive and vis-versa, read/write are about 90-100MB/s :smile:

 

iSCSI works fine in lio mode after dsm setup without modifying anything. If someone can confirm on other hardware.

 

BUT iSCSI support is broken in betas (too many things added, like virtualization, xen, kvm...), and I can't successfully build working iscsi modules :sad:

I decide to restart from scratch with v1.0 config, and add things step by step to not break the iSCSI support.

 

 

I notice with the new beta v1.4, that CPU temps seem to be stuck at 40c

Normal Repack v1.0 temps change and read (I hope) properly :wink:

 

With my ASUS P5KPL-AM SE temp is alway (with v1.0 and beta v4) stuck at 40c...

 

Hi Trantor.

 

The issue I especially found with ISCSI, was when I mapped RAW LUN, this made the GUI hang, and I could not configure any ISCSI, and could not connect to the target. I have tried this on two different platforms. Can you confirm that RAW LUN mapping is working now?

 

And again thank you very much for the great work you are doing!!!

Share this post


Link to post
Share on other sites
Just made a clean install of v1.0 on my test computer (ASUS P5KPL-AM SE, Q8200, 4GB, 160GB 2.5", Intel PRO1000 PT Server) to test iSCSI.

After setup, I can create lun/target without error in DSM (few errors in the console about failed to mount boot device /dev/synoboot2/, I will try to fake it in the future).

I can connect it with my Win7 Pro computer, reboot XPEnology, windows autoreconnect iscsi drive and vis-versa, read/write are about 90-100MB/s :smile:

 

iSCSI works fine in lio mode after dsm setup without modifying anything. If someone can confirm on other hardware.

 

BUT iSCSI support is broken in betas (too many things added, like virtualization, xen, kvm...), and I can't successfully build working iscsi modules :sad:

I decide to restart from scratch with v1.0 config, and add things step by step to not break the iSCSI support.

 

 

I notice with the new beta v1.4, that CPU temps seem to be stuck at 40c

Normal Repack v1.0 temps change and read (I hope) properly :wink:

 

With my ASUS P5KPL-AM SE temp is alway (with v1.0 and beta v4) stuck at 40c...

 

confirm working with a clean config.

Share this post


Link to post
Share on other sites

The issue I especially found with ISCSI, was when I mapped RAW LUN, this made the GUI hang, and I could not configure any ISCSI, and could not connect to the target. I have tried this on two different platforms. Can you confirm that RAW LUN mapping is working now?

 

And again thank you very much for the great work you are doing!!!

 

Indeed, I can create RAW LUN (block level) and map it to a target. But when I try to map it to my Win7, I got segfault about LIO_iblock.

v1.0 kernel is missing some important options like TCM/IBLOCK, TCM/FILEIO...

 

I'm working on a way to get this all working, but have some issues to understand what synology did with the target_core_mod module (it seems it include iblock, fileio.... But in kernel config I can only build all of them as separate modules)

 

EDIT:

Found an iSCSI module made by synology:

filename:       iscsi_extent_pool.ko
license:        Proprietary
description:    LIO Extent-Mapping Module
author:         Yi-Lin Zhuo 

 

it may complicate things...

 

EDIT2:

The new iSCSI (LIO) currently is not enabled with Trantor's kernel build, but there's still a problem even if its enabled which I'm trying to figure out. To make iSCSI work, you have to change iscsi target type to IET in synoinfo.conf.

 

I tried "IET" (only Regular File, I can't try Block Level) and it works, but only with LUN's advanced features turned off.

 

Just tried in iet mode with Block Level, same result as LIO ; kernel segfault (fs/bio-integrity, Process istiod2)

Share this post


Link to post
Share on other sites

 

Indeed, I can create RAW LUN (block level) and map it to a target. But when I try to map it to my Win7, I got segfault about LIO_iblock.

v1.0 kernel is missing some important options like TCM/IBLOCK, TCM/FILEIO...

 

I'm working on a way to get this all working, but have some issues to understand what synology did with the target_core_mod module (it seems it include iblock, fileio.... But in kernel config I can only build all of them as separate modules)

 

EDIT:

Found an iSCSI module made by synology:

filename:       iscsi_extent_pool.ko
license:        Proprietary
description:    LIO Extent-Mapping Module
author:         Yi-Lin Zhuo 

 

it may complicate things...

 

EDIT2:

The new iSCSI (LIO) currently is not enabled with Trantor's kernel build, but there's still a problem even if its enabled which I'm trying to figure out. To make iSCSI work, you have to change iscsi target type to IET in synoinfo.conf.

 

I tried "IET" (only Regular File, I can't try Block Level) and it works, but only with LUN's advanced features turned off.

 

Just tried in iet mode with Block Level, same result as LIO ; kernel segfault (fs/bio-integrity, Process istiod2)

 

Very nice, good job :smile: I'm very much looking forward to getting RAW LUN's working so I can try it with a few SSD's.

In my opinion this is the greatest NAS build out there, as it let's use much better hardware the the crap Synology ships with. I have a DS1813+ the preformence is very bad.

 

My XPEnology build:

U-NAS NSC-800 Case

ASROCK C2750D4I Motherboadr/CPU

16 GB Memory

8 x 2TB Samsung Spinpoint F4EG in raid 6

 

It leaves the DS1813+ in the dust!!!

 

Trantor you work is very much appreciated.

Share this post


Link to post
Share on other sites

I tried to disassemble target_core_mod, it shows some customizations that Synology did to the module. Another thing, it is an older version of LIO, compared to what is included in linux-3.x source (3.4 vs 4.x). So compiling a new one will not work either, unless we have the source code. You can verify that by checking /sys/kernel/config/target/version.

 

cat /sys/kernel/config/target/version
Target Engine Core ConfigFS Infrastructure v3.4.0 on Linux/x86_64 on 3.2.40

 

I think Synology is violating GPL license for not including it :evil::-| .

Share this post


Link to post
Share on other sites

I think Synology is violating GPL license for not including it :evil::-| .

You know that they don't have to publish it and do it voluntary. They should share (make available) it by request though. You can contact them and ask for source code if you feel that you need it.

Share this post


Link to post
Share on other sites
Another thing, it is an older version of LIO, compared to what is included in linux-3.x source (3.4 vs 4.x).

 

How can we update available LIO sources to v4.x ? Or downgrade them to 3.4 ?

 

They should share (make available) it by request though. You can contact them and ask for source code if you feel that you need it.

 

Yes requesting source code to recompile target_core_mod is a good idea but I don't think Syno will post them.

Share this post


Link to post
Share on other sites
I have the similar problem with HP EX490 MediaSmart Server ...it has a sil3531 E-SATA

 

It does detect the enclosure, but only finds one of the 4 drives inside it ....

 

Ubuntu is no problem finding all 4 drives

 

.

 

Hey I have the same server. any improvements over 4.2?. I havent made the jump yet since I have data on the 4.2. My understanding is I gotta start from scratch and if so I have to move the data off the ex490 before I can go with 4.3. I dont use eSata ever so that I dont care about as of yet.

Share this post


Link to post
Share on other sites

Got IET block level working by recompiling the module. I don't own a Synology hardware and have no valid reason to request the LIO source code. Any volunteers?

Share this post


Link to post
Share on other sites

having issues on my N36L. NFS is not working for me, I can browse to top level folder but thats it. Thats only possble after running the following:

insmod /lib/modules/auth_rpcgss.ko

/usr/syno/etc/rc.d/S83nfsd.sh restart

 

 

any suggestions? I miss my media :sad: . Also unable to set up router (WAG160n) even though it has all the port stting pre-configured from previous build.

 

Joshua

Edited by Guest

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now