Jump to content
XPEnology Community

wickedgtr

Transition Member
  • Posts

    6
  • Joined

  • Last visited

Posts posted by wickedgtr

  1. 21 hours ago, IG-88 said:

     

    lets take this as exaple

    https://www.amazon.com/Controller-Expression-Profile-Bracket-Converter/dp/B07S8CB398

    they give good information, not just the chips also what it does

    "Chip: ASM 1062(PCIE to SATA Controller)+ASM 1093(Port Multiplier)"

    so with port multiplier its a no go for us

    also the pcie type is a hint, pcie 1x for a 8 port controller - the bandwidth of pcie 1x is to low for this (and it for sure be a controller with port multiplier)

     

     

    I literally just installed this card as the replacement to the HP240.  I was having trouble finding a card with >1x PCIe lanes and at least 4-ports that costs less than an actual enterprise SAS controller.  I haven't yet confirmed it works, but now I guess I need to hurry up and test it.

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

  3. I am using HW pass-though for the disk controllers, including now a HP H240  as I  have run out of SATA ports, and it was cheaper than (already had it) and the bios wouldnt detect any of the LSI based controllers - 

     

    I basically have a HP Z220 workstation running 3 VMs, XPenology, Plex (HW Passthough GTX 1060) and a MineOS on one box. ESXi boots from a USB stick, then the datastore is a old/very slow NVMe disk, hosting the 3 VMs including the XPenology loader drive.

     

    I tested it with the extra file replaced, and it never responded to pings, reverted snapshot, and it came back online.

     

    copying out the hpsa.ko and using insmod hpsa.ko does successfully load the module, but I cant see the disks attached or an additional scsi controller is /sys/bus/scsi/devices/

  4. Maybe I am missing it, but I dont see any download for a extra.lzma for loader 1.03b at all.  Only for 1.04 and 1.02 - I did try insmod the hpsa.ko that is in the 1.04b loader:

     

    insmod: ERROR: could not insert module hpsa.ko: Invalid module format
     

    Not sure where to go from here.

     

    checked dmesg - its the from kernel version - again maybe I am missing the correct download for extra.lzma

    hpsa: version magic '4.4.59+ SMP preempt mod_unload ' should be '3.10.105 SMP mod_unload '
     

  5. On 11/26/2019 at 1:10 PM, IG-88 said:

    we will see in about 2 weeks, i have got ideas what to try with 918+ when redoing the driver and i have a good kernel config to try out

    good to know same names now being able to test ixgbe and even i40e

    i will stop trying to get sas/scsi drivers working for 3615/16 on 6.2.2, network drivers seem to work fine and 3615 has mpt2sas and 3617 has mpt2sas and mpt3sas, good enough

    @IG-88  - 

     

    I know I am a new member, but I've been reading this forum for a long time.

     

    I really appreciate your efforts on improving hardware support for the loaders, and if there is anyway I can encourage you to continue on the 3615/17 (1.03b) modules -  I am specifically looking for the hpsa module. I have a lot of different hardware, and would gladly assist in testing for you.  I just found the threads on building the modules/extra.lzma, so if you are 100% done working on 3615/17 I can go that route on compiling and creating a custom extra.lzma.  Thank you for everything you've done so far (and continue to do).

     

×
×
  • Create New...