Re: "LA check failed" with decommissioned 6TB Samsung "Enterprise Capacity" drives

From: Kenneth D. Merry <ken_at_FreeBSD.ORG>
Date: Fri, 21 Apr 2023 20:49:04 UTC
On Sun, Apr 16, 2023 at 11:48:08 +1000, Mark Gladman wrote:
> Hey all,
> 
> My first time posting so I hope I've done everything right..!
> 
> I recently got some 6TB "Enterprise Capacity" Samsung SAS (They're 
> marked 'Enterprise Capacity 2.5 HDD v4') drives pulled from some devices 
> from work that have been decommissioned and I've been trying to set them 
> up on my home server.
> I have an SAS9211-8i controller with a SATA/SAS backplane that they're 
> connected to.
> 
> I'm getting these errors (it's the same for all of them but just showing 
> one for brevity):
> 
> dmesg
> da3 at mps0 bus 0 scbus0 target 11 lun 0
> da3: <SEAGATE DKS2F-H6R0SS 7FA6> Fixed Direct Access SPC-3 SCSI device
> da3: Serial Number Z4D47M960000R630UXCC
> da3: 600.000MB/s transfers
> da3: Command Queueing enabled
> da3: 5723166MB (11721045168 512 byte sectors)
> (da3:mps0:0:11:0): WRITE(6). CDB: 0a 00 00 00 01 00
> (da3:mps0:0:11:0): CAM status: SCSI Status Error
> (da3:mps0:0:11:0): SCSI status: Check Condition
> (da3:mps0:0:11:0): SCSI sense: HARDWARE FAILURE asc:81,0 (LA Check Failed)
> (da3:mps0:0:11:0): Info: 0
> (da3:mps0:0:11:0): Command Specific Info: 0

Hmm, not sure what LA Check means, perhaps logical address.

> When I attempt to add anything via gpart it throws:
> gpart: Input/output error
> 
> and triggers more of the SCSI status errors (identical to what's above)
> 
> I can see it's connected to the SAS controller properly (it's 
> 5000c500852f6575 below):
> 
> mpsutil show all
> Adapter:
> mps0 Adapter:
>         Board Name: SAS9211-8i
>     Board Assembly:
>          Chip Name: LSISAS2008
>      Chip Revision: ALL
>      BIOS Revision: 7.39.02.00
> Firmware Revision: 20.00.07.00
>    Integrated RAID: no
>           SATA NCQ: ENABLED
>   PCIe Width/Speed: x8 (5.0 GB/sec)
>          IOC Speed: Full
>        Temperature: Unknown/Unsupported
> 
> PhyNum  CtlrHandle  DevHandle  Disabled  Speed   Min    Max    Device
> 0       0001        0009       N         6.0     1.5    6.0    SAS Initiator
> 1       0002        000a       N         3.0     1.5    6.0    SAS Initiator
> 2                              N                 1.5    6.0    SAS Initiator
> 3                              N                 1.5    6.0    SAS Initiator
> 4       0005        000d       N         6.0     1.5    6.0    SAS Initiator
> 5       0004        000c       N         3.0     1.5    6.0    SAS Initiator
> 6                              N                 1.5    6.0    SAS Initiator
> 7       0003        000b       N         3.0     1.5    6.0    SAS Initiator
> 
> Devices:
> B____T    SAS Address      Handle  Parent    Device        Speed Enc 
> Slot  Wdt
> 00   04   4433221100000000 0009    0001      SATA Target   6.0   0001 03 
>     1
> 00   05   4433221101000000 000a    0002      SATA Target   3.0   0001 02 
>     1
> 00   08   4433221107000000 000b    0003      SATA Target   3.0   0001 04 
>     1
> 00   10   4433221105000000 000c    0004      SATA Target   3.0   0001 06 
>     1
> 00   11   5000c500852f6575 000d    0005      SAS Target    6.0   0001 07 
>     1
> 
> Enclosures:
> Slots      Logical ID     SEPHandle  EncHandle    Type
>    08    500605b007f41c80               0001     Direct Attached SGPIO
> 
> 
> I did some searching and some suggested they might've been set to 520 
> byte sectors if they came from a NetApp device but I can confirm they're 
> not (or I believe what's reported below is confirming it)
> 
> diskinfo -v /dev/da3
> /dev/da3
>          512             # sectorsize
>          6001175126016   # mediasize in bytes (5.5T)
>          11721045168     # mediasize in sectors
>          4096            # stripesize
>          0               # stripeoffset
>          729601          # Cylinders according to firmware.
>          255             # Heads according to firmware.
>          63              # Sectors according to firmware.
>          SEAGATE DKS2F-H6R0SS    # Disk descr.
>          Z4D47M960000R630UXCC    # Disk ident.
>          mps0            # Attachment
>          No              # TRIM/UNMAP support
>          7200            # Rotation rate in RPM
>          Not_Zoned       # Zone Mode

Yep, you've got 512 byte sectors, so that isn't the problem.

> I've been able to find very little info on the specific error "LA Check 
> Failed". I looked a /usr/src/sys/cam/scsi/scsi_all.c and honestly that 
> doesn't help me at all (I'll admit I'm more 'admin' than 'developer' 
> too) and it appears to be a Seagate specific error but otherwise I'm lost.
> 
> Any help would be most appreciated!

Well, one thing to try, since you can't write to it anyway, is formatting
it.

You can do it with camcontrol format or if you install sg3_utils you can do
it with sg_format.

If that doesn't work, you can try getting the log pages and smart data off
the drive to see if there is anything interesting.

If you install sg3_utils, you can do:

sg_logs -a /dev/da3

And if you install smartmontools:

smartctl -a /dev/da3

Those might give you a hint about what is going on.

Ken
-- 
Kenneth Merry
ken@FreeBSD.ORG