Jump to content
XPEnology Community

Recommended Posts

Hardware:

SUPERMICRO X10SDV-TLN4F D-1541 (2 x 10 GbE LAN & 2 x Intel i350-AM2 GbE LAN)

LSI HBA with 8 HDDs (onboard STA controllers disabled)


Previous attempts  using TCRP & broadwellnk failed because I couldn't get a network connection (may be related to 10g NICs)

Using TCRP & broadwell gets me further because the device is now discoverable in Synology Assistant, however, I keep getting "no drives" found.

SataPortMap=8 DiskIdxMap=00 and SataPortMap=1 DiskIdxMap=00

tc@box:~$ ls -la /sys/class/ata_port
total 0
 
tc@box:~$ lspci -tvnnq
-+-[0000:ff]-+-0b.0  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D R3 QPI Link 0/1 [8086:6f81]
 |           +-0b.1  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D R3 QPI Link 0/1 [8086:6f36]
 |           +-0b.2  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D R3 QPI Link 0/1 [8086:6f37]
 |           +-0b.3  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D R3 QPI Link Debug [8086:6f76]
 |           +-0c.0  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent [8086:6fe0]
 |           +-0c.1  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent [8086:6fe1]
 |           +-0c.2  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent [8086:6fe2]
 |           +-0c.3  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent [8086:6fe3]
 |           +-0c.4  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent [8086:6fe4]
 |           +-0c.5  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent [8086:6fe5]
 |           +-0c.6  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent [8086:6fe6]
 |           +-0c.7  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent [8086:6fe7]
 |           +-0f.0  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent [8086:6ff8]
 |           +-0f.4  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent [8086:6ffc]
 |           +-0f.5  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent [8086:6ffd]
 |           +-0f.6  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent [8086:6ffe]
 |           +-10.0  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D R2PCIe Agent [8086:6f1d]
 |           +-10.1  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D R2PCIe Agent [8086:6f34]
 |           +-10.5  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Ubox [8086:6f1e]
 |           +-10.6  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Ubox [8086:6f7d]
 |           +-10.7  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Ubox [8086:6f1f]
 |           +-12.0  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Home Agent 0 [8086:6fa0]
 |           +-12.1  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Home Agent 0 [8086:6f30]
 |           +-13.0  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Target Address/Thermal/RAS [8086:6fa8]
 |           +-13.1  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Target Address/Thermal/RAS [8086:6f71]
 |           +-13.2  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel Target Address Decoder [8086:6faa]
 |           +-13.3  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel Target Address Decoder [8086:6fab]
 |           +-13.4  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel Target Address Decoder [8086:6fac]
 |           +-13.5  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel Target Address Decoder [8086:6fad]
 |           +-13.6  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DDRIO Channel 0/1 Broadcast [8086:6fae]
 |           +-13.7  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DDRIO Global Broadcast [8086:6faf]
 |           +-14.0  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel 0 Thermal Control [8086:6fb0]
 |           +-14.1  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel 1 Thermal Control [8086:6fb1]
 |           +-14.2  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel 0 Error [8086:6fb2]
 |           +-14.3  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel 1 Error [8086:6fb3]
 |           +-14.4  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DDRIO Channel 0/1 Interface [8086:6fbc]
 |           +-14.5  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DDRIO Channel 0/1 Interface [8086:6fbd]
 |           +-14.6  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DDRIO Channel 0/1 Interface [8086:6fbe]
 |           +-14.7  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DDRIO Channel 0/1 Interface [8086:6fbf]
 |           +-15.0  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel 2 Thermal Control [8086:6fb4]
 |           +-15.1  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel 3 Thermal Control [8086:6fb5]
 |           +-15.2  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel 2 Error [8086:6fb6]
 |           +-15.3  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel 3 Error [8086:6fb7]
 |           +-1e.0  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Power Control Unit [8086:6f98]
 |           +-1e.1  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Power Control Unit [8086:6f99]
 |           +-1e.2  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Power Control Unit [8086:6f9a]
 |           +-1e.3  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Power Control Unit [8086:6fc0]
 |           +-1e.4  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Power Control Unit [8086:6f9c]
 |           +-1f.0  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Power Control Unit [8086:6f88]
 |           \-1f.2  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Power Control Unit [8086:6f8a]
 \-[0000:00]-+-00.0  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DMI2 [8086:6f00]
             +-01.0-[01]--
             +-02.0-[02]--+-00.0  Intel Corporation Xeon Processor D Family QuickData Technology Register DMA Channel 0 [8086:6f50]
             |            +-00.1  Intel Corporation Xeon Processor D Family QuickData Technology Register DMA Channel 1 [8086:6f51]
             |            +-00.2  Intel Corporation Xeon Processor D Family QuickData Technology Register DMA Channel 2 [8086:6f52]
             |            \-00.3  Intel Corporation Xeon Processor D Family QuickData Technology Register DMA Channel 3 [8086:6f53]
             +-02.2-[03]--+-00.0  Intel Corporation Ethernet Connection X552/X557-AT 10GBASE-T [8086:15ad]
             |            \-00.1  Intel Corporation Ethernet Connection X552/X557-AT 10GBASE-T [8086:15ad]
             +-03.0-[04]----00.0  LSI Logic / Symbios Logic SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] [1000:0072]
             +-05.0  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Map/VTd_Misc/System Management [8086:6f28]
             +-05.1  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D IIO Hot Plug [8086:6f29]
             +-05.2  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D IIO RAS/Control Status/Global Errors [8086:6f2a]
             +-14.0  Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI [8086:8c31]
             +-16.0  Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #1 [8086:8c3a]
             +-16.1  Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #2 [8086:8c3b]
             +-1a.0  Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 [8086:8c2d]
             +-1c.0-[05]--+-00.0  Intel Corporation I350 Gigabit Network Connection [8086:1521]
             |            \-00.1  Intel Corporation I350 Gigabit Network Connection [8086:1521]
             +-1c.4-[06-07]----00.0-[07]----00.0  ASPEED Technology, Inc. ASPEED Graphics Family [1a03:2000]
             +-1d.0  Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 [8086:8c26]
             +-1f.0  Intel Corporation C224 Series Chipset Family Server Standard SKU LPC Controller [8086:8c54]
             +-1f.3  Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller [8086:8c22]
             \-1f.6  Intel Corporation 8 Series Chipset Family Thermal Management Controller [8086:8c24]

 

Link to comment
Share on other sites

The LSI has to be recognized by DSM.  You are posting results from Tinycore.

 

SataPortMap=1 and DiskIdxMap=00 is correct for baremetal and no AHCI SATA disks.  Is the "no disks" error from DSM installation?  Then you need to look at serial output in junior mode (when GUI is at installation) and see how the HBA disks are being addressed, if at all.

 

ls -la /sys/class/scsi_disk

Link to comment
Share on other sites

I've tried various things but can't get serial-over-lan to show me any console output other than the typical startup stuff prior to tcrp booting...I'm completely mystified. .
Is there something I should be doing with the loader to activate/allow this?

Link to comment
Share on other sites

12 hours ago, trublu said:

Gave it a shot but no luck

 

How about this:

 

1.  Shut down the machine and plug out all the disks and remember the orders, just in case;

2. Reboot to DSM USB;

3. Use the assistant to find the NAS. Should return no disk error, right?

4. Plug in 1 disk, and retry it in the assitant;

Link to comment
Share on other sites

On 6/24/2022 at 2:17 AM, justinavril said:

 

How about this:

 

1.  Shut down the machine and plug out all the disks and remember the orders, just in case;

2. Reboot to DSM USB;

3. Use the assistant to find the NAS. Should return no disk error, right?

4. Plug in 1 disk, and retry it in the assitant;

That’s exactly what I did. I even let it sit for a few minutes after plugging hard drives in.

Link to comment
Share on other sites

58 minutes ago, trublu said:

That’s exactly what I did. I even let it sit for a few minutes after plugging hard drives in.

 

What is the model number of LSI HBA?

 

LSI Logic / Symbios Logic SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] [1000:0072]

 

Link to comment
Share on other sites

  • 3 weeks later...

I'm also having trouble with No Drives Detected.  

 

Any help would be appreciated. I've been trying to get this working for the last 10 hours and no luck.

 

Followed these instructions:

 

 ./rploader.sh update
 ./rploader.sh fullupgrade

 

 Configure System-Specific Parameters
 USB flash drive VID/PID      : ./rploader.sh identifyusb
 Serial number/MAC  : ./rploader.sh serialgen DS3622xs+ realmac

 

 Build the Loader
 ./rploader.sh build broadwellnk-7.1.0-42661
 exitcheck.sh reboot

 

My user_config.json file is:

 

{
  "extra_cmdline": {
    "mac2": "001132A8B800",
    "netif_num": "2",
    "pid": "0x6364",
    "vid": "0x058f",
    "sn": "1430ODN024343",
    "mac1": "0011327B8CF8",
    "SataPortMap": "58",
    "DiskIdxMap": "0A00"
  },
  "synoinfo": {
    "internalportcfg": "0xffff",
    "maxdisks": "16",
    "support_bde_internal_10g": "no",
    "support_disk_compatibility": "no",
    "support_memory_compatibility": "no"
  },
  "ramdisk_copy": {}
}

 

 

image.thumb.png.b13eb18990483fdacb2b59d1db027553.png

 

 

Link to comment
Share on other sites

1 hour ago, Steve W said:

I'm also having trouble with No Drives Detected.  

 

Any help would be appreciated. I've been trying to get this working for the last 10 hours and no luck.

 

Followed these instructions:

 

 ./rploader.sh update
 ./rploader.sh fullupgrade

 

 Configure System-Specific Parameters
 USB flash drive VID/PID      : ./rploader.sh identifyusb
 Serial number/MAC  : ./rploader.sh serialgen DS3622xs+ realmac

 

 Build the Loader
 ./rploader.sh build broadwellnk-7.1.0-42661
 exitcheck.sh reboot

 

My user_config.json file is:

 

{
  "extra_cmdline": {
    "mac2": "001132A8B800",
    "netif_num": "2",
    "pid": "0x6364",
    "vid": "0x058f",
    "sn": "1430ODN024343",
    "mac1": "0011327B8CF8",
    "SataPortMap": "58",
    "DiskIdxMap": "0A00"
  },
  "synoinfo": {
    "internalportcfg": "0xffff",
    "maxdisks": "16",
    "support_bde_internal_10g": "no",
    "support_disk_compatibility": "no",
    "support_memory_compatibility": "no"
  },
  "ramdisk_copy": {}
}

 

 

image.thumb.png.b13eb18990483fdacb2b59d1db027553.png

 

 

Test with this

 

./rploader.sh satamap

 

Or change manually 

 

    "SataPortMap": "58",
    "DiskIdxMap": "0A00"

 

Link to comment
Share on other sites

I did a fresh install and no difference. 

 

New updated user_config.json

{
  "extra_cmdline": {
    "pid": "0xa4a5",
    "vid": "0x0525",
    "sn": "20C0SQRFE3QPZ",
    "mac1": "74D4358EF252",
    "SataPortMap": "1",
    "DiskIdxMap": "00"
  },
  "synoinfo": {
    "internalportcfg": "0xffff",
    "maxdisks": "16",
    "support_bde_internal_10g": "no",
    "support_disk_compatibility": "no",
    "support_memory_compatibility": "no"
  },
  "ramdisk_copy": {}
}

 

Still not detecting drives.

 

Any more suggestions?

Link to comment
Share on other sites

7 hours ago, Steve W said:

I did a fresh install and no difference. 

 

New updated user_config.json

{
  "extra_cmdline": {
    "pid": "0xa4a5",
    "vid": "0x0525",
    "sn": "20C0SQRFE3QPZ",
    "mac1": "74D4358EF252",
    "SataPortMap": "1",
    "DiskIdxMap": "00"
  },
  "synoinfo": {
    "internalportcfg": "0xffff",
    "maxdisks": "16",
    "support_bde_internal_10g": "no",
    "support_disk_compatibility": "no",
    "support_memory_compatibility": "no"
  },
  "ramdisk_copy": {}
}

 

Still not detecting drives.

 

Any more suggestions?

 

can you provide the following from TCRP 0.9 ?

 

lspci -nnk

lspci -nnq

fdisk -l 

 

 

Link to comment
Share on other sites

Posted (edited)
8 hours ago, Steve W said:

I did a fresh install and no difference. 

 

New updated user_config.json

{
  "extra_cmdline": {
    "pid": "0xa4a5",
    "vid": "0x0525",
    "sn": "20C0SQRFE3QPZ",
    "mac1": "74D4358EF252",
    "SataPortMap": "1",
    "DiskIdxMap": "00"
  },
  "synoinfo": {
    "internalportcfg": "0xffff",
    "maxdisks": "16",
    "support_bde_internal_10g": "no",
    "support_disk_compatibility": "no",
    "support_memory_compatibility": "no"
  },
  "ramdisk_copy": {}
}

 

Still not detecting drives.

 

Any more suggestions?

 

Don't skip commands needed for the build process.
    "pid": "0xa4a5",
     "vid": "0x0525",
This value is the original initial value of TCRP.

 

And build in jun mode if possible
If you install DSM in jot mode like now, the latest version 7.1 update 3 will be installed and you will run into another problem.

 

All commands are used without omitting them, and jun mode is built as follows.

 

./rploader.sh build broadwellnk-7.0.1-42218-JUN jun

 

Don't worry about the 7.0.1 bootloader being built
You can use the latest version of DSM, 7.1, during the DSM installation process.

 

 

Edited by Peter Suh
Link to comment
Share on other sites

 

I'm using RPTC 0.8.0.0

I've attached outputs to file.

 

Commands used are:

 

 Update & Upgrade
 ./rploader.sh update
 ./rploader.sh fullupgrade

 

Configure System-Specific Parameters
 USB flash drive VID/PID: ./rploader.sh identifyusb
 Serial number/MAC  : ./rploader.sh serialgen DS3622xs+ realmac
./rploader.sh satamap now

 

Build the Loader
 ./rploader.sh build broadwellnk-7.1.0-42661 (Original attempted that failed to detect drives.)
./rploader.sh build broadwellnk-7.0.1-42218-JUN jun (Unable to detect in Synology Assistant after this build)
 exitcheck.sh reboot

 

 

user_config.json file

{
  "extra_cmdline": {
    "pid": "0x6364",
    "vid": "0x058f",
    "sn": "2030SQRNPPZHX",
    "mac1": "00004F898FBD",
    "SataPortMap": "1",
    "DiskIdxMap": "00"
  },
  "synoinfo": {
    "internalportcfg": "0xffff",
    "maxdisks": "16",
    "support_bde_internal_10g": "no",
    "support_disk_compatibility": "no",
    "support_memory_compatibility": "no"
  },
  "ramdisk_copy": {}
}

 

I'm still not having any luck.

Query.txt

Link to comment
Share on other sites

On 7/18/2022 at 9:06 AM, Steve W said:

 

Can you please send me the link with instructions and I'll try it?

Burn this .img Release v0.3-alpha3 · fbelavenuto/arpl (github.com)

 

Only need to type menu.sh or enter with browser to ip that shows or with putty and root/Redp1lL-1s-4weSomE

 

Then choose model, serialgen, add drivers, build and load, wait and find with Synology Assistant or find.synoly.com or wireless network watcher

Link to comment
Share on other sites

Цитата

Then choose model, serialgen, add drivers, build and load, wait and find with Synology Assistant or find.synoly.com or wireless network watcher

good afternoon. Tell me how to add drivers through this bootloader?

 

Link to comment
Share on other sites

Then choose model, serialgen, add drivers, build and load, wait and find with Synology Assistant or find.synoly.com or wireless network watcher
good afternoon. Tell me how to add drivers through this bootloader?
 

There is an option, you can add drivers and write r6189.addons for example
Link to comment
Share on other sites

I was experiencing the same issue, it's definitely related to SATA port mapping. On all previous occasions tinycore wanted to override detected configuration claiming that otherwise DSM installation will fail. I've decided not to allow it to do so and left original values presented below:

 

"SataPortMap": "6",
"DiskIdxMap": "00"

 

It complained that DSM installation will fail but it actually worked perfectly fine. Try that if possible, my chipset is H470 if that's of any help.

Good luck

Link to comment
Share on other sites

Posted (edited)

I am a happy owner of a sata controller Asmtdia Asm 1062.

In the BIOS, the controller was determined and the disks on it are visible in the photo. When installing hpenlog shows only two ports and one drive.

motherboard gigabit H170n-wi-fi. I install via Redpill Loader. Is it possible to load drivers there when building the bootloader? Can someone come across this?

controller has 6 ports

1.jpg

2.jpg

 

image.png.b40c9cad9d3231476efc048e34742389.png

 

image.png.36aed0e539fe5d05df9c8cad363acc4e.png

 

Edited by Wiki42
Link to comment
Share on other sites

Posted (edited)

In the TCRP bootloader, when installing dsm, I set sataportmap = 1. After installing dsm, it does not see the rest of the disks.

image.thumb.png.06479d2d8b86cb7186d03047419af57b.png

Maybe some drivers are missing?
Tell me what could be the problem. I've been struggling with it for a week now.

 

Edited by Wiki42
Link to comment
Share on other sites

9 hours ago, Wiki42 said:

In the TCRP bootloader, when installing dsm, I set sataportmap = 1. After installing dsm, it does not see the rest of the disks.

image.thumb.png.06479d2d8b86cb7186d03047419af57b.png

Maybe some drivers are missing?
Tell me what could be the problem. I've been struggling with it for a week now.

 

Have  you tried disabling some of the onboard SATA ports if you don’t intend to use them, or editing the user config max disk to 20?

Your build error shows your port count exceed the max disks

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.   Paste as plain text instead

  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.

 Share

×
×
  • Create New...