User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:33.0) Gecko/20100101
Firefox/33.0
Build Identifier:
This script no longer "finds new" or "removes no longer attached" scsi devices.
As shown below, I have a scsi disk at scsi ID-0 at /dev/sg5.
# lsscsi -g
[0:0:0:0] disk ATA ST3320620AS K /dev/sda /dev/sg0
[13:0:0:0] process Marvell 91xx Config 1.01 - /dev/sg1
[16:0:0:0] disk IMPRIMIS 94601-15 4614 /dev/sdd /dev/sg5
[17:0:0:0] cd/dvd LITE-ON DVDRW LH-20A1P KL0G /dev/sr0 /dev/sg2
[18:0:0:0] disk ATA ST3160811AS E /dev/sdb /dev/sg3
[18:0:1:0] disk ATA ST3160815AS B /dev/sdc /dev/sg4
I remove the drive at scsi ID-0 drive and install an additional drive at scsi
ID-1 then run the script.
# rescan-scsi-bus.sh
Scanning SCSI subsystem for new devices
Scanning host 0 for SCSI target IDs 0 1 2 3 4 5 6 7, all LUNs
Scanning for device 0 0 0 0 ...
OLD: Host: scsi0 Channel: 00 Id: 00 Lun: 00
Vendor: ATA Model: ST3320620AS Rev: K
Type: Direct-Access ANSI SCSI revision: 05
Scanning host 1 for SCSI target IDs 0 1 2 3 4 5 6 7, all LUNs
Scanning host 2 for SCSI target IDs 0 1 2 3 4 5 6 7, all LUNs
Scanning host 3 for SCSI target IDs 0 1 2 3 4 5 6 7, all LUNs
Scanning host 4 for SCSI target IDs 0 1 2 3 4 5 6 7, all LUNs
Scanning host 5 for SCSI target IDs 0 1 2 3 4 5 6 7, all LUNs
Scanning host 6 for SCSI target IDs 0 1 2 3 4 5 6 7, all LUNs
Scanning host 7 for SCSI target IDs 0 1 2 3 4 5 6 7, all LUNs
Scanning host 8 for SCSI target IDs 0 1 2 3 4 5 6 7, all LUNs
Scanning host 9 for SCSI target IDs 0 1 2 3 4 5 6 7, all LUNs
Scanning host 10 for SCSI target IDs 0 1 2 3 4 5 6 7, all LUNs
Scanning host 11 for SCSI target IDs 0 1 2 3 4 5 6 7, all LUNs
Scanning host 12 for SCSI target IDs 0 1 2 3 4 5 6 7, all LUNs
Scanning host 13 for SCSI target IDs 0 1 2 3 4 5 6 7, all LUNs
Scanning for device 13 0 0 0 ...
OLD: Host: scsi13 Channel: 00 Id: 00 Lun: 00
Vendor: Marvell Model: 91xx Config Rev: 1.01
Type: Processor ANSI SCSI revision: 05
Scanning host 14 for SCSI target IDs 0 1 2 3 4 5 6 7, all LUNs
Scanning host 15 for SCSI target IDs 0 1 2 3 4 5 6 7, all LUNs
Scanning host 16 for SCSI target IDs 0 1 2 3 4 5 6 7, all LUNs
Scanning for device 16 0 0 0 ...
OLD: Host: scsi16 Channel: 00 Id: 00 Lun: 00
Vendor: IMPRIMIS Model: 94601-15 Rev: 4614
Type: Direct-Access ANSI SCSI revision: 01
Scanning host 17 for SCSI target IDs 0 1 2 3 4 5 6 7, all LUNs
Scanning for device 17 0 0 0 ...
OLD: Host: scsi17 Channel: 00 Id: 00 Lun: 00
Vendor: LITE-ON Model: DVDRW LH-20A1P Rev: KL0G
Type: CD-ROM ANSI SCSI revision: 05
Scanning host 18 for SCSI target IDs 0 1 2 3 4 5 6 7, all LUNs
Scanning for device 18 0 0 0 ...
OLD: Host: scsi18 Channel: 00 Id: 00 Lun: 00
Vendor: ATA Model: ST3160811AS Rev: E
Type: Direct-Access ANSI SCSI revision: 05
Scanning for device 18 0 1 0 ...
OLD: Host: scsi18 Channel: 00 Id: 01 Lun: 00
Vendor: ATA Model: ST3160815AS Rev: B
Type: Direct-Access ANSI SCSI revision: 05
0 new or changed device(s) found.
0 remapped or resized device(s) found.
0 device(s) removed.
# lsscsi -g
[0:0:0:0] disk ATA ST3320620AS K /dev/sda /dev/sg0
[13:0:0:0] process Marvell 91xx Config 1.01 - /dev/sg1
[16:0:0:0] disk IMPRIMIS 94601-15 4614 /dev/sdd /dev/sg5
[17:0:0:0] cd/dvd LITE-ON DVDRW LH-20A1P KL0G /dev/sr0 /dev/sg2
[18:0:0:0] disk ATA ST3160811AS E /dev/sdb /dev/sg3
[18:0:1:0] disk ATA ST3160815AS B /dev/sdc /dev/sg4
It not only did not remove the one at ID-0 that was removed, but did not find
the new one attached. Below is an "lsscsi -g" after a reboot with BOTH drives
attached.
#lsscsi -g
[0:0:0:0] disk ATA ST3320620AS K /dev/sda /dev/sg0
[13:0:0:0] process Marvell 91xx Config 1.01 - /dev/sg1
[16:0:0:0] disk IMPRIMIS 94601-15 4614 /dev/sdd /dev/sg5
[16:0:1:0] disk IMPRIMIS 94601-15 4614 /dev/sde /dev/sg6
[17:0:0:0] cd/dvd LITE-ON DVDRW LH-20A1P KL0G /dev/sr0 /dev/sg2
[18:0:0:0] disk ATA ST3160811AS E /dev/sdb /dev/sg3
[18:0:1:0] disk ATA ST3160815AS B /dev/sdc /dev/sg4
Reproducible: Always
Steps to Reproduce:
1. See details
2.
3.
Actual Results:
This script, before SuSE-13.1 would remove any disks physically removed and add
any physically added since boot. It is broken
This is NOT kernel related as the same thing happens with a vanilla 3.16.7
kernel. I'm fairly certain this is a systemd issue.