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


Recommended Posts

 HP HPSA Driver (v 3.4.20-151)
 hpsa 0000:1b:00.0: MSI-X capable controller
 hpsa 0000:1b:00.0: irq 44 for MSI/MSI-X
 hpsa 0000:1b:00.0: Using 1 reply queue(s)
 Physical aborts supported: yes
 Logical aborts supported: no
 HP SSD Smart Path aborts supported: yes
 hpsa 0000:1b:00.0: hpsa0: <0x3239> at IRQ 44 using DAC
 bft2_offset = 0x8f4
 scsi7 : hpsa
 hpsa 0000:1b:00.0:             added scsi 7:0:0:0: RAID              HP       H240             controller SSDSmartPathCap- En- Exp=1 qd=1024
 hpsa 0000:1b:00.0:             added scsi 7:0:1:0: Direct-Access     ATA      MZ-5EA1000-0D3   PHYS DRV SSDSmartPathCap- En- Exp=1 qd=25
 hpsa 0000:1b:00.0:             added scsi 7:0:2:0: Direct-Access     ATA      MZ-5EA1000-0D3   PHYS DRV SSDSmartPathCap- En- Exp=1 qd=25
 BUG: unable to handle kernel NULL pointer dereference at           (null)
 IP: [<ffffffffa0f3cf3c>] hpsa_slave_alloc+0x3c/0x1e0 [hpsa]
 PGD 8a03e067 PUD 9faf8067 PMD 0
 Oops: 0000 [#1] SMP
 Modules linked in: hpsa(OF+) cifs udf isofs loop nfsd exportfs rpcsec_gss_krb5 hid_generic usbhid tcm_loop(O) iscsi_target_mod(O) hid target_core_ep(O) target_core_multi_file(O) target_core_file(O) target_core_iblock(O) usblp target_core_mod(O) syno_extent_pool(PO) rodsp_ep(O) bromolow_synobios(PO) button(F) ax88179_178a(F) usbnet tg3(F) cnic(F) bnx2(F) vmxnet3(F) pcnet32(F) e1000(F) sfc(F) netxen_nic(F) qlge(F) qlcnic(F) qla3xxx(F) pch_gbe(F) ptp_pch(F) sky2(F) skge(F) ipg(F) uio(F) alx(F) atl1c(F) atl1e(F) atl1(F) libphy(F) mii(F) exfat(O) btrfs synoacl_vfs(PO) zlib_deflate hfsplus md4 hmac bnx2x(O) libcrc32c mdio mlx5_core(O) mlx4_en(O) mlx4_core(O) mlx_compat(O) compat(O) qede(O) qed(O) ixgbe(O) be2net(O) igb(O) i2c_algo_bit e1000e(O) dca vxlan fuse vfat fat crc32c_intel aesni_intel
  glue_helper lrw gf128mul ablk_helper arc4 cryptd ecryptfs sha256_generic sha1_generic ecb aes_x86_64 authenc des_generic ansi_cprng cts md5 cbc cpufreq_conservative cpufreq_powersave cpufreq_performance cpufreq_ondemand mperf processor thermal_sys cpufreq_stats freq_table dm_snapshot crc_itu_t crc_ccitt quota_v2 quota_tree psnap p8022 llc sit tunnel4 ip_tunnel ipv6 zram(C) sg etxhci_hcd mpt3sas(F) mpt2sas(O) megaraid_sas(F) mptctl(F) mptsas(F) mptspi(F) mptscsih(F) mptbase(F) scsi_transport_spi(F) megaraid(F) megaraid_mbox(F) megaraid_mm(F) vmw_pvscsi(F) BusLogic(F) usb_storage xhci_hcd uhci_hcd ohci_hcd(F) ehci_pci ehci_hcd usbcore usb_common dfffucfffttf(OF) [last unloaded: bromolow_synobios]
 CPU: 0 PID: 20747 Comm: insmod Tainted: PF        C O 3.10.105 #24922
 Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 12/12/2018
 task: ffff880096117040 ti: ffff8800a4680000 task.ti: ffff8800a4680000
 RIP: 0010:[<ffffffffa0f3cf3c>]  [<ffffffffa0f3cf3c>] hpsa_slave_alloc+0x3c/0x1e0 [hpsa]
 RSP: 0018:ffff8800a4683660  EFLAGS: 00010046
 RAX: 0000000000000286 RBX: ffff88008aa90000 RCX: 0000000000000004
 RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffff88008aa90740
 RBP: ffff88008aa90740 R08: 000000000000000a R09: 000000000000fffb
 R10: 0000000000000000 R11: 00000000001fe200 R12: ffff8800a0593800
 R13: 0000000000000000 R14: ffff8800ae0e6c28 R15: 0000000000000000
 FS:  00007f302f345700(0000) GS:ffff8800bfa00000(0000) knlGS:0000000000000000
 CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
 CR2: 0000000000000000 CR3: 00000000a442c000 CR4: 00000000001607f0
 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
 DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
 Stack:
  ffff8800a0593800 ffff8800ae561800 ffff8800a0593800 ffff8800ae0e6c00
  ffffffff81326c62 0000000000000000 0000000000000000 ffff8800ae0e6c00
  0000000000000000 0000000000000000 ffffffff813271ad ffff8800ae0e6c38
 Call Trace:
  [<ffffffff81326c62>] ? scsi_alloc_sdev+0x232/0x2c0
  [<ffffffff813271ad>] ? scsi_probe_and_add_lun+0x4bd/0xf70
  [<ffffffff812760ed>] ? kobject_set_name_vargs+0x4d/0x70
  [<ffffffff813064b2>] ? dev_set_name+0x42/0x50
  [<ffffffffa00e2ee0>] ? spi_target_match+0x40/0x94 [scsi_transport_spi]
  [<ffffffff8130e49f>] ? attribute_container_add_device+0x4f/0x130
  [<ffffffff8130655e>] ? get_device+0xe/0x20
  [<ffffffff81326996>] ? scsi_alloc_target+0x276/0x310
  [<ffffffff81327f8d>] ? __scsi_scan_target+0x8d/0x5d0
  [<ffffffff8130831f>] ? device_create+0x2f/0x40
  [<ffffffff813285a3>] ? scsi_scan_target+0xd3/0xe0
  [<ffffffff8133490f>] ? sas_rphy_add+0x10f/0x170
  [<ffffffffa0f434a8>] ? adjust_hpsa_scsi_table+0xee8/0x1dc0 [hpsa]
  [<ffffffffa0f44f43>] ? hpsa_update_scsi_devices+0xbc3/0x2200 [hpsa]
  [<ffffffff814276a5>] ? netlink_broadcast_filtered+0x125/0x350
  [<ffffffff81307b3a>] ? device_add+0x12a/0x6e0
  [<ffffffff81332945>] ? sas_bsg_initialize+0x65/0x150
  [<ffffffff8130e800>] ? transport_remove_device+0x10/0x10
  [<ffffffff814b74cb>] ? klist_next+0x1b/0x110
  [<ffffffffa0f466c5>] ? hpsa_scan_start+0x145/0x210 [hpsa]
  [<ffffffff8132a56f>] ? scsi_sysfs_add_host+0x7f/0x90
  [<ffffffff8132883d>] ? do_scsi_scan_host+0x2d/0x80
  [<ffffffffa0f4b0a2>] ? hpsa_init_one+0x1db2/0x20d1 [hpsa]
  [<ffffffff8129f810>] ? pci_device_probe+0x60/0xa0
  [<ffffffff8130aace>] ? driver_probe_device+0x7e/0x3e0
  [<ffffffff8130aeeb>] ? __driver_attach+0x7b/0x80
  [<ffffffff8130ae70>] ? __device_attach+0x40/0x40
  [<ffffffff81308b23>] ? bus_for_each_dev+0x53/0x90
  [<ffffffff8130a148>] ? bus_add_driver+0x1c8/0x280
  [<ffffffff8130b4d8>] ? driver_register+0x68/0x150
  [<ffffffffa0f54000>] ? 0xffffffffa0f53fff
  [<ffffffffa0f54038>] ? hpsa_init+0x38/0x58 [hpsa]
  [<ffffffff8100038a>] ? do_one_initcall+0xca/0x180
  [<ffffffff8108b63c>] ? load_module+0x1d0c/0x2360
  [<ffffffff8128feb0>] ? ddebug_proc_write+0xe0/0xe0
  [<ffffffff810f9663>] ? vfs_read+0xf3/0x160
  [<ffffffff8108bdf5>] ? SYSC_finit_module+0x75/0xa0
  [<ffffffff814ccdc4>] ? system_call_fastpath+0x22/0x27
 Code: 08 05 00 00 48 8d ab 40 07 00 00 48 89 ef e8 5c e2 58 e0 41 8b b4 24 88 00 00 00 85 f6 0f 85 cc 00 00 00 49 8b 94 24 68 01 00 00 <4c> 8b 02 8b 93 44 07 00 00 85 d2 7e 39 83 ea 01 48 8d 8b 48 07
 RIP  [<ffffffffa0f3cf3c>] hpsa_slave_alloc+0x3c/0x1e0 [hpsa]
  RSP <ffff8800a4683660>
 CR2: 0000000000000000
 ---[ end trace ac8e3ed46c0f3c5a ]---

Module did load, added the host device in /sys/class/scsi_host/, but drives never appeared to be visible. It is possible the kernel panic/dump could be due to the actual disks attached, since they are very old untested disks that I was only using see if the devices would appear.

Link to post
Share on other sites
7 hours ago, xptopt said:

realtek  RLT8111F 

see one reply above, 8111 should be usable with the new 3615/17 0.5 test extra.lzma

 

5 hours ago, T-REX-XP said:

9P  drivers support

??? whats 9P

 

9 hours ago, wickedgtr said:

. It is possible the kernel panic/dump could be due to the actual disks attached,

for one we never got it working the last time and gave up on that driver, 2nd read my comment about compiled scsi/sas drivers for 6.2.2

i will not do anything further, if the kernel build in driver does not work and the latest from external source dont either i will not put more effort into this

 

Link to post
Share on other sites
19 hours ago, T-REX-XP said:

i guess it is virtio storage drivers:

https://www.linux-kvm.org/page/9p_virtio

the extra.lzma contains:

virtio.ko, virtio_balloon.ko,virtio_blk.ko, virtio_console.ko, virtio_mmio.ko, virtio_net.ko, virtio_pci.ko, virtio_ring.ko, virtio_scsi.ko

 

9P seems also to be modules so i can add them

try the attached modules for 3615

 

 

 

9p_3615.zip

Edited by IG-88
  • Thanks 1
Link to post
Share on other sites
31 minutes ago, IG-88 said:

the extra.lzma contains:

virtio.ko, virtio_balloon.ko,virtio_blk.ko, virtio_console.ko, virtio_mmio.ko, virtio_net.ko, virtio_pci.ko, virtio_ring.ko, virtio_scsi.ko

 

9P seems also to be modules so i can add them

try the attached modules for 3615

 

31 minutes ago, IG-88 said:

thanks, can you prepare modules for ds918 model???

Link to post
Share on other sites

Hii, I have been trying to use this latest extra.lzma file (although I am new to this), with virtio_net for use with KVM.

 

I downloaded the new extra.lzma file, and followed this guide:

I added in 'virtio_net' in the EXTRA_MODULES section on the rc.modules file, saved and re-compressed.

On windows I used OSFMount to mount the current 1.03b synoboot.img, mounted partition 1, copied (replaced) current extra.lzma file with new one, in OSFMount - dismount all and exit. Copied new synoboot.img over, created new VM, but cant get http://find.synology.com to find it, even using e1000 network. Creating a VM with the original 1.03b synoboot.img, I can get it working with e1000 network.

To check, I then just tried with the standard V1.03b, which works fine with e1000 nic. I then tried my V1.03b with your extra.lzma injected (untouched), and I cant even get that working with e1000 nic.

What I mean by 'cant get it working', is, it seems to load, but I cant see it on the network, meaning the network isn't working, so cant get access.

I have attached my edited extra.lzma fiel for reference.

Anything you can see what I am doing wrong?

extra.lzma

Edited by speedyrazor
Link to post
Share on other sites
5 hours ago, speedyrazor said:

Anything you can see what I am doing wrong?

like other kernel modules there are dependencies, you need to load some modules before the other

usually modprobe will look for you (by using a file that is not present in dsm)

when using insmod you will need to do it by your own

in modules.dep (created where kernel compiled) there is for virtio_net:

virtio_ring and virtio

(same for virtio_scsi)

 

when using google to find a load order for virtio its something like this

 

insmod virtio.ko
insmod virtio_ring.ko
insmod virtio_blk.ko
insmod virtio-rng.ko
insmod virtio_console.ko
insmod virtio_net.ko
insmod scsi_transport_spi.ko
insmod virtio_scsi.ko
insmod virtio_balloon.ko
insmod virtio_mmio.ko

 

your extra.lzma only loads virtio_net and virtio_scsi, defiantly missing dependencies to two other drivers of virtio

 

Link to post
Share on other sites

Hello @IG-88

Thanks so much for your work. I had a 6.1 DSM working but wanted to try with DSM 6.2.2. My Xpenology is a 918+ and my hardware is a Dell Optiplex 9020 that comes with an Intel i217LM, which sadly seems to not work with the 1.04b loader. I've bricked my NAS now :( 

 

I've tried to follow your insutrctions and copy the extra.lzma and extra2.lzma to the USB, but when I connect it to Windows I just can't read the USB stick, it will just ask for format. What I was able to do is to modify the synoboot image and copy those files there, then writing again the image to the USB stick. When booting the PC I get the migrate screen, click next, select the latest PAT file for my NAS (https://archive.synology.com/download/DSM/release/6.2.2/24922/DSM_DS918+_24922.pat) it installs, restarts and I'm unable to connect again (no ping on IP either).

 

I'm not entirely sure what else to do. I know that if I format my HDDs I can install it again, but I will lose all my data. 

 

I'm also not sure how to downgrade, because even if I burn the original 1.04b loader on the USB and at boot select the Reinstall option, when the DSM installation ask for the PAT file it won't accept anything below 6.2.2 now (see image below)

 

Any help will be greatly appreciated, really looking forward to access my data again :D. Thanks!

Screenshot 2019-12-21 at 00.02.19.png

Edited by bluepr0
Link to post
Share on other sites

I was able to recover my HDDs by downgrading using this guide 

 

 

I installed back 6.2.1-23824 which seems to work just fine. However DSM was showing an update, 6.2.1-24XXX-4 (sorry can't remember exact numbers) which I accepted to install because it was still 6.2.1 and IT BRICKED IT AGAIN!. What's going on here?

Link to post
Share on other sites

I just tried to install with test 3615xs but failed due to the Atheros driver I think, before I need to use the special driver in following post to install the 6.1, other then that I cannot find the system in the network, is the new test version including following driver?  Thanks.

 

 

Link to post
Share on other sites
On 12/20/2019 at 2:21 PM, IG-88 said:

like other kernel modules there are dependencies, you need to load some modules before the other

usually modprobe will look for you (by using a file that is not present in dsm)

when using insmod you will need to do it by your own

in modules.dep (created where kernel compiled) there is for virtio_net:

virtio_ring and virtio

(same for virtio_scsi)

 

when using google to find a load order for virtio its something like this

 

insmod virtio.ko
insmod virtio_ring.ko
insmod virtio_blk.ko
insmod virtio-rng.ko
insmod virtio_console.ko
insmod virtio_net.ko
insmod scsi_transport_spi.ko
insmod virtio_scsi.ko
insmod virtio_balloon.ko
insmod virtio_mmio.ko

 

your extra.lzma only loads virtio_net and virtio_scsi, defiantly missing dependencies to two other drivers of virtio

 

 

Thanks for the info, I think I understand. I have created a new extra.lzma file (although I do get 'large inode number truncated: Result too large' in every line, outout_log.txt attached).

I have inserted this into the ds3615 v1.03b, but although I get the loading screen (so it's loading the synoboot.img) I still can't get it to discover it on the network using 'http://find.synology.com/'. I have also attached my latest extra.lzma file.

output_log.txt extra.lzma

Link to post
Share on other sites

For info, I want to migrate from 1.02b/3617xs/6.1 to 1.03b/3615xs/6.2.2 using the 16th December update of extra drivers,  tested with test HDD/SDD.

 

I successfully installed a HP Gen8 micro with 6.2.2 24922 DSM version, applying a fresh install targetting finally a migration mode, and it is working fine with:

 

- integrated NiC Broadcom working

- DELL H310 SAS controller w/ LSI 9211-8i P20 IT Mode, working, connected on an expansion rack of mixed SAS/SATA disks

 

>> Working 3615XS w/Broadcom HP Gen  8 NiC under DSM  6.2.2/24922

 

Very very good news and job from the Master of drivers, many thanks ☺️

 

But I have an issue :-( , not sure if linked with drivers extension, the internal eSata is not detected it means DSM see the whole disks connected to the H310 ... connected disks on internal eSata are identified under 1.02b etc. is it any change in loader configuration or Bios to customize between the 2 loaders main version ?

 

Thanks for the huge work of drivers adaptation and support to community

Edited by satdream
Link to post
Share on other sites
8 hours ago, speedyrazor said:

I have inserted this into the ds3615 v1.03b, but although I get the loading screen (so it's loading the synoboot.img) I still can't get it to discover it on the network using 'http://find.synology.com/'. I have also attached my latest extra.lzma file.

 

i will not do anything beside providing the modules, someone else will hat to do the tests to find out if and how its usable with kvm/proxmox

there is a whole section for virtual environment, there should be people with enough experience to make it use and tell how load them  without causing problems

Link to post
Share on other sites
6 hours ago, satdream said:

But I have an issue :-( , not sure if linked with drivers extension, the internal eSata is not detected it means DSM see the whole disks connected to the H310 ... connected disks on internal eSata are identified under 1.02b etc. is it any change in loader configuration or Bios to customize between the 2 loaders main version ?

 

you can try loader 1.03b as it comes from jun, dsm 6.2.0 and look for the esata connected disk, if its there ander this config then its my extra.lzma, if its not usable i this config either then is something different

i remember taht there might be a bios update for microserver to set the esta into ahci mode

look for other micriserver user in the section where people write about successfull updates, you might find hints like special mods or you can pm one or the other to ast about it

 

Link to post
Share on other sites
il y a 2 minutes, IG-88 a dit :

 

you can try loader 1.03b as it comes from jun, dsm 6.2.0 and look for the esata connected disk, if its there ander this config then its my extra.lzma, if its not usable i this config either then is something different

i remember taht there might be a bios update for microserver to set the esta into ahci mode

look for other micriserver user in the section where people write about successfull updates, you might find hints like special mods or you can pm one or the other to ast about it

 

 

Many thanks, you'are perfectly right, btw BIOS needed to be reconfigure in AHCI and then now the internal eSata is correctly detected. Now issue is that few HDD are not mapped/detected correctly (posted on DSM 6.2 loader topic)

Link to post
Share on other sites

Hardware: HP Microserver Gen8 micro with 6.2.2 24922 DSM version

DSM Version: 6.2.2 24922 Update 4

Install Method: Fresh install

Additional NICs: Mellanox MCX312A-XCBT ConnectX-3 EN 10GbE Dual Port SFP+ PCIe3.0 Card CX312A

Results: Success

Notes: Default card worked to load the OS, but the Mellanox card did not show up until DMS was loaded. My next test is the upgrade method from 6.1 to 6.2.2.

Link to post
Share on other sites

Hardware: Dell PowerEdge R410 with 6.2.2 24922 DSM version

DSM Version: 6.2.2 24922 Update 4

Install Method: Migration from 6.1.7.51284

Results: Success

Notes: I migrated from from DS3615xs 6.1.7.51284 to DS3617xs 6.2.2 24922 for no real reason, just wanted to try.  All data was successfully migrated as well.

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.