BASH 通过 PCI ID 查找 USB 驱动器连接到的端口

BASH find which port a USB drive is attached to by the PCI ID

提问by bing281

Basically I need to verify that a USB Drive is connected to a certain USB Port. I have the following:

基本上我需要验证 USB 驱动器是否连接到某个 USB 端口。我有以下几点：

USB Drives are labeled virtually:

USB 驱动器实际上标记为：

• White, Green, Red

• 白色、绿色、红色

I have 3 USB Ports that are also labeled physically:

我有 3 个 USB 端口，它们也有物理标记：

• White, Green, Red

• 白色、绿色、红色

Using BLKID I can receive information from the drives such as

使用 BLKID 我可以从驱动器接收信息，例如

BLKID Example
/dec/sdb1: SEC_TYPE="msdos" LABEL="WHTIE" UUID="78FE-870D" TYPE="vfat"

Therefore I know a lot about the drive itself by only knowing the label. Now I using LSPCI I can get the information about the USB port as I know the ID's of each bridge. For example:

因此，我只知道标签就对驱动器本身有了很多了解。现在我使用 LSPCI 我可以获得有关 USB 端口的信息，因为我知道每个网桥的 ID。例如：

LSPCI Example
0a.00.0 USB Controller: some info 4d88

So that last part 4d88 is the PCI ID.

所以最后一部分 4d88 是 PCI ID。

So I know the PCI ID's of each port and need to match them up to the USB Drive itself such as:

所以我知道每个端口的 PCI ID 并且需要将它们与 USB 驱动器本身匹配，例如：

• 4d88 = WHITE
• 4dC0 = GREEN
• 4d84 = RED

• 4d88 = 白色
• 4dC0 = 绿色
• 4d84 = 红色

I don't know how to match / check that relationship. Any help will be appreciated.

我不知道如何匹配/检查这种关系。任何帮助将不胜感激。

ANSWER:Thanks for all the help.

回答：谢谢大家的帮助。

#!/bin/bash

#variables
error="ERROR : Incorrect Command use 'usb_pci.sh'"
pci="USB PCI Check Successful"

errorstatus_white_pci="ERROR : USB PCI FAILED : WHITE Drive"
errorstatus_green_pci="ERROR : USB PCI FAILED : GREEN Drive"
errorstatus_red_pci="ERROR : USB PCI FAILED : RED Drive"

pci_check_white=4dc9
pci_check_green=4d81
pci_check_red=4dc5

#Takes USB label and gets /sys/block/sd?
echo "checking path for USB Label" 
path_white=$(blkid | grep WHITE | cut -d : -f 1 | sed 's|[0-9]*$||; s|^/dev/|/sys/block/|')
echo "white: "$path_white
path_green=$(blkid | grep GREEN | cut -d : -f 1 | sed 's|[0-9]*$||; s|^/dev/|/sys/block/|')
echo "green: "$path_green
path_red=$(blkid | grep RED | cut -d : -f 1 | sed 's|[0-9]*$||; s|^/dev/|/sys/block/|')
echo "red: "$path_red

#Takes /sys/block/sd? and gets PCI Path xx:xx.x
echo "checking path to PCI path" 
pci_path_white=$(ls -l ${path_white} | xargs | cut -d / -f 8 | cut -b 6-13)
echo "white: "$pci_path_white
pci_path_green=$(ls -l ${path_green} | xargs | cut -d / -f 8 | cut -b 6-13)
echo "green: "$pci_path_green
pci_path_red=$(ls -l ${path_red} | xargs | cut -d / -f 8 | cut -b 6-13)
echo "red: "$pci_path_red

#Takes xx:xx.x and gets the PCI Device ID xxxx
echo "checking PCI path to PCI Device ID" 
pci_device_id_white=$(lspci -s ${pci_path_white} | tail -c -5)
echo "white: "$pci_device_id_white
pci_device_id_green=$(lspci -s ${pci_path_green} | tail -c -5)
echo "green: "$pci_device_id_green
pci_device_id_red=$(lspci -s ${pci_path_red} | tail -c -5)
echo "red: "$pci_device_id_red

#check if pci_device_id_xxxx = pci_check_xxxx
echo "checking PCI Device ID equals what it should" 
if [ $pci_device_id_white = $pci_check_white ] ; then
    echo "WHITE USB PCI Check Successful"
else
    echo $errorstatus_white_pci
    exit 1
fi
if [ $pci_device_id_green = $pci_check_green ] ; then
    echo "GREEN USB PCI Check Successful"
else
    echo $errorstatus_green_pci
    exit 1
fi
if [ $pci_device_id_red = $pci_check_red ] ; then
    echo "RED USB PCI Check Successful"
else
    echo $errorstatus_red_pci
    exit 1
fi
echo $pci
exit 0

Edit:

编辑：

As requested dumps of lspci, lsusb, blkid.

根据要求转储 lspci、lsusb、blkid。

lspci
00:00.0 Host bridge: Intel Corporation Unknown device 0104 (rev 09)
00:02.0 VGA compatible controller: Intel Corporation Unknown device 0126 (rev 09)
00:16.0 Communication controller: Intel Corporation Unknown device 1c3a (rev 04)
00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network Connection (rev 04)
00:1a.0 USB Controller: Intel Corporation Unknown device 1c2d (rev 04)
00:1b.0 Audio device: Intel Corporation Unknown device 1c20 (rev 04)
00:1c.0 PCI bridge: Intel Corporation Unknown device 1c10 (rev b4)
00:1c.2 PCI bridge: Intel Corporation Unknown device 1c14 (rev b4)
00:1c.3 PCI bridge: Intel Corporation Unknown device 1c16 (rev b4)
00:1c.5 PCI bridge: Intel Corporation Unknown device 1c1a (rev b4)
00:1d.0 USB Controller: Intel Corporation Unknown device 1c26 (rev 04)
00:1f.0 ISA bridge: Intel Corporation Unknown device 1c4f (rev 04)
00:1f.2 RAID bus controller: Intel Corporation Mobile 82801 SATA RAID Controller (rev 04)
00:1f.3 SMBus: Intel Corporation Unknown device 1c22 (rev 04)
08:00.0 PCI bridge: Integrated Device Technology, Inc. PES4T4 PCI Express Switch (rev 0e)
09:02.0 PCI bridge: Integrated Device Technology, Inc. PES4T4 PCI Express Switch (rev 0e)
09:03.0 PCI bridge: Integrated Device Technology, Inc. PES4T4 PCI Express Switch (rev 0e)
09:04.0 PCI bridge: Integrated Device Technology, Inc. PES4T4 PCI Express Switch (rev 0e)
0a:00.0 USB Controller:  Unknown device 4d88
0a:00.1 USB Controller:  Unknown device 4dc9
0a:00.2 System peripheral:  Unknown device 4dca
0a:00.3 Communication controller:  Unknown device 4d8b
0b:00.0 USB Controller:  Unknown device 4dc0
0b:00.1 USB Controller:  Unknown device 4d81
0b:00.2 System peripheral:  Unknown device 4d8e
0b:00.3 Serial controller:  Unknown device 4dcf
0c:00.0 USB Controller:  Unknown device 4d84
0c:00.1 USB Controller:  Unknown device 4dc5
0c:00.2 System peripheral:  Unknown device 4dc6
0c:00.3 Communication controller:  Unknown device 4d87
0d:00.0 SD Host controller: O2 Micro, Inc. Unknown device 8221 (rev 05)
0d:00.1 Mass storage controller: O2 Micro, Inc. Unknown device 8231 (rev 03)

lsusb
Bus 004 Device 001: ID 0000:0000  
Bus 006 Device 001: ID 0000:0000  
Bus 005 Device 001: ID 0000:0000  
Bus 001 Device 002: ID 8087:0024  
Bus 001 Device 001: ID 0000:0000  
Bus 007 Device 001: ID 0000:0000  
Bus 008 Device 001: ID 0000:0000  
Bus 003 Device 003: ID 0718:063d Imation Corp. 
Bus 003 Device 001: ID 0000:0000  
Bus 002 Device 002: ID 8087:0024  
Bus 002 Device 004: ID 0a5c:5800 Broadcom Corp. BCM5880 Secure Applications Processor
Bus 002 Device 001: ID 0000:0000  
Bus 002 Device 003: ID 413c:3012 Dell Computer Corp. Optical Wheel Mouse

blkid
/dev/mapper/VolGroup00-LogVol01: TYPE="swap" UUID="6b361baf-08ae-4f2c-933b-5028c15b6fb5" 
/dev/mapper/VolGroup00-LogVol00: UUID="d15840ac-0073-483d-b630-7d2a497eaac9" TYPE="ext3" 
/dev/sda1: LABEL="/boot" UUID="39331b93-a08d-45b5-b1ea-fcc6586be7bd" TYPE="ext3" 
/dev/VolGroup00/LogVol00: UUID="d15840ac-0073-483d-b630-7d2a497eaac9" TYPE="ext3" 
/dev/VolGroup00/LogVol01: TYPE="swap" UUID="6b361baf-08ae-4f2c-933b-5028c15b6fb5" 
/dev/sdb1: SEC_TYPE="msdos" LABEL="WHITE" UUID="78FE-870D" TYPE="vfat" 
/dev/sdc1: SEC_TYPE="msdos" LABEL="GREEN" UUID="61FE-B32E" TYPE="vfat" 
/dev/sdd1: SEC_TYPE="msdos" LABEL="RED" UUID="E5DB-4A1A" TYPE="vfat" 

回答by thkala

This is how I would do it on my system:

这就是我在我的系统上的做法：

Step 1:Find the device node:

第一步：找到设备节点：

# blkid | grep MyDisk
/dev/sdj1: LABEL="MyDisk-0" UUID="4876-5945" TYPE="vfat" 

The device node is /dev/sdj1.

设备节点是/dev/sdj1。

Step 2:/sysis your friend:

第 2 步：/sys是你的朋友：

# ll /sys/block/sdj
lrwxrwxrwx 1 root root 0 Feb  3 00:40 /sys/block/sdj -> ../devices/pci0000:00/0000:00:1a.7/usb1/1-2/1-2:1.0/host15/target15:0:0/15:0:0:0/block/sdj/

The symbolic link target above contains a lotof useful information, including the path from your flash drive back to the PCI bridge via the SCSI and USB subsystems.

上面的符号链接目标包含许多有用的信息，包括从闪存驱动器通过 SCSI 和 USB 子系统返回到 PCI 桥的路径。

Step 3:From the link target above isolate the PCI bus ID (00:1a.7in this case) and check with lspci:

步骤 3：从上面的链接目标中分离出 PCI 总线 ID（00:1a.7在本例中）并检查lspci：

# lspci | grep 00:1a.7
00:1a.7 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB2 EHCI Controller #2

If in doubt, inspect the lspcioutput visually...

如果有疑问，请lspci目视检查输出...

EDIT:

编辑：

Here is an extremely crude and extremely fragile way to automate the process above:

这是自动化上述过程的一种极其粗糙且极其脆弱的方法：

blkid |
    grep Label |
    cut -d : -f 1 |
    sed 's|[0-9]*$||; s|^/dev/|/sys/block/|' |
    xargs readlink |
    cut -d / -f 4 |
    xargs -n 1 lspci -s

NOTE: This works on my system, but it is by no means safe (or recommended):

注意：这适用于我的系统，但绝不安全（或推荐）：

1. It will break if a kernel update changes the layout of the /sysfilesystem.

2. It can break if you have a different device layout, although you should be able to adjust for that.

1. 如果内核更新更改/sys文件系统的布局，它将中断。

2. 如果您有不同的设备布局，它可能会中断，尽管您应该能够对此进行调整。