Stefan G. Weichinger:
> On an older server the customer replaced a SAS drive.
> 
> I see it as /dev/sg11, but not yes as /dev/sdX, it is not visible in "lsblk"
...

Not that I think it will help you much, but there is sys-apps/sg3_utils:

# lsscsi 
[0:0:0:0]    disk    ATA      TOSHIBA MG03ACA3 FL1A  /dev/sda 
[1:0:0:0]    disk    ATA      TOSHIBA MG03ACA3 FL1A  /dev/sdb 
[5:0:0:0]    cd/dvd  ASUS     DRW-24F1ST   a   1.00  /dev/scd0
# sg_map -x -i
/dev/sg0  0 0 0 0  0  /dev/sda  ATA       TOSHIBA MG03ACA3  FL1A
/dev/sg1  1 0 0 0  0  /dev/sdb  ATA       TOSHIBA MG03ACA3  FL1A
/dev/sg2  5 0 0 0  5  /dev/scd0  ASUS      DRW-24F1ST   a    1.00
# sg_inq /dev/sg1
standard INQUIRY:
  PQual=0  Device_type=0  RMB=0  LU_CONG=0  version=0x05  [SPC-3]
  [AERC=0]  [TrmTsk=0]  NormACA=0  HiSUP=0  Resp_data_format=2
  SCCS=0  ACC=0  TPGS=0  3PC=0  Protect=0  [BQue=0]
  EncServ=0  MultiP=0  [MChngr=0]  [ACKREQQ=0]  Addr16=0
  [RelAdr=0]  WBus16=0  Sync=0  [Linked=0]  [TranDis=0]  CmdQue=1
  [SPI: Clocking=0x0  QAS=0  IUS=0]
    length=96 (0x60)   Peripheral device type: disk
 Vendor identification: ATA     
 Product identification: TOSHIBA MG03ACA3
 Product revision level: FL1A
 Unit serial number:            14UAKBPDF

You have theese two:
> 07:01.0 SCSI storage controller: LSI Logic / Symbios Logic 53c1030 PCI-X
> 0a:0e.0 RAID bus controller: Adaptec AAC-RAID

 I guess that the tape drive and mediachanger is on the 53c1030:
> [0:0:1:0]    tape    HP       Ultrium 4-SCSI   B12H  /dev/st0
> [0:0:1:1]    mediumx OVERLAND NEO Series       0510  /dev/sch0

 And theese on the aac, since they have the same scsi host, and I guess
 that scsi ch.0 is for the configured drives and ch.1 for the raw drives:
> [1:0:1:0]    disk    ICP      SAS2             V1.0  /dev/sda
> [1:0:2:0]    disk    ICP      Device 2         V1.0  /dev/sdb
> [1:0:3:0]    disk    ICP      Device 3         V1.0  /dev/sdc
> [1:0:4:0]    disk    ICP      Device 4         V1.0  /dev/sdd
> [1:0:5:0]    disk    ICP      Device 5         V1.0  /dev/sde
> [1:0:6:0]    disk    ICP      Device 6         V1.0  /dev/sdf
> [1:0:7:0]    disk    ICP      Device 7         V1.0  /dev/sdg
> [1:0:8:0]    disk    ICP      Device 8         V1.0  /dev/sdh
> [1:0:9:0]    disk    ICP      Device 9         V1.0  /dev/sdi
> [1:1:0:0]    disk    TOSHIBA  MG04SCA20EE      0104  
> [1:1:1:0]    disk    SEAGATE  ST373455SS       0002  -
> [1:1:3:0]    disk    WDC      WD7500AZEX-00RKK 0A80  -
> [1:1:4:0]    disk    WDC      WD7500AZEX-00RKK 0A80  -
> [1:1:5:0]    disk    WDC      WD7500AZEX-00RKK 0A80  -
> [1:1:6:0]    disk    WDC      WD7500AZEX-00BN5 1A01  -
> [1:1:7:0]    disk    WDC      WD7500AZEX-00BN5 1A01  -
> [1:1:8:0]    disk    WDC      WD7500AZEX-00RKK 0A80  -
> [1:1:9:0]    disk    ST375052 8AS              CC44  -
> [1:1:10:0]   disk    WDC      WD7500AZEX-00BN5 1A01  -
> [1:1:11:0]   disk    WDC      WD7500AZEX-00BN5 1A01  -

Perhaps theese links will help:
 
https://www.cyberciti.biz/faq/linux-checking-sas-sata-disks-behind-adaptec-raid-controllers/
 http://updates.aslab.com/doc/disk-controller/aacraid_guide.pdf
 https://hwraid.le-vert.net/wiki/Adaptec

Just a poke in the dark, does ldd report all libs found, as in:
$ ldd /bin/ls
        linux-vdso.so.1 (0x00007ffcbab4c000)
        libc.so.6 => /lib64/libc.so.6 (0x00007fece3ad5000)
        /lib64/ld-linux-x86-64.so.2 (0x00007fece3d1c000)
$

Regards,
/Karl Hammar



Reply via email to