How to correctly identify/relate a Disk on 3ware Controller
by HiFish from LinuxQuestions.org on (#5GDY7)
Hello Everyone,
I am currently going through all the steps to follow some advice on how to reassemble a broken softraid array and run into an unexpected puzzle: I have collected detailed information from mdadm on each of the /dev/sd[...] and have also collected SMART info with smartctl. Now i am stumped by not being able to relate those 2 datasets with each other. I have gotten this far:
smartctl -t -d 3ware,0 /dev/twa0
this will give me detalied Info on the Disk connected to the first Port of the controller, including a serial number, but not what /dev/sdX this is
lshw -short
This will list all 8 Disks as "2TB 9550SX-12 DISK" without serial numbers.
Code:/0/100/1c/0/2/0.1.0 /dev/sdb disk 2TB 9550SX-12 DISK
/0/100/1c/0/2/0.2.0 /dev/sdc disk 2TB 9550SX-12 DISK
/0/100/1c/0/2/0.3.0 /dev/sdd disk 2TB 9550SX-12 DISK
/0/100/1c/0/2/0.4.0 /dev/sde disk 2TB 9550SX-12 DISK
/0/100/1c/0/2/0.5.0 /dev/sdf disk 2TB 9550SX-12 DISK
/0/100/1c/0/2/0.6.0 /dev/sdg disk 2TB 9550SX-12 DISK
/0/100/1c/0/2/0.7.0 /dev/sdh disk 2TB 9550SX-12 DISK
/0/100/1c/0/2/0.8.0 /dev/sdi disk 2TB 9550SX-12 DISKNow this might lead one to suspect that the drive on the first port is /dev/sdb, but how can i verify this?
/sbin/hdparm -i /dev/sdb just returns
Code:/dev/sdb:
HDIO_DRIVE_CMD(identify) failed: Invalid argument
HDIO_GET_IDENTITY failed: Invalid argumentand /sbin/udevadm info --query=property --name=sdb does return some information but not the serial number of the disk.
Code:DEVLINKS=/dev/disk/by-id/scsi-1AMCC_01840939000000000000 /dev/disk/by-path/pci-0000:02:02.0-scsi-0:0:1:0
DEVNAME=/dev/sdb
DEVPATH=/devices/pci0000:00/0000:00:1c.0/0000:01:00.0/0000:02:02.0/host0/target0:0:1/0:0:1:0/block/sdb
DEVTYPE=disk
ID_BUS=scsi
ID_FS_LABEL=ServhoernchenX5:multiverse
ID_FS_LABEL_ENC=ServhoernchenX5:multiverse
ID_FS_TYPE=linux_raid_member
ID_FS_USAGE=raid
ID_FS_UUID=7321c640-335b-eec5-3b12-db8267ca35c5
ID_FS_UUID_ENC=7321c640-335b-eec5-3b12-db8267ca35c5
ID_FS_UUID_SUB=d28d0061-9ba7-8e66-6d6b-2a66f2edae09
ID_FS_UUID_SUB_ENC=d28d0061-9ba7-8e66-6d6b-2a66f2edae09
ID_FS_VERSION=1.2
ID_MODEL=9550SX-12_DISK
ID_MODEL_ENC=9550SX-12\x20\x20DISK\x20
ID_PATH=pci-0000:02:02.0-scsi-0:0:1:0
ID_PATH_TAG=pci-0000_02_02_0-scsi-0_0_1_0
ID_REVISION=3.04
ID_SCSI=1
ID_SCSI_SERIAL=01840939000000000000
ID_SERIAL=1AMCC_01840939000000000000
ID_SERIAL_SHORT=AMCC_01840939000000000000
ID_TYPE=disk
ID_VENDOR=AMCC
ID_VENDOR_ENC=AMCC\x20\x20\x20\x20
MAJOR=8
MINOR=16
SUBSYSTEM=block
TAGS=:systemd:
USEC_INITIALIZED=5211612Sadly the ancient hardware is the opposite of accessible and hotplug-capable, so i am scared to figure this out by manualy disconnecting the disks. A reboot might also scramble the letters and even more confuse my efforts to reassmble the array.
Has anybody any suggestion on how To correctly identify the disk with the Serial WD-WCC300067052 that is connectet to Port ID 4 of a 3ware 9550SX-12 Controller?
Greetings and thank you for reading all of this :-).
Edit: I almost forgot: uname -r gives 4.4.0-78-generic
I am currently going through all the steps to follow some advice on how to reassemble a broken softraid array and run into an unexpected puzzle: I have collected detailed information from mdadm on each of the /dev/sd[...] and have also collected SMART info with smartctl. Now i am stumped by not being able to relate those 2 datasets with each other. I have gotten this far:
smartctl -t -d 3ware,0 /dev/twa0
this will give me detalied Info on the Disk connected to the first Port of the controller, including a serial number, but not what /dev/sdX this is
lshw -short
This will list all 8 Disks as "2TB 9550SX-12 DISK" without serial numbers.
Code:/0/100/1c/0/2/0.1.0 /dev/sdb disk 2TB 9550SX-12 DISK
/0/100/1c/0/2/0.2.0 /dev/sdc disk 2TB 9550SX-12 DISK
/0/100/1c/0/2/0.3.0 /dev/sdd disk 2TB 9550SX-12 DISK
/0/100/1c/0/2/0.4.0 /dev/sde disk 2TB 9550SX-12 DISK
/0/100/1c/0/2/0.5.0 /dev/sdf disk 2TB 9550SX-12 DISK
/0/100/1c/0/2/0.6.0 /dev/sdg disk 2TB 9550SX-12 DISK
/0/100/1c/0/2/0.7.0 /dev/sdh disk 2TB 9550SX-12 DISK
/0/100/1c/0/2/0.8.0 /dev/sdi disk 2TB 9550SX-12 DISKNow this might lead one to suspect that the drive on the first port is /dev/sdb, but how can i verify this?
/sbin/hdparm -i /dev/sdb just returns
Code:/dev/sdb:
HDIO_DRIVE_CMD(identify) failed: Invalid argument
HDIO_GET_IDENTITY failed: Invalid argumentand /sbin/udevadm info --query=property --name=sdb does return some information but not the serial number of the disk.
Code:DEVLINKS=/dev/disk/by-id/scsi-1AMCC_01840939000000000000 /dev/disk/by-path/pci-0000:02:02.0-scsi-0:0:1:0
DEVNAME=/dev/sdb
DEVPATH=/devices/pci0000:00/0000:00:1c.0/0000:01:00.0/0000:02:02.0/host0/target0:0:1/0:0:1:0/block/sdb
DEVTYPE=disk
ID_BUS=scsi
ID_FS_LABEL=ServhoernchenX5:multiverse
ID_FS_LABEL_ENC=ServhoernchenX5:multiverse
ID_FS_TYPE=linux_raid_member
ID_FS_USAGE=raid
ID_FS_UUID=7321c640-335b-eec5-3b12-db8267ca35c5
ID_FS_UUID_ENC=7321c640-335b-eec5-3b12-db8267ca35c5
ID_FS_UUID_SUB=d28d0061-9ba7-8e66-6d6b-2a66f2edae09
ID_FS_UUID_SUB_ENC=d28d0061-9ba7-8e66-6d6b-2a66f2edae09
ID_FS_VERSION=1.2
ID_MODEL=9550SX-12_DISK
ID_MODEL_ENC=9550SX-12\x20\x20DISK\x20
ID_PATH=pci-0000:02:02.0-scsi-0:0:1:0
ID_PATH_TAG=pci-0000_02_02_0-scsi-0_0_1_0
ID_REVISION=3.04
ID_SCSI=1
ID_SCSI_SERIAL=01840939000000000000
ID_SERIAL=1AMCC_01840939000000000000
ID_SERIAL_SHORT=AMCC_01840939000000000000
ID_TYPE=disk
ID_VENDOR=AMCC
ID_VENDOR_ENC=AMCC\x20\x20\x20\x20
MAJOR=8
MINOR=16
SUBSYSTEM=block
TAGS=:systemd:
USEC_INITIALIZED=5211612Sadly the ancient hardware is the opposite of accessible and hotplug-capable, so i am scared to figure this out by manualy disconnecting the disks. A reboot might also scramble the letters and even more confuse my efforts to reassmble the array.
Has anybody any suggestion on how To correctly identify the disk with the Serial WD-WCC300067052 that is connectet to Port ID 4 of a 3ware 9550SX-12 Controller?
Greetings and thank you for reading all of this :-).
Edit: I almost forgot: uname -r gives 4.4.0-78-generic