Jump to content
XPEnology Community

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


IG-88

Recommended Posts

16 minutes ago, IG-88 said:

 

that driver is part of jun's 1.02 loader so its available for a while

 

I was trying to figure it out another ways, but didn't realize that your extra file is updated, same with Jun's loaders. Shame on me, so lame. But trust me, I am really excited now thanks to you

Edited by leeon82
Link to comment
Share on other sites

On ‎12‎/‎13‎/‎2017 at 11:57 AM, 4sag said:

nvme support ?


lspci -k | grep 'Kernel driver'
        Kernel driver in use: pcieport
        Kernel driver in use: pcieport
        Kernel driver in use: ehci-pci
        Kernel driver in use: pcieport
        Kernel driver in use: pcieport
        Kernel driver in use: pcieport
        Kernel driver in use: pcieport
        Kernel driver in use: ehci-pci
        Kernel driver in use: lpc_ich
        Kernel driver in use: ahci
        Kernel driver in use: hpilo
        Kernel driver in use: uhci_hcd
        Kernel driver in use: tg3
        Kernel driver in use: tg3
        Kernel driver in use: xhci_hcd
        Kernel driver in use: nvme

fdisk -l
Disk /dev/nvme0n1: 238.5 GiB, 256060514304 bytes, 500118192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

in syno ds3615xs 6.1.4-15217.3 not disk nvme !

256 ГБ SSD M.2 накопитель Intel 600p [SSDPEKKW256G7]


No Synology build currently has disk support for NVMe devices.  FSxxxx only support SATA/SAS. NVMe slots on DS918+, and M2D17 M.2 SATA slots are only for SSD Cache (show up only as Cache Device, not disk), at least for now. The above is evidence that the hardware is being recognized and the device is working with the driver loaded in extra.lzma.  Just DSM is not seeing it, probably due to /dev/nvme* name and DSM internal scripting for /dev/sd*.  IG88, please keep the nvme module in!

 

I am motivated to find a hack to recognize NVMe as disk, as I have ordered some NVMe drives I would like to use for system/swap/docker.  I will document in a new thread, and not clutter this one up with discussion about it.

 

Edited by flyride
Link to comment
Share on other sites

hi,

 

i had no intention of removing it

as long as it does not interfere with the normal use of the extra.lzma its a nice option, its still possible to use nvme on a "individual" level like tweaking of udev to get it recognized as /dev/sd or doing any kind of scripted mounting, if nvme gets used it will start by experimenting and that's easier possible if the device is available

 

Link to comment
Share on other sites

Hello guys,

I'm coming after few hours, weeks to search why i'm not able to update my xpenology 5.2

For information the device is : HP Proliant Gen8 1610T

I've tried many time to flash my usb drive, with & without the extra.irma ...

 

My start is locked on : Starting kernel.

But network seems to be off.

My router doesn't display the device, with his IP.

Synology Assistant is not able to see the new device ... 

 

I've tried to search the linux driver, without sucess.

My NIC seems to be : HP Ethernet 1Gb 2-Port 332i Adapter.

 

I've follow your advice by using cmd on my old dms (who's working)

Can you give me advise, or confirm my action were good.

And if it's possible, i've seen other users of Gen8 without issue but I don't know how did they do.

 

Thx in advance.

2018-02-16 03_33_44-IMG_20180216_030046.jpg ‎- Photos.jpg

2018-02-16 03_34_07-IMG_20180216_021102.jpg ‎- Photos.jpg

2018-02-16 03_50_33-IMG_20180216_034900.jpg ‎- Photos.jpg

Edited by pedrolit0
Link to comment
Share on other sites

hi,

 

hp 332i is supposed to be a broadcom controller (often used on hp as onboard), hp does offer broadcom firmware for it so it must be

tg3 two times in the first screenshot seem proof of it, 3rd screenshot looks wired bu you picked the "wrong" search (should have bin "eth0"?) so intel stand above the 2 connection messages but phy 5720c is leading to broadcom

https://www.broadcom.com/products/ethernet-connectivity/controllers/bcm5720

 

tg3 driver got positive feedback to work and i have not changed it since then (9/2017)

can you get log data trough serial port (or iLO?) , jun's loader (synology) does not output to screen, log is on serial port maybe that gives any hint whats wrong

it should work with my extra.lzma

did you use 3615/3617?, 916+ might not work on this hardware

Link to comment
Share on other sites

Thx for your quick answer & your precisions.
Are you able to give me more informations about how can I get the log data ?

I've tried to throught iLO but there is no information about loader ... 

 

Or i've missed something ... but I don't know what...

 

About version, i've only used the 3615xs version, as it's this version who's already installed.

 

thx.

Link to comment
Share on other sites

to see a log about whats going on you will need serial connection, the loader dumps the output to com1 an if you connect a serial teminal you can read it, the same like communication with a analog modem or configuring a network switch over a serial port connection (ok thats realy last century way of doing stuff, but if you started in the 70/80's with computers it should sound familiar)

maybe iLO does provide a way to get it over network, if not you will need a serial cable and a computer with putty (as console), i only used it with my virtualbox vm's, you can search the forum tor it

 

also found this so i think you will not need a real cable

https://serverfault.com/questions/830748/how-to-enable-and-use-the-serial-terminal-of-a-hp-microserver-gen9

 

edit: the easier way would be to add a additional network card taht is supported (intel, realtek, ...) install dsm with it an see whats in the log about tg3 driver after installing

 

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

[    6.568515] sg: version magic '3.10.35 SMP mod_unload ' should be '3.10.102 SMP mod_unload '

3.10.35 is the kernel of dsm 6.0 and jun's loader 1.01

3.10.102 is kernel of dsm 6.1, jun's laoder 1.02 and my extra.lzma

what loader did you try with the extra.lzma

 

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

please connect the usb drive you used for the log to a computer and check on 1st partition what file date "grubenv" has, it should be 17.06.2017 when its 1.02b

also check the size of the extra.lzma to be sure its the right version

if the files are extracted the names are the same for newer and older versions (synoboot.img and extra.lzma), easy to choose a wrong version when writing the img to usb or when copying the extra.lzma

or maybe just redo the whole usb drive and double check you are using the right versions, its just the vid/pid that has to be set, mac or serial can be changed later, even after installing

Link to comment
Share on other sites

Bad new, i'm really tired of my many tries ...

Not your fault ;)  You're really usefull and you take many time to understand and help me.

 

Here some screenshot of i've done to flash my usb... 

Conclusion now : IZMA data is corrupt ... :/

And no out data on serie port.

 

I've tried to write the synoboot, without any modification, but still not works :/

2018-02-19 03_14_16-Flash Drive Information Extractor 9.0.0.612.jpg

2018-02-19 03_16_48-MAJ Syno.jpg

2018-02-19 03_19_26-_Y__grub_grub.cfg - Notepad++.jpg

2018-02-19 03_22_36-Disque local (Z_).jpg

2018-02-19 03_26_06-Sélectionner une image disque.jpg

2018-02-19 03_27_30-C__Users_Pedrolit0_Downloads_MAJ Syno_synoboot.img_.jpg

2018-02-19 03_27_39-C__Users_Pedrolit0_Downloads_MAJ Syno_synoboot.img_boot.img_grub_.jpg

2018-02-19 03_27_58-C__Users_Pedrolit0_Downloads_MAJ Syno_synoboot.img_image.img_.jpg

Link to comment
Share on other sites

hi,

 

i checked the kernel version in you log "3.10.35" is dsm 5.2, whatever is booting it not just what comes from usb (kernel and extra.lzma)

you can check by removing all disk, the system shoud boot and be found in network (no disks only means you cant install the *.pat but it proofs you usb and extra.lzma is working), if that does work you could even try a single empty disk and install dsm 6.1

if you are willing to loose the settings and plugins of your plugins of your 5.2 installation you can plugin in your old disk at this stage (as 2nd, 3rd, ...) and repair so the system of the fresh 6.1 will be installed to the system partitions on you old disks, the data partition should be found at this point

 

in theory your 5.2 installation should be at least overwritten when migration ins not possible, i dont know why there is some mixed system in your log

the md5 checksum of the extra.lzma 4.5 for 3615 should be "0B263AD8F386F19B8EFA3774B4D90B7D" but i dont think thats the problem, must be someting else

 

 

Link to comment
Share on other sites

Im using an intel s2400sc server motherboard with dual xeon processors... i have an issue where with the included drivers in jun's loader1.02  my sata ports all work but not the sas port... when i use the extra.lzma drivers my sata ports no longer works but my sas port works and it numbers the drives in sequence with the sata ports... but also causes a constant reboot after about 5-7 min of use and bc the machine boots up slowly its hard to get in and check any log files.. my question is.. is there anyway to get the isci : Intel C600 Series Chipset SAS Controller driver installed on a running machine and have the sas port work? any advice would be greatly appreciated. i have tried compiling drivers with no luck what so ever. I can see all my drives (on sata ports and the sas port) in every other os install that i do.

Edited by strkdout383
Link to comment
Share on other sites

1 hour ago, strkdout383 said:

Im using an intel s2400sc server motherboard with dual xeon processors... i have an issue where with the included drivers in jun's loader1.02  my sata ports all work but not the sas port... when i use the extra.lzma drivers my sata ports no longer works but my sas port works and it numbers the drives in sequence with the sata ports... but also causes a constant reboot after about 5-7 min of use and bc the machine boots up slowly its hard to get in and check any log files.. my question is.. is there anyway to get the isci : Intel C600 Series Chipset SAS Controller driver installed on a running machine and have the sas port work? any advice would be greatly appreciated. i have tried compiling drivers with no luck what so ever. I can see all my drives (on sata ports and the sas port) in every other os install that i do.

I'm not fully clear on your description - is it all of the SATA not working with the enhanced extra.lzma or just some of them? If its some then may be because the total drive count is 14 (6 sata and 8 sas) ? You might need to edit synoinfo.conf to match 14 drives or disable some of the SATA ports to get a 12 drive count. 

Not sure about the reboot issue, maybe related to the drive count or maybe a cache issue (if the controller has one) so disable it, as well as making sure the controller is set to non-raid/jbod mode

Link to comment
Share on other sites

it is 4 sas.  Without enhanced extra.lzma the sas dosent work. With enhanced extra.lzma the sas works but sata does not.. but sas drive numbering is sequential to sata ports.. id sata ports are 0-5 and sas adds 7-9  i am currently working on extracting the isci.ko from the extra.lzma and recompling adding just that file to the original extra.lzma  also i do have the controller set to passthrough so in the bios it reads 4sata ports

Edited by strkdout383
Link to comment
Share on other sites

2 hours ago, sbv3000 said:

I'm not fully clear on your description - is it all of the SATA not working with the enhanced extra.lzma or just some of them? If its some then may be because the total drive count is 14 (6 sata and 8 sas) ? You might need to edit synoinfo.conf to match 14 drives or disable some of the SATA ports to get a 12 drive count. 

Not sure about the reboot issue, maybe related to the drive count or maybe a cache issue (if the controller has one) so disable it, as well as making sure the controller is set to non-raid/jbod mode

 

 

Upon Further checks and recompiling the original extra.lzma file with the isci.ko I believe it is this module that is causing the reboot... without the file it runs fine and with it it will just reboot before it can get dhcp. I have included a pic of my bios settings showing the sas drive settings. any ideas???IMG_2023.png.357f7fa1e30ed356797c4042f4ce08ec.png

Edited by strkdout383
Link to comment
Share on other sites

6 hours ago, sbv3000 said:

I'm not fully clear on your description - is it all of the SATA not working with the enhanced extra.lzma or just some of them? If its some then may be because the total drive count is 14 (6 sata and 8 sas) ? You might need to edit synoinfo.conf to match 14 drives or disable some of the SATA ports to get a 12 drive count. 

Not sure about the reboot issue, maybe related to the drive count or maybe a cache issue (if the controller has one) so disable it, as well as making sure the controller is set to non-raid/jbod mode

 

 

ok so after hours of hair pulling i started trying 1 drive at a time on my sas port and i could get one drive to work sometimes... when it did work and i added another drive the system would reboot.  i bypassed my hot swap cage and have it all hooked up to the sata ports on the motherboard. the hotswap cage works perfect. i beleive that i have a bad cable. about 90% sure that its the cable. Im going to order a new one. a better one and see what happens.  The isci.ko is definitely running on the system now. so it wasnt the driver problem.   could there be any  other issues that anyone else could think of? I really appreciate the time to respond. 

 

Thanks

Link to comment
Share on other sites

Hey guys. So I'm fairly sure I've done my homework here before posting - I've done the following, but cannot load/detect an LSI 9361-8i storage adapter despite loading the extra driver modules. I do have a working installation, though.

 

  • ESXi 6.5
  • Virtual DS3617xs
  • DSM 6.1.5-15254
  • Kernel 3.10.102
  • Jun's official v1.02b loader (notably the DS3617xs derivative)
  • extra.lzma for ds3617 v4.5
  • LSI 9361-8i adapter, passed through to the VM (confirmed was working fine in passthrough for an Ubuntu VM)
  • lspci -v output:
    • 0000:0c:00.0 Class 0104: Device 1000:005d (rev 02)
              Subsystem: Device 1000:9361
              Flags: fast devsel, IRQ 19
              I/O ports at 4000 [disabled]
              Memory at fe100000 (64-bit, non-prefetchable) 
              Memory at fe000000 (64-bit, non-prefetchable) 
              Capabilities: <access denied>
       
  • Two additional virtual paravirtual SCSI disks are attached and working fine (hence why I have a working install).
  • Due to booting in virtual/ESXi mode, the bootloader SATA device is not showing up in DSM (this is good/desired).
  • I can't enable write cache in DSM. I'm concerned this will torpedo my further efforts and performance, but I think it is probably irrelevant when virtualizing. 
  • Can't also see estimated lifespan, sector counts, temperature, serial number, firmware version of the virtual disks. This is something I'm still investigating, though. May not really matter in the end.
     

Anyway it seems that the extra kernel module is not being loaded here, or it's not satisfied with the hardware. I haven't gone down the path of trying to compile things myself. Any suggestions or thoughts?
 

I figure I could just disable passthrough of the adapter and set up the disks as physical RDMs for the VM, but that masks the disks a bit too much for comfort.

 

Edit: Booted back into Ubuntu to double-check what module was loaded (megaraid_sas, since I've flashed this adapter into IT mode). Annnd the device isn't showing any drives, I think the firmware crashed. Going to reboot and see if it works the Syno VM!

Edited by kachunkachunk
update
Link to comment
Share on other sites

Ah, needed a reboot. So now it looks like megasas is loading, but it's deffo panicking. Also turns out megasas is included in the original ramdisk file, so no need for the extra/extension stuff in the mix after all. May have to pose elsewhere.

 

Boot logs  

 

Quote

[Fri Feb 23 01:15:08 2018] megasas: 06.506.00.00-rc1 Sat. Feb. 9 17:00:00 PDT 2013
[Fri Feb 23 01:15:08 2018] megasas: 0x1000:0x005d:0x1000:0x9361: bus 12:slot 0:func 0
[Fri Feb 23 01:15:08 2018] megaraid_sas 0000:0c:00.0: enabling device (0000 -> 0002)
[Fri Feb 23 01:15:08 2018] megasas: Waiting for FW to come to ready state
[Fri Feb 23 01:15:08 2018] megasas: FW now in Ready state
[Fri Feb 23 01:15:08 2018] megaraid_sas 0000:0c:00.0: irq 74 for MSI/MSI-X
[Fri Feb 23 01:15:08 2018] megaraid_sas 0000:0c:00.0: irq 75 for MSI/MSI-X
[Fri Feb 23 01:15:08 2018] megaraid_sas 0000:0c:00.0: irq 76 for MSI/MSI-X
[Fri Feb 23 01:15:08 2018] megaraid_sas 0000:0c:00.0: irq 77 for MSI/MSI-X
[Fri Feb 23 01:15:08 2018] megasas:IOC Init cmd success
[Fri Feb 23 01:15:08 2018] tsc: Refined TSC clocksource calibration: 3066.656 MHz
[Fri Feb 23 01:15:08 2018] Switching to clocksource tsc
[Fri Feb 23 01:15:08 2018] megasas: INIT adapter done
[Fri Feb 23 01:15:08 2018] scsi4 : LSI SAS based MegaRAID driver
[Fri Feb 23 01:15:08 2018] scsi 4:0:11:0: Direct-Access     SEAGATE  ST6000NM0034             E001 PQ: 0 ANSI: 6
[Fri Feb 23 01:15:08 2018] BUG: unable to handle kernel paging request at 000000000000348c
[Fri Feb 23 01:15:08 2018] IP: [<ffffffff813314f3>] sd_probe+0x1d3/0x960
[Fri Feb 23 01:15:08 2018] PGD 234b73067 PUD 234ad2067 PMD 0 
[Fri Feb 23 01:15:08 2018] Oops: 0002 [#1] SMP 
[Fri Feb 23 01:15:08 2018] Modules linked in: 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)
[Fri Feb 23 01:15:08 2018] CPU: 0 PID: 4263 Comm: insmod Tainted: G           O 3.10.102 #15254
[Fri Feb 23 01:15:08 2018] Hardware name: VMware, Inc. VMware7,1/440BX Desktop Reference Platform, BIOS VMW71.00V.0.B64.1704110547 04/11/2017
[Fri Feb 23 01:15:08 2018] task: ffff880235261040 ti: ffff880234b94000 task.ti: ffff880234b94000
[Fri Feb 23 01:15:08 2018] RIP: 0010:[<ffffffff813314f3>]  [<ffffffff813314f3>] sd_probe+0x1d3/0x960
[Fri Feb 23 01:15:08 2018] RSP: 0000:ffff880234b978a0  EFLAGS: 00010286
[Fri Feb 23 01:15:08 2018] RAX: 0000000000000000 RBX: ffff8802316c6970 RCX: 0000000000000000
[Fri Feb 23 01:15:08 2018] RDX: 000000000000000b RSI: 0000000000000000 RDI: ffff88023080e000
[Fri Feb 23 01:15:08 2018] RBP: ffff880233e4ac00 R08: ffff88023080e000 R09: 0000000000000000
[Fri Feb 23 01:15:08 2018] R10: ffff88023e84a980 R11: 0000000000002258 R12: 00000000fffffff4
[Fri Feb 23 01:15:08 2018] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
[Fri Feb 23 01:15:08 2018] FS:  00007f74ad881700(0000) GS:ffff88023fc00000(0000) knlGS:0000000000000000
[Fri Feb 23 01:15:08 2018] CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
[Fri Feb 23 01:15:08 2018] CR2: 000000000000348c CR3: 00000002315a0000 CR4: 00000000000007f0
[Fri Feb 23 01:15:08 2018] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[Fri Feb 23 01:15:08 2018] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[Fri Feb 23 01:15:08 2018] Stack:
[Fri Feb 23 01:15:08 2018]  ffff880231797800 0000000000000000 ffff8802316c6970 ffff8802316c6970
[Fri Feb 23 01:15:08 2018]  ffff8802316c6970 ffffffff818490c8 0000000000000005 ffff880233da4428
[Fri Feb 23 01:15:08 2018]  ffff880234b97ab0 ffffffffa00007f7 ffff8802316c6970 ffff8802316c6970
[Fri Feb 23 01:15:08 2018] Call Trace:
[Fri Feb 23 01:15:08 2018]  [<ffffffffa00007f7>] ? 0xffffffffa00007f6
[Fri Feb 23 01:15:08 2018]  [<ffffffff812f853a>] ? really_probe+0x5a/0x220
[Fri Feb 23 01:15:08 2018]  [<ffffffff812f8700>] ? really_probe+0x220/0x220
[Fri Feb 23 01:15:08 2018]  [<ffffffff812f68d3>] ? bus_for_each_drv+0x53/0x90
[Fri Feb 23 01:15:08 2018]  [<ffffffff812f84c8>] ? device_attach+0x88/0xa0
[Fri Feb 23 01:15:08 2018]  [<ffffffff812f7a38>] ? bus_probe_device+0x88/0xb0
[Fri Feb 23 01:15:08 2018]  [<ffffffff812f5d9f>] ? device_add+0x52f/0x6a0
[Fri Feb 23 01:15:08 2018]  [<ffffffff812fbe80>] ? transport_setup_classdev+0x20/0x20
[Fri Feb 23 01:15:08 2018]  [<ffffffff81316cfa>] ? scsi_sysfs_add_sdev+0x6a/0x2c0
[Fri Feb 23 01:15:08 2018]  [<ffffffff813148f3>] ? scsi_probe_and_add_lun+0xee3/0xf70
[Fri Feb 23 01:15:08 2018]  [<ffffffff813136b6>] ? scsi_alloc_target+0x276/0x310
[Fri Feb 23 01:15:08 2018]  [<ffffffff81314ce7>] ? __scsi_scan_target+0xc7/0x5c0
[Fri Feb 23 01:15:08 2018]  [<ffffffff8104741f>] ? call_usermodehelper_exec+0x6f/0x150
[Fri Feb 23 01:15:08 2018]  [<ffffffff8126abce>] ? kobject_uevent_env+0x11e/0x4a0
[Fri Feb 23 01:15:08 2018]  [<ffffffff81315314>] ? scsi_scan_channel.part.12+0x54/0x70
[Fri Feb 23 01:15:08 2018]  [<ffffffff81315491>] ? scsi_scan_host_selected+0xc1/0x150
[Fri Feb 23 01:15:08 2018]  [<ffffffffa01c2e26>] ? megasas_probe_one+0x1106/0x13d0 [megaraid_sas]
[Fri Feb 23 01:15:08 2018]  [<ffffffff8128db50>] ? pci_device_probe+0x60/0xa0
[Fri Feb 23 01:15:08 2018]  [<ffffffff812f853a>] ? really_probe+0x5a/0x220
[Fri Feb 23 01:15:08 2018]  [<ffffffff812f87c1>] ? __driver_attach+0x81/0x90
[Fri Feb 23 01:15:08 2018]  [<ffffffff812f8740>] ? __device_attach+0x40/0x40
[Fri Feb 23 01:15:08 2018]  [<ffffffff812f6833>] ? bus_for_each_dev+0x53/0x90
[Fri Feb 23 01:15:08 2018]  [<ffffffff812f7cd8>] ? bus_add_driver+0x158/0x250
[Fri Feb 23 01:15:08 2018]  [<ffffffffa01cf000>] ? 0xffffffffa01cefff
[Fri Feb 23 01:15:08 2018]  [<ffffffff812f8dc8>] ? driver_register+0x68/0x150
[Fri Feb 23 01:15:08 2018]  [<ffffffffa01cf000>] ? 0xffffffffa01cefff
[Fri Feb 23 01:15:08 2018]  [<ffffffffa01cf0a3>] ? megasas_init+0xa3/0x1bb [megaraid_sas]
[Fri Feb 23 01:15:08 2018]  [<ffffffffa01cf000>] ? 0xffffffffa01cefff
[Fri Feb 23 01:15:08 2018]  [<ffffffff810003aa>] ? do_one_initcall+0xea/0x140
[Fri Feb 23 01:15:08 2018]  [<ffffffff8108905f>] ? load_module+0x1d0f/0x2060
[Fri Feb 23 01:15:08 2018]  [<ffffffff81085f10>] ? store_uevent+0x40/0x40
[Fri Feb 23 01:15:08 2018]  [<ffffffff81089441>] ? SYSC_init_module+0x91/0xc0
[Fri Feb 23 01:15:08 2018]  [<ffffffff814b0672>] ? system_call_fastpath+0x16/0x1b
[Fri Feb 23 01:15:08 2018] Code: 01 00 00 8b 8b 14 ff ff ff 8b 93 10 ff ff ff 8b b3 18 ff ff ff ff d0 41 89 c7 41 89 c5 48 8b 83 90 fe ff ff 48 8b 80 08 05 00 00 <44> 89 b8 8c 34 00 00 66 0f 1f 44 00 00 48 8d 54 24 10 44 89 fe 
[Fri Feb 23 01:15:08 2018] RIP  [<ffffffff813314f3>] sd_probe+0x1d3/0x960
[Fri Feb 23 01:15:08 2018]  RSP <ffff880234b978a0>
[Fri Feb 23 01:15:08 2018] CR2: 000000000000348c
[Fri Feb 23 01:15:08 2018] ---[ end trace 378b74546dad533e ]---

Hide  

 

 

Link to comment
Share on other sites

On 2/22/2018 at 5:09 AM, strkdout383 said:

  The isci.ko is definitely running on the system now. so it wasnt the driver problem.   could there be any  other issues that anyone else could think of? I really appreciate the time to respond.

 

you can extract the isci.ko with 7zip and copy the file to an system installed with the standard extra.lzma

place it in /usr/local/modules/update/

you can then load it manually with insmod or edit rc.modules to load it at boot, just add it to the disk_modules section and reboot

i dont see how it should interfere with ahci, the ahci support is compiled into the synology kernel so it present in the same way with the standard extra.lzma and my extra.lzma and as it is just the standard driver from the kernel it should work but as seen with the hpsa.ko driver, it did load but drives where nut usable (but it did not crash anything)

 

Link to comment
Share on other sites

7 hours ago, kachunkachunk said:

Ah, needed a reboot. So now it looks like megasas is loading, but it's deffo panicking. Also turns out megasas is included in the original ramdisk file, so no need for the extra/extension stuff in the mix after all. May have to pose elsewhere.

 

as its already part of jun's extra.lzma i just took it into the extended version, as long as no one has complains and we find a better driver its going to stay i'd say

 

does the reflashed controller work with a ubuntu vm?

what firmware did you flash, broadcom does not offer it firmware for this model

 

broadcom does provide a newer driver for LSI 9361-8i, if the controller does work with another system (no flash problem) the we can try to compile the newer driver und put it to a test with your controller

 

Link to comment
Share on other sites

Yeah, I think the LSI drivers/hardware is fairly ubiquitous so it's pretty safe to err on wider inclusion.

 

I ended up pulling the card and swapping it for an older LSI 2008-based controller (IBM M1015, cross-flashed to LSI 9211-8i).

This actually matches my working-good system where another XPenology VM is already working fine with its passthrough adapter. Since I wanted to play with Syno HA, may as well stick with this.

 

Some additional clarifications:

  • Turns out the LSI 9361-8i cannot be cross-flashed, so I was mistaken about my own setup - I had disabled its BIOS (I'm not booting from a RAID on it), and the devices were just in JBOD mode.
  • The adapter firmware was not current, so I'm not certain if that played a role in a device discovery panic like above.
  • The included megasas driver appears to be quite old. There's a good chance that a newer driver would do some good here, but admittedly recompiling instructions were making my eyes glaze over, and I deemed that a challenge for another day. :P

 

To answer your questions - the controller always worked wonderfully in passthrough to another Ubuntu VM with current updates (I'm intending on moving from a hand-built NAS VM to XPenology). When troubleshooting, I can power down the XPenology machine, then power on the original Ubuntu VM and see the module load, and disks are detected/working without issue.

 

So strictly speaking this looks to me a driver/kernel centric issue but probably correctable with a new driver.

I'm afraid I just won't be testing that since I moved the card out. Appreciate your input though! If you do update the loader or extras, it could still help people.

 

Edited by kachunkachunk
formatting
Link to comment
Share on other sites

11 hours ago, IG-88 said:

 

you can extract the isci.ko with 7zip and copy the file to an system installed with the standard extra.lzma

place it in /usr/local/modules/update/

you can then load it manually with insmod or edit rc.modules to load it at boot, just add it to the disk_modules section and reboot

i dont see how it should interfere with ahci, the ahci support is compiled into the synology kernel so it present in the same way with the standard extra.lzma and my extra.lzma and as it is just the standard driver from the kernel it should work but as seen with the hpsa.ko driver, it did load but drives where nut usable (but it did not crash anything)

 

 

 

The motherboard I’m using has the intel c602 chipset. And everything I’ve read and tried has not worked. I am able to use the onboard sata ports but need more.  The board has two scsi ports that can be configured as sas/sata passthrough. I have reconfigured the synoinfo.conf Files to add more disks in the operating system. I was able to get the port to work with one drive attatched and as soon as I plugged another drive in they system rebooted. And continued to reboot. I have tested all the hard drives with the onboard sata ports and none of the drives themselves are bad. 

 

Im actually thinking of just disabling the onboard scsi ports and picking up an LSI 9207 SAS controller.  I have seen video of that card being installed and working with the standard files. 

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...