IG-88

Driver extension jun 1.02b/DSM6.1.x for 3615xs / 3617xs / 916+

Recommended Posts

5 hours ago, zOnDeR said:

I did everything according to the instructions on which you gave the link

-(DSM 6.0.2, v1.01 loader, Customized extra.lzma ramdisk.)

please open a new topic then if you want to go deeper into 6.0

Share this post


Link to post
Share on other sites

Hello,

 

I just managed to run Xpenoboot DS3615xs 5.2 5644 with the DSM_DS3615xs_5644.pat.

I works perfectly fine, I just can't use the first HDD slot but this should be easily fixed with BIOS access and modified Boot order.

 

Any idea why it would work under 5.2.5644 and not above ?

If you think it could be driver related, let me know if I can get some interesting data output for you to put your eyes on. If not, next post will be in a more appropriate thread.

 

Thanks,

 

 

Share this post


Link to post
Share on other sites
Posted (edited)

the interesting part for 6.1 would be the log when loading the realtek driver (on the booting/running 6.1 system), from the lspci with ubuntu 16.04 you did we already know the drivers needed for the hardware (r8169 for nic and ahci for storage)

kind of crazy that it does get a dhcp adress and cant be reached/found in network, in theory when ping does work the network is up and running so it might be something else, but that thing should happen too when using a different nic i guess

 

did you configure the real mac address in grub.cfg with 6.1?

also disconnecting any additional hardware when trying to install 6.1 could be a thing

 

Edited by IG-88

Share this post


Link to post
Share on other sites

Hi @IG-88. Can you please look into r8168.ko for DS3617xs? It seems that the new DSM 6.1.6 is breaking that module. I have seen two reports of people not being able to have network access after the update. Both users where running DS3617xs with following boards: EP45-DS3L (Realtek 8111C) and N3150ITX-DC (Realtek RTL8111GR). Not sure if DS3615xs is also affected.

Share this post


Link to post
Share on other sites

 

On 3/29/2018 at 2:22 PM, Polanskiman said:

Can you please look into r8168.ko for DS3617xs? It seems that the new DSM 6.1.6 is breaking that module.

 

Nothing general I'd say

I have a pci-e card with rtl8168e for testing

jun's 1.02b (3617, only vid/pid changed), extra.lzma 4.7, dsm 6.1.6 fresh install -> no problems

I will do a update test later (6.1.5->6.1.6)

 

there seem to be unsuccessfuls with 3617 on esxi too, maybe nothing to do with the nic?

 

i could do a test version with just the original kernel driver instead of the realtek driver if that helps

 

also there is a entry with success with a 8111C

    - Outcome of the update: SUCCESSFUL
    - DSM version prior update: DSM 6.1.5
    - Loader version and model: JUN'S LOADER v1.02b - DS3617xs
    - Using custom extra.lzma: YES - extra.lzma for DS3617 v4.5 made by IG-88
    - Installation type: BAREMETAL Asus  P5Q-EM
    - Additional comments: REBOOT REQUIRED

 

from my extra.lzma change log

[13.12.2017] new 4.3 with newer realtek r8168/r8169 drivers

so if he used 4.5 it has the same drivers as the actual 4.7

 

EDIT: also tested update 6.1..5->6.1.6, no problems found

 

Share this post


Link to post
Share on other sites

Yeah strange not sure what is going on. Didn’t actually look in details and don’t have those nics so couldn’t test. It was just a guess because the two first who reported issues had two different realtek NICs using that module. But something is wrong with ds3617xs because even re-imaging the loader and trying to reinstall did not work for them. VMs are also experiencing issues. Only using 3615xs did work for all of them. As for that entry it was posted after.

 

 

Share this post


Link to post
Share on other sites
Le 28/03/2018 à 00:53, IG-88 a dit :

did you configure the real mac address in grub.cfg with 6.1?

also disconnecting any additional hardware when trying to install 6.1 could be a thing

 

 

I've ran another set of tests to check this area.

 

I can confirm that the mac address i get with any working setup is 00:26:2d:01:d2:2a

I have tried 6.1 with this mac@ in grub cfg with no disk, same result as usual : request an IP and is ping-able but is not discovered by the syno assistant and cannot be directly reached with a browser.

I have tried 6.1 with a random mac@ in grub.cfg with no disk, same as above.

 

Is there a tutorial that could guide me on how to provide the log for driver init on 6.1 ?

 

Just in case, here's an extract of my grub.cfg :

set vid=0x0951
set pid=0x1666
set sn=1430LWN003630
set mac1=00262D01D22A
set rootdev=/dev/md0
set netif_num=1
set extra_args_3615=''

 

 

Share this post


Link to post
Share on other sites
On 3/29/2018 at 2:22 PM, Polanskiman said:

Hi @IG-88. Can you please look into r8168.ko for DS3617xs? It seems that the new DSM 6.1.6 is breaking that module. I have seen two reports of people not being able to have network access after the update. Both users where running DS3617xs with following boards: EP45-DS3L (Realtek 8111C) and N3150ITX-DC (Realtek RTL8111GR). Not sure if DS3615xs is also affected.

There seems to be something odd with 6.1.6, on a ESXi VM with DS3617xs the paravirtual controller and virtual LSI SAS controller don't load either:

Loading module vmw_pvscsi[ 3.849379] general protection fault
Loading module mptsas[ 3.997779] BUG: unable to handle kernel paging request

 

Share this post


Link to post
Share on other sites
On 3/31/2018 at 9:29 PM, swords80 said:

There seems to be something odd with 6.1.6, on a ESXi VM with DS3617xs the paravirtual controller and virtual LSI SAS controller don't load either:

 

Loading module vmw_pvscsi[ 3.849379] general protection fault

Loading module mptsas[ 3.997779] BUG: unable to handle kernel paging request

 

However, if Xpenology ESXi VM is booted with a USB key attached to the virtual USB controller, these modules load fine.

root@testnas:/etc# cat /proc/cmdline
syno_hdd_powerup_seq=0 HddHotplug=0 syno_hw_version=DS3617xs vender_format_version=2 console=ttyS0,115200n8
withefi quiet root=/dev/md0 sn=[redacted] mac1=[redacted] netif_num=1
root@testnas:/etc# cat /etc.defaults/VERSION
majorversion="6"
minorversion="1"
productversion="6.1.6"
buildphase="GM"
buildnumber="15266"
smallfixnumber="0"
builddate="2018/03/26"
buildtime="16:58:27"
root@testnas:/etc# lsmod | grep mptsas
mptsas                 38463  2
mptscsih               18705  2 mptsas,mptspi
mptbase                61898  4 mptctl,mptsas,mptspi,mptscsih
root@testnas:/etc# lsmod | grep vmw_pvscsi
vmw_pvscsi             15239  0

 

 

Share this post


Link to post
Share on other sites
On 3/31/2018 at 1:30 PM, BonanzaCreek said:

Is there a tutorial that could guide me on how to provide the log for driver init on 6.1 ?

 

you would need a serial port an the system that installs dsm and you would connect that with a serial cable to another system and use putty over serial as console

for most people thats to much (they dont even have a serial cable and if the computer that is used as console does not have a serial ports you would also need a usb2serial converter), in you case the easiest way would be to install a 2nd nic, install dsm with it and when dsm boots normal you can (over network with 2nd nic) check the logs to see whats wrong with the onboard realtek and if its to much hassle just leave the 2nd nic and use it for dsm and ignore the onbard nic

 

Share this post


Link to post
Share on other sites

EP45-DS3L user here. NIC broken with latest FW and DS3617xs indeed, works with DS3615xs though. JFYI.

Share this post


Link to post
Share on other sites

Thanks for the help @IG-88

 

The ex-490 does not have a serial or ILO.

I also tried to add a second NIC using a USB/RJ45 cable, but apparently it is not recognized by the system.

 

I guess that will be the end of the line.

 

For general knowledge, 5.2.5967 works perfectly fine with the ex490 bare metal without any tinkering in the BIOS and XPEnoboot_DS3615xs_5.2-5644.4 loader.

Share this post


Link to post
Share on other sites

Hi all. Faced with strange bug, maybe someone could help.

Got an ASUS P9A-I/C2750/SAS/4L motherboard with two Marvell 88SE9485 controllers onboard.

Made a bootable usb flash with 3617xs image, put there extra.lzma v4.7, installed DSM successfully.

All works fine, except sas-controllers:


admin@fSyn:/$ lspci -k | grep 'Kernel driver'
        Kernel driver in use: pcieport
        Kernel driver in use: pcieport
        Kernel driver in use: pcieport
        Kernel driver in use: pcieport
        Kernel driver in use: igb
        Kernel driver in use: igb
        Kernel driver in use: igb
        Kernel driver in use: igb
        Kernel driver in use: ehci-pci
        Kernel driver in use: ahci
        Kernel driver in use: lpc_ich
admin@fSyn:/$ lsmod | grep mvsas
mvsas                  53061  0
admin@fSyn:/$ lspci -v
...
0000:01:00.0 Class 0104: Device 1b4b:9485 (rev c3)
        Subsystem: Device 1043:8635
        Flags: bus master, fast devsel, latency 0, IRQ 7
        Memory at de240000 (64-bit, non-prefetchable) [size=128K]
        Memory at de200000 (64-bit, non-prefetchable) [size=256K]
        Expansion ROM at de260000 [disabled] [size=64K]
        Capabilities: <access denied>

0000:02:00.0 Class 0104: Device 1b4b:9485 (rev c3)
        Subsystem: Device 1043:8635
        Flags: bus master, fast devsel, latency 0, IRQ 7
        Memory at de140000 (64-bit, non-prefetchable) [size=128K]
        Memory at de100000 (64-bit, non-prefetchable) [size=256K]
        Expansion ROM at de160000 [disabled] [size=64K]
        Capabilities: <access denied>
...

For some reason driver doesn't recognize controller.

Checked device id's in kernel sources at https://sourceforge.net/projects/dsgpl/files/Synology NAS GPL Source/15047branch/broadwell-source/ - mvsas driver have these ids in mv_init.c

There is nothing in dmesg regarding mvsas.

Also all work fine on Ubuntu 17.10

Have no idea what to check next.

Please help :)

Share this post


Link to post
Share on other sites

Motherboard GA-G31M-ES2L
Intel® Celeron® E3300 2.50 GHz processor
Memory two modules of 1 GB DDR2 Patriot Memory PSD21G8002
One hard drive WD Red WD40EFRX, 4TB, HDD, SATA III, 3.5 "
Two drives ST4000DM005-2DP166 4TB, HDD, SATA III, 3.5 "
Two disks lWD Caviar Black WD1003FZEX 1Tb SATA III, 3.5 "

Controller Adaptec RAID ASR-5405Z

When installing DSM DSM 6.1.5 with the modified Customized extra.lzma ramdisk, unfortunately Controller Adaptec RAID ASR-5405Z did not detect the hard drive.

cat /var/log/dmesg >> /volumeUSB1/usbshare/dmesg.log

dmesg.log

admin@NAS13:/$ lspci -k | grep 'Kernel driver'  

admin@NAS13:/$ lspci -k | grep 'Kernel driver'
        Kernel driver in use: pcieport
        Kernel driver in use: pcieport
        Kernel driver in use: pcieport
        Kernel driver in use: uhci_hcd
        Kernel driver in use: uhci_hcd
        Kernel driver in use: uhci_hcd
        Kernel driver in use: uhci_hcd
        Kernel driver in use: ehci-pci
        Kernel driver in use: lpc_ich
        Kernel driver in use: ata_piix
        Kernel driver in use: aacraid
        Kernel driver in use: e1000e
        Kernel driver in use: atl1c

Hide  
How to fix?
sorry for my English
Thank you!

Share this post


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

Controller Adaptec RAID ASR-5405Z

When installing DSM DSM 6.1.5 with the modified Customized extra.lzma ramdisk, unfortunately Controller Adaptec RAID ASR-5405Z did not detect the hard drive.

cat /var/log/dmesg >> /volumeUSB1/usbshare/dmesg.log

dmesg.log

 

the driver crashed on load, try to install dsm 6.1.3 (thats the version the source for the drivers is used) also try to use the new 4.8 version (it will contain a frehly compiled version, but i dont think that will fix it, the drivers seemed to be compiled in a way that thea where working, could also be a incompatibility from synology or a general one that was fixed in later kernel versions)

Share this post


Link to post
Share on other sites
Posted (edited)
5 hours ago, tr33ks said:

Hi all. Faced with strange bug, maybe someone could help.

Got an ASUS P9A-I/C2750/SAS/4L motherboard with two Marvell 88SE9485 controllers onboard.

...

- mvsas driver have these ids in mv_init.c

There is nothing in dmesg regarding mvsas.

Also all work fine on Ubuntu 17.10

Have no idea what to check next.

Please help :)

 

found this patch

https://marc.info/?l=linux-scsi&m=146005515401214

i will change the kernel source and compile a new driver, new extra.lzma version 4.8 should be ready later this evening

 

Edited by IG-88

Share this post


Link to post
Share on other sites
В 08.04.2018 в 22:11, IG-88 сказал:

 

found this patch

https://marc.info/?l=linux-scsi&m=146005515401214

i will change the kernel source and compile a new driver, new extra.lzma version 4.8 should be ready later this evening

 

 

Thanks for help.

Took me a while to find a com cable, but now i have a log.

Something went wrong.

log  

:: Loading module sx8 ... [  OK  ]
:: Loading module aacraid ... [  OK  ]
:: Loading module aic94xx ... [  OK  ]
:: Loading module 3w-9xxx ... [  OK  ]
:: Loading module 3w-sas ... [  OK  ]
:: Loading module mvumi ... [  OK  ]
:: Loading module mvsas[    8.208271] sd 3:0:0:0: [synoboot] No Caching mode page found
[    8.214351] sd 3:0:0:0: [synoboot] Assuming drive cache: write through
[    8.224186] sd 3:0:0:0: [synoboot] No Caching mode page found
[    8.230211] sd 3:0:0:0: [synoboot] Assuming drive cache: write through
[    8.491062] sd 3:0:0:0: [synoboot] No Caching mode page found
[    8.496934] sd 3:0:0:0: [synoboot] Assuming drive cache: write through
[   12.950713] BUG: unable to handle kernel NULL pointer dereference at 0000000000000078
[   12.958773] IP: [<ffffffff81329ed2>] sas_scsi_recover_host+0xf2/0xd20
[   12.965356] PGD 4673a5067 PUD 4670a7067 PMD 0
[   12.969950] Oops: 0002 [#1] SMP
[   12.973296] Modules linked in: mvsas(+) mvumi 3w_sas 3w_9xxx aic94xx aacraid sx8 mpt3sas(O) mpt2sas(O) megaraid_sas ata_piix mptctl mptsas mptspi mptscsih mptbase scsi_transport_spi megaraid megaraid_mbox megaraid_mm vmw_pvscsi BusLogic usb_storage xhci_hcd uhci_hcd ohci_hcd ehci_pci ehci_hcd usbcore usb_common mv14xx(O) el000(O)
[   13.003617] CPU: 0 PID: 3982 Comm: scsi_eh_2 Tainted: G           O 3.10.102 #15266
[   13.011417] Hardware name: ASUS P9A-I/C2750/SAS/4L/P9A-I/C2750/SAS/4L, BIOS 1902 11/07/2016
[   13.019944] task: ffff88046ad3f800 ti: ffff8804669c8000 task.ti: ffff8804669c8000
[   13.027555] RIP: 0010:[<ffffffff81329ed2>]  [<ffffffff81329ed2>] sas_scsi_recover_host+0xf2/0xd20
[   13.036601] RSP: 0000:ffff8804669cbda8  EFLAGS: 00010296
[   13.041993] RAX: 0000000000000078 RBX: ffff8804669af800 RCX: 000000000000000e
[   13.049254] RDX: 0000000000000032 RSI: 0000000000000246 RDI: ffffffff81a66968
[   13.056528] RBP: ffff8804669af800 R08: 000000000000000a R09: 000000000000fffe
[   13.063795] R10: 00007fcc7ae1d9d0 R11: 00000000000002bc R12: ffff88046ad3f800
[   13.071079] R13: ffff8804669cbe78 R14: ffff88046ad3f800 R15: 0000000000000000
[   13.078348] FS:  0000000000000000(0000) GS:ffff88047fc00000(0000) knlGS:0000000000000000
[   13.086568] CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
[   13.092421] CR2: 0000000000000078 CR3: 0000000469fe0000 CR4: 00000000001007f0
[   13.099687] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[   13.106962] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[   13.114254] Stack:
[   13.116310]  0000000000000000 ffff88046ad3f800 ffffffff8106522b 0000000000000000
[   13.123942]  ffff8804669af800 0000000000000000 000000016aca5410 0000000000000078
[   13.131562]  0000000000000080 0000000000000198 0000000000009000 ffff8804669af888
[   13.139185] Call Trace:
[   13.141690]  [<ffffffff8106522b>] ? idle_balance+0x11b/0x140
[   13.147435]  [<ffffffff81060103>] ? pick_next_task_fair+0x63/0x160
[   13.153714]  [<ffffffff8130f0bb>] ? scsi_error_handler+0x9b/0x470
[   13.159949]  [<ffffffff814aee97>] ? __schedule+0x3a7/0x8e0
[   13.165532]  [<ffffffff8130f020>] ? scsi_eh_get_sense+0x100/0x100
[   13.171741]  [<ffffffff810501ff>] ? kthread+0xaf/0xc0
[   13.176885]  [<ffffffff81050150>] ? kthread_create_on_node+0x110/0x110
[   13.183544]  [<ffffffff814b0f48>] ? ret_from_fork+0x58/0x90
[   13.189232]  [<ffffffff81050150>] ? kthread_create_on_node+0x110/0x110
[   13.195874] Code: 58 80 00 01 fb 8b 8b dc 00 00 00 8b 93 d8 00 00 00 48 c7 c6 e0 6d 65 81 48 c7 c7 90 91 72 81 31 c0 e8 64 04 18 00 48 8b 44 24 38 <f0> 80 08 08 48 8b 83 10 05 00 00 4c 8b 6c 24 68 48 8b 8b c8 00
[   13.216398] RIP  [<ffffffff81329ed2>] sas_scsi_recover_host+0xf2/0xd20
[   13.223084]  RSP <ffff8804669cbda8>
[   13.226640] CR2: 0000000000000078
[   13.230040] ---[ end trace acef4991e89cc10b ]---

Hide  

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

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

Create an account

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

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now