HGST SAS drive not working

carbonfiber

New Member
Credits
26
Hi, I have a problem with getting a SAS drive working on Linux.

Software: Ubuntu 18.04
Hardware: Dell Precision T5500 with DELL Perc H200 controller card
Hard drive in question: HGST HUS724030ALS640 (UltraStar 7K4000 3 TB SAS)

The controller card firmware was updated by following this guide:
I did this because the card would not recognize the drive before.

The controller shows up with lspci:

Code:
[email protected]:~$ lspci | grep -i sas
23:00.0 Serial Attached SCSI controller: LSI Logic / Symbios Logic SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] (rev 03)
Now the disk shows up in the Gnome Disk utility as /dev/sda with the correct model number but it shows up with "No Media" and I can't format the drive.
GParted doesn't see the drive.
The smartctl command shows instead the following info:

Code:
[email protected]:~$ sudo smartctl -x /dev/sda
smartctl 6.6 2016-05-31 r4324 [x86_64-linux-5.3.0-28-generic] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Vendor:               HGST
Product:              HUS724030ALS640
Revision:             A1C5
Compliance:           SPC-4
User Capacity:        3,047,477,247,360 bytes [3.04 TB]
Logical block size:   520 bytes
LU is resource provisioned, LBPRZ=0
Rotation Rate:        7200 rpm
Form Factor:          3.5 inches
Logical Unit id:      0x5000cca027c2bac8
Serial number:        P8KG2XSW
Device type:          disk
Transport protocol:   SAS (SPL-3)
Local Time is:        Sun Oct 25 18:19:19 2020 UTC
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:     35 C
Drive Trip Temperature:        85 C

Manufactured in week 10 of year 2014
Specified cycle count over device lifetime:  50000
Accumulated start-stop cycles:  16
Specified load-unload count over device lifetime:  600000
Accumulated load-unload cycles:  16
Elements in grown defect list: 0

Vendor (Seagate) cache information
  Blocks sent to initiator = 1509949440

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:          0        0         0         0          0          0.001           0
write:         0        0         0         0          0          0.000           0
verify:        0        0         0         0          2          0.000           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                   -       5                 - [-   -    -]

Long (extended) Self Test duration: 29637 seconds [493.9 minutes]

Background scan results log
  Status: scan is active
    Accumulated power on time, hours:minutes 6:22 [382 minutes]
    Number of background scans performed: 0,  scan progress: 3.84%
    Number of background medium scans performed: 0

Protocol Specific port log page for SAS SSP
relative target port id = 1
  generation code = 1
  number of phys = 1
  phy identifier = 0
    attached device type: SAS or SATA device
    attached reason: power on
    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 = 0x5000cca027c2bac9
    attached SAS address = 0x5d4ae520b1ed8e00
    attached phy identifier = 7
    Invalid DWORD count = 31
    Running disparity error count = 27
    Loss of DWORD synchronization = 9
    Phy reset problem = 0
    Phy event descriptors:
     Invalid word count: 31
     Running disparity error count: 27
     Loss of dword synchronization count: 9
     Phy reset problem count: 0
relative target port id = 2
  generation code = 1
  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 = 0x5000cca027c2baca
    attached SAS address = 0x0
    attached phy identifier = 0
    Invalid DWORD count = 0
    Running disparity error count = 0
    Loss of DWORD synchronization = 0
    Phy reset problem = 0
    Phy event descriptors:
     Invalid word count: 0
     Running disparity error count: 0
     Loss of dword synchronization count: 0
     Phy reset problem count: 0
If I run the smartctl short self-test I can hear the drive moving the heads around so I don't think it has a mechanical problem.

Also I tried a couple of tests with hdparm:

Code:
[email protected]:~$ sudo hdparm -Tt /dev/sda

/dev/sda:
read() hit EOF - device too small
 Timing buffered disk reads: read() hit EOF - device too small


[email protected]:~$ sudo hdparm -I /dev/sda | more
SG_IO: bad/missing sense data, sb[]:  70 00 05 00 00 00 00 18 00 00 00 00 20 00 00 c0 00 00 00 00 f8 21 00 00 00 00 00 00 00 00 00 00
SG_IO: bad/missing sense data, sb[]:  70 00 05 00 00 00 00 18 00 00 00 00 20 00 00 c0 00 00 00 00 f8 21 00 00 00 00 00 00 00 00 00 00
 HDIO_DRIVE_CMD(identify) failed: Input/output error

/dev/sda:
It seems I can't access the drive itself and I don't exactly know how to make it work.
 


Eugor

Member
Credits
196
Don't know if this could be it, but...

if there's an issue with disk finding or operation, once on the right firmware, consider the cable first. Even if a SAS cable can detect SATA drives it still might not work properly for SAS - I've had this and it's a hard one to trouble shoot if you wrongly assume that "my card can see SATA drives" implies that the cable is sure to be good for SAS as well. If in doubt, Adaptec/Microsemi make reliable cables. Dell's adapter cables which came with my card also look fairly well-made. The cheap thin SAS cables off EBay that work for SATA but not SAS drives (no idea how that can be but it's what happened to me, first time) could be a hidden issue.

If the issue's still not solved and it's not the cable, and other troubleshooting fails, then SBR might be a candidate (see link below), or ask for help in the forums.


Excert taken from https://www.truenas.com/community/r...-lsi-9211-9300-9305-9311-hba-and-variants.54/
 

carbonfiber

New Member
Credits
26
Don't know if this could be it, but...

if there's an issue with disk finding or operation, once on the right firmware, consider the cable first. Even if a SAS cable can detect SATA drives it still might not work properly for SAS - I've had this and it's a hard one to trouble shoot if you wrongly assume that "my card can see SATA drives" implies that the cable is sure to be good for SAS as well. If in doubt, Adaptec/Microsemi make reliable cables. Dell's adapter cables which came with my card also look fairly well-made. The cheap thin SAS cables off EBay that work for SATA but not SAS drives (no idea how that can be but it's what happened to me, first time) could be a hidden issue.

If the issue's still not solved and it's not the cable, and other troubleshooting fails, then SBR might be a candidate (see link below), or ask for help in the forums.


Excert taken from https://www.truenas.com/community/r...-lsi-9211-9300-9305-9311-hba-and-variants.54/
But the data I am getting with smartctl comes from the SAS drive that has the SAS interface, so the SAS interface between controller card and drive is working; the cables that I am using are the SAS cables that came with the controller card.
Anyway I will check the link to see if I find some answers, thanks.
 


Members online


Latest posts

Top