Identifying Directly Connected SATA Drives vs LSI Expansion Card Drives From GUI (or Terminal?)

[wheel]

Possibly a random question with a stupid easy answer for a competent Linux head, but I’ve been searching for hours with no luck:

 

Is there an easy way in the GUI (or terminal) to determine which disks (by any unique identifier, think I could reverse engineer the info I need from there) are being read directly through the SATA ports on my motherboard vs. the ones plugged into my LSI cards?

 

When I initially set up this box (with 4 stacked 5-in-3 Norco hotswap cages), I wasn’t paying attention to which cable ports on the back were associated with which drives (in a left to right order), and when I compare it to another box using the same Norco hotswap cages, I’ve realized they probably changed production between my building the two boxes (both hotswap cage sets are SS-500s, but have different port layouts on the back and different light colors up front) and online instructions aren’t really helping now.

 

So my initial plans of just tracing the motherboard-connected plugs to the hotswap cage cable port fell flat, and now I’m just trying to determine which of these swap cage trays are the ones connected directly to the board so I can use them for Parity drives specifically (as parity’s taking forever on this system and I’m following all the steps for even marginal improvement).

 

Is there an easy way to just see if a certain disk / which disks are SATA1/2/3/4 (the four ports I have on the motherboard) and which are running through the LSIs (16 out of 20)?

 

Thanks for any help, and sorry if this is the dumbest question I’ve ever asked on here. Always appreciate the assistance!

 

 

[Squid]

You could sort it out by digging through the syslog to see which drives are coming up after the HBA is initialized, but

3 hours ago, wheel said:

as parity’s taking forever on this system

Simply rearranging the drives pretty much isn't going to give any improvement because on any parity build / rebuild / check, all the drives are involved in the operations, and if nothing is actually wrong, you may be running into bandwidth issues on HBAs / slots they're plugged into vs # of drives.

[JorgeB]

You can check with "lsscsi -v", you'll get something like this:

 

 lsscsi -v
[0:0:0:0]    disk    Kingston DataTraveler 2.0 PMAP  /dev/sda
  dir: /sys/bus/scsi/devices/0:0:0:0  [/sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/host0/target0:0:0/0:0:0:0]
[1:0:0:0]    disk    ATA      WDC WD100EMAZ-00 0A83  /dev/sdb
  dir: /sys/bus/scsi/devices/1:0:0:0  [/sys/devices/pci0000:00/0000:00:17.0/ata1/host1/target1:0:0/1:0:0:0]
[2:0:0:0]    disk    ATA      WDC WD60EZRZ-00G 0A80  /dev/sdc
  dir: /sys/bus/scsi/devices/2:0:0:0  [/sys/devices/pci0000:00/0000:00:17.0/ata2/host2/target2:0:0/2:0:0:0]
[3:0:0:0]    disk    ATA      WDC WD60EZRX-00M 0A80  /dev/sdd
  dir: /sys/bus/scsi/devices/3:0:0:0  [/sys/devices/pci0000:00/0000:00:17.0/ata3/host3/target3:0:0/3:0:0:0]
[4:0:0:0]    disk    ATA      WDC WD60EFRX-68M 0A82  /dev/sde
  dir: /sys/bus/scsi/devices/4:0:0:0  [/sys/devices/pci0000:00/0000:00:17.0/ata4/host4/target4:0:0/4:0:0:0]
[9:0:0:0]    disk    ATA      WDC  WDS500G1R0B 00WR  /dev/sdj
  dir: /sys/bus/scsi/devices/9:0:0:0  [/sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/ata9/host9/target9:0:0/9:0:0:0]
[10:0:0:0]   disk    ATA      WDC  WDS500G1R0B 00WR  /dev/sdk
  dir: /sys/bus/scsi/devices/10:0:0:0  [/sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/ata10/host10/target10:0:0/10:0:0:0]
[11:0:0:0]   disk    ATA      WDC  WDS500G1R0B 00WR  /dev/sdl
  dir: /sys/bus/scsi/devices/11:0:0:0  [/sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/ata11/host11/target11:0:0/11:0:0:0]
[12:0:0:0]   disk    ATA      WDC  WDS500G1R0B 00WR  /dev/sdm
  dir: /sys/bus/scsi/devices/12:0:0:0  [/sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/ata12/host12/target12:0:0/12:0:0:0]
[14:0:0:0]   disk    ATA      ST1000LM014-1EJ1 HPP1  /dev/sdn
  dir: /sys/bus/scsi/devices/14:0:0:0  [/sys/devices/pci0000:00/0000:00:1c.0/0000:04:00.0/ata14/host14/target14:0:0/14:0:0:0]
[16:0:0:0]   disk    ATA      TOSHIBA MQ01ABD1 5J    /dev/sdo
  dir: /sys/bus/scsi/devices/16:0:0:0  [/sys/devices/pci0000:00/0000:00:1c.0/0000:04:00.0/ata16/host16/target16:0:0/16:0:0:0]
[17:0:0:0]   disk    ATA      TOSHIBA MQ01ABD1 2C    /dev/sdp
  dir: /sys/bus/scsi/devices/17:0:0:0  [/sys/devices/pci0000:00/0000:00:1c.0/0000:04:00.0/ata17/host17/target17:0:0/17:0:0:0]
[18:0:0:0]   disk    ATA      TOSHIBA MQ01ABD1 4M    /dev/sdq
  dir: /sys/bus/scsi/devices/18:0:0:0  [/sys/devices/pci0000:00/0000:00:1c.0/0000:04:00.0/ata18/host18/target18:0:0/18:0:0:0]
[N:0:8215:1] dsk/nvm WDS500G3X0C-00SJG0__1                      /dev/nvme0n1
  dir: /sys/class/nvme/nvme0/nvme0n1  [/sys/devices/pci0000:00/0000:00:01.1/0000:02:00.0/nvme/nvme0/nvme0n1]
[N:1:0:1]    dsk/nvm TOSHIBA-RD400__1                           /dev/nvme1n1
  dir: /sys/class/nvme/nvme1/nvme1n1  [/sys/devices/pci0000:00/0000:00:01.2/0000:03:00.0/nvme/nvme1/nvme1n1]

Look at the PCI devices, in this case there are drives on devices 00:17.0, 01:00.0 and 04:00.0, then type lspci to identify them:

 

lspci
00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host Bridge/DRAM Registers (rev 07)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor PCIe Controller (x16) (rev 07)
00:01.1 PCI bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor PCIe Controller (x8) (rev 07)
00:01.2 PCI bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor PCIe Controller (x4) (rev 07)
00:13.0 Non-VGA unclassified device: Intel Corporation 100 Series/C230 Series Chipset Family Integrated Sensor Hub (rev 31)
00:14.0 USB controller: Intel Corporation 100 Series/C230 Series Chipset Family USB 3.0 xHCI Controller (rev 31)
00:14.2 Signal processing controller: Intel Corporation 100 Series/C230 Series Chipset Family Thermal Subsystem (rev 31)
00:16.0 Communication controller: Intel Corporation 100 Series/C230 Series Chipset Family MEI Controller #1 (rev 31)
00:16.1 Communication controller: Intel Corporation 100 Series/C230 Series Chipset Family MEI Controller #2 (rev 31)
00:17.0 SATA controller: Intel Corporation Q170/Q150/B150/H170/H110/Z170/CM236 Chipset SATA Controller [AHCI Mode] (rev 31)
00:1c.0 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #1 (rev f1)
00:1c.4 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #5 (rev f1)
00:1d.0 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #9 (rev f1)
00:1d.1 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #10 (rev f1)
00:1d.2 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #11 (rev f1)
00:1f.0 ISA bridge: Intel Corporation C236 Chipset LPC/eSPI Controller (rev 31)
00:1f.2 Memory controller: Intel Corporation 100 Series/C230 Series Chipset Family Power Management Controller (rev 31)
00:1f.4 SMBus: Intel Corporation 100 Series/C230 Series Chipset Family SMBus (rev 31)
01:00.0 SATA controller: JMicron Technology Corp. Device 0585
02:00.0 Non-Volatile memory controller: Sandisk Corp WD Black 2018/PC SN720 NVMe SSD
03:00.0 Non-Volatile memory controller: OCZ Technology Group, Inc. RD400/400A SSD (rev 01)
04:00.0 SATA controller: JMicron Technology Corp. Device 0585
05:00.0 Ethernet controller: Mellanox Technologies MT27500 Family [ConnectX-3]
06:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network Connection (rev 03)
07:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network Connection (rev 03)
08:00.0 PCI bridge: ASPEED Technology, Inc. AST1150 PCI-to-PCI Bridge (rev 03)
09:00.0 VGA compatible controller: ASPEED Technology, Inc. ASPEED Graphics Family (rev 30)

 

00:17.0 is the onboard Intel SATA controller, 01:00.0 and 04:00.0 are JMB controllers.