shackwove Posted July 23, 2013 Share #51 Posted July 23, 2013 I'm running DS3612xs DSM 4.1 build 2668++ (more hardware) on a Pentium-D with 1gb of DDR2 and it's working great, no performance issues whatsoever. However the OS becomes unresponsive from time to time, the PC doesn't shutdown but i'm unable to perform any actions such as using the web client, pinging the PC or detecting it via synology assistant. The only solution i've found when this happens is to hard shut down the PC with the power button which i really want to avoid. So yeah, there it is, not sure if it's a network error (cutting the communication between the nas and router) or a software issue. I don't even know where to start to troubleshoot the issue. Admin edit: Moved to viewtopic.php?f=2&t=937 Quote Link to comment Share on other sites More sharing options...
Trantor Posted July 24, 2013 Author Share #52 Posted July 24, 2013 Just little update (I'm very busy at work) for the next update. Two "major" features are in testing stage ^^ - Add command like lspci, modinfo... If you want some please tell me (apt-* / dpkg not planned for now, maybe in future release with complete chroot of latest debian). - Wifi drivers (I'm not a wifi expert, for now I successfully detect/load driver for atheros and realtek card but got error when I "up" the interface: wlan0: link is not ready If someone want beta build to help debugging wireless Quote Link to comment Share on other sites More sharing options...
Akhlan Posted July 24, 2013 Share #53 Posted July 24, 2013 Félicitations pour ton taf Trantor, j'ai enfin pu installer XPEnology ^^ Reste plus qu'à mettre tout ça en place... Quote Link to comment Share on other sites More sharing options...
Kanedo Posted July 31, 2013 Share #54 Posted July 31, 2013 I have a setup with a total of 12 drives. 8 drives on the LSI 9211-8i and 4 drives on motherboard. With only the 8 drives on LSI connected, the initial setup doesn't even see any drives. With only the 4 mobo SATA drives connected, I have no problem installing v1.3a and running just fine. However, when I have all 12 drives connected. It would boot half way and just shutdown. I think this is similar to a problem another member posted. Any chance LSI 9211-8i will be supported soon? Thanks for everything so far. Quote Link to comment Share on other sites More sharing options...
Trantor Posted July 31, 2013 Author Share #55 Posted July 31, 2013 I have a setup with a total of 12 drives. 8 drives on the LSI 9211-8i and 4 drives on motherboard. With only the 8 drives on LSI connected, the initial setup doesn't even see any drives. With only the 4 mobo SATA drives connected, I have no problem installing v1.3a and running just fine. However, when I have all 12 drives connected. It would boot half way and just shutdown. I think this is similar to a problem another member posted. Any chance LSI 9211-8i will be supported soon? Thanks for everything so far. LSI drivers are already included (built in the kernel, I think old drivers). I will build latest LSI drivers (like I did for intel network card) as modules in next build. Can you boot your system with livecd like ubuntu and see if all disks are detected (post dmesg, message and/or modinfo) ? Quote Link to comment Share on other sites More sharing options...
Kanedo Posted July 31, 2013 Share #56 Posted July 31, 2013 LSI drivers are already included (built in the kernel, I think old drivers). I will build latest LSI drivers (like I did for intel network card) as modules in next build. Can you boot your system with livecd like ubuntu and see if all disks are detected (post dmesg, message and/or modinfo) ? Sure. Which version of Ubuntu LiveCD? Quote Link to comment Share on other sites More sharing options...
colombodk Posted July 31, 2013 Share #57 Posted July 31, 2013 This version, XPEnology DS3612xs DSM 4.1 build 2668++ (repack v1.3a), is confirmed working correctly with the following motherboard: Itox G5C100-N-G mini-itx dual on-board Marvell 88E8053 (Yukon) using an Intel C2D T7200 CPU, booting from USB and using the ICH7M on-board hard disk controller. I will also test with the RocketRaid 1740 /1742 PCI hard disk controller (based on Marvell 88SX6042). Quote Link to comment Share on other sites More sharing options...
Kanedo Posted August 1, 2013 Share #58 Posted August 1, 2013 LSI drivers are already included (built in the kernel, I think old drivers). I will build latest LSI drivers (like I did for intel network card) as modules in next build. Can you boot your system with livecd like ubuntu and see if all disks are detected (post dmesg, message and/or modinfo) ? Using Ubuntu Desktop 13.04 x64 Live CD, the LSI card is detected and all drives are showing. Quote Link to comment Share on other sites More sharing options...
totalnas Posted August 1, 2013 Share #59 Posted August 1, 2013 Just little update (I'm very busy at work) for the next update. Two "major" features are in testing stage ^^ Please Trantor, add also support for LVM mirror. See: viewtopic.php?f=2&t=915#p4291 You only need to add this three modules: dm-mirror.ko, dm-region-hash.ko and dm-log.ko Quote Link to comment Share on other sites More sharing options...
Trantor Posted August 1, 2013 Author Share #60 Posted August 1, 2013 LSI drivers are already included (built in the kernel, I think old drivers). I will build latest LSI drivers (like I did for intel network card) as modules in next build. Can you boot your system with livecd like ubuntu and see if all disks are detected (post dmesg, message and/or modinfo) ? Using Ubuntu Desktop 13.04 x64 Live CD, the LSI card is detected and all drives are showing. [attachment=0]all drives showing.png[/attachment] dmesg [ 4.741139] mpt2sas version 14.100.00.00 loaded [ 4.744295] ahci 0000:00:1f.2: version 3.0 [ 4.744353] ahci 0000:00:1f.2: irq 49 for MSI/MSI-X [ 4.744711] scsi0 : Fusion MPT SAS Host [ 4.753556] mpt2sas0: 64 BIT PCI BUS DMA ADDRESSING SUPPORTED, total mem (8088124 kB) [ 4.753627] mpt2sas 0000:01:00.0: irq 50 for MSI/MSI-X [ 4.753649] mpt2sas0-msix0: PCI-MSI-X enabled: IRQ 50 [ 4.753651] mpt2sas0: iomem(0x00000000bfe40000), mapped(0xffffc90000c70000), size(16384) [ 4.753653] mpt2sas0: ioport(0x000000000000d000), size(256) [ 4.759325] ahci 0000:00:1f.2: AHCI 0001.0300 32 slots 6 ports 6 Gbps 0x3f impl SATA mode [ 4.759330] ahci 0000:00:1f.2: flags: 64bit ncq sntf pm led clo pio slum part ems apst [ 4.759335] ahci 0000:00:1f.2: setting latency timer to 64 [ 4.799610] scsi1 : ahci [ 4.799664] scsi2 : ahci [ 4.799728] scsi3 : ahci [ 4.799777] scsi4 : ahci [ 4.799814] scsi5 : ahci [ 4.799857] scsi6 : ahci [ 4.799884] ata1: SATA max UDMA/133 abar m2048@0xfbd05000 port 0xfbd05100 irq 49 [ 4.799887] ata2: SATA max UDMA/133 abar m2048@0xfbd05000 port 0xfbd05180 irq 49 [ 4.799890] ata3: SATA max UDMA/133 abar m2048@0xfbd05000 port 0xfbd05200 irq 49 [ 4.799892] ata4: SATA max UDMA/133 abar m2048@0xfbd05000 port 0xfbd05280 irq 49 [ 4.799895] ata5: SATA max UDMA/133 abar m2048@0xfbd05000 port 0xfbd05300 irq 49 [ 4.799898] ata6: SATA max UDMA/133 abar m2048@0xfbd05000 port 0xfbd05380 irq 49 [ 4.800419] [drm] Memory usable by graphics device = 2048M [ 4.800424] i915 0000:00:02.0: setting latency timer to 64 [ 4.830898] e1000e 0000:03:00.0 eth0: (PCI Express:2.5GT/s:Width x1) cc:52:af:ea:7d:f0 [ 4.830901] e1000e 0000:03:00.0 eth0: Intel(R) PRO/1000 Network Connection [ 4.830986] e1000e 0000:03:00.0 eth0: MAC: 3, PHY: 8, PBA No: FFFFFF-0FF [ 4.831006] e1000e 0000:04:00.0: Disabling ASPM L0s L1 [ 4.831019] i915 0000:00:02.0: irq 51 for MSI/MSI-X [ 4.831039] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). [ 4.831040] [drm] Driver supports precise vblank timestamp query. [ 4.831074] vgaarb: device changed decodes: PCI:0000:00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem [ 4.831173] e1000e 0000:04:00.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode [ 4.831280] e1000e 0000:04:00.0: irq 52 for MSI/MSI-X [ 4.831284] e1000e 0000:04:00.0: irq 53 for MSI/MSI-X [ 4.831288] e1000e 0000:04:00.0: irq 54 for MSI/MSI-X [ 4.938741] e1000e 0000:04:00.0 eth1: (PCI Express:2.5GT/s:Width x1) cc:52:af:ea:7d:f1 [ 4.938745] e1000e 0000:04:00.0 eth1: Intel(R) PRO/1000 Network Connection [ 4.938830] e1000e 0000:04:00.0 eth1: MAC: 3, PHY: 8, PBA No: FFFFFF-0FF [ 4.938842] e1000e 0000:05:00.0: Disabling ASPM L0s L1 [ 4.938999] e1000e 0000:05:00.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode [ 4.939107] e1000e 0000:05:00.0: irq 55 for MSI/MSI-X [ 4.939112] e1000e 0000:05:00.0: irq 56 for MSI/MSI-X [ 4.939116] e1000e 0000:05:00.0: irq 57 for MSI/MSI-X [ 4.958950] usb 1-1: new high-speed USB device number 2 using ehci-pci [ 4.998863] mpt2sas0: sending message unit reset !! [ 5.006848] mpt2sas0: message unit reset: SUCCESS [ 5.046495] e1000e 0000:05:00.0 eth2: (PCI Express:2.5GT/s:Width x1) cc:52:af:ea:7d:f2 [ 5.046498] e1000e 0000:05:00.0 eth2: Intel(R) PRO/1000 Network Connection [ 5.046582] e1000e 0000:05:00.0 eth2: MAC: 3, PHY: 8, PBA No: FFFFFF-0FF [ 5.046589] e1000e 0000:06:00.0: Disabling ASPM L0s L1 [ 5.046729] e1000e 0000:06:00.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode [ 5.046855] e1000e 0000:06:00.0: irq 58 for MSI/MSI-X [ 5.046860] e1000e 0000:06:00.0: irq 59 for MSI/MSI-X [ 5.046864] e1000e 0000:06:00.0: irq 60 for MSI/MSI-X [ 5.091120] usb 1-1: New USB device found, idVendor=8087, idProduct=0024 [ 5.091125] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 5.091416] hub 1-1:1.0: USB hub found [ 5.091452] hub 1-1:1.0: 6 ports detected [ 5.118646] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 5.118681] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 5.122617] ata6: SATA link down (SStatus 0 SControl 300) [ 5.122646] ata5: SATA link down (SStatus 0 SControl 300) [ 5.123611] ata3.00: ATA-8: WDC WD20EARS-00MVWB0, 51.0AB51, max UDMA/133 [ 5.123619] ata3.00: 3907029168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA [ 5.123648] ata4.00: ATA-8: WDC WD20EARS-00MVWB0, 51.0AB51, max UDMA/133 [ 5.123651] ata4.00: 3907029168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA [ 5.126638] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 5.128599] ata3.00: configured for UDMA/133 [ 5.128632] ata4.00: configured for UDMA/133 [ 5.130271] ata1.00: ATA-8: WDC WD20EARX-00PASB0, 51.0AB51, max UDMA/133 [ 5.130276] ata1.00: 3907029168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA [ 5.133751] ata1.00: configured for UDMA/133 [ 5.133964] scsi 1:0:0:0: Direct-Access ATA WDC WD20EARX-00P 51.0 PQ: 0 ANSI: 5 [ 5.134100] sd 1:0:0:0: [sda] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB) [ 5.134102] sd 1:0:0:0: [sda] 4096-byte physical blocks [ 5.134131] sd 1:0:0:0: Attached scsi generic sg0 type 0 [ 5.134194] sd 1:0:0:0: [sda] Write Protect is off [ 5.134197] sd 1:0:0:0: [sda] Mode Sense: 00 3a 00 00 [ 5.134230] sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 5.138613] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 5.143074] ata2.00: ATA-8: WDC WD20EARS-00MVWB0, 51.0AB51, max UDMA/133 [ 5.143079] ata2.00: 3907029168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA [ 5.147050] ata2.00: configured for UDMA/133 [ 5.147237] scsi 2:0:0:0: Direct-Access ATA WDC WD20EARS-00M 51.0 PQ: 0 ANSI: 5 [ 5.147349] sd 2:0:0:0: Attached scsi generic sg1 type 0 [ 5.147398] sd 2:0:0:0: [sdb] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB) [ 5.147431] sd 2:0:0:0: [sdb] Write Protect is off [ 5.147433] sd 2:0:0:0: [sdb] Mode Sense: 00 3a 00 00 [ 5.147437] scsi 3:0:0:0: Direct-Access ATA WDC WD20EARS-00M 51.0 PQ: 0 ANSI: 5 [ 5.147448] sd 2:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 5.147522] sd 3:0:0:0: Attached scsi generic sg2 type 0 [ 5.147600] scsi 4:0:0:0: Direct-Access ATA WDC WD20EARS-00M 51.0 PQ: 0 ANSI: 5 [ 5.147680] sd 4:0:0:0: Attached scsi generic sg3 type 0 [ 5.147734] sd 4:0:0:0: [sdd] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB) [ 5.147772] sd 3:0:0:0: [sdc] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB) [ 5.147780] sd 4:0:0:0: [sdd] Write Protect is off [ 5.147782] sd 4:0:0:0: [sdd] Mode Sense: 00 3a 00 00 [ 5.147812] sd 4:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 5.147846] sd 3:0:0:0: [sdc] Write Protect is off [ 5.147848] sd 3:0:0:0: [sdc] Mode Sense: 00 3a 00 00 [ 5.147861] sd 3:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 5.152107] sda: sda1 sda2 sda3 [ 5.152328] sd 1:0:0:0: [sda] Attached SCSI disk [ 5.154586] e1000e 0000:06:00.0 eth3: (PCI Express:2.5GT/s:Width x1) cc:52:af:ea:7d:f3 [ 5.154589] e1000e 0000:06:00.0 eth3: Intel(R) PRO/1000 Network Connection [ 5.154674] e1000e 0000:06:00.0 eth3: MAC: 3, PHY: 8, PBA No: FFFFFF-0FF [ 5.160714] mpt2sas0: Allocated physical memory: size(7418 kB) [ 5.160718] mpt2sas0: Current Controller Queue Depth(3307), Max Controller Queue Depth(3432) [ 5.160719] mpt2sas0: Scatter Gather Elements per IO(128) [ 5.163274] sdb: sdb1 sdb2 sdb3 [ 5.163556] sd 2:0:0:0: [sdb] Attached SCSI disk [ 5.167781] sdd: sdd1 sdd2 sdd3 [ 5.167965] sd 4:0:0:0: [sdd] Attached SCSI disk [ 5.173215] sdc: sdc1 sdc2 sdc3 [ 5.173507] sd 3:0:0:0: [sdc] Attached SCSI disk [ 5.195562] fbcon: inteldrmfb (fb0) is primary device [ 5.202461] usb 2-1: new high-speed USB device number 2 using ehci-pci [ 5.334501] usb 2-1: New USB device found, idVendor=8087, idProduct=0024 [ 5.334503] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 5.334795] hub 2-1:1.0: USB hub found [ 5.334894] hub 2-1:1.0: 8 ports detected [ 5.382571] mpt2sas0: LSISAS2008: FWVersion(15.00.00.00), ChipRevision(0x03), BiosVersion(07.29.00.00) [ 5.382575] mpt2sas0: Protocol=(Initiator,Target), Capabilities=(TLR,EEDP,Snapshot Buffer,Diag Trace Buffer,Task Set Full,NCQ) [ 5.382693] mpt2sas0: sending port enable !! [ 5.385798] mpt2sas0: host_add: handle(0x0001), sas_addr(0x500605b0054c2de0), phys(8) [ 5.398096] mpt2sas0: port enable: SUCCESS [ 5.405868] scsi 0:0:0:0: Direct-Access ATA WDC WD20EARS-00M AB51 PQ: 0 ANSI: 6 [ 5.405873] scsi 0:0:0:0: SATA: handle(0x000c), sas_addr(0x4433221103000000), phy(3), device_name(0x50014ee6ab2ae67a) [ 5.405875] scsi 0:0:0:0: SATA: enclosure_logical_id(0x500605b0054c2de0), slot(0) [ 5.405957] scsi 0:0:0:0: atapi(n), ncq(y), asyn_notify(n), smart(y), fua(y), sw_preserve(y) [ 5.405960] scsi 0:0:0:0: qdepth(32), tagged(1), simple(0), ordered(0), scsi_level(7), cmd_que(1) [ 5.406234] usb 1-1.1: new high-speed USB device number 3 using ehci-pci [ 5.413463] scsi 0:0:1:0: Direct-Access ATA WDC WD20EARS-00M AB51 PQ: 0 ANSI: 6 [ 5.413467] scsi 0:0:1:0: SATA: handle(0x0009), sas_addr(0x4433221100000000), phy(0), device_name(0x50014ee2afb8054b) [ 5.413468] scsi 0:0:1:0: SATA: enclosure_logical_id(0x500605b0054c2de0), slot(3) [ 5.413601] scsi 0:0:1:0: atapi(n), ncq(y), asyn_notify(n), smart(y), fua(y), sw_preserve(y) [ 5.413604] scsi 0:0:1:0: qdepth(32), tagged(1), simple(0), ordered(0), scsi_level(7), cmd_que(1) [ 5.420496] scsi 0:0:2:0: Direct-Access ATA WDC WD20EARS-00M AB51 PQ: 0 ANSI: 6 [ 5.420500] scsi 0:0:2:0: SATA: handle(0x000a), sas_addr(0x4433221101000000), phy(1), device_name(0x50014ee2056f08ca) [ 5.420501] scsi 0:0:2:0: SATA: enclosure_logical_id(0x500605b0054c2de0), slot(2) [ 5.420635] scsi 0:0:2:0: atapi(n), ncq(y), asyn_notify(n), smart(y), fua(y), sw_preserve(y) [ 5.420638] scsi 0:0:2:0: qdepth(32), tagged(1), simple(0), ordered(0), scsi_level(7), cmd_que(1) [ 5.421543] Console: switching to colour frame buffer device 210x65 [ 5.424991] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device [ 5.424992] i915 0000:00:02.0: registered panic notifier [ 5.425007] i915: No ACPI video bus found [ 5.425031] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0 [ 5.428575] scsi 0:0:3:0: Direct-Access ATA WDC WD20EARS-00M AB51 PQ: 0 ANSI: 6 [ 5.428586] scsi 0:0:3:0: SATA: handle(0x000b), sas_addr(0x4433221102000000), phy(2), device_name(0x50014ee057d83700) [ 5.428589] scsi 0:0:3:0: SATA: enclosure_logical_id(0x500605b0054c2de0), slot(1) [ 5.428678] scsi 0:0:3:0: atapi(n), ncq(y), asyn_notify(n), smart(y), fua(y), sw_preserve(y) [ 5.428683] scsi 0:0:3:0: qdepth(32), tagged(1), simple(0), ordered(0), scsi_level(7), cmd_que(1) [ 5.435570] scsi 0:0:4:0: Direct-Access ATA WDC WD20EARS-00M AB51 PQ: 0 ANSI: 6 [ 5.435578] scsi 0:0:4:0: SATA: handle(0x000d), sas_addr(0x4433221104000000), phy(4), device_name(0x50014ee25ac3b0b4) [ 5.435581] scsi 0:0:4:0: SATA: enclosure_logical_id(0x500605b0054c2de0), slot(7) [ 5.435674] scsi 0:0:4:0: atapi(n), ncq(y), asyn_notify(n), smart(y), fua(y), sw_preserve(y) [ 5.435678] scsi 0:0:4:0: qdepth(32), tagged(1), simple(0), ordered(0), scsi_level(7), cmd_que(1) [ 5.443732] scsi 0:0:5:0: Direct-Access ATA WDC WD20EARS-00M AB51 PQ: 0 ANSI: 6 [ 5.443738] scsi 0:0:5:0: SATA: handle(0x000e), sas_addr(0x4433221105000000), phy(5), device_name(0x50014ee057d83553) [ 5.443741] scsi 0:0:5:0: SATA: enclosure_logical_id(0x500605b0054c2de0), slot(6) [ 5.443825] scsi 0:0:5:0: atapi(n), ncq(y), asyn_notify(n), smart(y), fua(y), sw_preserve(y) [ 5.443829] scsi 0:0:5:0: qdepth(32), tagged(1), simple(0), ordered(0), scsi_level(7), cmd_que(1) [ 5.451962] scsi 0:0:6:0: Direct-Access ATA WDC WD20EARS-00M AB51 PQ: 0 ANSI: 6 [ 5.451973] scsi 0:0:6:0: SATA: handle(0x000f), sas_addr(0x4433221106000000), phy(6), device_name(0x50014ee2055057a8) [ 5.451976] scsi 0:0:6:0: SATA: enclosure_logical_id(0x500605b0054c2de0), slot(5) [ 5.452081] scsi 0:0:6:0: atapi(n), ncq(y), asyn_notify(n), smart(y), fua(y), sw_preserve(y) [ 5.452085] scsi 0:0:6:0: qdepth(32), tagged(1), simple(0), ordered(0), scsi_level(7), cmd_que(1) [ 5.460384] scsi 0:0:7:0: Direct-Access ATA WDC WD20EARS-00M AB51 PQ: 0 ANSI: 6 [ 5.460392] scsi 0:0:7:0: SATA: handle(0x0010), sas_addr(0x4433221107000000), phy(7), device_name(0x50014ee600aa4694) [ 5.460395] scsi 0:0:7:0: SATA: enclosure_logical_id(0x500605b0054c2de0), slot(4) [ 5.460517] scsi 0:0:7:0: atapi(n), ncq(y), asyn_notify(n), smart(y), fua(y), sw_preserve(y) [ 5.460523] scsi 0:0:7:0: qdepth(32), tagged(1), simple(0), ordered(0), scsi_level(7), cmd_que(1) [ 5.460806] sd 0:0:0:0: Attached scsi generic sg4 type 0 [ 5.460935] sd 0:0:1:0: Attached scsi generic sg5 type 0 [ 5.461103] sd 0:0:2:0: Attached scsi generic sg6 type 0 [ 5.461223] sd 0:0:3:0: Attached scsi generic sg7 type 0 [ 5.461336] sd 0:0:4:0: Attached scsi generic sg8 type 0 [ 5.461440] sd 0:0:5:0: Attached scsi generic sg9 type 0 [ 5.461563] sd 0:0:6:0: Attached scsi generic sg10 type 0 [ 5.461664] sd 0:0:7:0: Attached scsi generic sg11 type 0 [ 5.464482] sd 0:0:2:0: [sdg] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB) [ 5.464528] sd 0:0:1:0: [sdf] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB) [ 5.464617] sd 0:0:0:0: [sde] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB) [ 5.464676] sd 0:0:4:0: [sdi] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB) [ 5.464988] sd 0:0:3:0: [sdh] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB) [ 5.465376] sd 0:0:5:0: [sdj] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB) [ 5.465415] sd 0:0:6:0: [sdk] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB) [ 5.465629] sd 0:0:7:0: [sdl] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB) [ 5.488696] sd 0:0:4:0: [sdi] Write Protect is off [ 5.488702] sd 0:0:4:0: [sdi] Mode Sense: 7f 00 10 08 [ 5.489349] sd 0:0:2:0: [sdg] Write Protect is off [ 5.489352] sd 0:0:2:0: [sdg] Mode Sense: 7f 00 10 08 [ 5.489957] sd 0:0:0:0: [sde] Write Protect is off [ 5.489961] sd 0:0:0:0: [sde] Mode Sense: 7f 00 10 08 [ 5.490213] sd 0:0:1:0: [sdf] Write Protect is off [ 5.490217] sd 0:0:1:0: [sdf] Mode Sense: 7f 00 10 08 [ 5.490495] sd 0:0:3:0: [sdh] Write Protect is off [ 5.490498] sd 0:0:3:0: [sdh] Mode Sense: 7f 00 10 08 [ 5.490991] sd 0:0:6:0: [sdk] Write Protect is off [ 5.490994] sd 0:0:6:0: [sdk] Mode Sense: 7f 00 10 08 [ 5.491059] sd 0:0:5:0: [sdj] Write Protect is off [ 5.491062] sd 0:0:5:0: [sdj] Mode Sense: 7f 00 10 08 [ 5.491739] sd 0:0:7:0: [sdl] Write Protect is off [ 5.491742] sd 0:0:7:0: [sdl] Mode Sense: 7f 00 10 08 [ 5.495491] sd 0:0:4:0: [sdi] Write cache: enabled, read cache: enabled, supports DPO and FUA [ 5.496207] sd 0:0:2:0: [sdg] Write cache: enabled, read cache: enabled, supports DPO and FUA [ 5.497376] sd 0:0:0:0: [sde] Write cache: enabled, read cache: enabled, supports DPO and FUA [ 5.497545] sd 0:0:1:0: [sdf] Write cache: enabled, read cache: enabled, supports DPO and FUA [ 5.498837] sd 0:0:3:0: [sdh] Write cache: enabled, read cache: enabled, supports DPO and FUA [ 5.499173] sd 0:0:6:0: [sdk] Write cache: enabled, read cache: enabled, supports DPO and FUA [ 5.499432] sd 0:0:5:0: [sdj] Write cache: enabled, read cache: enabled, supports DPO and FUA [ 5.500138] sd 0:0:7:0: [sdl] Write cache: enabled, read cache: enabled, supports DPO and FUA [ 5.506698] usb 1-1.1: New USB device found, idVendor=05ac, idProduct=1006 [ 5.506702] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 5.506704] usb 1-1.1: Product: Keyboard Hub [ 5.506707] usb 1-1.1: Manufacturer: Apple, Inc. [ 5.506709] usb 1-1.1: SerialNumber: 000000000000 [ 5.506980] hub 1-1.1:1.0: USB hub found [ 5.507044] hub 1-1.1:1.0: 3 ports detected [ 5.530780] sdi: sdi1 sdi2 sdi3 < sdi5 > [ 5.531324] sdg: [ 5.534834] sde: [ 5.535095] sdf: [ 5.537429] sdh: [ 5.537530] sdk: [ 5.537943] sdj: [ 5.538405] sdl: [ 5.566234] sd 0:0:2:0: [sdg] Attached SCSI disk [ 5.566538] sd 0:0:4:0: [sdi] Attached SCSI disk [ 5.571241] sd 0:0:0:0: [sde] Attached SCSI disk [ 5.571561] sd 0:0:1:0: [sdf] Attached SCSI disk [ 5.575067] sd 0:0:3:0: [sdh] Attached SCSI disk [ 5.576302] sd 0:0:6:0: [sdk] Attached SCSI disk [ 5.576679] sd 0:0:5:0: [sdj] Attached SCSI disk [ 5.577120] sd 0:0:7:0: [sdl] Attached SCSI disk [ 5.577756] tsc: Refined TSC clocksource calibration: 2594.107 MHz [ 5.577760] Switching to clocksource tsc [ 5.605874] usb 2-1.4: new high-speed USB device number 3 using ehci-pci [ 5.698683] usb 2-1.4: New USB device found, idVendor=125f, idProduct=312b [ 5.698689] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 5.698692] usb 2-1.4: Product: ADATA USB Flash Drive [ 5.698694] usb 2-1.4: Manufacturer: ADATA [ 5.698697] usb 2-1.4: SerialNumber: 233071105004006B lsmod Module Size Used by dm_crypt 22820 0 snd_hda_codec_hdmi 36913 1 snd_hda_intel 39619 4 snd_hda_codec 136453 2 snd_hda_codec_hdmi,snd_hda_intel joydev 17377 0 coretemp 13355 0 snd_hwdep 13602 1 snd_hda_codec kvm_intel 132891 0 snd_pcm 97451 3 snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel kvm 443165 1 kvm_intel psmouse 95870 0 mac_hid 13205 0 snd_page_alloc 18710 2 snd_pcm,snd_hda_intel snd_seq_midi 13324 0 snd_seq_midi_event 14899 1 snd_seq_midi snd_rawmidi 30180 1 snd_seq_midi snd_seq 61554 2 snd_seq_midi_event,snd_seq_midi ghash_clmulni_intel 13259 0 cryptd 20373 1 ghash_clmulni_intel gpio_ich 13476 0 snd_seq_device 14497 3 snd_seq,snd_rawmidi,snd_seq_midi snd_timer 29425 2 snd_pcm,snd_seq serio_raw 13215 0 dm_multipath 22843 0 snd 68876 17 snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_seq,snd_rawmidi,snd_hda_codec,snd_hda_intel,snd_seq_device lpc_ich 17061 0 scsi_dh 14843 1 dm_multipath mei 41158 0 parport_pc 28152 0 bnep 18036 2 soundcore 12680 1 snd rfcomm 42641 0 ppdev 17073 0 microcode 22881 0 bluetooth 228619 10 bnep,rfcomm lp 17759 0 parport 46345 3 lp,ppdev,parport_pc squashfs 36522 1 overlayfs 28003 1 nls_utf8 12557 1 isofs 39815 1 dm_raid45 76725 0 xor 17116 1 dm_raid45 dm_mirror 21946 0 dm_region_hash 20820 1 dm_mirror dm_log 18529 3 dm_region_hash,dm_mirror,dm_raid45 hid_logitech_dj 18604 0 hid_apple 13237 0 usbhid 47074 1 hid_logitech_dj hid 101002 3 usbhid,hid_logitech_dj,hid_apple usb_storage 57204 1 i915 600351 3 video 19390 1 i915 ahci 25731 4 libahci 31364 1 ahci i2c_algo_bit 13413 1 i915 mpt2sas 155423 1 drm_kms_helper 49394 1 i915 drm 286313 4 i915,drm_kms_helper e1000e 198787 0 raid_class 13525 1 mpt2sas scsi_transport_sas 40901 1 mpt2sas modinfo mpt2sas ubuntu@ubuntu:~$ modinfo mpt2sas filename: /lib/modules/3.8.0-19-generic/kernel/drivers/scsi/mpt2sas/mpt2sas.ko version: 14.100.00.00 license: GPL description: LSI MPT Fusion SAS 2.0 Device Driver author: LSI Corporation srcversion: 0CDAC54AA3FB6BD11682E57 alias: pci:v00001000d0000007Esv*sd*bc*sc*i* alias: pci:v00001000d0000006Esv*sd*bc*sc*i* alias: pci:v00001000d00000087sv*sd*bc*sc*i* alias: pci:v00001000d00000086sv*sd*bc*sc*i* alias: pci:v00001000d00000085sv*sd*bc*sc*i* alias: pci:v00001000d00000084sv*sd*bc*sc*i* alias: pci:v00001000d00000083sv*sd*bc*sc*i* alias: pci:v00001000d00000082sv*sd*bc*sc*i* alias: pci:v00001000d00000081sv*sd*bc*sc*i* alias: pci:v00001000d00000080sv*sd*bc*sc*i* alias: pci:v00001000d00000065sv*sd*bc*sc*i* alias: pci:v00001000d00000064sv*sd*bc*sc*i* alias: pci:v00001000d00000077sv*sd*bc*sc*i* alias: pci:v00001000d00000076sv*sd*bc*sc*i* alias: pci:v00001000d00000074sv*sd*bc*sc*i* alias: pci:v00001000d00000072sv*sd*bc*sc*i* alias: pci:v00001000d00000070sv*sd*bc*sc*i* depends: scsi_transport_sas,raid_class intree: Y vermagic: 3.8.0-19-generic SMP mod_unload modversions parm: logging_level: bits for enabling additional logging info (default=0) parm: max_sectors:max sectors, range 64 to 32767 default=32767 (ushort) parm: max_lun: max lun, default=16895 (int) parm: diag_buffer_enable: post diag buffers (TRACE=1/SNAPSHOT=2/EXTENDED=4/default=0) (int) parm: prot_mask: host protection capabilities mask, def=7 (int) parm: max_queue_depth: max controller queue depth (int) parm: max_sgl_entries: max sg entries (int) parm: msix_disable: disable msix routed interrupts (default=0) (int) parm: missing_delay: device missing delay , io missing delay (array of int) parm: mpt2sas_fwfault_debug: enable detection of firmware fault and halt firmware - (default=0) parm: disable_discovery: disable discovery (int) Try with this : http://xpenology.trantor.be/mpt2sas-v16.7z Replace zImage on your usb stick with this one and put mpt2sas.ko (latest from LSI website) in /lib/modules/. Reboot and test. (maybe you will need to insmod the module) Waiting your feedback Just little update (I'm very busy at work) for the next update. Two "major" features are in testing stage ^^ Please Trantor, add also support for LVM mirror. See: viewtopic.php?f=2&t=915#p4291 You only need to add this three modules: dm-mirror.ko, dm-region-hash.ko and dm-log.ko I will include these Quote Link to comment Share on other sites More sharing options...
Kanedo Posted August 2, 2013 Share #61 Posted August 2, 2013 Try with this : http://xpenology.trantor.be/mpt2sas-v16.7zReplace zImage on your usb stick with this one and put mpt2sas.ko (latest from LSI website) in /lib/modules/. Reboot and test. (maybe you will need to insmod the module) Waiting your feedback Trantor. Awesome work. Here's what I've noticed. the new zImage alone doesn't see the LSI drives for initital setup. After installation with onboard SATA drives and insmod /lib/modules/mpt2sas.ko, I'm able to see all 12 drives. Is there an more automated way for the system to automatically load the driver upon bootup? Thanks. Quote Link to comment Share on other sites More sharing options...
Kanedo Posted August 2, 2013 Share #62 Posted August 2, 2013 However, I discovered a new issue. Everytime I do "insmod /lib/modules/mpt2sas.ko", I would get some show up as Disks and some show up as eSATA with 0 GB. This changes everytime I restart and do the insmod. Quote Link to comment Share on other sites More sharing options...
Kanedo Posted August 2, 2013 Share #63 Posted August 2, 2013 However, I discovered a new issue. Everytime I do "insmod /lib/modules/mpt2sas.ko", I would get some show up as Disks and some show up as eSATA with 0 GB. This changes everytime I restart and do the insmod. Okay, I guess I fixed this problem by modifying /etc.defaults/synoinfo. changed internalportcfg="0xfff" to internalportcfg="0xfffff" This change in mask gave me more internal ports. changed esataportcfg="0xff0000" to esataportcfg="0x00000" This change in mask because I don't have any eSATA ports. I was also able to make the module load on boot up by adding "mpt2sas" to KERNEL_MODULES in /etc/rc. Is this the correct way to do it? Quote Link to comment Share on other sites More sharing options...
Kanedo Posted August 2, 2013 Share #64 Posted August 2, 2013 Trantor, so everything works, except DSM4.1 is considerably slower than DSM4.2 when transferring files using AFP. Any chance you might release a DSM 4.2 build? Thanks. Quote Link to comment Share on other sites More sharing options...
Trantor Posted August 2, 2013 Author Share #65 Posted August 2, 2013 I pleased to help Yes this fix will of course included in v1.4. Modifying /etc/rc is a way to autoload module, I will update the ramdrive to load the mpt2sas module at boot. Your fix in /etc.defaults/synoinfo is very great I'm waiting synology to release proper sources to compil and repack the 4.2 and/or maybe 4.3 (beta)..... Quote Link to comment Share on other sites More sharing options...
Kanedo Posted August 2, 2013 Share #66 Posted August 2, 2013 I pleased to help Yes this fix will of course included in v1.4. Modifying /etc/rc is a way to autoload module, I will update the ramdrive to load the mpt2sas module at boot. Your fix in /etc.defaults/synoinfo is very great I'm waiting synology to release proper sources to compil and repack the 4.2 and/or maybe 4.3 (beta)..... I see 4.2 Toolchain in here http://sourceforge.net/projects/dsgpl/files/ What's all needed? I'm interested in building my own as well. Quote Link to comment Share on other sites More sharing options...
pmcnano Posted August 3, 2013 Share #67 Posted August 3, 2013 Hello! Just tried it and it works great atm, have to test a little longer, however. Will 1.4 be build 4.2? Quote Link to comment Share on other sites More sharing options...
Trantor Posted August 3, 2013 Author Share #68 Posted August 3, 2013 I pleased to help Yes this fix will of course included in v1.4. Modifying /etc/rc is a way to autoload module, I will update the ramdrive to load the mpt2sas module at boot. Your fix in /etc.defaults/synoinfo is very great I'm waiting synology to release proper sources to compil and repack the 4.2 and/or maybe 4.3 (beta)..... I see 4.2 Toolchain in here http://sourceforge.net/projects/dsgpl/files/ What's all needed? I'm interested in building my own as well. As I already tell, we need x86_64 v3.2.30 4.2 Tool Chain to build DSM 4.2 from scratch (atm only Intel x86 Linux 3.2.30 (Evansport : atom 32bits platform) is available for x86 arch) Hello! Just tried it and it works great atm, have to test a little longer, however. Will 1.4 be build 4.2? No 1.4 will still be 4.1, but maybe the last of 4.1 branch...(if synology release what we need) Quote Link to comment Share on other sites More sharing options...
pmcnano Posted August 3, 2013 Share #69 Posted August 3, 2013 I pleased to help Yes this fix will of course included in v1.4. Modifying /etc/rc is a way to autoload module, I will update the ramdrive to load the mpt2sas module at boot. Your fix in /etc.defaults/synoinfo is very great I'm waiting synology to release proper sources to compil and repack the 4.2 and/or maybe 4.3 (beta)..... I see 4.2 Toolchain in here http://sourceforge.net/projects/dsgpl/files/ What's all needed? I'm interested in building my own as well. As I already tell, we need x86_64 v3.2.30 4.2 Tool Chain to build DSM 4.2 from scratch (atm only Intel x86 Linux 3.2.30 (Evansport : atom 32bits platform) is available for x86 arch) Hello! Just tried it and it works great atm, have to test a little longer, however. Will 1.4 be build 4.2? No 1.4 will still be 4.1, but maybe the last of 4.1 branch...(if synology release what we need) Thanks Im confused about the 4.2 build in the general forum then. Whats the differencE? Thanks Quote Link to comment Share on other sites More sharing options...
colombodk Posted August 3, 2013 Share #70 Posted August 3, 2013 I pleased to help Yes this fix will of course included in v1.4. Modifying /etc/rc is a way to autoload module, I will update the ramdrive to load the mpt2sas module at boot. Your fix in /etc.defaults/synoinfo is very great I'm waiting synology to release proper sources to compil and repack the 4.2 and/or maybe 4.3 (beta)..... I see 4.2 Toolchain in here http://sourceforge.net/projects/dsgpl/files/ What's all needed? I'm interested in building my own as well. As I already tell, we need x86_64 v3.2.30 4.2 Tool Chain to build DSM 4.2 from scratch (atm only Intel x86 Linux 3.2.30 (Evansport : atom 32bits platform) is available for x86 arch) Hello! Just tried it and it works great atm, have to test a little longer, however. Will 1.4 be build 4.2? No 1.4 will still be 4.1, but maybe the last of 4.1 branch...(if synology release what we need) Trantor: Thank you for your excellent work! Can you point to somewhere it is explained, if anywhere, why Tool Chains for Bromolow (or Pineview, both being x86_64) 3.2.11 won't work? Is it the architecture or the kernel revision that is the problem? Evansport (AKA Berryville?!?) is apparently for the new Synology "x14+"-series featuring the Intel CE5300-series CPU, which does not do 64-bit code, but only x86. I am, and possible others too are a bit confused because, if the released Tool Chain for Intel x86 Linux 3.2.11 (Bromolow) doesn't work correctly with the released 4.2 cource code, then how have the various 4.2-versions versions available via this site been compiled? Is there a discussion thread on this site, or somewhere else, where these matters are laid out? edit: +1 for the AFP update to fix performance issues. Quote Link to comment Share on other sites More sharing options...
Trantor Posted August 4, 2013 Author Share #71 Posted August 4, 2013 colombodk and pmcnano you point in the good direction and so I double check what's blocking us to compil full custom DSM 4.2. Existing 4.2 build on the forum use original kernel from syno + cross compiled modules (network, usb....) to support additional hardware. My last tries to compil 4.2 (3.2.30) kernel (with gpl sources from syno), result in a machine shutdowning/restarting itself Today I restart from the begenning my test on compiling custom DSM 4.2: - Clean install of debian 7 (compiling / building lab) - Using gcc420_glibc236_x64_bromolow-GPL tool chain (Intel x86 Linux 3.2.11 (Bromolow) ; yes I know I said this will result in corrupt compilation...but wait & see) - Kernel from syno GPL (synogpl-3201-bromolow) + fix to few .c files (from andy's git and nighthawk) - Use odie's build (DSM 4.2 build 3202) as base DSM 4.1 and 4.2 use both gcc 4.20 and glibc 2.36. (I think this is why using 3.2.11 tool chain instead of missing 3.2.30 is working) Few hours later (and lot of cofee ^^), I finally succeeded to boot with my brand new 4.2 kernel First 4.2 beta very soon Quote Link to comment Share on other sites More sharing options...
Kanedo Posted August 5, 2013 Share #72 Posted August 5, 2013 Excellent news Trantor. I can't wait for the 4.2 release. The current v1.3a + modified zImage + mpt2sas.ko works for my hardware using LSI card, but performance is quite bad. 4.2 will surely fix the problem. I'll be happy to it out once your release is available. Keep up the awesome work. On a side note, it would be awesome if you could write up the instruction how your workflow to build 4.2, so others like myself can tweak it and offer better support for you. Thanks. Quote Link to comment Share on other sites More sharing options...
Trantor Posted August 5, 2013 Author Share #73 Posted August 5, 2013 Excellent news Trantor. I can't wait for the 4.2 release. The current v1.3a + modified zImage + mpt2sas.ko works for my hardware using LSI card, but performance is quite bad. 4.2 will surely fix the problem. I'll be happy to it out once your release is available. Keep up the awesome work. On a side note, it would be awesome if you could write up the instruction how your workflow to build 4.2, so others like myself can tweak it and offer better support for you. Thanks. Yes 4.2 have AFP fixes : AFP (Apple File Protocol) Performance Enhancements -- The speed of file transfers to the DiskStation has improved up to 52% Quote Link to comment Share on other sites More sharing options...
interested Posted August 6, 2013 Share #74 Posted August 6, 2013 AFP speed is one thing, rest is here (Changelog): http://www.synology.com/releaseNote_enu/DS109j.php Quote Link to comment Share on other sites More sharing options...
jolife Posted August 6, 2013 Share #75 Posted August 6, 2013 I think I have found a bug? Let me explain...... I set up volume 1 SHR with 4 disks (I am using a Tranquil SQA5H, so I have 5 disk bays) and loaded data onto it. I then (some time later) added a new disk into the 5th drive bay. There does not seem to be any way for me to manage this volume and allow me to add the 5th disk to it. Yes, I can set the 5th disk as volume 2, but cannot get it to join volume 1. I have a real DS 412+ and this Tranquil box. On the real one yuo can click on the "manage" volume. On the Tranquil, the "manage" box is not clickable. Anyone got any ideas? Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.