nick413

make configuration from FS3017

Recommended Posts

Hi!

 

MB: SuperMicro X10DRI-O

Network card: Mellanox MCX314A-BCCT - 40Gb

SAS Controller: LSI Logic SAS 9300-8i SGL - 2

Сhassis: Chenbro RM238 - 24x2.5’’ - Backplane support 12G SAS.

RAM - 64GB

CPU - 2 x Xeon E5-2620v3

Toshiba THNSN81Q92CSE ET - 16 

Network card from motherboard - Intel I350 1gbe dual port

 

Jun's Loader v1.03b DS3615xs - "dont found hard drive"

Jun's Loader v1.03b DS3617xs - "dont found hard drive"

Jun's Loader v1.04b DS918+ - works, sees drives, but does not support RAID F1 and the Mellanox network card

 

How to make Jun's Loader for DS3617xs work?

Share this post


Link to post
Share on other sites
14 hours ago, nick413 said:

SAS Controller: LSI Logic SAS 9300-8i SGL - 2

chip is SAS3008, driver mpt3sas, ds3617 image from synology comes with this driver in dsm (3615 does not)

so in theory it should work, whats the vendor id when listing it with lspci?

 

14 hours ago, nick413 said:

Jun's Loader v1.04b DS918+ - works, sees drives, but does not support RAID F1 and the Mellanox network card

 

the F1 Raid mode might be present, you can try to switch of the SHR Support by reverting whats written about enabling SHR

https://xpenology.com/forum/topic/9394-installation-faq/?do=findComment&comment=81094

so disable shr support and use raidgroups instead, maybe the F1 option will appear, synology seems to use the same base for all

getting a network driver working seems much less hassle then getting mpt sas drivers working, i did try to add newer drivers last year and it did not work

 

 

 

15 hours ago, nick413 said:

Network card: Mellanox MCX314A-BCCT - 40Gb

thats a ConnectX-3 card, also can you give the vendor id from lspci

 

taking into accout that even the newly compiled mpt2sas driver from 3615 (kernel 3.10.105) did not work (loads but when devices are found crashes, also happens with other scsi/sas drivers, might be a kernel source problem, synology using a newer changed kernel, we only have >2 year old beta kernel)) and we will have to use the drivers coming with dsm when it comes to scsi/sas you might be better off with 918+ when the storage is working, i see more hope getting a nic driver to work the scsi/sas

 

not sure why you choose the sas controller, when it comes to xpenology (hacked dsm) then ahci is 1st choice (imho)

the board has 10 x sata already and plenty of pcie slots for 4port or 8port ahci cards (in your case just two 4port cards with marvel 9215 might be enough)

 

Share this post


Link to post
Share on other sites

Hi, thanks for the reply. I try to follow your advice.

How to solve the problem with long loading of network card?

After the inscription "Happy hacking"

The device appears on the network in 20-25 minutes.
NIC - Intel I350

Share this post


Link to post
Share on other sites

Should the system show that two processors are installed?

 

788702669_screen1.thumb.PNG.562971b33ab4fc425c8f1aaa1ddc76ab.PNG

Added extra.ism and extra2.ism files from the topic: 

Disks are in the server from 1-16

In DSM it is displayed from 11-25 (14 disks), somewhere 2 disks disappeared.

1427967926_screen3.thumb.PNG.4e49b81ed78d5c42cd85aa74d182d1a5.PNG

 

Share this post


Link to post
Share on other sites
On 12/10/2019 at 5:04 AM, IG-88 said:

thats a ConnectX-3 card, also can you give the vendor id from lspci

0000:82:00.0 Class 0200: Device 15b3:1007
        Subsystem: Device 15b3:0006
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0, Cache Line Size: 32 bytes
        Interrupt: pin A routed to IRQ 11
        Region 0: Memory at fbc00000 (64-bit, non-prefetchable)
        Region 2: Memory at fb000000 (64-bit, prefetchable)
        Expansion ROM at fbb00000 [disabled]
        Capabilities: [40] Power Management version 3
                Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
                Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
        Capabilities: [48] Vital Product Data
                Product Name: CX314A - ConnectX-3 Pro QSFP
                Read-only fields:
                        [PN] Part number: MCX314A-BCCT
                        [EC] Engineering changes: AC
                        [SN] Serial number: MT1843X01291
                        [V0] Vendor specific: PCIe Gen3 x8
                        [RV] Reserved: checksum good, 0 byte(s) reserved
                Read/write fields:
                        [V1] Vendor specific: N/A
                        [YA] Asset tag: N/A
                        [RW] Read-write area: 101 byte(s) free
                        [RW] Read-write area: 253 byte(s) free
                        [RW] Read-write area: 253 byte(s) free
                        [RW] Read-write area: 253 byte(s) free
                        [RW] Read-write area: 253 byte(s) free
                        [RW] Read-write area: 253 byte(s) free
                        [RW] Read-write area: 253 byte(s) free
                        [RW] Read-write area: 253 byte(s) free
                        [RW] Read-write area: 253 byte(s) free
                        [RW] Read-write area: 253 byte(s) free
                        [RW] Read-write area: 253 byte(s) free
                        [RW] Read-write area: 253 byte(s) free
                        [RW] Read-write area: 253 byte(s) free
                        [RW] Read-write area: 253 byte(s) free
                        [RW] Read-write area: 253 byte(s) free
                        [RW] Read-write area: 252 byte(s) free
                End
        Capabilities: [9c] MSI-X: Enable- Count=128 Masked-
                Vector table: BAR=0 offset=0007c000
                PBA: BAR=0 offset=0007d000
        Capabilities: [60] Express (v2) Endpoint, MSI 00
                DevCap: MaxPayload 512 bytes, PhantFunc 0, Latency L0s <64ns, L1 unlimited
                        ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset+
                DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
                        RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- FLReset-
                        MaxPayload 256 bytes, MaxReadReq 512 bytes
                DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend-
                LnkCap: Port #8, Speed 8GT/s, Width x8, ASPM L0s, Exit Latency L0s unlimited, L1 unlimited
                        ClockPM- Surprise- LLActRep- BwNot-
                LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+
                        ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
                LnkSta: Speed 8GT/s, Width x8, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
                DevCap2: Completion Timeout: Range ABCD, TimeoutDis+, LTR-, OBFF Not Supported
                DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled
                LnkCtl2: Target Link Speed: 8GT/s, EnterCompliance- SpeedDis-
                         Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
                         Compliance De-emphasis: -6dB
                LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete+, EqualizationPhase1+
                         EqualizationPhase2+, EqualizationPhase3+, LinkEqualizationRequest-
        Capabilities: [c0] Vendor Specific Information: Len=18 <?>
        Capabilities: [100 v1] Alternative Routing-ID Interpretation (ARI)
                ARICap: MFVC- ACS-, Next Function: 0
                ARICtl: MFVC- ACS-, Function Group: 0
        Capabilities: [148 v1] Device Serial Number 98-03-9b-03-00-cf-01-e0
        Capabilities: [108 v1] Single Root I/O Virtualization (SR-IOV)
                IOVCap: Migration-, Interrupt Message Number: 000
                IOVCtl: Enable- Migration- Interrupt- MSE- ARIHierarchy+
                IOVSta: Migration-
                Initial VFs: 8, Total VFs: 8, Number of VFs: 0, Function Dependency Link: 00
                VF offset: 1, stride: 1, Device ID: 1004
                Supported Page Size: 000007ff, System Page Size: 00000001
                Region 2: Memory at 0000000000000000 (64-bit, prefetchable)
                VF Migration: offset: 00000000, BIR: 0
        Capabilities: [154 v2] Advanced Error Reporting
                UESta:  DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
                UEMsk:  DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
                UESvrt: DLP+ SDES- TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
                CESta:  RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr-
                CEMsk:  RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
                AERCap: First Error Pointer: 00, GenCap+ CGenEn- ChkCap+ ChkEn-
        Capabilities: [18c v1] #19

 

Edited by Polanskiman
Added code tag.

Share this post


Link to post
Share on other sites
1 hour ago, nick413 said:

After the inscription "Happy hacking"

The device appears on the network in 20-25 minutes.
NIC - Intel I350

you did not mention this above

on every  boot or just when installing?

any log you can provide for this?

unusual, cant remember any case where waiting that long made a difference, the driver works or it doesn't , should be a matter of seconds

i will do a reworked 918+ extra/extra2 that hopefully have recent drivers for intel nic's and if you can provide a log from a booted up system that shows something about the menalox driver loading might help, ConnectX-3 seems not to be very new, also provide a vendor id from lspci, with that i can check against the driver source if it should be detected or not

 

56 minutes ago, nick413 said:

Disks are in the server from 1-16

In DSM it is displayed from 11-25 (14 disks), somewhere 2 disks disappeared.

disable onboard sata, 10 sata ports an 16 follow up ports is more then 24 so kind of normal that 2 drives are missing in this configuration (10+16 =26)

(btw. changing the max. drive for 918+ is pretty easy as juns patch already contains a change from 4 to 16 drives, 3615/17 have a syanology default of 12 drives, so jun's patch does not contain anything you could chande to a higher value, it needs a new diff from original synoinfo.conf and modded one and pasting this into jun's patch an the extra.lzma - still one of the things i want to do, its clear what to do but it needs to doene and testing)

Share this post


Link to post
Share on other sites
7 hours ago, IG-88 said:

on every  boot or just when installing?

On every  boot

 

7 hours ago, IG-88 said:

any log you can provide for this?

How to upload logs correctly?

 

7 hours ago, IG-88 said:

menalox driver loading might help, ConnectX-3 seems not to be very new, also provide a vendor id from lspci, with that i can check against the driver source if it should be detected or not

I in the previous message, unloaded the information

 

7 hours ago, nick413 said:

0000:82:00.0 Class 0200: Device 15b3:1007
        Subsystem: Device 15b3:0006
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0, Cache Line Size: 32 bytes
        Interrupt: pin A routed to IRQ 11
        Region 0: Memory at fbc00000 (64-bit, non-prefetchable)
        Region 2: Memory at fb000000 (64-bit, prefetchable)
        Expansion ROM at fbb00000 [disabled]
        Capabilities: [40] Power Management version 3
                Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
                Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
        Capabilities: [48] Vital Product Data
                Product Name: CX314A - ConnectX-3 Pro QSFP
                Read-only fields:
                        [PN] Part number: MCX314A-BCCT
                        [EC] Engineering changes: AC
                        [SN] Serial number: MT1843X01291
                        [V0] Vendor specific: PCIe Gen3 x8
                        [RV] Reserved: checksum good, 0 byte(s) reserved
                Read/write fields:
                        [V1] Vendor specific: N/A
                        [YA] Asset tag: N/A
                        [RW] Read-write area: 101 byte(s) free
                        [RW] Read-write area: 253 byte(s) free
                        [RW] Read-write area: 253 byte(s) free
                        [RW] Read-write area: 253 byte(s) free
                        [RW] Read-write area: 253 byte(s) free
                        [RW] Read-write area: 253 byte(s) free
                        [RW] Read-write area: 253 byte(s) free
                        [RW] Read-write area: 253 byte(s) free
                        [RW] Read-write area: 253 byte(s) free
                        [RW] Read-write area: 253 byte(s) free
                        [RW] Read-write area: 253 byte(s) free
                        [RW] Read-write area: 253 byte(s) free
                        [RW] Read-write area: 253 byte(s) free
                        [RW] Read-write area: 253 byte(s) free
                        [RW] Read-write area: 253 byte(s) free
                        [RW] Read-write area: 252 byte(s) free
                End
        Capabilities: [9c] MSI-X: Enable- Count=128 Masked-
                Vector table: BAR=0 offset=0007c000
                PBA: BAR=0 offset=0007d000
        Capabilities: [60] Express (v2) Endpoint, MSI 00
                DevCap: MaxPayload 512 bytes, PhantFunc 0, Latency L0s <64ns, L1 unlimited
                        ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset+
                DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
                        RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- FLReset-
                        MaxPayload 256 bytes, MaxReadReq 512 bytes
                DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend-
                LnkCap: Port #8, Speed 8GT/s, Width x8, ASPM L0s, Exit Latency L0s unlimited, L1 unlimited
                        ClockPM- Surprise- LLActRep- BwNot-
                LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+
                        ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
                LnkSta: Speed 8GT/s, Width x8, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
                DevCap2: Completion Timeout: Range ABCD, TimeoutDis+, LTR-, OBFF Not Supported
                DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled
                LnkCtl2: Target Link Speed: 8GT/s, EnterCompliance- SpeedDis-
                         Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
                         Compliance De-emphasis: -6dB
                LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete+, EqualizationPhase1+
                         EqualizationPhase2+, EqualizationPhase3+, LinkEqualizationRequest-
        Capabilities: [c0] Vendor Specific Information: Len=18 <?>
        Capabilities: [100 v1] Alternative Routing-ID Interpretation (ARI)
                ARICap: MFVC- ACS-, Next Function: 0
                ARICtl: MFVC- ACS-, Function Group: 0
        Capabilities: [148 v1] Device Serial Number 98-03-9b-03-00-cf-01-e0
        Capabilities: [108 v1] Single Root I/O Virtualization (SR-IOV)
                IOVCap: Migration-, Interrupt Message Number: 000
                IOVCtl: Enable- Migration- Interrupt- MSE- ARIHierarchy+
                IOVSta: Migration-
                Initial VFs: 8, Total VFs: 8, Number of VFs: 0, Function Dependency Link: 00
                VF offset: 1, stride: 1, Device ID: 1004
                Supported Page Size: 000007ff, System Page Size: 00000001
                Region 2: Memory at 0000000000000000 (64-bit, prefetchable)
                VF Migration: offset: 00000000, BIR: 0
        Capabilities: [154 v2] Advanced Error Reporting
                UESta:  DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
                UEMsk:  DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
                UESvrt: DLP+ SDES- TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
                CESta:  RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr-
                CEMsk:  RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
                AERCap: First Error Pointer: 00, GenCap+ CGenEn- ChkCap+ ChkEn-
        Capabilities: [18c v1] #19

 

 

 

7 hours ago, IG-88 said:

disable onboard sata, 10 sata ports an 16 follow up ports is more then 24 so kind of normal that 2 drives are missing in this configuration (10+16 =26)

Where can I disable? grub.cfg or jun.patch or 'synoinfo.conf' file, located under '/etc.defaults'

Edited by Polanskiman
Added code tag.

Share this post


Link to post
Share on other sites
3 minutes ago, nick413 said:

Where can I disable? grub.cfg or jun.patch or 'synoinfo.conf' file, located under '/etc.defaults'

in bios so dsm does not "see" it

4 minutes ago, nick413 said:

How to upload logs correctly?

just copy the part where the melanox driver (mlx4*, mlx5*) is loaded from /var/log/dmesg

 

also copy the part from the driver "igb", thats your i350

 

 

can you provide the lspci output of your sas controller(s)

 

 

Share this post


Link to post
Share on other sites
19 минут назад, IG-88 сказал:

just copy the part where the melanox driver (mlx4*, mlx5*) is loaded from /var/log/dmesg

I completely uploaded this file, its contents are strange.

dmesg

Share this post


Link to post
Share on other sites

I had 3  SAS controllers.

I disabled one SAS controller, disabled all SATA ports, eSATA too.
It became faster to boot and the device began to appear faster on the network, according to the logs, I realized that the problem was in the third SAS controller.

Left to do:
- activate RAID F1
- activate Mellanos 40G network card

 

I have 2 processors, how do I know if the system uses one processor or two?

 

152485098_screen23.thumb.PNG.5823b75ea3e70040db9e18a8312b2a6d.PNG

Edited by nick413

Share this post


Link to post
Share on other sites
1 час назад, IG-88 сказал:

in bios so dsm does not "see" it

just copy the part where the melanox driver (mlx4*, mlx5*) is loaded from /var/log/dmesg

 

also copy the part from the driver "igb", thats your i350

 

 

can you provide the lspci output of your sas controller(s)

 

 

There are no problems with the i350.

It was loaded for a long time due to the extra SAS controller.

Share this post


Link to post
Share on other sites
В 10.12.2019 в 01:04, IG-88 сказал:

the F1 Raid mode might be present, you can try to switch of the SHR Support by reverting whats written about enabling SHR

https://xpenology.com/forum/topic/9394-installation-faq/?do=findComment&comment=81094

so disable shr support and use raidgroups instead, maybe the F1 option will appear, synology seems to use the same base for all

I performed this, but RAID F1 did not appear.

Before checking, I restarted the server.

 

1425199100_screen24.thumb.PNG.170e71898d982cce54f038c6609e1834.PNG

1304106762_screen25.PNG.4592292dca67266e879b383b314b93ff.PNG

 

There are ideas, what else can be done?

918+ according to the technical documentation does not support RAID F1.

Share this post


Link to post
Share on other sites
On 12/11/2019 at 7:22 AM, nick413 said:

918+ according to the technical documentation does not support RAID F1.

well i guess you could say the same about 3617?

https://global.download.synology.com/download/Document/Hardware/DataSheet/DiskStation/17-year/DS3617xs/enu/Synology_DS3617xs_Data_Sheet_enu.pdf

there is no raid f1 too

 

you try to find out if f1 is working on 3617 by using some disks on the internal sata ports, they should show up ootb

maybe f1 needs to be present in a different way then other common raid modes so it might only availible on FS* stations, but can also be some switches in conf, i dont konw, you might need to find out on your own

 

there is a raid related switch present in ds3617 and fs3017 but not 918+

support_diffraid="yes"

i dont know what it does but you can try to set it in 918+ too

 

 

On 12/11/2019 at 5:36 AM, nick413 said:

I completely uploaded this file, its contents are strange.

i'd say ~330 errors per second in the log file is more alarming

does not look like as it would really working

 

Share this post


Link to post
Share on other sites
18 минут назад, IG-88 сказал:

ну, я думаю, вы могли бы сказать то же самое о 3617?

https://www.synology.com/en-global/knowledgebase/DSM/tutorial/Storage/Which_Synology_NAS_models_support_RAID_F1

 

There is support for RAID F1 model DS3617xs.

But the server does not see hard drives in Jun's Loader v1.03b DS3617xs.

Similar picture from the internet*

image.thumb.png.e4490e8c6a49667b212165178c7f22c0.png

--------

loading time is still long.
1. 10 minutes after the start, the IP address appears
2. In another 8-10 minutes the web interface starts to load.

 

18 минут назад, IG-88 сказал:

there is a raid related switch present in ds3617 and fs3017 but not 918+

support_diffraid="yes"

i dont know what it does but you can try to set it in 918+ too

I will try this, thanks for the answers.

Edited by nick413

Share this post


Link to post
Share on other sites
7 minutes ago, nick413 said:

But the server does not see hard drives in Jun's Loader v1.03b DS3617xs.

 

there is still the option to connect the disks to sata as mentioned above, that way you dont need mpt sas support, ahci is part of the pre compiled synology kernel

 

 

Share this post


Link to post
Share on other sites
Только что, IG-88 сказал:

 

there is still the option to connect the disks to sata as mentioned above, that way you dont need mpt sas support, ahci is part of the pre compiled synology kernel

 

 

I have only SSD drives and need better performance than SATA 6G

My SAS controllers supports 12G

Share this post


Link to post
Share on other sites

your spec from above looked like you would use sata drives, so it would be no loss using sata ports

 

Share this post


Link to post
Share on other sites
16 часов назад, IG-88 сказал:

your spec from above looked like you would use sata drives, so it would be no loss using sata ports

 

I brought synoinfo.conf settings to the same settings as the FS3017 model

I left the parameters for the WOL network.

RAID F1 appeared in the menu.

image.thumb.png.c17654b35d3fc76b041fa73a0a992cac.png

But does not work.

image.png.510e2149c85bf3034f62a3e473203faa.png

 

1 in 1 settings like FS 3017

but if i turn on - support_sas = "yes"
then everything disappears, the bootloader does not see the disks

 

image.thumb.png.e9e99d8401e64cb284cd9ef39d9e5ee4.png

 

 

Edited by nick413

Share this post


Link to post
Share on other sites

seeing your last test and the 330 messages per second in the log of 918+ and knowing the 3617 supports f1 ootb,  i'd go with sata/ahci and 3617 image

 

 

Share this post


Link to post
Share on other sites
1 час назад, IG-88 сказал:

seeing your last test and the 330 messages per second in the log of 918+ and knowing the 3617 supports f1 ootb,  i'd go with sata/ahci and 3617 image

 

 

How do you like the idea of getting firewood from the image.pat of FS3017?

My server model is assembled on iron the same way with the contents of the internals of the FS3017.

 

Chipset C612

2 X SAS LSI 9300-8i

CPU - 2X Xeon E5-2620v3

RAM 64GB

 

 

Share this post


Link to post
Share on other sites
В 10.12.2019 в 01:04, IG-88 сказал:
В 09.12.2019 в 09:37, nick413 сказал:

SAS Controller: LSI Logic SAS 9300-8i SGL - 2

chip is SAS3008, driver mpt3sas, ds3617 image from synology comes with this driver in dsm (3615 does not)

image.thumb.png.395ccdc637bf9c549276a10f1502b5dc.png

I think this is just the right driver for the LSI 9300-8i, no?

Share this post


Link to post
Share on other sites

keep in mind the synology limits things on  purpose (like only allowing there own esata extenders) and the loader you are using is kind of a hack as it disables checks for the original hardware and enables loading of additional drivers

usually the bast way is to stay close to the hardware of the image you are using or you will depend on additional drivers

building the same as fs3017 and not being able to use that image ...

the sas stuff also exeeds the 24 drive limit we usually see with the normal images and uses diffrent mechanisms to implement it and they need (as esata) special firmware that will be identified when connection/using stuff - so additional trip wires

atm i cant compile better/newer mpt sas drivers (or any scsi/sas drivers) for 3615/17 so dont expect a miracle in the next weeks/months

if you really want to user f1 raid and dsm  then 3617 and ahci/sata seems to be the realistic way

if you have huge amounts of time and are good in reverse engineering and using IDA you might find a solution, but thats nothing i can do

if you can do this you might reverse jun's way and make a loader for the dsm system of your choice afaik its mainly about making dsm see the hardware of the original system when checking but i can be wrong here its just what i got from reading here

Share this post


Link to post
Share on other sites
7 минут назад, IG-88 сказал:

keep in mind the synology limits things on  purpose (like only allowing there own esata extenders) and the loader you are using is kind of a hack as it disables checks for the original hardware and enables loading of additional drivers

usually the bast way is to stay close to the hardware of the image you are using or you will depend on additional drivers

building the same as fs3017 and not being able to use that image ...

the sas stuff also exeeds the 24 drive limit we usually see with the normal images and uses diffrent mechanisms to implement it and they need (as esata) special firmware that will be identified when connection/using stuff - so additional trip wires

atm i cant compile better/newer mpt sas drivers (or any scsi/sas drivers) for 3615/17 so dont expect a miracle in the next weeks/months

if you really want to user f1 raid and dsm  then 3617 and ahci/sata seems to be the realistic way

if you have huge amounts of time and are good in reverse engineering and using IDA you might find a solution, but thats nothing i can do

if you can do this you might reverse jun's way and make a loader for the dsm system of your choice afaik its mainly about making dsm see the hardware of the original system when checking but i can be wrong here its just what i got from reading here

Thanks for the answer,

3617 or 3615 bootloader will be enough for me for RAID F1

But the network doesn't work with them - Intel i350 and also LSI 9300-8i

If you give me information on how to compile the drivers and insert them into extra.izma, I will try to implement the necessary drivers myself.
I need instructions, I think I can do it.

Share this post


Link to post
Share on other sites

Intel I350 -T2 Dual Port NIC 

 

Information from Supermicro.

This release includes Base Drivers for Intel(R) Ethernet Network Connections.

- igb driver supports all 82575-, 82576-, 82580-, I350-, I210-, I211- and
  I354-based gigabit network connections.
- igbvf driver supports 82576-based virtual function devices that can only
  be activated on kernels that support SR-IOV.
- e1000e driver supports all PCI Express gigabit network connections, except
  those that are 82575-, 82576-, 82580-, and I350-, I210-, and I211-based*.
  * NOTES:
    - The Intel(R) PRO/1000 P Dual Port Server Adapter is supported by
      the e1000 driver, not the e1000e driver due to the 82546 part being used
      behind a PCI Express bridge.
    - Gigabit devices based on the Intel(R) Ethernet Controller X722 are
      supported by the i40e driver.
 

From the information I need to implement the e1000 driver for 3617 or 3615.

Share this post


Link to post
Share on other sites
16 hours ago, nick413 said:

From the information I need to implement the e1000 driver for 3617 or 3615.

 

i already did this in the (not public available) test version, your problem is the mpt3sas driver, if the one coming with dsm does not work with your controller i dont see how to get it working atm - it might hurt but either you get yourself sas controllers working with 3617 or you throw out sas and use sata

3617:

mpt3sas = version 22.00.02.00

mpt2sas = version 20.00.00.00

this version must be from external source, as kernel 3.10.105 has different version numbers

 

whats the vendor id of your controllers (lspci)?

edit:

if you want to try to build your own drivers and extra.lzma, my "old" descrition is still good, just look at the end of the thread for some infos about waht to change for dsm 6.2.2

https://xpenology.com/forum/topic/7187-how-to-build-and-inject-missing-drivers-in-jun-loader-102a/

 

edit2:

if you take the source of the mpt3sas 22.00.02.00

mp3sas_base.h contains names and id's of controllers supported (thats the version from dsm)

so if you insist on sas3 there would be the Dell HBA330 12G but there are others too

 

Spoiler

...

/*
 * Intel SAS2 HBA branding
 */
#define MPT2SAS_INTEL_RMS25JB080_BRANDING    \
    "Intel(R) Integrated RAID Module RMS25JB080"
#define MPT2SAS_INTEL_RMS25JB040_BRANDING    \
    "Intel(R) Integrated RAID Module RMS25JB040"
#define MPT2SAS_INTEL_RMS25KB080_BRANDING    \
    "Intel(R) Integrated RAID Module RMS25KB080"
#define MPT2SAS_INTEL_RMS25KB040_BRANDING    \
    "Intel(R) Integrated RAID Module RMS25KB040"
#define MPT2SAS_INTEL_RMS25LB040_BRANDING    \
    "Intel(R) Integrated RAID Module RMS25LB040"
#define MPT2SAS_INTEL_RMS25LB080_BRANDING    \
    "Intel(R) Integrated RAID Module RMS25LB080"
#define MPT2SAS_INTEL_RMS2LL080_BRANDING    \
    "Intel Integrated RAID Module RMS2LL080"
#define MPT2SAS_INTEL_RMS2LL040_BRANDING    \
    "Intel Integrated RAID Module RMS2LL040"
#define MPT2SAS_INTEL_RS25GB008_BRANDING    \
    "Intel(R) RAID Controller RS25GB008"
#define MPT2SAS_INTEL_SSD910_BRANDING        \
    "Intel(R) SSD 910 Series"

/*
 * Intel SAS2 HBA SSDIDs
 */
#define MPT2SAS_INTEL_RMS25JB080_SSDID         0x3516
#define MPT2SAS_INTEL_RMS25JB040_SSDID         0x3517
#define MPT2SAS_INTEL_RMS25KB080_SSDID         0x3518
#define MPT2SAS_INTEL_RMS25KB040_SSDID         0x3519
#define MPT2SAS_INTEL_RMS25LB040_SSDID         0x351A
#define MPT2SAS_INTEL_RMS25LB080_SSDID         0x351B
#define MPT2SAS_INTEL_RMS2LL080_SSDID          0x350E
#define MPT2SAS_INTEL_RMS2LL040_SSDID          0x350F
#define MPT2SAS_INTEL_RS25GB008_SSDID          0x3000
#define MPT2SAS_INTEL_SSD910_SSDID             0x3700

/*
 * Intel SAS3 HBA branding
 */
#define MPT3SAS_INTEL_RMS3JC080_BRANDING       \
    "Intel(R) Integrated RAID Module RMS3JC080"
#define MPT3SAS_INTEL_RS3GC008_BRANDING       \
        "Intel(R) RAID Controller RS3GC008"
#define MPT3SAS_INTEL_RS3FC044_BRANDING       \
        "Intel(R) RAID Controller RS3FC044"
#define MPT3SAS_INTEL_RS3UC080_BRANDING       \
        "Intel(R) RAID Controller RS3UC080"
#define MPT3SAS_INTEL_RS3PC_BRANDING       \
        "Intel(R) RAID Integrated RAID RS3PC"

/*
 * Intel SAS3 HBA SSDIDs
 */
#define MPT3SAS_INTEL_RMS3JC080_SSDID        0x3521
#define MPT3SAS_INTEL_RS3GC008_SSDID         0x3522
#define MPT3SAS_INTEL_RS3FC044_SSDID         0x3523
#define MPT3SAS_INTEL_RS3UC080_SSDID         0x3524
#define MPT3SAS_INTEL_RS3PC_SSDID            0x3527

/*
 * Dell SAS2 HBA branding
 */
#define MPT2SAS_DELL_6GBPS_SAS_HBA_BRANDING        "Dell 6Gbps SAS HBA"
#define MPT2SAS_DELL_PERC_H200_ADAPTER_BRANDING    "Dell PERC H200 Adapter"
#define MPT2SAS_DELL_PERC_H200_INTEGRATED_BRANDING "Dell PERC H200 Integrated"
#define MPT2SAS_DELL_PERC_H200_MODULAR_BRANDING    "Dell PERC H200 Modular"
#define MPT2SAS_DELL_PERC_H200_EMBEDDED_BRANDING   "Dell PERC H200 Embedded"
#define MPT2SAS_DELL_PERC_H200_BRANDING            "Dell PERC H200"
#define MPT2SAS_DELL_6GBPS_SAS_BRANDING            "Dell 6Gbps SAS"

/*
 * Dell SAS2 HBA SSDIDs
 */
#define MPT2SAS_DELL_6GBPS_SAS_HBA_SSDID           0x1F1C
#define MPT2SAS_DELL_PERC_H200_ADAPTER_SSDID       0x1F1D
#define MPT2SAS_DELL_PERC_H200_INTEGRATED_SSDID    0x1F1E
#define MPT2SAS_DELL_PERC_H200_MODULAR_SSDID       0x1F1F
#define MPT2SAS_DELL_PERC_H200_EMBEDDED_SSDID      0x1F20
#define MPT2SAS_DELL_PERC_H200_SSDID               0x1F21
#define MPT2SAS_DELL_6GBPS_SAS_SSDID               0x1F22
/*
 * Dell SAS3 HBA branding
 */
#define MPT3SAS_DELL_HBA330_ADP_BRANDING    \
    "Dell HBA330 Adp"
#define MPT3SAS_DELL_12G_HBA_BRANDING       \
        "Dell 12Gbps SAS HBA"
#define MPT3SAS_DELL_HBA330_MINI_BRANDING    \
    "Dell HBA330 Mini"

/*
 * Dell SAS3 HBA SSDIDs
 */
#define MPT3SAS_DELL_HBA330_ADP_SSDID    0x1F45
#define MPT3SAS_DELL_12G_HBA_SSDID    0x1F46
#define MPT3SAS_DELL_HBA330_MINI_SSDID    0x1F53

/*
 * Cisco SAS3 HBA branding
 */
#define MPT3SAS_CISCO_12G_8E_HBA_BRANDING       \
        "Cisco 9300-8E 12G SAS HBA"
#define MPT3SAS_CISCO_12G_8I_HBA_BRANDING       \
        "Cisco 9300-8i 12G SAS HBA"
#define MPT3SAS_CISCO_12G_AVILA_HBA_BRANDING       \
        "Cisco 12G Modular SAS Pass through Controller"
#define MPT3SAS_CISCO_12G_COLUSA_MEZZANINE_HBA_BRANDING       \
        "UCS C3X60 12G SAS Pass through Controller"        
/*
 * Cisco SAS3 HBA SSSDIDs
 */
#define MPT3SAS_CISCO_12G_8E_HBA_SSDID  0x14C
#define MPT3SAS_CISCO_12G_8I_HBA_SSDID  0x154
#define MPT3SAS_CISCO_12G_AVILA_HBA_SSDID  0x155
#define MPT3SAS_CISCO_12G_COLUSA_MEZZANINE_HBA_SSDID  0x156

/*
 * HP SAS2 HBA branding
 */
#define MPT2SAS_HP_3PAR_SSVID            0x1590
#define MPT2SAS_HP_2_4_INTERNAL_BRANDING    \
    "HP H220 Host Bus Adapter"
#define MPT2SAS_HP_2_4_EXTERNAL_BRANDING    \
    "HP H221 Host Bus Adapter"
#define MPT2SAS_HP_1_4_INTERNAL_1_4_EXTERNAL_BRANDING    \
    "HP H222 Host Bus Adapter"
#define MPT2SAS_HP_EMBEDDED_2_4_INTERNAL_BRANDING    \
    "HP H220i Host Bus Adapter"
#define MPT2SAS_HP_DAUGHTER_2_4_INTERNAL_BRANDING    \
    "HP H210i Host Bus Adapter"

/*
 * HP SAS2 HBA SSDIDs
 */
#define MPT2SAS_HP_2_4_INTERNAL_SSDID            0x0041
#define MPT2SAS_HP_2_4_EXTERNAL_SSDID            0x0042
#define MPT2SAS_HP_1_4_INTERNAL_1_4_EXTERNAL_SSDID    0x0043
#define MPT2SAS_HP_EMBEDDED_2_4_INTERNAL_SSDID        0x0044
#define MPT2SAS_HP_DAUGHTER_2_4_INTERNAL_SSDID        0x0046

...

 

Edited by IG-88
  • Like 1

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.