Jump to content
XPEnology Community

Help needed - Expand Xpenology (DSM7) beyond x drives


Recommended Posts

I am currently switching from DSM 6.2 to 7.1 and my setup is as follows:

 

How to expand drive number in DSM7?

Now my problem is, that it is not possible to do the same trick in DSM 7 to expand beyond x drives like it was in 6.2. (My setup would allow 22 in total from which 14 are used for now)

 

 

I already chattet with @Peter Suhabout this topic but unfortunetly we could not solve my problem.

 

Things I tried:

 

Building the loader as described by @Peter Suh (Guide)

 

  1. installed the latest tcrp image with rufus on usb
  2. booted in tc & connected via ssh
  3. ./rploader.sh update
    ./my.sh
    ./rploader.sh clean
    ./my.sh DS3622xs+J poco noclean

 

Building the loader as described by @flyride (Guide)

 

  1. installed the latest tcrp image with rufus on usb
  2. booted in tc & connected via ssh
  3. ./rploader.sh update
    ./rploader.sh fullupgrade
    ./rploader.sh identifyusb
    ./rploader.sh serialgen DS3622xs+

     

  4. #I tried building the loader with and without this command
    ./rploader.sh satamap

     

  5. vi user_config.json
    # adding those lines:
        "maxdisks" : "22",
        "esataportcfg" : "0x00",
        "usbportcfg" : "0xc000000",
        "internalportcfg" : "0x3fffff", 
  6. ./rploader.sh build broadwellnk-7.1.0-42661
    ./rploader.sh backup
    ./rploader.sh backuploader
    exitcheck.sh reboot

     

 

 

Seutp & outcome

 

VM or BareMetal : BareMetal
Hardware (Motherboard/CPU) : MSI MPG Z390 / Intel 9900T

Storage-Controller: 2x LSI SAS 9211-8i (HBA in IT mode)
Hot Plug Applied : Yes
Network Interface 1 : Intel i217v (e1000e)
Network Interface 2 : Intel X540-T2 (10 Gbit)
Network Interface 3 : Intel X540-T2 (10 Gbit)
Loader : TCRP 0.4.6
version of rploader.sh : 0.8.3
Platform : 3622xs+
Platform Version : 7.1
Platform Revision : 42661-U1
GRUB Boot selection : USB

 

Unfortunetly both methods resulted in the same outcome which is the following:

 

My NAS looks physically like this. I numbered the drive slots from 1 - 22 to have an easier time explaining my issue. 

 

image.thumb.png.ea89589a04c6319cfd945ea11d2cc8db.png

 

So slotnumber

  • 1-8 are connected to HBA 2
  • 9,10 and 17-22 are connected to HBA 1
  • 11-16 are connected to the mainboard SATA ports

I have 3 PCIx16 Slots on my mainboard

  • First one is used for Intel X540 T2 10 GBit NIC
  • Second one is used for HBA1
  • Third one is used for HBA2

Currently the slots below are occupied:

  • 1-4 = 4 HDDs
  • 6-9 = 4 HDDs
  • 11-13 = 3 SSDs
  • 17-19 = 3 SSDs

= 14 drives in total.

Now in this config either slot 6 or 7 isnt recognised in DSM, every other drive works.

When I put the drive from slot 6 into slot 5 it is reconised, BUT unfortunately one drive from slots 1-4 is missing then.

 

I tried this with multiple combinations. The outcome was always that 1 drive was missing (not a specific HDD/SSD or SLOT). As soon as I add more than 13 drives it keeps getting weird. Since my setup worked in DSM6 my guess is that either I am missing something or TCRP is missing something.

 

Troubleshooting:

 

TinyCore sd list

lrwxrwxrwx 1 root root 0 Jun 26 09:08 loop0 -> ../devices/virtual/block/loop0
lrwxrwxrwx 1 root root 0 Jun 26 09:08 loop1 -> ../devices/virtual/block/loop1
lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop10 -> ../devices/virtual/block/loop10
lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop11 -> ../devices/virtual/block/loop11
lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop12 -> ../devices/virtual/block/loop12
lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop13 -> ../devices/virtual/block/loop13
lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop14 -> ../devices/virtual/block/loop14
lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop15 -> ../devices/virtual/block/loop15
lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop16 -> ../devices/virtual/block/loop16
lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop17 -> ../devices/virtual/block/loop17
lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop18 -> ../devices/virtual/block/loop18
lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop19 -> ../devices/virtual/block/loop19
lrwxrwxrwx 1 root root 0 Jun 26 09:08 loop2 -> ../devices/virtual/block/loop2
lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop20 -> ../devices/virtual/block/loop20
lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop21 -> ../devices/virtual/block/loop21
lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop22 -> ../devices/virtual/block/loop22
lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop23 -> ../devices/virtual/block/loop23
lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop24 -> ../devices/virtual/block/loop24
lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop25 -> ../devices/virtual/block/loop25
lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop26 -> ../devices/virtual/block/loop26
lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop27 -> ../devices/virtual/block/loop27
lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop28 -> ../devices/virtual/block/loop28
lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop29 -> ../devices/virtual/block/loop29
lrwxrwxrwx 1 root root 0 Jun 26 09:08 loop3 -> ../devices/virtual/block/loop3
lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop30 -> ../devices/virtual/block/loop30
lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop31 -> ../devices/virtual/block/loop31
lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop32 -> ../devices/virtual/block/loop32
lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop33 -> ../devices/virtual/block/loop33
lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop34 -> ../devices/virtual/block/loop34
lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop35 -> ../devices/virtual/block/loop35
lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop36 -> ../devices/virtual/block/loop36
lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop37 -> ../devices/virtual/block/loop37
lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop38 -> ../devices/virtual/block/loop38
lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop39 -> ../devices/virtual/block/loop39
lrwxrwxrwx 1 root root 0 Jun 26 09:08 loop4 -> ../devices/virtual/block/loop4
lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop40 -> ../devices/virtual/block/loop40
lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop41 -> ../devices/virtual/block/loop41
lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop42 -> ../devices/virtual/block/loop42
lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop43 -> ../devices/virtual/block/loop43
lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop44 -> ../devices/virtual/block/loop44
lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop45 -> ../devices/virtual/block/loop45
lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop46 -> ../devices/virtual/block/loop46
lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop47 -> ../devices/virtual/block/loop47
lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop48 -> ../devices/virtual/block/loop48
lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop49 -> ../devices/virtual/block/loop49
lrwxrwxrwx 1 root root 0 Jun 26 09:08 loop5 -> ../devices/virtual/block/loop5
lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop50 -> ../devices/virtual/block/loop50
lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop51 -> ../devices/virtual/block/loop51
lrwxrwxrwx 1 root root 0 Jun 26 09:08 loop6 -> ../devices/virtual/block/loop6
lrwxrwxrwx 1 root root 0 Jun 26 09:08 loop7 -> ../devices/virtual/block/loop7
lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop8 -> ../devices/virtual/block/loop8
lrwxrwxrwx 1 root root 0 Jun 26 09:11 loop9 -> ../devices/virtual/block/loop9
lrwxrwxrwx 1 root root 0 Jun 26 09:08 ram0 -> ../devices/virtual/block/ram0
lrwxrwxrwx 1 root root 0 Jun 26 09:08 ram1 -> ../devices/virtual/block/ram1
lrwxrwxrwx 1 root root 0 Jun 26 09:08 ram2 -> ../devices/virtual/block/ram2
lrwxrwxrwx 1 root root 0 Jun 26 09:08 ram3 -> ../devices/virtual/block/ram3
lrwxrwxrwx 1 root root 0 Jun 26 09:08 ram4 -> ../devices/virtual/block/ram4
lrwxrwxrwx 1 root root 0 Jun 26 09:08 ram5 -> ../devices/virtual/block/ram5
lrwxrwxrwx 1 root root 0 Jun 26 09:08 ram6 -> ../devices/virtual/block/ram6
lrwxrwxrwx 1 root root 0 Jun 26 09:08 ram7 -> ../devices/virtual/block/ram7
lrwxrwxrwx 1 root root 0 Jun 26 09:08 sda -> ../devices/pci0000:00/0000:00:17.0/ata1/host0/target0:0:0/0:0:0:0/block/sda
lrwxrwxrwx 1 root root 0 Jun 26 09:08 sdb -> ../devices/pci0000:00/0000:00:17.0/ata2/host1/target1:0:0/1:0:0:0/block/sdb
lrwxrwxrwx 1 root root 0 Jun 26 09:08 sdc -> ../devices/pci0000:00/0000:00:17.0/ata5/host4/target4:0:0/4:0:0:0/block/sdc
lrwxrwxrwx 1 root root 0 Jun 26 09:08 sdd -> ../devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5:1.0/host6/target6:0:0/6:0:0:0/block/sdd
lrwxrwxrwx 1 root root 0 Jun 26 09:08 zram0 -> ../devices/virtual/block/zram0

 

Synology sd list

dummy@NAS:~$ ll /sys/block
total 0
drwxr-xr-x  2 root root 0 Jun 26 11:00 .
dr-xr-xr-x 12 root root 0 Jun 26 11:00 ..
lrwxrwxrwx  1 root root 0 Jun 26 11:05 dm-0 -> ../devices/virtual/block/dm-0
lrwxrwxrwx  1 root root 0 Jun 26 11:05 dm-1 -> ../devices/virtual/block/dm-1
lrwxrwxrwx  1 root root 0 Jun 26 11:05 dm-2 -> ../devices/virtual/block/dm-2
lrwxrwxrwx  1 root root 0 Jun 26 11:05 dm-3 -> ../devices/virtual/block/dm-3
lrwxrwxrwx  1 root root 0 Jun 26 11:00 dm-4 -> ../devices/virtual/block/dm-4
lrwxrwxrwx  1 root root 0 Jun 26 11:00 dm-5 -> ../devices/virtual/block/dm-5
lrwxrwxrwx  1 root root 0 Jun 26 11:00 dm-6 -> ../devices/virtual/block/dm-6
lrwxrwxrwx  1 root root 0 Jun 26 11:05 loop0 -> ../devices/virtual/block/loop0
lrwxrwxrwx  1 root root 0 Jun 26 11:05 loop1 -> ../devices/virtual/block/loop1
lrwxrwxrwx  1 root root 0 Jun 26 11:05 loop2 -> ../devices/virtual/block/loop2
lrwxrwxrwx  1 root root 0 Jun 26 11:05 loop3 -> ../devices/virtual/block/loop3
lrwxrwxrwx  1 root root 0 Jun 26 11:05 loop4 -> ../devices/virtual/block/loop4
lrwxrwxrwx  1 root root 0 Jun 26 11:05 loop5 -> ../devices/virtual/block/loop5
lrwxrwxrwx  1 root root 0 Jun 26 11:05 loop6 -> ../devices/virtual/block/loop6
lrwxrwxrwx  1 root root 0 Jun 26 11:05 loop7 -> ../devices/virtual/block/loop7
lrwxrwxrwx  1 root root 0 Jun 26 11:00 md0 -> ../devices/virtual/block/md0
lrwxrwxrwx  1 root root 0 Jun 26 11:00 md1 -> ../devices/virtual/block/md1
lrwxrwxrwx  1 root root 0 Jun 26 11:00 md2 -> ../devices/virtual/block/md2
lrwxrwxrwx  1 root root 0 Jun 26 11:00 md3 -> ../devices/virtual/block/md3
lrwxrwxrwx  1 root root 0 Jun 26 11:00 md5 -> ../devices/virtual/block/md5
lrwxrwxrwx  1 root root 0 Jun 26 11:05 ram0 -> ../devices/virtual/block/ram0
lrwxrwxrwx  1 root root 0 Jun 26 11:05 ram1 -> ../devices/virtual/block/ram1
lrwxrwxrwx  1 root root 0 Jun 26 11:05 ram10 -> ../devices/virtual/block/ram10
lrwxrwxrwx  1 root root 0 Jun 26 11:05 ram11 -> ../devices/virtual/block/ram11
lrwxrwxrwx  1 root root 0 Jun 26 11:05 ram12 -> ../devices/virtual/block/ram12
lrwxrwxrwx  1 root root 0 Jun 26 11:05 ram13 -> ../devices/virtual/block/ram13
lrwxrwxrwx  1 root root 0 Jun 26 11:05 ram14 -> ../devices/virtual/block/ram14
lrwxrwxrwx  1 root root 0 Jun 26 11:05 ram15 -> ../devices/virtual/block/ram15
lrwxrwxrwx  1 root root 0 Jun 26 11:05 ram2 -> ../devices/virtual/block/ram2
lrwxrwxrwx  1 root root 0 Jun 26 11:05 ram3 -> ../devices/virtual/block/ram3
lrwxrwxrwx  1 root root 0 Jun 26 11:05 ram4 -> ../devices/virtual/block/ram4
lrwxrwxrwx  1 root root 0 Jun 26 11:05 ram5 -> ../devices/virtual/block/ram5
lrwxrwxrwx  1 root root 0 Jun 26 11:05 ram6 -> ../devices/virtual/block/ram6
lrwxrwxrwx  1 root root 0 Jun 26 11:05 ram7 -> ../devices/virtual/block/ram7
lrwxrwxrwx  1 root root 0 Jun 26 11:05 ram8 -> ../devices/virtual/block/ram8
lrwxrwxrwx  1 root root 0 Jun 26 11:05 ram9 -> ../devices/virtual/block/ram9
lrwxrwxrwx  1 root root 0 Jun 26 11:00 sda -> ../devices/pci0000:00/0000:00:17.0/ata1/host0/target0:0:0/0:0:0:0/block/sda
lrwxrwxrwx  1 root root 0 Jun 26 11:00 sdb -> ../devices/pci0000:00/0000:00:17.0/ata2/host1/target1:0:0/1:0:0:0/block/sdb
lrwxrwxrwx  1 root root 0 Jun 26 11:00 sde -> ../devices/pci0000:00/0000:00:17.0/ata5/host4/target4:0:0/4:0:0:0/block/sde
lrwxrwxrwx  1 root root 0 Jun 26 11:00 sdg -> ../devices/pci0000:00/0000:00:01.1/0000:02:00.0/host6/port-6:0/end_device-6:0/target6:0:0/6:0:0:0/block/sdg
lrwxrwxrwx  1 root root 0 Jun 26 11:00 sdh -> ../devices/pci0000:00/0000:00:01.1/0000:02:00.0/host6/port-6:1/end_device-6:1/target6:0:1/6:0:1:0/block/sdh
lrwxrwxrwx  1 root root 0 Jun 26 11:00 sdi -> ../devices/pci0000:00/0000:00:01.1/0000:02:00.0/host6/port-6:2/end_device-6:2/target6:0:2/6:0:2:0/block/sdi
lrwxrwxrwx  1 root root 0 Jun 26 11:00 sdj -> ../devices/pci0000:00/0000:00:01.1/0000:02:00.0/host6/port-6:3/end_device-6:3/target6:0:3/6:0:3:0/block/sdj
lrwxrwxrwx  1 root root 0 Jun 26 11:00 sdk -> ../devices/pci0000:00/0000:00:1b.4/0000:04:00.0/host8/port-8:0/end_device-8:0/target8:0:0/8:0:0:0/block/sdk
lrwxrwxrwx  1 root root 0 Jun 26 11:00 sdl -> ../devices/pci0000:00/0000:00:1b.4/0000:04:00.0/host8/port-8:1/end_device-8:1/target8:0:1/8:0:1:0/block/sdl
lrwxrwxrwx  1 root root 0 Jun 26 11:00 sdm -> ../devices/pci0000:00/0000:00:1b.4/0000:04:00.0/host8/port-8:2/end_device-8:2/target8:0:2/8:0:2:0/block/sdm
lrwxrwxrwx  1 root root 0 Jun 26 11:00 sdn -> ../devices/pci0000:00/0000:00:1b.4/0000:04:00.0/host8/port-8:3/end_device-8:3/target8:0:3/8:0:3:0/block/sdn
lrwxrwxrwx  1 root root 0 Jun 26 11:00 sdo -> ../devices/pci0000:00/0000:00:1b.4/0000:04:00.0/host8/port-8:4/end_device-8:4/target8:0:4/8:0:4:0/block/sdo
lrwxrwxrwx  1 root root 0 Jun 26 11:00 sdp -> ../devices/pci0000:00/0000:00:1b.4/0000:04:00.0/host8/port-8:5/end_device-8:5/target8:0:5/8:0:5:0/block/sdp
lrwxrwxrwx  1 root root 0 Jun 26 11:00 synoboot -> ../devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5:1.0/host7/target7:0:0/7:0:0:0/block/synoboot
lrwxrwxrwx  1 root root 0 Jun 26 11:00 zram0 -> ../devices/virtual/block/zram0
lrwxrwxrwx  1 root root 0 Jun 26 11:00 zram1 -> ../devices/virtual/block/zram1
lrwxrwxrwx  1 root root 0 Jun 26 11:00 zram2 -> ../devices/virtual/block/zram2
lrwxrwxrwx  1 root root 0 Jun 26 11:00 zram3 -> ../devices/virtual/block/zram3
lrwxrwxrwx  1 root root 0 Jun 26 11:00 zram4 -> ../devices/virtual/block/zram4
lrwxrwxrwx  1 root root 0 Jun 26 11:00 zram5 -> ../devices/virtual/block/zram5
lrwxrwxrwx  1 root root 0 Jun 26 11:00 zram6 -> ../devices/virtual/block/zram6
lrwxrwxrwx  1 root root 0 Jun 26 11:00 zram7 -> ../devices/virtual/block/zram7

 

Ubuntu tryout sd list

root@ubuntu:~# ll /sys/block
total 0
drwxr-xr-x  2 root root 0 Jun 26 09:24 ./
dr-xr-xr-x 13 root root 0 Jun 26 09:24 ../
lrwxrwxrwx  1 root root 0 Jun 26 09:24 loop0 -> ../devices/virtual/block/loop0/
lrwxrwxrwx  1 root root 0 Jun 26 09:24 loop1 -> ../devices/virtual/block/loop1/
lrwxrwxrwx  1 root root 0 Jun 26 09:24 loop2 -> ../devices/virtual/block/loop2/
lrwxrwxrwx  1 root root 0 Jun 26 09:24 loop3 -> ../devices/virtual/block/loop3/
lrwxrwxrwx  1 root root 0 Jun 26 09:24 loop4 -> ../devices/virtual/block/loop4/
lrwxrwxrwx  1 root root 0 Jun 26 09:24 loop5 -> ../devices/virtual/block/loop5/
lrwxrwxrwx  1 root root 0 Jun 26 09:24 loop6 -> ../devices/virtual/block/loop6/
lrwxrwxrwx  1 root root 0 Jun 26 09:24 loop7 -> ../devices/virtual/block/loop7/
lrwxrwxrwx  1 root root 0 Jun 26 09:25 loop8 -> ../devices/virtual/block/loop8/
lrwxrwxrwx  1 root root 0 Jun 26 09:27 loop9 -> ../devices/virtual/block/loop9/
lrwxrwxrwx  1 root root 0 Jun 26 09:24 sda -> ../devices/pci0000:00/0000:00:01.1/0000:02:00.0/host0/port-0:0/end_device-0:0/target0:0:0/0:0:0:0/block/sda/
lrwxrwxrwx  1 root root 0 Jun 26 09:24 sdb -> ../devices/pci0000:00/0000:00:01.1/0000:02:00.0/host0/port-0:1/end_device-0:1/target0:0:1/0:0:1:0/block/sdb/
lrwxrwxrwx  1 root root 0 Jun 26 09:24 sdc -> ../devices/pci0000:00/0000:00:01.1/0000:02:00.0/host0/port-0:2/end_device-0:2/target0:0:2/0:0:2:0/block/sdc/
lrwxrwxrwx  1 root root 0 Jun 26 09:24 sdd -> ../devices/pci0000:00/0000:00:01.1/0000:02:00.0/host0/port-0:3/end_device-0:3/target0:0:3/0:0:3:0/block/sdd/
lrwxrwxrwx  1 root root 0 Jun 26 09:24 sde -> ../devices/pci0000:00/0000:00:1b.4/0000:04:00.0/host7/port-7:0/end_device-7:0/target7:0:0/7:0:0:0/block/sde/
lrwxrwxrwx  1 root root 0 Jun 26 09:24 sdf -> ../devices/pci0000:00/0000:00:1b.4/0000:04:00.0/host7/port-7:1/end_device-7:1/target7:0:1/7:0:1:0/block/sdf/
lrwxrwxrwx  1 root root 0 Jun 26 09:24 sdg -> ../devices/pci0000:00/0000:00:1b.4/0000:04:00.0/host7/port-7:2/end_device-7:2/target7:0:2/7:0:2:0/block/sdg/
lrwxrwxrwx  1 root root 0 Jun 26 09:24 sdh -> ../devices/pci0000:00/0000:00:1b.4/0000:04:00.0/host7/port-7:3/end_device-7:3/target7:0:3/7:0:3:0/block/sdh/
lrwxrwxrwx  1 root root 0 Jun 26 09:24 sdi -> ../devices/pci0000:00/0000:00:1b.4/0000:04:00.0/host7/port-7:4/end_device-7:4/target7:0:4/7:0:4:0/block/sdi/
lrwxrwxrwx  1 root root 0 Jun 26 09:24 sdj -> ../devices/pci0000:00/0000:00:1b.4/0000:04:00.0/host7/port-7:5/end_device-7:5/target7:0:5/7:0:5:0/block/sdj/
lrwxrwxrwx  1 root root 0 Jun 26 09:24 sdk -> ../devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5:1.0/host8/target8:0:0/8:0:0:0/block/sdk/
lrwxrwxrwx  1 root root 0 Jun 26 09:24 sdl -> ../devices/pci0000:00/0000:00:17.0/ata1/host1/target1:0:0/1:0:0:0/block/sdl/
lrwxrwxrwx  1 root root 0 Jun 26 09:24 sdm -> ../devices/pci0000:00/0000:00:17.0/ata2/host2/target2:0:0/2:0:0:0/block/sdm/
lrwxrwxrwx  1 root root 0 Jun 26 09:24 sdn -> ../devices/pci0000:00/0000:00:17.0/ata5/host5/target5:0:0/5:0:0:0/block/sdn/

 

I would appreciate any hints🙂

Link to comment
Share on other sites

7 minutes ago, smileyworld said:
    "usbportcfg" : "0xc000000",
    "internalportcfg" : "0x3fffff", 

in theory there should be one zero less in usbportcfg

0xc00000
0x3fffff

the 3 and the c shold be on the same position

but i dont think that causes a problem here

maybe you try to do the same with 3617 (broadwell-7.1.0-42661)

Link to comment
Share on other sites

It seems to be right to have a list of 14 disks from the beginning and compare them from there.

 

First install the scsi driver below on TC linux

 

tce-load -iw scsi-5.10.3-tinycore64.tcz

 

Please upload only the disk list again with the command below.

 

ll /sys/block | grep ata

 

Link to comment
Share on other sites

@Peter SuhLooks like only drives in slot 11-13 are recognised by tc even though the scsi-5.10.3-tinycore64.tcz was saved and I got an OK message.

 

lrwxrwxrwx 1 root root 0 Jul  2 03:52 sda -> ../devices/pci0000:00/0000:00:17.0/ata1/host0/target0:0:0/0:0:0:0/block/sda
lrwxrwxrwx 1 root root 0 Jul  2 03:52 sdb -> ../devices/pci0000:00/0000:00:17.0/ata2/host1/target1:0:0/1:0:0:0/block/sdb
lrwxrwxrwx 1 root root 0 Jul  2 03:52 sdc -> ../devices/pci0000:00/0000:00:17.0/ata5/host4/target4:0:0/4:0:0:0/block/sdc

 

Link to comment
Share on other sites

@Peter SuhLooks like only drives in slot 11-13 are recognised by tc even though the scsi-5.10.3-tinycore64.tcz was saved and I got an OK message.
 
lrwxrwxrwx 1 root root 0 Jul  2 03:52 sda -> ../devices/pci0000:00/0000:00:17.0/ata1/host0/target0:0:0/0:0:0:0/block/sdalrwxrwxrwx 1 root root 0 Jul  2 03:52 sdb -> ../devices/pci0000:00/0000:00:17.0/ata2/host1/target1:0:0/1:0:0:0/block/sdblrwxrwxrwx 1 root root 0 Jul  2 03:52 sdc -> ../devices/pci0000:00/0000:00:17.0/ata5/host4/target4:0:0/4:0:0:0/block/sdc

 


As I mentioned last time, I use the same HBA. I think the disks were all listed up when I used that scasi driver. I will let you know after doing the same test. Did you check /sys/block on junior with me and PM? This is actually the most important point.


Sent from my iPhone using Tapatalk
Link to comment
Share on other sites

1 hour ago, Peter Suh said:


As I mentioned last time, I use the same HBA. I think the disks were all listed up when I used that scasi driver. I will let you know after doing the same test. Did you check /sys/block on junior with me and PM? This is actually the most important point.


Sent from my iPhone using Tapatalk

 

The grep filter I gave you is wrong.
Try changing it to target as shown below.
I also installed 7 disks in HBA2, but there was a problem that 1 was not visible.
action is being taken

 

ll /sys/block | grep target

 

tc@box:~$ ll /sys/block | grep target
lrwxrwxrwx 1 root root 0 Jul  2 08:16 sda -> ../devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda
lrwxrwxrwx 1 root root 0 Jul  2 08:16 sdb -> ../devices/pci0000:00/0000:00:1f.2/ata2/host1/target1:0:0/1:0:0:0/block/sdb
lrwxrwxrwx 1 root root 0 Jul  2 08:16 sdc -> ../devices/pci0000:00/0000:00:1f.2/ata3/host2/target2:0:0/2:0:0:0/block/sdc
lrwxrwxrwx 1 root root 0 Jul  2 08:16 sdd -> ../devices/pci0000:00/0000:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sdd
lrwxrwxrwx 1 root root 0 Jul  2 08:16 sde -> ../devices/pci0000:00/0000:00:1f.2/ata5/host4/target4:0:0/4:0:0:0/block/sde
lrwxrwxrwx 1 root root 0 Jul  2 08:16 sdf -> ../devices/pci0000:00/0000:00:1f.2/ata6/host5/target5:0:0/5:0:0:0/block/sdf
lrwxrwxrwx 1 root root 0 Jul  2 08:16 sdg -> ../devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.0/host6/target6:0:0/6:0:0:0/block/sdg
lrwxrwxrwx 1 root root 0 Jul  2 08:17 sdh -> ../devices/pci0000:00/0000:00:01.1/0000:02:00.0/host7/port-7:0/end_device-7:0/target7:0:0/7:0:0:0/block/sdh
lrwxrwxrwx 1 root root 0 Jul  2 08:17 sdi -> ../devices/pci0000:00/0000:00:01.1/0000:02:00.0/host7/port-7:1/end_device-7:1/target7:0:1/7:0:1:0/block/sdi
lrwxrwxrwx 1 root root 0 Jul  2 08:17 sdj -> ../devices/pci0000:00/0000:00:01.1/0000:02:00.0/host7/port-7:2/end_device-7:2/target7:0:2/7:0:2:0/block/sdj
lrwxrwxrwx 1 root root 0 Jul  2 08:17 sdk -> ../devices/pci0000:00/0000:00:01.1/0000:02:00.0/host7/port-7:3/end_device-7:3/target7:0:3/7:0:3:0/block/sdk
lrwxrwxrwx 1 root root 0 Jul  2 08:17 sdl -> ../devices/pci0000:00/0000:00:01.1/0000:02:00.0/host7/port-7:4/end_device-7:4/target7:0:4/7:0:4:0/block/sdl
lrwxrwxrwx 1 root root 0 Jul  2 08:17 sdm -> ../devices/pci0000:00/0000:00:01.1/0000:02:00.0/host7/port-7:5/end_device-7:5/target7:0:5/7:0:5:0/block/sdm

Link to comment
Share on other sites

Posted (edited)

This is my case.

  • 1-6 are internal Sata Port  (6 port)
  • 7-14 are connected to HBA 1  (8 port)
  • 15-22 are connected to HBA 2 (8 port) 

I have 1 PCIx16 Slot and 2 PCIx4 Slots on my mainboard

  • First one is used for HBA2
  • Second one is empty ( PCIx16 )
  • Third one is used for HBA1

Currently the slots below are occupied:

  • 1-3 = 3 SSDs & HDDs
  • 7-9 = 3 HDDs
  • 15-21 = 7 HDDs

= 13 drives in total.

 

But, In HBA2 only one Disk is disapear, same as you.

 

This is my Mobo bios , HBA bios and TC linux screen shot.

 

1723526257_.thumb.jpg.d789b2a6faffe774eb9bbf9decf2c893.jpg

 

 

E2C9C99E-23D2-41C2-8379-56D5F664A79C_1_105_c.thumb.jpeg.9d19652d57b0687dd41ea12e54966007.jpeg

 

 

1331635741_2022-07-027_57_32.thumb.png.a6cb63524a531dc5a79b2389ecb2e61c.png

Edited by Peter Suh
Link to comment
Share on other sites

14 hours ago, Peter Suh said:


As I mentioned last time, I use the same HBA. I think the disks were all listed up when I used that scasi driver. I will let you know after doing the same test. Did you check /sys/block on junior with me and PM? This is actually the most important point.


Sent from my iPhone using Tapatalk

Yes that was me and I checked it.

13 hours ago, Peter Suh said:

 

The grep filter I gave you is wrong.
Try changing it to target as shown below.
I also installed 7 disks in HBA2, but there was a problem that 1 was not visible.
action is being taken

 

ll /sys/block | grep target

 

tc@box:~$ ll /sys/block | grep target
lrwxrwxrwx 1 root root 0 Jul  2 08:16 sda -> ../devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda
lrwxrwxrwx 1 root root 0 Jul  2 08:16 sdb -> ../devices/pci0000:00/0000:00:1f.2/ata2/host1/target1:0:0/1:0:0:0/block/sdb
lrwxrwxrwx 1 root root 0 Jul  2 08:16 sdc -> ../devices/pci0000:00/0000:00:1f.2/ata3/host2/target2:0:0/2:0:0:0/block/sdc
lrwxrwxrwx 1 root root 0 Jul  2 08:16 sdd -> ../devices/pci0000:00/0000:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sdd
lrwxrwxrwx 1 root root 0 Jul  2 08:16 sde -> ../devices/pci0000:00/0000:00:1f.2/ata5/host4/target4:0:0/4:0:0:0/block/sde
lrwxrwxrwx 1 root root 0 Jul  2 08:16 sdf -> ../devices/pci0000:00/0000:00:1f.2/ata6/host5/target5:0:0/5:0:0:0/block/sdf
lrwxrwxrwx 1 root root 0 Jul  2 08:16 sdg -> ../devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.0/host6/target6:0:0/6:0:0:0/block/sdg
lrwxrwxrwx 1 root root 0 Jul  2 08:17 sdh -> ../devices/pci0000:00/0000:00:01.1/0000:02:00.0/host7/port-7:0/end_device-7:0/target7:0:0/7:0:0:0/block/sdh
lrwxrwxrwx 1 root root 0 Jul  2 08:17 sdi -> ../devices/pci0000:00/0000:00:01.1/0000:02:00.0/host7/port-7:1/end_device-7:1/target7:0:1/7:0:1:0/block/sdi
lrwxrwxrwx 1 root root 0 Jul  2 08:17 sdj -> ../devices/pci0000:00/0000:00:01.1/0000:02:00.0/host7/port-7:2/end_device-7:2/target7:0:2/7:0:2:0/block/sdj
lrwxrwxrwx 1 root root 0 Jul  2 08:17 sdk -> ../devices/pci0000:00/0000:00:01.1/0000:02:00.0/host7/port-7:3/end_device-7:3/target7:0:3/7:0:3:0/block/sdk
lrwxrwxrwx 1 root root 0 Jul  2 08:17 sdl -> ../devices/pci0000:00/0000:00:01.1/0000:02:00.0/host7/port-7:4/end_device-7:4/target7:0:4/7:0:4:0/block/sdl
lrwxrwxrwx 1 root root 0 Jul  2 08:17 sdm -> ../devices/pci0000:00/0000:00:01.1/0000:02:00.0/host7/port-7:5/end_device-7:5/target7:0:5/7:0:5:0/block/sdm

I will report back tomorrow. Maybe I found something which would explain the behavior, but I want to double check first.

Link to comment
Share on other sites

@Peter Suh

 

 

I am not so sure anymore that it has solely to do with tcrp or DSM7.

 

I tried plugging in 22 drives and even in mint only 20 are recognized.

 

Maybe there is also an issue with the HBA or a cable.

 

image.thumb.png.8503a9acbca1bd49c633714037148cba.png

 

I also saw during boot that there my two HBAs are on different BIOSes.

 

My plan is to identify the missing drives first and then changing the drives to different slots, so I can be sure all drives are ok.

 

Next thing will be to upgrade firmware of my HBAs.

 

If that doesnt help, than i really dont know where to look even further.

Link to comment
Share on other sites

Posted (edited)

I am also perplexed as I first discovered this issue in the SAS2008 IT Mode firmware.
I think we should do a search on the internet to see if this issue originally existed.
I also have a Dell Perc H200, with the same firmware and
The same phenomenon occurs when drives disappear one by one.
I'll have to double-check all the firmware versions currently being applied.
Currently, only legacy firmware is applied and used.
I'm thinking of trying to change to EFI firmware.

Edited by Peter Suh
  • Like 1
Link to comment
Share on other sites

7 hours ago, smileyworld said:

There also seems to be a known issue with duplicate drives which is documented even by broadcom itself. Interestingly this is also a bad firmware problem.

 

https://www.broadcom.com/support/knowledgebase/1211161495925/flash-upgrading-firmware-on-lsi-sas-hbas-upgraded-firmware-on-92

 

However, this solution seems to have been shared too long ago.
The latest revision is already up to P20.
Problems solved in P9 are likely to be included in P20 as well.
Perhaps you too will use the P19 or P20 revision.
If you enter the SAS BIOS by pressing CTRL+C, it is the first number in the FW revision item.

Link to comment
Share on other sites

Posted (edited)

@Peter Suh
Yes that's true.

 

It looks like it's a firmware issue after all.

 

I connected my NAS to a display and was wondering why only one of the HBAs was displaying in BIOS (ctrl +c). Now 2 hours later I learned that I have 2 different controller cards even though they were sold both as LSI 9211-8i (IT-mode). It seems there was so much rebranding and the companies used same or similar chips (sas2008) but different BIOSes.

 

At least someone mentioned this here

--------------------------------------------------------------------------------------------

image.png.921486d9de07d3b63f8b7ee5c9f63f2b.png

--------------------------------------------------------------------------------------------

 

MegaRAID is however able to see both HBAs and collects the following data from both cards.

image.thumb.png.40e8996705886ca2cbfe39bc679856cd.png

image.thumb.png.dccf1f47eb210436b2fd52e25d45dcbe.png

 

I thought it would make troubleshooting easier when I simplify things (install same Firmware/BIOS) but oh boy it keeps getting more and more complex😅

  • HBA SGX-SAS6-INT-Z
    • has BIOS version 07.39.02.00_07.24.01.00
    • is working but I cannot enter the BIOS at all
    • It wont let me "update" the BIOS with 07.39.02.00 probably because downgrading firmware is not allowed
    • windows server 2016 cant find a suitable driver for this card
  • HBA SAS9211-8i
    • has BIOS version 07.39.02.00
    • has a working BIOS which I can enter with Ctrl + C.
    • windows server 2016 installs the best driver for this card on its own.

image.thumb.png.e5040c205dfd55ba1feee3619293ba9c.png

 

So at this point I do not know where to find either a firmware newer than 07.39.02.00_07.24.01.00 with a working BIOS or a way to downgrade the SGX-SAS6-INT-Z HBA to 07.39.02.00.

Furthermore I am not sure if this would fix my/our problem.

 

Do both of your HBAs have the same BIOS version?

Edited by smileyworld
Link to comment
Share on other sites

To be precise, I have a total of 4 HBAs.
Two of them are Dell Perc H310
1 x Dell Perc H200
The last one is the 9211-4i for 4 ports.

 

The HBA used in this test was
One Dell Perc H310 and one Dell Perc H200.

I tried to install 7-8 disks in H310.

 

Bios version and firmware revision seem to be managed as separate versions.
As you can see in the picture, my version of Bios is v7.39.02.00.

The target that needs to be updated is not the Bios version.
It's like a FW revision.

 

F5B46EFE-8A45-42E2-81A5-B5F75EFA0369_1_105_c.thumb.jpeg.c4139f4b09281e318119cceb20f175ad.jpeg

 

This firmware revision was mentioned as P7, P8, P9, P19, P20, etc.
Among them, it seems that I am already using the P20.

 

As you can see in the picture, both HBA cards are using the same IT mode FW revision.

This FW revision can be freely changed,

 

However, to change it, it seems to apply the desired FW revision after using the P7 first.

This part seems to be in the Broadcom guide you linked above.

 

If the FW revision of the two cards is different, will the issue disappear?

Link to comment
Share on other sites

I can finally report that I fixed it.

What I did to resolve my issue

  1. tried to determine if it is a hardware/software failure
    1. connected 8 disks to 1 HBA (HBA2 was not installed at that time) and checked if every disk was listed (computer management in windows server 2016, another OS would probably work as well)
    2. unplugged HBA1 and connected HBA2 -> also checked if 8 disks were listed -> one disk was missing, so I checked all connectors and one was loose.
    3. flashed firmware of my second HBA.
    4. connected both HBAs, installed 22 disks and all were listed in WIN server 2016
    5. unplugged my X540-T2 10Gbit NIC
  2. installed Xpenology as follows
    1. ran command by command
      1. ./rploader.sh clean
        ./rploader.sh update
        ./rploader.sh fullupgrade
        ./rploader.sh identifyusb
        ./rploader.sh serialgen DS3622xs+
        vi user_config.json
    2. adapted my user_config.json to my environment
      1. {
          "extra_cmdline": {
            "pid": "0x1000",
            "vid": "0x090c",
            "sn": "xxxxxxxxxxxxx",
            "mac1": "xxxxxxxxxxxxx",
            "mac2": "xxxxxxxxxxxxx",
            "mac3": "xxxxxxxxxxxxx",
            "SataPortMap": "",
            "DiskIdxMap": ""
          },
          "synoinfo": {
            "esataportcfg" : "0x00",
            "usbportcfg" : "0xc00000",
            "internalportcfg" : "0x3fffff",
            "maxdisks": "22",
            "support_bde_internal_10g": "no",
            "support_disk_compatibility": "no",
            "support_memory_compatibility": "no"
          },
          "ramdisk_copy": {}
    3. ran these commands to finish the tcrp loader
      1. ./rploader.sh build broadwellnk-7.1.0-42661
        ./rploader.sh backup
        ./rploader.sh backuploader
        exitcheck.sh reboot
    4. plugged my x540 in connected my LAN cable to one of the LAN ports
    5. booted from USB and installed the appropriate DSM_DS3622xs+_42661.pat

Special thanks to @Peter Suh @IG-88 @flyride for your support.

  • Like 1
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...