Jump to content
XPEnology Community

Atlas

Rookie
 View Profile  See their activity

  • Posts

    2

  • Joined

  • Last visited

 Content Type 

Posts posted by Atlas

    Develop and refine the DS3622xs+ loader

    in Developer Discussion Room

    Posted · Edited by Atlas

    I digged further into the disk 1 slot and I found it was a known issue in DSM 6.2.3 however is DSM7.0.1 the boot loader disk is not showing in storage manager but is taking up disk 1 in the background

    Also in dmesg I can clearly see ata1 which should be hidden. 

     

    Quote

    [    4.444588] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
    [    4.444627] ata1.00: ATA-6: VMware Virtual SATA Hard Drive, 00000001, max UDMA/100
    [    4.444636] ata1.00: 2097152 sectors, multi 0: LBA48 NCQ (depth 31/32)
    [    4.444646] ata1.00: SN:00000000000000000001
    [    4.444686] ata1.00: configured for UDMA/100
    [    4.444726] ata1.00: Find SSD disks. [VMware Virtual SATA Hard Drive]
    [    4.444908] scsi 0:0:0:0: Direct-Access     VMware   Virtual SATA Hard Drive  0001 PQ: 0 ANSI: 5
    [    4.444986] <redpill/scsi_notifier.c:65> Probing SCSI device using sd_probe_shim
    [    4.445044] <redpill/scsi_notifier.c:77> Triggering SCSI_EVT_DEV_PROBING notifications
    [    4.445080] <redpill/native_sata_boot_shim.c:153> Found new SCSI disk vendor="VMware  Virtual         0001" model="Virtual SATA Hard Drive ": checking boot shim viability
    [    4.445129] <redpill/boot_shim_base.c:34> Checking if SATA disk is a shim target - id=0 channel=0 vendor="VMware  Virtual         0001" model="Virtual SATA Hard Drive "
    [    4.445191] <redpill/boot_shim_base.c:56> Device has capacity of ~1024 MiB - it is a shimmable target (<=1024)
    [    4.445268] <redpill/native_sata_boot_shim.c:124> Trying to shim SCSI device vendor="VMware  Virtual         0001" model="Virtual SATA Hard Drive "
    [    4.445359] <redpill/native_sata_boot_shim.c:133> Shimming device to vendor="SATADOM-" model="TYPE D 3SE"
    [    4.445390] <redpill/scsi_notifier.c:87> Calling original sd_probe()
    [    4.445455] <redpill/scsi_notifier.c:91> Triggering SCSI_EVT_DEV_PROBED notifications - sd_probe() exit=0
    [    4.445498] sd 0:0:0:0: [synoboot] 2097152 512-byte logical blocks: (1.07 GB/1.00 GiB)
    [    4.445530] sd 0:0:0:0: [synoboot] Write Protect is off
    [    4.445532] sd 0:0:0:0: [synoboot] Mode Sense: 00 3a 00 00
    [    4.445545] sd 0:0:0:0: [synoboot] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
    [    4.445841]  synoboot: synoboot1 synoboot2 synoboot3
    [    4.446089] sd 0:0:0:0: [synoboot] Attached SCSI disk
    [    4.446496] Freeing unused kernel memory: 928K
    [    4.446544] Write protecting the kernel read-only data: 8192k
    [    4.446649] Freeing unused kernel memory: 592K
    [    4.446955] Freeing unused kernel memory: 312K
    [    4.473628] ACPI: bus type USB registered
    [    4.473688] usbcore: registered new interface driver usbfs
    [    4.473739] usbcore: registered new interface driver hub
    [    4.473795] usbcore: registered new interface driver ethub
    [    4.473856] usbcore: registered new device driver usb
    [    4.477658] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
    [    4.479119] ehci-pci: EHCI PCI platform driver
    [    4.487608] usbcore: registered new interface driver usb-storage
    [    4.490599] mpt3sas version 41.00.00.00 loaded
    [    4.490923] mpt3sas_cm0: 63 BIT PCI BUS DMA ADDRESSING SUPPORTED, total mem (4012796 kB)
    [    4.567585] mpt3sas_cm0: IOC Number : 0
    [    4.568589] mpt3sas0-msix0: PCI-MSI-X enabled: IRQ 57
    [    4.568599] mpt3sas0-msix1: PCI-MSI-X enabled: IRQ 58
    [    4.568609] mpt3sas0-msix2: PCI-MSI-X enabled: IRQ 59
    [    4.568618] mpt3sas0-msix3: PCI-MSI-X enabled: IRQ 60
    [    4.568628] mpt3sas_cm0: iomem(0x00000000e7900000), mapped(0xffffc90000400000), size(1048576)
    [    4.568638] mpt3sas_cm0: ioport(0x0000000000004000), size(256)
    [    4.644584] mpt3sas_cm0: IOC Number : 0
    [    4.680592] mpt3sas_cm0: scatter gather: sge_in_main_msg(0), sge_per_chain(7), sge_per_io(128), chains_per_io(19)
    [    4.680601] mpt3sas_cm0: request pool(0xffff880134900000) - dma(0x134900000): depth(6756), frame_size(128), pool_size(844 kB)
    [    4.777602] mpt3sas_cm0: sense pool(0xffff8800b7100000) - dma(0xb7100000): depth(6551), element_size(96), pool_size (614 kB)
    [    4.777612] mpt3sas_cm0: reply pool(0xffff880134a00000) - dma(0x134a00000): depth(6820)frame_size(128), pool_size(852 kB)
    [    4.777622] mpt3sas_cm0: config page(0xffff8800b7d4b000) - dma(0xb7d4b000): size(512)
    [    4.777631] mpt3sas_cm0: Allocated physical memory: size(28966 kB)
    [    4.777641] mpt3sas_cm0: Current Controller Queue Depth(6548), Max Controller Queue Depth(6656)
    [    4.835637] mpt3sas_cm0: FW Package Version(22.00.00.00)
    [    4.836180] mpt3sas_cm0: SAS3416: FWVersion(22.00.00.00), ChipRevision(0x01)
    [    4.836189] mpt3sas_cm0: Protocol=(Initiator,Target,NVMe), Capabilities=(TLR,EEDP,Diag Trace Buffer,Task Set Full,NCQ)
    [    4.836402] mpt3sas_cm0: : host protection capabilities enabled  DIF1 DIF2 DIF3
    [    4.836412] scsi host1: Fusion MPT SAS Host
    [    4.836647] mpt3sas_cm0: registering trace buffer support
    [    4.839604] mpt3sas_cm0: Trace buffer memory 2048 KB allocated
    [    4.839614] mpt3sas_cm0: sending port enable !!
    [    4.839848] mpt3sas_cm0: hba_port entry: ffff8800b4f15600, port: 0 is added to hba_port list
    [    4.840014] mpt3sas_cm0: hba_port entry: ffff8800b4f15740, port: 1 is added to hba_port list
    [    4.840213] mpt3sas_cm0: hba_port entry: ffff8800b4f15780, port: 2 is added to hba_port list
    [    4.840430] mpt3sas_cm0: hba_port entry: ffff8800b4f157c0, port: 3 is added to hba_port list
    [    4.840631] mpt3sas_cm0: hba_port entry: ffff8800b4f15800, port: 4 is added to hba_port list
    [    4.840860] mpt3sas_cm0: hba_port entry: ffff8800b4f15840, port: 5 is added to hba_port list
    [    4.841042] mpt3sas_cm0: hba_port entry: ffff8800b4f15880, port: 6 is added to hba_port list
    [    4.841267] mpt3sas_cm0: hba_port entry: ffff8800b4f158c0, port: 7 is added to hba_port list
    [    4.841508] mpt3sas_cm0: hba_port entry: ffff8800b4f15900, port: 8 is added to hba_port list
    [    4.841999] mpt3sas_cm0: hba_port entry: ffff8800b4f15940, port: 9 is added to hba_port list
    [    4.842332] mpt3sas_cm0: hba_port entry: ffff8800b4f15980, port: 10 is added to hba_port list
    [    4.842670] mpt3sas_cm0: hba_port entry: ffff8800b4f159c0, port: 11 is added to hba_port list
    [    4.842896] mpt3sas_cm0: vphy entry: ffff8800b864c880, port id: 0, phy:16 is added to port's vphys_list
    [    4.843521] mpt3sas_cm0: host_add: handle(0x0001), sas_addr(0x500605b0106daae0), phys(21)
    [    4.844451] mpt3sas_cm0: handle(0x17) sas_address(0x5000c50095257681) port_type(0x1)
    [    4.844654] mpt3sas_cm0: handle(0x1a) sas_address(0x5000c5009525989d) port_type(0x1)
    [    4.844844] mpt3sas_cm0: handle(0x1b) sas_address(0x5000c50095258915) port_type(0x1)
    [    4.845001] mpt3sas_cm0: handle(0x1c) sas_address(0x5000c50095257671) port_type(0x1)
    [    4.845173] mpt3sas_cm0: handle(0x1d) sas_address(0x5000c5009523199d) port_type(0x1)
    [    4.845410] mpt3sas_cm0: handle(0x1f) sas_address(0x5000c5009525378d) port_type(0x1)
    [    4.845600] mpt3sas_cm0: handle(0x1e) sas_address(0x5000c50095257d4d) port_type(0x1)
    [    4.845775] mpt3sas_cm0: handle(0x20) sas_address(0x5000c5009519be7d) port_type(0x1)
    [    4.845942] mpt3sas_cm0: handle(0x18) sas_address(0x300605b0106daae9) port_type(0x1)
    [    4.846121] mpt3sas_cm0: handle(0x19) sas_address(0x300605b0106daaeb) port_type(0x1)
    [    4.846301] mpt3sas_cm0: handle(0x21) sas_address(0x300605b0106daaed) port_type(0x1)
    [    4.846483] mpt3sas_cm0: handle(0x22) sas_address(0x300605b0106daaef) port_type(0x1)
    [    4.847336] mpt3sas_cm0: handle(0x11) sas_address(0x300705b0106daae0) port_type(0x0)
     

    Quote

    root@NAS:~# fdisk -l /dev/synoboot
    Disk /dev/synoboot: 1 GiB, 1073741824 bytes, 2097152 sectors
    Disk model: TYPE D 3SE
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disklabel type: dos
    Disk identifier: 0xf110ee87

    Device         Boot  Start     End Sectors  Size Id Type
    /dev/synoboot1 *      2048  100351   98304   48M 83 Linux
    /dev/synoboot2      100352  253951  153600   75M 83 Linux
    /dev/synoboot3      253952 2097151 1843200  900M 83 Linux
     

     

    I think we need a script or find a way to hide synoboot from DSM so disk 1 slot can be used.

     

     

    Develop and refine the DS3622xs+ loader

    in Developer Discussion Room

    Posted · Edited by Atlas

    I was wondering if there is any way to use drive 1 in DSM with LSI 9400-16i. If I use SataPortMap=1 and DiskIdxMap=00 in user_config.json it always skip drive 1 in DSM  

     

    image.thumb.png.c212670442646e2718cb80065a1b013c.png

     

    And if I do SataPortMap=58 and DiskIdxMap=0A00 it skips 1-5 disks

    I am using Vmware PCI passthrough 9400-16i and using boot loader on SATA(0:0)

    image.thumb.png.df368bda0b5d5b8819dee988030457c8.png

    Also if I install DSM without LSI HBA it uses disk 1 with SataPortMap=58 and DiskIdxMap=0A00 but only shows 8 disk as I have attached 16 disk

    image.thumb.png.a574a9463b32909a2d6939a42c24a559.png

    image.thumb.png.48b5437e51edbf44df6d91e36bf5e638.png

     

    Was wondering what should be the SataPortMap and DiskIdxMap value with LSI 9400-16i, I don’t want it to skip disk 1 in DSM 

     

×
×
  • Create New...