Same two HBA controllers being identified differently?


Recommended Posts

I bought two of these.  One is connected to sata drives and they work.  It is identified as this in unraid:

 

Serial Attached SCSI controller: Broadcom / LSI SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] (rev 03)

 

The other is attached to sas drives with these and the cables from the power supply.    It is identified as this in unraid:

 

RAID bus controller: Broadcom / LSI SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] (rev 03)

 

In Unraid the sas hard drive conected shows up as: [10:0:0:0] disk HGST HUH721010AL42C0 A3Z4 /dev/sdh - but is not shown on the "Main" page anywhere.  (the reason for only one drive showing up is I unplugged all the others until i can get this sorted out)

 

Im not sure where to go from here.  Any help would be awesome. 

Edited by ArrDee
Link to comment
8 minutes ago, ArrDee said:

I bought two of these.  One is connected to sata drives and they work.  It is identified as this in unraid:

 

Serial Attached SCSI controller: Broadcom / LSI SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] (rev 03)

 

The other is attached to sas drives with these and the cables from the power supply.    It is identified as this in unraid:

 

RAID bus controller: Broadcom / LSI SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] (rev 03)

 

In Unraid the sas hard drive conected shows up as: [10:0:0:0] disk HGST HUH721010AL42C0 A3Z4 /dev/sdh - but is not shown on the "Main" page anywhere.  (the reason for only one drive showing up is I unplugged all the others until i can get this sorted out)

 

Im not sure where to go from here.  Any help would be awesome. 

It maybe one is using IR firm the Raid controller and the other is it firmware suggest posting diagnostics

Link to comment

Sure looks to me like they're both in IT mode. 

 

LSI Corporation SAS2 Flash Utility
Version 20.00.00.00 (2014.09.18)
Copyright (c) 2008-2014 LSI Corporation. All rights reserved

        Adapter Selected is a LSI SAS: SAS2008(B2)   

        Controller Number              : 1
        Controller                     : SAS2008(B2)   
        PCI Address                    : 00:07:00:00
        SAS Address                    : 500605b-0-07a3-7aa0
        NVDATA Version (Default)       : 14.01.00.08
        NVDATA Version (Persistent)    : 14.01.00.08
        Firmware Product ID            : 0x2213 (IT)
        Firmware Version               : 20.00.07.00
        NVDATA Vendor                  : LSI
        NVDATA Product ID              : SAS9211-8i
        BIOS Version                   : 07.39.02.00
        UEFI BSD Version               : N/A
        FCODE Version                  : N/A
        Board Name                     : SAS9211-8i
        Board Assembly                 : N/A
        Board Tracer Number            : N/A

        Finished Processing Commands Successfully.
        Exiting SAS2Flash.
root@Tower:/dev/shm/lsi# ./sas2flash -c 00 -list
LSI Corporation SAS2 Flash Utility
Version 20.00.00.00 (2014.09.18)
Copyright (c) 2008-2014 LSI Corporation. All rights reserved

        Adapter Selected is a LSI SAS: SAS2008(B2)   

        Controller Number              : 0
        Controller                     : SAS2008(B2)   
        PCI Address                    : 00:01:00:00
        SAS Address                    : 500605b-0-0107-7e70
        NVDATA Version (Default)       : 14.01.00.08
        NVDATA Version (Persistent)    : 14.01.00.08
        Firmware Product ID            : 0x2213 (IT)
        Firmware Version               : 20.00.07.00
        NVDATA Vendor                  : LSI
        NVDATA Product ID              : SAS9211-8i
        BIOS Version                   : 07.39.02.00
        UEFI BSD Version               : N/A
        FCODE Version                  : N/A
        Board Name                     : SAS9211-8i
        Board Assembly                 : N/A
        Board Tracer Number            : N/A

        Finished Processing Commands Successfully.
        Exiting SAS2Flash.

 

So, i don't know where to go from here.  I still have the issue where the harddrive on the second board is listed as a device in unraid, but not shown in main section,  I could use any guidance ya got. 

Link to comment
12 hours ago, ArrDee said:

Sure looks to me like they're both in IT mode. 

 

LSI Corporation SAS2 Flash Utility
Version 20.00.00.00 (2014.09.18)
Copyright (c) 2008-2014 LSI Corporation. All rights reserved

        Adapter Selected is a LSI SAS: SAS2008(B2)   

        Controller Number              : 1
        Controller                     : SAS2008(B2)   
        PCI Address                    : 00:07:00:00
        SAS Address                    : 500605b-0-07a3-7aa0
        NVDATA Version (Default)       : 14.01.00.08
        NVDATA Version (Persistent)    : 14.01.00.08
        Firmware Product ID            : 0x2213 (IT)
        Firmware Version               : 20.00.07.00
        NVDATA Vendor                  : LSI
        NVDATA Product ID              : SAS9211-8i
        BIOS Version                   : 07.39.02.00
        UEFI BSD Version               : N/A
        FCODE Version                  : N/A
        Board Name                     : SAS9211-8i
        Board Assembly                 : N/A
        Board Tracer Number            : N/A

        Finished Processing Commands Successfully.
        Exiting SAS2Flash.
root@Tower:/dev/shm/lsi# ./sas2flash -c 00 -list
LSI Corporation SAS2 Flash Utility
Version 20.00.00.00 (2014.09.18)
Copyright (c) 2008-2014 LSI Corporation. All rights reserved

        Adapter Selected is a LSI SAS: SAS2008(B2)   

        Controller Number              : 0
        Controller                     : SAS2008(B2)   
        PCI Address                    : 00:01:00:00
        SAS Address                    : 500605b-0-0107-7e70
        NVDATA Version (Default)       : 14.01.00.08
        NVDATA Version (Persistent)    : 14.01.00.08
        Firmware Product ID            : 0x2213 (IT)
        Firmware Version               : 20.00.07.00
        NVDATA Vendor                  : LSI
        NVDATA Product ID              : SAS9211-8i
        BIOS Version                   : 07.39.02.00
        UEFI BSD Version               : N/A
        FCODE Version                  : N/A
        Board Name                     : SAS9211-8i
        Board Assembly                 : N/A
        Board Tracer Number            : N/A

        Finished Processing Commands Successfully.
        Exiting SAS2Flash.

 

So, i don't know where to go from here.  I still have the issue where the harddrive on the second board is listed as a device in unraid, but not shown in main section,  I could use any guidance ya got. 

The device is showing as zero size.

 

Jan 20 14:43:11 Tower kernel: scsi 10:0:0:0: Direct-Access     HGST     HUH721010AL42C0  A3Z4 PQ: 0 ANSI: 6
Jan 20 14:43:11 Tower kernel: scsi 10:0:0:0: SSP: handle(0x0009), sas_addr(0x5000cca26a671bd9), phy(0), device_name(0x5000cca26a671bdb)
Jan 20 14:43:11 Tower kernel: scsi 10:0:0:0: enclosure logical id (0x500605b007a37aa0), slot(3) 
Jan 20 14:43:11 Tower kernel: scsi 10:0:0:0: qdepth(254), tagged(1), scsi_level(7), cmd_que(1)
Jan 20 14:43:11 Tower kernel: scsi 10:0:0:0: Power-on or device reset occurred
Jan 20 14:43:11 Tower kernel: sd 10:0:0:0: Attached scsi generic sg7 type 0
Jan 20 14:43:11 Tower kernel: sd 10:0:0:0: [sdh] Spinning up disk...
Jan 20 14:43:11 Tower kernel: end_device-10:0: add: handle(0x0009), sas_addr(0x5000cca26a671bd9)
Jan 20 14:43:11 Tower kernel: .....
Jan 20 14:43:11 Tower kernel: mpt2sas_cm1: port enable: SUCCESS
Jan 20 14:43:11 Tower kernel: .............................................................................................not responding...
Jan 20 14:43:11 Tower kernel: sd 10:0:0:0: [sdh] Read Capacity(16) failed: Result: hostbyte=0x00 driverbyte=DRIVER_OK
Jan 20 14:43:11 Tower kernel: sd 10:0:0:0: [sdh] Sense Key : 0x2 [current] [descriptor] 
Jan 20 14:43:11 Tower kernel: sd 10:0:0:0: [sdh] ASC=0x4 ASCQ=0x2 
Jan 20 14:43:11 Tower kernel: sd 10:0:0:0: [sdh] Read Capacity(10) failed: Result: hostbyte=0x00 driverbyte=DRIVER_OK
Jan 20 14:43:11 Tower kernel: sd 10:0:0:0: [sdh] Sense Key : 0x2 [current] [descriptor] 
Jan 20 14:43:11 Tower kernel: sd 10:0:0:0: [sdh] ASC=0x4 ASCQ=0x2 
Jan 20 14:43:11 Tower kernel: sd 10:0:0:0: [sdh] 0 512-byte logical blocks: (0 B/0 B)
Jan 20 14:43:11 Tower kernel: sd 10:0:0:0: [sdh] 0-byte physical blocks
Jan 20 14:43:11 Tower kernel: sd 10:0:0:0: [sdh] Write Protect is off
Jan 20 14:43:11 Tower kernel: sd 10:0:0:0: [sdh] Mode Sense: f7 00 10 08
Jan 20 14:43:11 Tower kernel: sd 10:0:0:0: [sdh] Write cache: disabled, read cache: enabled, supports DPO and FUA
Jan 20 14:43:11 Tower kernel: sd 10:0:0:0: [sdh] Attached SCSI disk

 

Jan 20 14:43:34 Tower emhttpd: device /dev/sdh has size zero

 

There is no smart info for that drive in diags, do you get any output from smartctl -a /dev/sdh

 

@JorgeB any suggestions?

Link to comment

 

Yes.  And it the issue follows across OS's.  Something is up with this model HDD.  I have 5 of them and they're all exhibiting the same behavior.  Could these be vendor locked and if so, how would I figure that out?

 

=== START OF INFORMATION SECTION ===
Vendor:               HGST
Product:              HUH721010AL42C0
Revision:             A3Z4
Compliance:           SPC-4
LU is fully provisioned
Rotation Rate:        7200 rpm
Form Factor:          3.5 inches
Logical Unit id:      0x5000cca26a671bd8
Serial number:        2THUPWND
Device type:          disk
Transport protocol:   SAS (SPL-3)
Local Time is:        Sun Jan 21 14:14:05 2024 UTC
device is NOT READY (e.g. spun down, busy)
A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.

Edited by ArrDee
Link to comment
56 minutes ago, ArrDee said:

 

Yes.  And it the issue follows across OS's.  Something is up with this model HDD.  I have 5 of them and they're all exhibiting the same behavior.  Could these be vendor locked and if so, how would I figure that out?

 

=== START OF INFORMATION SECTION ===
Vendor:               HGST
Product:              HUH721010AL42C0
Revision:             A3Z4
Compliance:           SPC-4
LU is fully provisioned
Rotation Rate:        7200 rpm
Form Factor:          3.5 inches
Logical Unit id:      0x5000cca26a671bd8
Serial number:        2THUPWND
Device type:          disk
Transport protocol:   SAS (SPL-3)
Local Time is:        Sun Jan 21 14:14:05 2024 UTC
device is NOT READY (e.g. spun down, busy)
A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.

Can you try -x this is for one of my SAS drives.

 

root@Tower:~# smartctl -x /dev/sdg
smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.1.64-Unraid] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Vendor:               HGST
Product:              HUS724030ALS640
Revision:             A1C4
Compliance:           SPC-4
User Capacity:        3,000,592,982,016 bytes [3.00 TB]
Logical block size:   512 bytes
LU is resource provisioned, LBPRZ=0
Rotation Rate:        7200 rpm
Form Factor:          3.5 inches
Logical Unit id:      0x5000cca0277fb12c
Serial number:        P8J870AV
Device type:          disk
Transport protocol:   SAS (SPL-4)
Local Time is:        Sun Jan 21 15:11:21 2024 GMT
SMART support is:     Available - device has SMART capability.
SMART support is:     Enabled
Temperature Warning:  Enabled
Read Cache is:        Enabled
Writeback Cache is:   Enabled

=== START OF READ SMART DATA SECTION ===
SMART Health Status: OK

Current Drive Temperature:     30 C
Drive Trip Temperature:        85 C

Manufactured in week 51 of year 2013
Specified cycle count over device lifetime:  50000
Accumulated start-stop cycles:  3574
Specified load-unload count over device lifetime:  600000
Accumulated load-unload cycles:  25588
Elements in grown defect list: 0

Vendor (Seagate Cache) information
  Blocks sent to initiator = 12377123238969344

Error counter log:
           Errors Corrected by           Total   Correction     Gigabytes    Total
               ECC          rereads/    errors   algorithm      processed    uncorrected
           fast | delayed   rewrites  corrected  invocations   [10^9 bytes]  errors
read:   32484643        5         0  32484648   90556184     360684.117           0
write:         0        0         0         0    1285537      99909.049           0
verify:  1254503        0         0   1254503     343776     151110.867           0

Non-medium error count:        0

SMART Self-test log
Num  Test              Status                 segment  LifeTime  LBA_first_err [SK ASC ASQ]
     Description                              number   (hours)
# 1  Background short  Completed                   -   41257                 - [-   -    -]
# 2  Background short  Completed                   -   41257                 - [-   -    -]

Long (extended) Self-test duration: 29637 seconds [8.2 hours]

Background scan results log
  Status: no scans active
    Accumulated power on time, hours:minutes 42071:03 [2524263 minutes]
    Number of background scans performed: 260,  scan progress: 0.00%
    Number of background medium scans performed: 260

General statistics and performance log page:
  General access statistics and performance:
    Number of read commands: 2522036871
    Number of write commands: 737734034
    number of logical blocks received: 704461165187
    number of logical blocks transmitted: 195134860386
    read command processing intervals: 0
    write command processing intervals: 0
    weighted number of read commands plus write commands: 0
    weighted read command processing plus write command processing: 0
  Idle time:
    Idle time intervals: 964381968
      in seconds: 48219098.400
      in hours: 13394.194

Protocol Specific port log page for SAS SSP
relative target port id = 1
  generation code = 2
  number of phys = 1
  phy identifier = 0
    attached device type: SAS or SATA device
    attached reason: unknown
    reason: unknown
    negotiated logical link rate: phy enabled; 6 Gbps
    attached initiator port: ssp=1 stp=1 smp=1
    attached target port: ssp=0 stp=0 smp=0
    SAS address = 0x5000cca0277fb12d
    attached SAS address = 0x5003048011c7eb04
    attached phy identifier = 7
    Invalid DWORD count = 63
    Running disparity error count = 57
    Loss of DWORD synchronization count = 19
    Phy reset problem count = 0
relative target port id = 2
  generation code = 2
  number of phys = 1
  phy identifier = 1
    attached device type: no device attached
    attached reason: unknown
    reason: power on
    negotiated logical link rate: phy enabled; unknown
    attached initiator port: ssp=0 stp=0 smp=0
    attached target port: ssp=0 stp=0 smp=0
    SAS address = 0x5000cca0277fb12e
    attached SAS address = 0x0
    attached phy identifier = 0
    Invalid DWORD count = 0
    Running disparity error count = 0
    Loss of DWORD synchronization count = 0
    Phy reset problem count = 0
 

Link to comment
1 hour ago, SimonF said:

Can you try -x this is for one of my SAS drives.

 

root@Tower:~# smartctl -x /dev/sdg
smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.1.64-Unraid] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Vendor:               HGST
Product:              HUS724030ALS640
Revision:             A1C4
Compliance:           SPC-4
User Capacity:        3,000,592,982,016 bytes [3.00 TB]
Logical block size:   512 bytes
LU is resource provisioned, LBPRZ=0
Rotation Rate:        7200 rpm
Form Factor:          3.5 inches
Logical Unit id:      0x5000cca0277fb12c
Serial number:        P8J870AV
Device type:          disk
Transport protocol:   SAS (SPL-4)
Local Time is:        Sun Jan 21 15:11:21 2024 GMT
SMART support is:     Available - device has SMART capability.
SMART support is:     Enabled
Temperature Warning:  Enabled
Read Cache is:        Enabled
Writeback Cache is:   Enabled

=== START OF READ SMART DATA SECTION ===
SMART Health Status: OK

Current Drive Temperature:     30 C
Drive Trip Temperature:        85 C

Manufactured in week 51 of year 2013
Specified cycle count over device lifetime:  50000
Accumulated start-stop cycles:  3574
Specified load-unload count over device lifetime:  600000
Accumulated load-unload cycles:  25588
Elements in grown defect list: 0

Vendor (Seagate Cache) information
  Blocks sent to initiator = 12377123238969344

Error counter log:
           Errors Corrected by           Total   Correction     Gigabytes    Total
               ECC          rereads/    errors   algorithm      processed    uncorrected
           fast | delayed   rewrites  corrected  invocations   [10^9 bytes]  errors
read:   32484643        5         0  32484648   90556184     360684.117           0
write:         0        0         0         0    1285537      99909.049           0
verify:  1254503        0         0   1254503     343776     151110.867           0

Non-medium error count:        0

SMART Self-test log
Num  Test              Status                 segment  LifeTime  LBA_first_err [SK ASC ASQ]
     Description                              number   (hours)
# 1  Background short  Completed                   -   41257                 - [-   -    -]
# 2  Background short  Completed                   -   41257                 - [-   -    -]

Long (extended) Self-test duration: 29637 seconds [8.2 hours]

Background scan results log
  Status: no scans active
    Accumulated power on time, hours:minutes 42071:03 [2524263 minutes]
    Number of background scans performed: 260,  scan progress: 0.00%
    Number of background medium scans performed: 260

General statistics and performance log page:
  General access statistics and performance:
    Number of read commands: 2522036871
    Number of write commands: 737734034
    number of logical blocks received: 704461165187
    number of logical blocks transmitted: 195134860386
    read command processing intervals: 0
    write command processing intervals: 0
    weighted number of read commands plus write commands: 0
    weighted read command processing plus write command processing: 0
  Idle time:
    Idle time intervals: 964381968
      in seconds: 48219098.400
      in hours: 13394.194

Protocol Specific port log page for SAS SSP
relative target port id = 1
  generation code = 2
  number of phys = 1
  phy identifier = 0
    attached device type: SAS or SATA device
    attached reason: unknown
    reason: unknown
    negotiated logical link rate: phy enabled; 6 Gbps
    attached initiator port: ssp=1 stp=1 smp=1
    attached target port: ssp=0 stp=0 smp=0
    SAS address = 0x5000cca0277fb12d
    attached SAS address = 0x5003048011c7eb04
    attached phy identifier = 7
    Invalid DWORD count = 63
    Running disparity error count = 57
    Loss of DWORD synchronization count = 19
    Phy reset problem count = 0
relative target port id = 2
  generation code = 2
  number of phys = 1
  phy identifier = 1
    attached device type: no device attached
    attached reason: unknown
    reason: power on
    negotiated logical link rate: phy enabled; unknown
    attached initiator port: ssp=0 stp=0 smp=0
    attached target port: ssp=0 stp=0 smp=0
    SAS address = 0x5000cca0277fb12e
    attached SAS address = 0x0
    attached phy identifier = 0
    Invalid DWORD count = 0
    Running disparity error count = 0
    Loss of DWORD synchronization count = 0
    Phy reset problem count = 0
 

root@ubuntu:~# smartctl -x /dev/sda
smartctl 7.2 2020-12-30 r5155 [x86_64-linux-6.2.0-26-generic] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Vendor:               HGST
Product:              HUH721010AL42C0
Revision:             A3Z4
Compliance:           SPC-4
LU is fully provisioned
Rotation Rate:        7200 rpm
Form Factor:          3.5 inches
Logical Unit id:      0x5000cca26a66c478
Serial number:        2THUJ28D
Device type:          disk
Transport protocol:   SAS (SPL-3)
Local Time is:        Sun Jan 21 16:50:57 2024 UTC
device is NOT READY (e.g. spun down, busy)
A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.

Link to comment
2 hours ago, SimonF said:

Any way to connect the sas to the working card? May be an issue with HBA. 

 

Can you provide more info on case and connections?

Ok, So I have a ASUS z790 mobo, 12700k, and two LSI 9201-8i HBAs (one is listed as a RAID controller, one as SCSI, both are flashed with latest fw and in IT mode). 

 

I removed the one identified as a RAID controller.  The other works with SATA drives no problem.  I disconnect everything from them.  I put the HGST drive in another room, Im not fighting with them any more until i get this thing working.

 

I plug in an 8tb Dell SAS drive.  It is not recognized.  It is the only drive connected to the HBA that works with SATA drives.  lsblk doesnt show anything but the boot drive and the nvme.  

 

I have two sets of CABLEDECONN Mini SAS 36 SFF-8087 to (4) SFF-8482 Connectors with SATA Power.  I have tried switching those and trying the other port on the working HBA.  Nothing.  Could I somehow have the wrong cables?

Edited by ArrDee
Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.