Jump to content
XPEnology Community

Driver extension jun 1.03b/1.04b for DSM6.2.2 for 3615xs / 3617xs / 918+


IG-88

Recommended Posts

Hi @IG-88

 

I was able to update all my servers (in the signature), from the version DSM 6.1.7 U3 to the version DSM 6.2.2 U6 using your file extra.lzma v0.5_test.

 

All servers were updated, but the server on the motherboard Asus P8Z68-V LX is now not visible on the network.

 

Load from the new bootloader, and upgrade to version DSM 6.2.2 U6 - normal. Then the server reboots and the server is not visible on the network.

I tried replacing the file extra.lzma v0.5_test with the original file extra.lzma from the Jun bootloader. The result is the same, the server is not visible on the network.

 

How can I fix this situation? Thanks.

 

P.S. Asus P8Z68-V LX has a Realtek 8111E network interface, which worked perfectly on the DSM6.1.7U3 version.

Link to comment
Share on other sites

38 minutes ago, aleksey_z said:

Load from the new bootloader, and upgrade to version DSM 6.2.2 U6 - normal. Then the server reboots and the server is not visible on the network.

I tried replacing the file extra.lzma v0.5_test with the original file extra.lzma from the Jun bootloader. The result is the same, the server is not visible on the network.

sounds like you did the loader first and after finding the system in network you updated to 6.2.2 (migration), if thats the case we might rule out problems with uefi/csm as 1.03b need csm/legacy mode and also the usb device choosen for boot needs to be "non uefi" (often the uefi devices have uefi in there name)

 

you might try jun's original loader 1.03b with just your vid/pid, mac and sn (that would be original extra.lzma and kernel files from dsm 6.2.0)

if visible in network you can try to update to the now recent 6.2.3, that version uses the same driver as the "old" 6.2.x before 6.2.2

 

Link to comment
Share on other sites

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

sounds like you did the loader first and after finding the system in network you updated to 6.2.2 (migration)

yes.

 

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

you might try jun's original loader 1.03b with just your vid/pid, mac and sn (that would be original extra.lzma and kernel files from dsm 6.2.0)

if visible in network you can try to update to the now recent 6.2.3, that version uses the same driver as the "old" 6.2.x before 6.2.2

I'm try now.

Link to comment
Share on other sites

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

sounds like you did the loader first and after finding the system in network you updated to 6.2.2 (migration)

Hmm. I again tried the bootloader with the file extra.lzma v0.5_test, and the server became visible on the network. Everything works, updated to DSM 6.2.2 U6.

Link to comment
Share on other sites

On 5/28/2020 at 4:30 PM, richv31 said:

 Just found this post and I have been struggling with HDD hibernation also. Basically, HDD hibernation is completely broken on 1.04b/918+ with an LSI card (mpt3sas). It is broken with the vanilla 1.04b loader as well as the more recent extra.lzma versions.

 

we would need to find a driver that works, with 0.11 its mpt3sys 27.0 the mpt2sas code would be included and the driver mpt2sas driver has a name alias for mpt2sas

i do have a lsi 9211-8i so i would be able to test but its nothing that will be done by tomorrow

usually when doing drivers i check if the driver is working or not, with hardware i use for my own system a can say something about stability or long term experience (and its just one main nas and one for backups)

 

for my new setup system with 6.2.3 918+ i did not use lsi sas controller on purpose, its about going more native so i had chosen ahci (jmb585, pcie 3.0, 5port, beside the 6x onboard)

and i can at least say its not a general problem, the disks go into hibernation and come back without doing anything damage to the raid's (system or data)

Info System 2020-05-30 18:13:17 Internal disks woke up from hibemation.
Info System 2020-05-30 16:20:44 Internal disks woke up from hibemation.

 

On 5/28/2020 at 4:30 PM, richv31 said:

Unsure if this is a drive ordering issue on wake up that is preventing reassembly.

that would only be a point if one disk is slower to wake up (should be in the log as it would be a failed disk)

the order of the disks should be no problem, that behavior of the lsi driver was already there in 6.1.7

any one having problems like this should dig into the logs to see more then raid is broken, and repair, you would need to FIND the source

in general the 918+ has no native scsi/sas support, all this drivers are additional (there are scsi/sas base drivers too not just the device specific drivers) and it might be possible that the kernel config of the 918+ (every platform like brommolow, braswell and apollolake  has there own by synology), afair there is no lsi/scsi supported device in the apollolake platform so there might be things missing from the kernel supporting the drivers

 

also a word on messages about missing fan control and temperature, synology uses specific chips to do it and does not have support for other chips in kernel or driver as they using so its to expect to fail and supporting a myriad of those chips that are used and incorporating them into the way dsm uses it would be to time consuming, i use temp. control from bios for the fan's or if needed  i'd use some external way's like voltage reduction or a controller working on its own

 

Link to comment
Share on other sites

22 minutes ago, aleksey_z said:

I was able to upgrade two servers to 6.2.3-25426.

only 2? you can always try jun's extra.lzma when using 6.2.3  (as long as its not hardware trascoding with 918+) and if a device is missing you can try a extra.lzma i made

Link to comment
Share on other sites

3 часа назад, IG-88 сказал:

only 2?

I did not have time to update the rest of my servers today. I will do it tomorrow.

3 часа назад, IG-88 сказал:

you can always try jun's extra.lzma when using 6.2.3  (as long as its not hardware trascoding with 918+) and if a device is missing you can try a extra.lzma i made

I understood. Thank you for your help.

Link to comment
Share on other sites

10 hours ago, IG-88 said:

 

we would need to find a driver that works, with 0.11 its mpt3sys 27.0 the mpt2sas code would be included and the driver mpt2sas driver has a name alias for mpt2sas

i do have a lsi 9211-8i so i would be able to test but its nothing that will be done by tomorrow

usually when doing drivers i check if the driver is working or not, with hardware i use for my own system a can say something about stability or long term experience (and its just one main nas and one for backups)

 

for my new setup system with 6.2.3 918+ i did not use lsi sas controller on purpose, its about going more native so i had chosen ahci (jmb585, pcie 3.0, 5port, beside the 6x onboard)

and i can at least say its not a general problem, the disks go into hibernation and come back without doing anything damage to the raid's (system or data)


Info System 2020-05-30 18:13:17 Internal disks woke up from hibemation.
Info System 2020-05-30 16:20:44 Internal disks woke up from hibemation.

 

that would only be a point if one disk is slower to wake up (should be in the log as it would be a failed disk)

the order of the disks should be no problem, that behavior of the lsi driver was already there in 6.1.7

any one having problems like this should dig into the logs to see more then raid is broken, and repair, you would need to FIND the source

in general the 918+ has no native scsi/sas support, all this drivers are additional (there are scsi/sas base drivers too not just the device specific drivers) and it might be possible that the kernel config of the 918+ (every platform like brommolow, braswell and apollolake  has there own by synology), afair there is no lsi/scsi supported device in the apollolake platform so there might be things missing from the kernel supporting the drivers

Interesting, I have a jmb585 5 port card on order. My j4105 MB has only 2 onboard ports and a single pcie 2-lane slot that gives me 7 drives (my u-nas chassis can handle 8). Regarding my current system, on wake-up, the system seems to do a staggered (one drive at a time) wake-up. I looked up the error codes (ASC=0x4 ASCQ=0x2) - "Logical Unit Not Ready, Init. Cmd Required Indicates that the drive is ready to go, but it is not spinning. Generally, the drive needs to be spun up." So it looks like DSM is not waiting for the disks to be spun up before attempting to access them.

 

Spoiler

[   51.663675] FAT-fs (synoboot2): fat_set_state: set=1 process=synopkicompatsy pid=11143
[   51.679804] FAT-fs (synoboot2): fat_set_state: set=0 process=synopkicompatsy pid=11143
[   53.741388] ata1.00: failed to get NCQ Send/Recv Log Emask 0x1
[   53.741680] ata1.00: failed to get NCQ Send/Recv Log Emask 0x1
[   53.741744] ata1.00: configured for UDMA/133
[   53.743542] ata1: EH complete
[   53.743563] ata1.00: Enabling discard_zeroes_data
[   58.460556] iSCSI:target_core_rodsp_server.c:1027:rodsp_server_init RODSP server started, login_key(001132123456).
[   58.492479] iSCSI:extent_pool.c:766:ep_init syno_extent_pool successfully initialized
[   58.517653] iSCSI:target_core_device.c:617:se_dev_align_max_sectors Rounding down aligned max_sectors from 4294967295 to 4294967288
[   58.517780] iSCSI:target_core_lunbackup.c:361:init_io_buffer_head 512 buffers allocated, total 2097152 bytes successfully
[   58.593806] iSCSI:target_core_file.c:146:fd_attach_hba RODSP plugin for fileio is enabled.
[   58.593813] iSCSI:target_core_file.c:153:fd_attach_hba ODX Token Manager is enabled.
[   58.593827] iSCSI:target_core_multi_file.c:91:fd_attach_hba RODSP plugin for multifile is enabled.
[   58.593839] iSCSI:target_core_ep.c:786:ep_attach_hba RODSP plugin for epio is enabled.
[   58.593840] iSCSI:target_core_ep.c:793:ep_attach_hba ODX Token Manager is enabled.
[   58.687936] capability: warning: `nginx' uses 32-bit capabilities (legacy support in use)
[   59.079129] loop: module loaded
[ 4851.309911] sd 2:0:0:0: [sdc] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
[ 4851.309926] sd 2:0:0:0: [sdc] tag#0 Sense Key : 0x2 [current]
[ 4851.309934] sd 2:0:0:0: [sdc] tag#0 ASC=0x4 ASCQ=0x2
[ 4851.309942] sd 2:0:0:0: [sdc] tag#0 CDB: opcode=0x28 28 00 00 4c 06 80 00 00 08 00
[ 4851.309949] blk_update_request: I/O error, dev sdc, sector in range 4980736 + 0-2(12)
[ 4856.022445] sd 2:0:0:0: [sdc] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
[ 4856.022459] sd 2:0:0:0: [sdc] tag#0 Sense Key : 0x2 [current]
[ 4856.022466] sd 2:0:0:0: [sdc] tag#0 ASC=0x4 ASCQ=0x2
[ 4856.022474] sd 2:0:0:0: [sdc] tag#0 CDB: opcode=0x28 28 00 00 90 00 08 00 00 08 00
[ 4856.022480] blk_update_request: I/O error, dev sdc, sector in range 9437184 + 0-2(12)
[ 4856.023055] sd 2:0:2:0: [sde] tag#1 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
[ 4856.023062] sd 2:0:2:0: [sde] tag#1 Sense Key : 0x2 [current]
[ 4856.023069] sd 2:0:2:0: [sde] tag#1 ASC=0x4 ASCQ=0x2
[ 4856.023075] sd 2:0:2:0: [sde] tag#1 CDB: opcode=0x28 28 00 00 4c 06 80 00 00 08 00
[ 4856.023080] blk_update_request: I/O error, dev sde, sector in range 4980736 + 0-2(12)
[ 4856.023624] sd 2:0:2:0: [sde] tag#2 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
[ 4856.023630] sd 2:0:2:0: [sde] tag#2 Sense Key : 0x2 [current]
[ 4856.023636] sd 2:0:2:0: [sde] tag#2 ASC=0x4 ASCQ=0x2
[ 4856.023642] sd 2:0:2:0: [sde] tag#2 CDB: opcode=0x28 28 00 00 90 00 08 00 00 08 00
[ 4856.023646] blk_update_request: I/O error, dev sde, sector in range 9437184 + 0-2(12)
[ 4856.024265] sd 2:0:3:0: [sdf] tag#3 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
[ 4856.024272] sd 2:0:3:0: [sdf] tag#3 Sense Key : 0x2 [current]
[ 4856.024281] sd 2:0:3:0: [sdf] tag#3 ASC=0x4 ASCQ=0x2
[ 4856.024291] sd 2:0:3:0: [sdf] tag#3 CDB: opcode=0x28 28 00 00 4c 06 80 00 00 08 00
[ 4856.024296] blk_update_request: I/O error, dev sdf, sector in range 4980736 + 0-2(12)
[ 4856.024849] sd 2:0:3:0: [sdf] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
[ 4856.024855] sd 2:0:3:0: [sdf] tag#0 Sense Key : 0x2 [current]
[ 4856.024860] sd 2:0:3:0: [sdf] tag#0 ASC=0x4 ASCQ=0x2
[ 4856.024866] sd 2:0:3:0: [sdf] tag#0 CDB: opcode=0x28 28 00 00 90 00 08 00 00 08 00
[ 4856.024871] blk_update_request: I/O error, dev sdf, sector in range 9437184 + 0-2(12)
[ 4856.025431] sd 2:0:4:0: [sdg] tag#1 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
[ 4856.025446] sd 2:0:4:0: [sdg] tag#1 Sense Key : 0x2 [current]
[ 4856.025451] sd 2:0:4:0: [sdg] tag#1 ASC=0x4 ASCQ=0x2
[ 4856.025457] sd 2:0:4:0: [sdg] tag#1 CDB: opcode=0x28 28 00 00 4c 06 80 00 00 08 00
[ 4856.025462] blk_update_request: I/O error, dev sdg, sector in range 4980736 + 0-2(12)
[ 4856.026010] sd 2:0:4:0: [sdg] tag#2 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
[ 4856.026016] sd 2:0:4:0: [sdg] tag#2 Sense Key : 0x2 [current]
[ 4856.026021] sd 2:0:4:0: [sdg] tag#2 ASC=0x4 ASCQ=0x2
[ 4856.026027] sd 2:0:4:0: [sdg] tag#2 CDB: opcode=0x28 28 00 00 90 00 08 00 00 08 00
[ 4856.026032] blk_update_request: I/O error, dev sdg, sector in range 9437184 + 0-2(12)
[ 4856.865160] sd 2:0:2:0: [sde] tag#1 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
[ 4856.865182] sd 2:0:2:0: [sde] tag#1 Sense Key : 0x2 [current]
[ 4856.865190] sd 2:0:2:0: [sde] tag#1 ASC=0x4 ASCQ=0x2
[ 4856.865200] sd 2:0:2:0: [sde] tag#1 CDB: opcode=0x35 35 00 00 00 00 00 00 00 00 00
[ 4856.865214] blk_update_request: I/O error, dev sde, sector in range 4980736 + 0-2(12)
[ 4856.865746] md: super_written gets error=-5
[ 4856.865758] md_error: sde1 is being to be set faulty
[ 4856.865763] raid1: Disk failure on sde1, disabling device.
                Operation continuing on 4 devices
[ 4856.866456] sd 2:0:3:0: [sdf] tag#2 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
[ 4856.866465] sd 2:0:3:0: [sdf] tag#2 Sense Key : 0x2 [current]
[ 4856.866472] sd 2:0:3:0: [sdf] tag#2 ASC=0x4 ASCQ=0x2
[ 4856.866480] sd 2:0:3:0: [sdf] tag#2 CDB: opcode=0x35 35 00 00 00 00 00 00 00 00 00
[ 4856.866489] blk_update_request: I/O error, dev sdf, sector 4982400
[ 4856.866918] md: super_written gets error=-5
[ 4856.866938] md_error: sdf1 is being to be set faulty
[ 4856.866952] raid1: Disk failure on sdf1, disabling device.
                Operation continuing on 3 devices
[ 4856.867687] sd 2:0:4:0: [sdg] tag#3 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
[ 4856.867693] sd 2:0:4:0: [sdg] tag#3 Sense Key : 0x2 [current]
[ 4856.867698] sd 2:0:4:0: [sdg] tag#3 ASC=0x4 ASCQ=0x2
[ 4856.867705] sd 2:0:4:0: [sdg] tag#3 CDB: opcode=0x35 35 00 00 00 00 00 00 00 00 00
[ 4856.867711] blk_update_request: I/O error, dev sdg, sector 4982400
[ 4856.868134] md: super_written gets error=-5
[ 4856.868140] md_error: sdg1 is being to be set faulty
[ 4856.868143] raid1: Disk failure on sdg1, disabling device.
                Operation continuing on 2 devices
[ 4867.014224] sd 2:0:0:0: [sdc] tag#1 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
[ 4867.014238] sd 2:0:0:0: [sdc] tag#1 Sense Key : 0x2 [current]
[ 4867.014245] sd 2:0:0:0: [sdc] tag#1 ASC=0x4 ASCQ=0x2
[ 4867.014253] sd 2:0:0:0: [sdc] tag#1 CDB: opcode=0x35 35 00 00 00 00 00 00 00 00 00
[ 4867.014262] blk_update_request: I/O error, dev sdc, sector 4982400
[ 4867.014693] md: super_written gets error=-5
[ 4867.014705] md_error: sdc1 is being to be set faulty
[ 4867.014710] raid1: Disk failure on sdc1, disabling device.
                Operation continuing on 1 devices
[ 4867.035989] RAID1 conf printout:
[ 4867.035997]  --- wd:1 rd:16
[ 4867.036003]  disk 0, wo:1, o:0, dev:sdc1
[ 4867.036008]  disk 1, wo:0, o:1, dev:sdd1
[ 4867.036012]  disk 2, wo:1, o:0, dev:sdg1
[ 4867.036016]  disk 3, wo:1, o:0, dev:sde1
[ 4867.036019]  disk 4, wo:1, o:0, dev:sdf1
[ 4867.040944] RAID1 conf printout:
[ 4867.040952]  --- wd:1 rd:16
[ 4867.040958]  disk 1, wo:0, o:1, dev:sdd1
[ 4867.040962]  disk 2, wo:1, o:0, dev:sdg1
[ 4867.040966]  disk 3, wo:1, o:0, dev:sde1
[ 4867.040970]  disk 4, wo:1, o:0, dev:sdf1
[ 4867.040982] RAID1 conf printout:
[ 4867.040985]  --- wd:1 rd:16
[ 4867.040988]  disk 1, wo:0, o:1, dev:sdd1
[ 4867.040992]  disk 2, wo:1, o:0, dev:sdg1
[ 4867.040995]  disk 3, wo:1, o:0, dev:sde1
[ 4867.040999]  disk 4, wo:1, o:0, dev:sdf1
[ 4867.049937] RAID1 conf printout:
[ 4867.049945]  --- wd:1 rd:16
[ 4867.049951]  disk 1, wo:0, o:1, dev:sdd1
[ 4867.049956]  disk 2, wo:1, o:0, dev:sdg1
[ 4867.049960]  disk 4, wo:1, o:0, dev:sdf1
[ 4867.049968] RAID1 conf printout:
[ 4867.049971]  --- wd:1 rd:16
[ 4867.049975]  disk 1, wo:0, o:1, dev:sdd1
[ 4867.049978]  disk 2, wo:1, o:0, dev:sdg1
[ 4867.049982]  disk 4, wo:1, o:0, dev:sdf1
[ 4867.056935] RAID1 conf printout:
[ 4867.056942]  --- wd:1 rd:16
[ 4867.056948]  disk 1, wo:0, o:1, dev:sdd1
[ 4867.056952]  disk 2, wo:1, o:0, dev:sdg1
[ 4867.056960] RAID1 conf printout:
[ 4867.056963]  --- wd:1 rd:16
[ 4867.056966]  disk 1, wo:0, o:1, dev:sdd1
[ 4867.056970]  disk 2, wo:1, o:0, dev:sdg1
[ 4867.063954] RAID1 conf printout:
[ 4867.063962]  --- wd:1 rd:16
[ 4867.063968]  disk 1, wo:0, o:1, dev:sdd1
 

Quote

also a word on messages about missing fan control and temperature, synology uses specific chips to do it and does not have support for other chips in kernel or driver as they using so its to expect to fail and supporting a myriad of those chips that are used and incorporating them into the way dsm uses it would be to time consuming, i use temp. control from bios for the fan's or if needed  i'd use some external way's like voltage reduction or a controller working on its own

 

I understand and I don't need temps or fan speeds. The interesting part is that something changed for ds3615 between 6.2.2 and 6.2.3 with these errors now showing up regularly in scemd.log. Also at the same time HDD hibernation stopped working in 3615/6.2.3 (drives will not hibernate) and I assume this is due to these errors and the log writing. I don't know if this issue is LSI controller specific or it also applies to ahci drives, I will test. Also, these errors are not present in the 918+/6.2.3 logs.

 

This is  how it looks for me in using the lsi 9211-8i controller:

 

Loader OS/ver/driver HDD go into hibernate HDD come out of hibernate
1.03b 3615/6.2.2/mpt2sas OK OK
1.03b 3615/6.2.3/mpt2sas NO n/a
1.04b 918+/6.2.2/mpt3sas OK OK for basic volume, Crash for RAID volumes
1.04b 918+/6.2.3/mpt3sas OK
OK for basic volume, Crash for RAID volumes

 

Edited by richv31
more info added on errors
  • Like 1
Link to comment
Share on other sites

On 5/2/2020 at 5:30 AM, IG-88 said:

 

any source code for a driver you can provide as a link?

do you have the pci vendor/device id of that card like [1924:0813] you can see with lspci or in dmesg log?

 

shortly had someone asking about a solarflare nic

https://xpenology.com/forum/topic/21663-driver-extension-jun-103b104b-for-dsm622-for-3615xs-3617xs-918/?do=findComment&comment=142932

it was for a solarflare sfn5162f and it looked like it might be supported already, yours might be older so it might work too

 

from reading a few specs is seems to use the SFC9020 controller and that would be pci id [1924:0803] and this id is in the driver sfc.ko of the 0.5 extra.lzma for 3615 and 3617

 

I have a Solarflare  SFN7122  which appears to use the SFC9120 controller. PCI ID: 1924:0903. Is that id listed in the sfc.ko driver included in the extra.lzma for 3615 & 3617?

 

My current config

dsm version 6.2.2

ds3617xs

Extracted the files needed from the dsm firmware & added the extra.lzma to the synoboot & used the steps listed in the beginning

I only see a single network interface under networks. It seems to only see the built in nic as I don't see other two interfaces for the Solarflare 10G dual port SFP+. I do have mac1, mac2, mac3 specified in the cfg.

I seem to see the sfc driver listed when I do an lsmod | grep sfc. Just unsure if the SFC9120 controller & model SFN 7122 is in this driver.

 


:~$ lsmod | grep sfc
sfc                   172339  0 
mdio                    3301  5 alx,sfc,cxgb,bnx2x,cxgb3
i2c_algo_bit            5128  1 sfc

 

Edit:

I am using the following extra.lzma:   DS3617: extra.lzma for loader 1.03b_mod ds3617 DSM 6.2.2 v0.5_test

When searching the forum I found a post where you mentioned this controller SFC9120 was listed in the sfc driver in the extra lzma 0.1. Is it still included in the v0.5_test version I am using?

 

LINK: 

 

Edited by rcriot25
Link to comment
Share on other sites

21 minutes ago, rcriot25 said:

I have a Solarflare  SFN7122  which appears to use the SFC9120 controller. PCI ID: 1924:0903. Is that id listed in the sfc.ko driver included in the extra.lzma for 3615 & 3617?

 

918+ driver from kernel 4.4.59 support:

1924:0923
1924:1903
1924:0903
1924:0813
1924:0803
1924:0710
1924:0703

 

3615 and 3617 from kernel 3.10.105 support

1924:813
1924:803
1924:710
1924:703

 

i fond a driver from 4/2020 but it does not compile because of various  errors and warnings

Link to comment
Share on other sites

1 hour ago, IG-88 said:

918+ driver from kernel 4.4.59 support:

1924:0923
1924:1903
1924:0903
1924:0813
1924:0803
1924:0710
1924:0703

 

3615 and 3617 from kernel 3.10.105 support

1924:813
1924:803
1924:710
1924:703

 

i fond a driver from 4/2020 but it does not compile because of various  errors and warnings

Thanks so much for posting that info! I will switch back to 918+ and try it with the current extra.lzma. i think if i read correctly in order to have more than 2 nic i have to update synoinfo. Will do all that and see if it works. Thanks again!

Link to comment
Share on other sites

  • 3 weeks later...

It is RTL8151, i couldnt see it listed in your post as a support nic. When i try to boot with an updated usb with your updated extra.lzma v0.5_test on partition 2 it fails to show up in find.synology. The mobo I am using is an MSI MS-7906.

Link to comment
Share on other sites

On 6/25/2020 at 8:10 AM, Mitt27 said:

It is RTL8151, i couldnt see it listed in your post as a support nic. When i try to boot with an updated usb with your updated extra.lzma v0.5_test on partition 2 it fails to show up in find.synology. The mobo I am using is an MSI MS-7906.

the board seems to be oem and msi has no info about it

please do a "lspci -k" on a system where the nic so working so i can see is vendor and product id and the driver used

Link to comment
Share on other sites

24 minutes ago, IG-88 said:

the board seems to be oem and msi has no info about it

please do a "lspci -k" on a system where the nic so working so i can see is vendor and product id and the driver used

 

Hi,

 

Yes thats correct its an old oem build that I was able to repurpose for a bare metal install and it has been going strong for some 5 years or so. I have copied the output below, thats very much for taking a look.

 

Matt@DiskStation:/$ lspci -k
0000:00:00.0 Class 0600: Device 1022:1422
        Subsystem: Device 103c:2b17
0000:00:02.0 Class 0600: Device 1022:1424
0000:00:02.1 Class 0604: Device 1022:1425
        Kernel driver in use: pcieport
0000:00:03.0 Class 0600: Device 1022:1424
0000:00:03.4 Class 0604: Device 1022:1426
        Kernel driver in use: pcieport
0000:00:04.0 Class 0600: Device 1022:1424
0000:00:10.0 Class 0c03: Device 1022:7814 (rev 09)
        Subsystem: Device 103c:2b17
        Kernel driver in use: xhci_hcd
0000:00:10.1 Class 0c03: Device 1022:7814 (rev 09)
        Subsystem: Device 103c:2b17
        Kernel driver in use: xhci_hcd
0000:00:11.0 Class 0106: Device 1022:7801 (rev 40)
        Subsystem: Device 103c:2b17
        Kernel driver in use: ahci
0000:00:12.0 Class 0c03: Device 1022:7807 (rev 11)
        Subsystem: Device 103c:2b17
        Kernel driver in use: ohci_hcd
0000:00:12.2 Class 0c03: Device 1022:7808 (rev 11)
        Subsystem: Device 103c:2b17
        Kernel driver in use: ehci-pci
0000:00:13.0 Class 0c03: Device 1022:7807 (rev 11)
        Subsystem: Device 103c:2b17
        Kernel driver in use: ohci_hcd
0000:00:13.2 Class 0c03: Device 1022:7808 (rev 11)
        Subsystem: Device 103c:2b17
        Kernel driver in use: ehci-pci
0000:00:14.0 Class 0c05: Device 1022:780b (rev 16)
        Subsystem: Device 103c:2b17
0000:00:14.2 Class 0403: Device 1022:780d (rev 01)
        Subsystem: Device 103c:2b17
0000:00:14.3 Class 0601: Device 1022:780e (rev 11)
        Subsystem: Device 103c:2b17
0000:00:14.4 Class 0604: Device 1022:780f (rev 40)
0000:00:14.5 Class 0c03: Device 1022:7809 (rev 11)
        Subsystem: Device 103c:2b17
        Kernel driver in use: ohci_hcd
0000:00:18.0 Class 0600: Device 1022:141a
0000:00:18.1 Class 0600: Device 1022:141b
0000:00:18.2 Class 0600: Device 1022:141c
0000:00:18.3 Class 0600: Device 1022:141d
0000:00:18.4 Class 0600: Device 1022:141e
0000:00:18.5 Class 0600: Device 1022:141f
0000:01:00.0 Class 0300: Device 10de:1380 (rev a2)
        Subsystem: Device 3842:3753
0000:01:00.1 Class 0403: Device 10de:0fbc (rev a1)
        Subsystem: Device 3842:3753
0000:02:00.0 Class 0200: Device 10ec:8168 (rev 0c)
        Subsystem: Device 103c:2b17
        Kernel driver in use: r8168
0001:00:02.0 Class 0000: Device 8086:6f04 (rev ff)
0001:00:02.2 Class 0000: Device 8086:6f06 (rev ff)
0001:00:03.0 Class 0000: Device 8086:6f08 (rev ff)
0001:00:03.2 Class 0000: Device 8086:6f0a (rev ff)
0001:00:1f.0 Class 0000: Device 8086:8c54 (rev ff)
0001:00:1f.3 Class 0000: Device 8086:8c22 (rev ff)
0001:06:00.0 Class 0000: Device 1b4b:1475 (rev ff)
0001:08:00.0 Class 0000: Device 1b4b:9235 (rev ff)
0001:09:00.0 Class 0000: Device 8086:1533 (rev ff)
0001:0c:00.0 Class 0000: Device 8086:1533 (rev ff)
0001:0d:00.0 Class 0000: Device 8086:1533 (rev ff)
Matt@DiskStation:/$ 
 

Link to comment
Share on other sites

11 minutes ago, Mitt27 said:

0000:02:00.0 Class 0200: Device 10ec:8168 (rev 0c)
        Subsystem: Device 103c:2b17
        Kernel driver in use: r8168

 

not sure where the fancy name came from you where using but from its device id its just the usual realtek nic and the driver is in the package and often used

whatever you tried, i guess the system was not booting at all or you used the wrong extra.lzma

maybe just try with jun's original extra.lzma (loader 1.02b)

 

when trying loader 1.03b keep in mind that one does only work in legacy bios mode (csm) not in uefi and it also need the legacy boot device selected from the list (no uefi in boot device name)

Edited by IG-88
Link to comment
Share on other sites

4 minutes ago, IG-88 said:

 

not sure where the fancy name came from you where using but from its device id its just the usual realtek nic and the driver is in the package and often used

whatever you tried, i guess the system was not booting at all or you used the wrong extra.lzma

maybe just try with jun's original extra.lzma (loader 1.02b)

 

when trying loader 1.03b keep in mind that one does only work in legacy bios mode (csm) not in uefi and it also need the legacy boot device selected from the list (no uefi in boot device name)

 
ok thanks will give it another try, assume I can just use the standard 1.03b bootloader and not worry about your additional steps for copying the kernal from dsm or do I still need to so that? I was getting as far as the bootloader menu and was able to select the first option but it just wouldnt go on to show in find.synology, is there maybe a way to see whats going on once the boot loader is running or does the screen just stop refreshing like it says on the screen?

 

thanks

Link to comment
Share on other sites

3 hours ago, Mitt27 said:

assume I can just use the standard 1.03b bootloader and not worry about your additional steps for copying the kernal from dsm or do I still need to so that?

depends on the dsm version you want to install but just for trying to find it in network you just boot up 1.03b as it comes, even the vid/pid (usb) part is not important as long as its just about loader booting and not installing dsm

the kernel and extra together is needed for 6.2.2, on 6.2.3 i'd suggest it but in most case the newer extra will work with the older 6.2.0 kernel in the loader

 

3 hours ago, Mitt27 said:

I was getting as far as the bootloader menu and was able to select the first option but it just wouldnt go on to show in find.synology

the basic booting is working but in case of loader 1.03b you could still fail when the uefi boot device is used

 

3 hours ago, Mitt27 said:

is there maybe a way to see whats going on once the boot loader is running or does the screen just stop refreshing like it says on the screen?

only way is to use a serial cable and a console (like putty) to see whats going on during boot

Edited by IG-88
  • Like 1
Link to comment
Share on other sites

Dear gurus and expirienced users,

Please help me please!

 

Is these Mini-PC compatible with Synology DeskStation?

 

1. GIGABYTE BRIX GB-BPCE-3455 (Apollo Lake)

 

Intel® Celeron® Processor J3455, Gigabit LAN (Realtek RTL8111HS) Apollo Lake

 

Full Specifications:

https://download.gigabyte.com/FileList/Manual/brix_apollo-lake_datasheet.pdf

 

and/or

 

2. GIGABYTE BRIX GB-BLCE-4105 (Gemini Lake)

 

Intel® Celeron® Processor J4105, Gigabit LAN (Realtek RTL8111HS)

 

Full Specifications:

http://download.gigabyte.cn/FileList/Manual/brix_gemini-lake-dual_datasheet.pdf

 

Advice please which model to choice for installation of Synology DSM.

And tell me please which bootloader I must to use for it  as DS918+ or RS3617xs/RS3615xs ?

Thank you very much in advance for your help!

Link to comment
Share on other sites

21 minutes ago, userru said:

Is these Mini-PC compatible with Synology DeskStation?

apollo lake and gemini lake work both with 918+ dsm 6.2.3 with hardware transcoding and loader 1.04b

should work with these barebones but only having 1x sata is kind of pointless or dangerous for a nas

also not much options to expand beside 2.5/5G usb nic

just to note, dsm does not support wifi, m.2 ssd's are ootb only supported as cache drive and usb hdd's can't be used a raid data disks (also ootb as dsm comes)

if it needs to be low cost then maybe a mini itx gemini lake with 4 sata ports is a option, the case might be a little bigger that way but you dont waste on wifi and have more option

or maybe look into open media vault, its not a (part) closed source appliance like dsm and its much more like a normal linux that can be expanded and tweaked,

 

Link to comment
Share on other sites

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

apollo lake and gemini lake work both with 918+ dsm 6.2.3 with hardware transcoding and loader 1.04b

 

Dear IG-88,

Thank you so much for your swift reply. I would like to use it for home close test, before buying. Trefore I have a question more,

is this Ethernet Realtek RTL8111HS also compatible with Synology DSM?

Since I read on the forum that some users with analogues models as Intel NUC with Ethernet Realtek RTL8111HN and  Ethernet Realtek RTL8111H has a problems with Lan.

 

With this Ethernet Realtek RTL8111HS will be all is ok?

Thank you so much again!

 

Link to comment
Share on other sites

2 minutes ago, userru said:

s this Ethernet Realtek RTL8111HS also compatible with Synology DSM?

same driver as rtl8168 aka r8168.ko

you can check with the network drviver list here, its still valid (i added some driver and refreshed some for the newer extra's for 6.2.3)

https://xpenology.com/forum/topic/12859-driver-extension-jun-103a2dsm62x-for-ds918/

 

6 minutes ago, userru said:

Since I read on the forum that some users with analogues models as Intel NUC with Ethernet Realtek RTL8111HN and  Ethernet Realtek RTL8111H has a problems with Lan.

imho most of the problems seen are board vendor made and not specific to a chip, at least i have not spotted a pattern yet about one chip not working in general

i use the latest driver source for  r8168 from the realtek website so so all chip revisions should work

 

10 minutes ago, userru said:

With this Ethernet Realtek RTL8111HS will be all is ok?

no guarantees, i use a realtek 8118 with the r8168 driver and that works ok (just some tests, i usually use a 10G nic for file access to my nas)

Link to comment
Share on other sites

  

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

same driver as rtl8168 aka r8168.ko

you can check with the network drviver list here, its still valid (i added some driver and refreshed some for the newer extra's for 6.2.3)

https://xpenology.com/forum/topic/12859-driver-extension-jun-103a2dsm62x-for-ds918/

 

Dear IG-88,

Thank you so much for your swift and promt reply.

I will try on the days and let you to know after it.

Have a nice day!

 

Edited by userru
Link to comment
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.

×
×
  • Create New...