Updating the HGST HDD & SSD firmware

Vahan

New Member
Sep 19, 2017
5
4
3
45
I have recently purchased several models of HGST HDD and SSD media and decided to synchronize their firmware versions, sharing the achieved results. I hope my following findings will save some time for the fellas attempting the same noble quest.

I wasn't able to find firmware upgrades on the HGST website, so the quest to find the recent version became more interesting. Having some of the drives with newer firmware helped to further narrow the search, and eventually, I was able to find a source that had not only HGST firmware but some other brands as well.

The whole process was done on SuperMicro servers running CentOS 7.5 x86_64. In my case, I had two servers, one with the BPN-SAS2-826A backplane connected to LSI 9201-16i HBA (SAS2116), and the other with the BPN-SAS3-216A backplane connected to 3 LSI 9300-8i (SAS3008) HBAs.

You will need the sg3_utils package:

Code:
yum install sg3_utils
Identify the drives installed by running the lsscsi command:

Code:
lsscsi -sig
HGST has specific names for the firmware files, and the larger chunk of the time was spent on finding the corresponding names for the models I own:

Code:
HUS724040ALS640    MPGNA3A0.bin
HUSSL4010ASS600    A0GNA182.bin
HUSSL4010BSS600    SRGNA1D0.bin
HUSMM1680ASS200    SPGNA204.bin
I was able to find these by googling the firmware revision versions I had on my drives and stumbled across a file named Drive_Firmware_1.13.tgz, apparently from a three letter brand and that file had lots of other models, with the model-firmware.bin pairs listed inside the fwupdate.ini file. Hint: search for "Drive Firmware Package Version 1.13 Release Notes" then browse around the pdf.

Next step: checking the official drive documentation for firmware update mechanisms:

https://www.hgst.com/sites/default/files/resources/Ultrastar_7K4000_SAS_Spec_V1.8.pdf
https://www.hgst.com/sites/default/files/resources/Ultrastar_SSD400S_SAS_V2.0.pdf
https://www.hgst.com/sites/default/files/resources/US_SSD800MH.B_1600MM_1600MR_ProdManual.pdf

I was able to confirm that the above models support SCSI firmware update operations, so the rest was easy:

Code:
# sg_write_buffer -vvvvv -m 5 --in SRGNA1D0.bin /dev/sg15
found bsg_major=248
open /dev/sg15 with flags=0x802
tried to read 8388608 bytes from SRGNA1D0.bin, got 1114112 bytes
will write 1114112 bytes
    Write buffer cmd: 3b 05 00 00 00 00 11 00 00 00
    Write buffer parameter list (first 256 bytes):
        11 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
        00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
        48 69 74 61 63 68 69 20  47 6c 6f 62 61 6c 20 53
        74 6f 72 61 67 65 20 54  65 63 68 6e 6f 6c 6f 67
        79 20 49 43 33 35 4c 78  78 78 55 78 44 33 32 31
        30 2d 30 20 4d 69 63 72  6f 63 6f 64 65 20 28 43
        29 20 43 6f 70 79 72 69  67 68 74 20 48 69 74 61
        63 68 69 20 43 6f 72 70  2e 20 32 30 30 33 2c 20
        32 30 30 34 2e 20 41 6c  6c 20 72 69 67 68 74 73
        20 72 65 73 65 72 76 65  64 2e 20 20 55 53 20 47
        6f 76 65 72 6e 6d 65 6e  74 20 55 73 65 72 73 20
        52 65 73 74 72 69 63 74  65 64 20 52 69 67 68 74
        73 20 2d 20 55 73 65 20  64 75 70 6c 69 63 61 74
        69 6f 6e 20 66 6f 72 20  64 69 73 63 6c 6f 73 75
        72 65 20 72 65 73 74 72  69 63 74 65 64 20 62 79
        20 47 43 41 20 41 44 50  20 53 63 68 65 64 75 6c
      duration=6747 ms
Make sure to address the drive by its /dev/sg?? name, not /dev/sd??, otherwise the operation will fail.

After the command completes, you can confirm the successful update by using the smartctl command, in my case:

Code:
smartctl -i /dev/sgXX | grep Revision
Note that the new firmware is not active until you reboot the server.

I also had some vendor-locked drives (HITACHI HUS72404CLAR4000, the branded version of the HGST HUS724040ALS640), and unfortunately, the same procedure failed for them:

Code:
# sg_write_buffer -vvvvvv -m 5 --in=MPGNA3A0.bin /dev/sg4
found bsg_major=248
open /dev/sg4 with flags=0x802
tried to read 8388608 bytes from MPGNA3A0.bin, got 1179648 bytes
will write 1179648 bytes
    Write buffer cmd: 3b 05 00 00 00 00 12 00 00 00
    Write buffer parameter list (first 256 bytes):
        12 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
        00 00 00 00 00 00 00 00  00 00 00 00 ff ff ff ff
        48 47 53 54 2c 20 61 20  57 65 73 74 65 72 6e 20
        44 69 67 69 74 61 6c 20  43 6f 6d 70 61 6e 79 20
        49 43 33 35 4c 78 78 78  55 78 44 33 32 31 30 2d
        30 20 4d 69 63 72 6f 63  6f 64 65 20 28 43 29 20
        43 6f 70 79 72 69 67 68  74 20 57 65 73 74 65 72
        6e 20 44 69 67 69 74 61  6c 20 43 6f 72 70 2e 20
        32 30 31 32 2c 20 32 30  31 32 2d 32 30 31 33 2e
        20 41 6c 6c 20 72 69 67  68 74 73 20 72 65 73 65
        72 76 65 64 2e 20 20 55  53 20 47 6f 76 65 72 6e
        6d 65 6e 74 20 55 73 65  72 73 20 52 65 73 74 72
        69 63 74 65 64 20 52 69  67 68 74 73 20 2d 20 55
        73 65 20 64 75 70 6c 69  63 61 74 69 6f 6e 20 66
        6f 72 20 64 69 73 63 6c  6f 73 75 72 65 20 72 65
        73 74 72 69 63 74 65 64  20 62 79 20 47 43 41 20
      duration=71 ms
write buffer:  Descriptor format, current;  Sense key: Illegal Request
 <<<Sense data overflow>>>
Additional sense: Parameter value invalid
  Descriptor type: Information
   >> descriptor too short
    00 00 00 00 00 00 00 00 00 00
  Descriptor type: Sense key specific: Field pointer
    Error in Data byte 0
  Descriptor type: Field replaceable unit
    code=0x0
  Descriptor type: Block commands
    Incorrect Length Indicator (ILI) clear
  Descriptor type: Vendor specific [0x80]
    f1 30
  Descriptor tybad field in Write buffer cdb
 
Last edited:

azev

Active Member
Jan 18, 2013
757
226
43
Just tried everything I can think of to try flashing sandisk ssd LT0800WM with a newer dell firmware on a supermicro server with no luck.
I also tried to flash IBM HGST HSVW800 with standard HGST firmware with no luck as well.

I am so tempted to buy both lenovo & dell server just so I can upgrade stuff when needed :(
 

747builder

Active Member
Dec 17, 2017
107
58
28
I have recently purchased several models of HGST HDD and SSD media and decided to synchronize their firmware versions, sharing the achieved results. I hope my following findings will save some time for the fellas attempting the same noble quest.

I wasn't able to find firmware upgrades on the HGST website, so the quest to find the recent version became more interesting. Having some of the drives with newer firmware helped to further narrow the search, and eventually, I was able to find a source that had not only HGST firmware but some other brands as well.

The whole process was done on SuperMicro servers running CentOS 7.5 x86_64. In my case, I had two servers, one with the BPN-SAS2-826A backplane connected to LSI 9201-16i HBA (SAS2116), and the other with the BPN-SAS3-216A backplane connected to 3 LSI 9300-8i (SAS3008) HBAs.

You will need the sg3_utils package:

Code:
yum install sg3_utils
Identify the drives installed by running the lsscsi command:

Code:
lsscsi -sig
HGST has specific names for the firmware files, and the larger chunk of the time was spent on finding the corresponding names for the models I own:

Code:
HUS724040ALS640    MPGNA3A0.bin
HUSSL4010ASS600    A0GNA182.bin
HUSSL4010BSS600    SRGNA1D0.bin
HUSMM1680ASS200    SPGNA204.bin
I was able to find these by googling the firmware revision versions I had on my drives and stumbled across a file named Drive_Firmware_1.13.tgz, apparently from a three letter brand and that file had lots of other models, with the model-firmware.bin pairs listed inside the fwupdate.ini file. Hint: search for "Drive Firmware Package Version 1.13 Release Notes" then browse around the pdf.

Next step: checking the official drive documentation for firmware update mechanisms:

https://www.hgst.com/sites/default/files/resources/Ultrastar_7K4000_SAS_Spec_V1.8.pdf
https://www.hgst.com/sites/default/files/resources/Ultrastar_SSD400S_SAS_V2.0.pdf
https://www.hgst.com/sites/default/files/resources/US_SSD800MH.B_1600MM_1600MR_ProdManual.pdf

I was able to confirm that the above models support SCSI firmware update operations, so the rest was easy:

Code:
# sg_write_buffer -vvvvv -m 5 --in SRGNA1D0.bin /dev/sg15
found bsg_major=248
open /dev/sg15 with flags=0x802
tried to read 8388608 bytes from SRGNA1D0.bin, got 1114112 bytes
will write 1114112 bytes
    Write buffer cmd: 3b 05 00 00 00 00 11 00 00 00
    Write buffer parameter list (first 256 bytes):
        11 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
        00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
        48 69 74 61 63 68 69 20  47 6c 6f 62 61 6c 20 53
        74 6f 72 61 67 65 20 54  65 63 68 6e 6f 6c 6f 67
        79 20 49 43 33 35 4c 78  78 78 55 78 44 33 32 31
        30 2d 30 20 4d 69 63 72  6f 63 6f 64 65 20 28 43
        29 20 43 6f 70 79 72 69  67 68 74 20 48 69 74 61
        63 68 69 20 43 6f 72 70  2e 20 32 30 30 33 2c 20
        32 30 30 34 2e 20 41 6c  6c 20 72 69 67 68 74 73
        20 72 65 73 65 72 76 65  64 2e 20 20 55 53 20 47
        6f 76 65 72 6e 6d 65 6e  74 20 55 73 65 72 73 20
        52 65 73 74 72 69 63 74  65 64 20 52 69 67 68 74
        73 20 2d 20 55 73 65 20  64 75 70 6c 69 63 61 74
        69 6f 6e 20 66 6f 72 20  64 69 73 63 6c 6f 73 75
        72 65 20 72 65 73 74 72  69 63 74 65 64 20 62 79
        20 47 43 41 20 41 44 50  20 53 63 68 65 64 75 6c
      duration=6747 ms
Make sure to address the drive by its /dev/sg?? name, not /dev/sd??, otherwise the operation will fail.

After the command completes, you can confirm the successful update by using the smartctl command, in my case:

Code:
smartctl -i /dev/sgXX | grep Revision
Note that the new firmware is not active until you reboot the server.

I also had some vendor-locked drives (HITACHI HUS72404CLAR4000, the branded version of the HGST HUS724040ALS640), and unfortunately, the same procedure failed for them:

Code:
# sg_write_buffer -vvvvvv -m 5 --in=MPGNA3A0.bin /dev/sg4
found bsg_major=248
open /dev/sg4 with flags=0x802
tried to read 8388608 bytes from MPGNA3A0.bin, got 1179648 bytes
will write 1179648 bytes
    Write buffer cmd: 3b 05 00 00 00 00 12 00 00 00
    Write buffer parameter list (first 256 bytes):
        12 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
        00 00 00 00 00 00 00 00  00 00 00 00 ff ff ff ff
        48 47 53 54 2c 20 61 20  57 65 73 74 65 72 6e 20
        44 69 67 69 74 61 6c 20  43 6f 6d 70 61 6e 79 20
        49 43 33 35 4c 78 78 78  55 78 44 33 32 31 30 2d
        30 20 4d 69 63 72 6f 63  6f 64 65 20 28 43 29 20
        43 6f 70 79 72 69 67 68  74 20 57 65 73 74 65 72
        6e 20 44 69 67 69 74 61  6c 20 43 6f 72 70 2e 20
        32 30 31 32 2c 20 32 30  31 32 2d 32 30 31 33 2e
        20 41 6c 6c 20 72 69 67  68 74 73 20 72 65 73 65
        72 76 65 64 2e 20 20 55  53 20 47 6f 76 65 72 6e
        6d 65 6e 74 20 55 73 65  72 73 20 52 65 73 74 72
        69 63 74 65 64 20 52 69  67 68 74 73 20 2d 20 55
        73 65 20 64 75 70 6c 69  63 61 74 69 6f 6e 20 66
        6f 72 20 64 69 73 63 6c  6f 73 75 72 65 20 72 65
        73 74 72 69 63 74 65 64  20 62 79 20 47 43 41 20
      duration=71 ms
write buffer:  Descriptor format, current;  Sense key: Illegal Request
 <<<Sense data overflow>>>
Additional sense: Parameter value invalid
  Descriptor type: Information
   >> descriptor too short
    00 00 00 00 00 00 00 00 00 00
  Descriptor type: Sense key specific: Field pointer
    Error in Data byte 0
  Descriptor type: Field replaceable unit
    code=0x0
  Descriptor type: Block commands
    Incorrect Length Indicator (ILI) clear
  Descriptor type: Vendor specific [0x80]
    f1 30
  Descriptor tybad field in Write buffer cdb
i know this thread is a few months old BUT.

so i figured out your post but couldnt download it from the 3 letter mfg. ended up grabbing the firmware archive from a ftp server.

do we know what firmware version the HUS724040ALS640 firmware is? and is it safe on flash on my HUS724040ALS640? they are normally 520 blocks where the rest of the industry is 512
 
Last edited:

Vahan

New Member
Sep 19, 2017
5
4
3
45
do we know what firmware version the HUS724040ALS640 firmware is? and is it safe on regular HUS724040ALS640? they are normally 520 blocks where the rest of the industry is 512
I think you've pasted the same model twice instead of the branded version?
 

muhfugen

Active Member
Dec 5, 2016
132
39
28
Does someone want to post a link for these firmware files? I'm trying to find some vSAN compatible firmware for my HGST SN200 disks but HGST refuses to provide them because they were OEM disks pulled from a Cisco UCS system.
 

747builder

Active Member
Dec 17, 2017
107
58
28
Does someone want to post a link for these firmware files? I'm trying to find some vSAN compatible firmware for my HGST SN200 disks but HGST refuses to provide them because they were OEM disks pulled from a Cisco UCS system.
the directions are in the first post but your welcome to send me a PM and can discuss getting them to you..
 

KJ4RNV

New Member
Nov 18, 2019
1
0
1
I have recently purchased several models of HGST HDD and SSD media and decided to synchronize their firmware versions, sharing the achieved results. I hope my following findings will save some time for the fellas attempting the same noble quest.

I wasn't able to find firmware upgrades on the HGST website, so the quest to find the recent version became more interesting. Having some of the drives with newer firmware helped to further narrow the search, and eventually, I was able to find a source that had not only HGST firmware but some other brands as well.

The whole process was done on SuperMicro servers running CentOS 7.5 x86_64. In my case, I had two servers, one with the BPN-SAS2-826A backplane connected to LSI 9201-16i HBA (SAS2116), and the other with the BPN-SAS3-216A backplane connected to 3 LSI 9300-8i (SAS3008) HBAs.

You will need the sg3_utils package:

Code:
yum install sg3_utils
Identify the drives installed by running the lsscsi command:

Code:
lsscsi -sig
HGST has specific names for the firmware files, and the larger chunk of the time was spent on finding the corresponding names for the models I own:

Code:
HUS724040ALS640    MPGNA3A0.bin
HUSSL4010ASS600    A0GNA182.bin
HUSSL4010BSS600    SRGNA1D0.bin
HUSMM1680ASS200    SPGNA204.bin
I was able to find these by googling the firmware revision versions I had on my drives and stumbled across a file named Drive_Firmware_1.13.tgz, apparently from a three letter brand and that file had lots of other models, with the model-firmware.bin pairs listed inside the fwupdate.ini file. Hint: search for "Drive Firmware Package Version 1.13 Release Notes" then browse around the pdf.

Next step: checking the official drive documentation for firmware update mechanisms:

https://www.hgst.com/sites/default/files/resources/Ultrastar_7K4000_SAS_Spec_V1.8.pdf
https://www.hgst.com/sites/default/files/resources/Ultrastar_SSD400S_SAS_V2.0.pdf
https://www.hgst.com/sites/default/files/resources/US_SSD800MH.B_1600MM_1600MR_ProdManual.pdf

I was able to confirm that the above models support SCSI firmware update operations, so the rest was easy:

Code:
# sg_write_buffer -vvvvv -m 5 --in SRGNA1D0.bin /dev/sg15
found bsg_major=248
open /dev/sg15 with flags=0x802
tried to read 8388608 bytes from SRGNA1D0.bin, got 1114112 bytes
will write 1114112 bytes
    Write buffer cmd: 3b 05 00 00 00 00 11 00 00 00
    Write buffer parameter list (first 256 bytes):
        11 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
        00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
        48 69 74 61 63 68 69 20  47 6c 6f 62 61 6c 20 53
        74 6f 72 61 67 65 20 54  65 63 68 6e 6f 6c 6f 67
        79 20 49 43 33 35 4c 78  78 78 55 78 44 33 32 31
        30 2d 30 20 4d 69 63 72  6f 63 6f 64 65 20 28 43
        29 20 43 6f 70 79 72 69  67 68 74 20 48 69 74 61
        63 68 69 20 43 6f 72 70  2e 20 32 30 30 33 2c 20
        32 30 30 34 2e 20 41 6c  6c 20 72 69 67 68 74 73
        20 72 65 73 65 72 76 65  64 2e 20 20 55 53 20 47
        6f 76 65 72 6e 6d 65 6e  74 20 55 73 65 72 73 20
        52 65 73 74 72 69 63 74  65 64 20 52 69 67 68 74
        73 20 2d 20 55 73 65 20  64 75 70 6c 69 63 61 74
        69 6f 6e 20 66 6f 72 20  64 69 73 63 6c 6f 73 75
        72 65 20 72 65 73 74 72  69 63 74 65 64 20 62 79
        20 47 43 41 20 41 44 50  20 53 63 68 65 64 75 6c
      duration=6747 ms
Make sure to address the drive by its /dev/sg?? name, not /dev/sd??, otherwise the operation will fail.

After the command completes, you can confirm the successful update by using the smartctl command, in my case:

Code:
smartctl -i /dev/sgXX | grep Revision
Note that the new firmware is not active until you reboot the server.

I also had some vendor-locked drives (HITACHI HUS72404CLAR4000, the branded version of the HGST HUS724040ALS640), and unfortunately, the same procedure failed for them:

Code:
# sg_write_buffer -vvvvvv -m 5 --in=MPGNA3A0.bin /dev/sg4
found bsg_major=248
open /dev/sg4 with flags=0x802
tried to read 8388608 bytes from MPGNA3A0.bin, got 1179648 bytes
will write 1179648 bytes
    Write buffer cmd: 3b 05 00 00 00 00 12 00 00 00
    Write buffer parameter list (first 256 bytes):
        12 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
        00 00 00 00 00 00 00 00  00 00 00 00 ff ff ff ff
        48 47 53 54 2c 20 61 20  57 65 73 74 65 72 6e 20
        44 69 67 69 74 61 6c 20  43 6f 6d 70 61 6e 79 20
        49 43 33 35 4c 78 78 78  55 78 44 33 32 31 30 2d
        30 20 4d 69 63 72 6f 63  6f 64 65 20 28 43 29 20
        43 6f 70 79 72 69 67 68  74 20 57 65 73 74 65 72
        6e 20 44 69 67 69 74 61  6c 20 43 6f 72 70 2e 20
        32 30 31 32 2c 20 32 30  31 32 2d 32 30 31 33 2e
        20 41 6c 6c 20 72 69 67  68 74 73 20 72 65 73 65
        72 76 65 64 2e 20 20 55  53 20 47 6f 76 65 72 6e
        6d 65 6e 74 20 55 73 65  72 73 20 52 65 73 74 72
        69 63 74 65 64 20 52 69  67 68 74 73 20 2d 20 55
        73 65 20 64 75 70 6c 69  63 61 74 69 6f 6e 20 66
        6f 72 20 64 69 73 63 6c  6f 73 75 72 65 20 72 65
        73 74 72 69 63 74 65 64  20 62 79 20 47 43 41 20
      duration=71 ms
write buffer:  Descriptor format, current;  Sense key: Illegal Request
 <<<Sense data overflow>>>
Additional sense: Parameter value invalid
  Descriptor type: Information
   >> descriptor too short
    00 00 00 00 00 00 00 00 00 00
  Descriptor type: Sense key specific: Field pointer
    Error in Data byte 0
  Descriptor type: Field replaceable unit
    code=0x0
  Descriptor type: Block commands
    Incorrect Length Indicator (ILI) clear
  Descriptor type: Vendor specific [0x80]
    f1 30
  Descriptor tybad field in Write buffer cdb
I know this is an old thread but, has anyone found out how to flash OEM vendor HDD's? Is it possible to flash a HGST 520 block drive after converting to 512 blocks using SG utility and then doing a firmware update using the same utility? Just curious to know anyone's success or failure. Sure would be nice knowing the bad block allocation table would be fixed.
 

ericmarshallu

New Member
Nov 15, 2019
2
0
1
If you've recently installed new hardware or an operating system on your computer, then you may want to update firmware and drivers for your hardware components. After you've downloaded your new firmware from the manufacturer's website, burn the ISO to a disc and perform the upgrade during system boot.
 

samwathegreat

New Member
Apr 1, 2020
17
14
3
Can anyone help me out here? Trying to update the firmware as per the OP, but the firmware is nowhere to be found. The vendor has locked down their downloads, and I can't access the needed file without a dell enterprise account. All I really need is the A0GNA182.bin firmware file, but if anyone could help me acquire the Drive_Firmware_1.13.tgz file, it would be much appreciated. I'm trying to update my drives that are on an old firmware version.

Thanks in advance
 
  • Like
Reactions: lte

NickM

Member
Jul 19, 2015
36
7
8
36
Ditto! It doesn't appear that the files as covertly-referenced in the original post are still available.

I have some new-to-me HGST sas drives (all model HUS726060AL5210) with mismatching firmware; the newer firmware drives perform great (160-200MB/sec writes), the older firmware drives are performing horribly (60-130MB/sec writes).

Could someone who has these relevant files saved please send them?
 

Vahan

New Member
Sep 19, 2017
5
4
3
45
NickM, the original archive I mentioned doesn't contain any firmware for your model, the closest is AHIST1EZ.bin for HUS726060ALA640
 

Vahan

New Member
Sep 19, 2017
5
4
3
45
Here is the full dump of fwupdate.ini from the OP archive.
Code:
# Disk firmware update config file
#
# The section name is the disk model.  Within each section, the
# current fw version maps to the pathname of the new firmware image we
# want to load.  The string "*" will match any firmware version that
# lacks a more specific version match.  A pathname of "None" will
# prevent any firmware upgrades for that firmware version.

[WDC WD1002FBYS-02A6B0]
*=/var/fw/disk/WDC/WD1002FBYS-02A6B0/0302C06.bin
03.02C06=None

[Hitachi HUA722020ALA330]
JKAOA20N=/var/fw/disk/Hitachi/JK07B3PA.BDX
JKAOA28A=/var/fw/disk/Hitachi/JK07B3PA.BDX
JKAOA3GA=/var/fw/disk/Hitachi/JK07B3PA.BD
JKAOA3MA=/var/fw/disk/Hitachi/JK07B3PA.BD
JKAOA3PA=None

[Hitachi HUA722010CLA330]
*=/var/fw/disk/Hitachi/JP07H3PA.BD
JP4OA3PA=None

[Hitachi HUA722050CLA330]
*=/var/fw/disk/Hitachi/JP07H3PA.BD
JP2OA3PA=None

[Hitachi HUA723030ALA640]
MKAOA580=/var/fw/disk/Hitachi/MK0PBA50.BC
MKAOA5V0=/var/fw/disk/Hitachi/MK0PBA50.BC
*=/var/fw/disk/Hitachi/MK0PBA50.BD
MKAOAA50=None

[Hitachi HUA723020ALA640]
MK7OA580=/var/fw/disk/Hitachi/MK0PBA50.BC
MK7OA5V0=/var/fw/disk/Hitachi/MK0PBA50.BC
*=/var/fw/disk/Hitachi/MK0PBA50.BD
MK7OAA50=None

[HITACHI HUSSL4010ASS600]
*=/var/fw/disk/Hitachi/A0GNA182.bin
A182=None

[HITACHI HUSSL4020ASS600]
*=/var/fw/disk/Hitachi/A0GNA182.bin
A182=None

[HITACHI HUSSL4040ASS600]
*=/var/fw/disk/Hitachi/A0GNA182.bin
A182=None

[HITACHI HUC109030CSS600]
*=/var/fw/disk/Hitachi/CEGNA5B0.bin
A5B0=None

[HITACHI HUC109060CSS600]
*=/var/fw/disk/Hitachi/CEGNA5B0.bin
A5B0=None

[HITACHI HUC109090CSS600]
*=/var/fw/disk/Hitachi/CEGNA5B0.bin
A5B0=None

[HITACHI HUSSL4010BSS600]
*=/var/fw/disk/Hitachi/SRGNA1D0.bin
A1D0=None

[HITACHI HUSSL4020BSS600]
*=/var/fw/disk/Hitachi/SRGNA1D0.bin
A1D0=None

[HITACHI HUSSL4040BSS600]
*=/var/fw/disk/Hitachi/SRGNA1D0.bin
A1D0=None

[HITACHI HUC106030CSS600]
*=/var/fw/disk/Hitachi/CDGNA430.bin
A430=None

[HITACHI HUC106060CSS600]
*=/var/fw/disk/Hitachi/CDGNA430.bin
A430=None

[HITACHI HUS156045VLS600]
*=/var/fw/disk/Hitachi/VCGNA760.bin
A760=None

[HGST HUS724040ALA640]
*=/var/fw/disk/Hitachi/MF0PBC50.BD
MFAOAC50=None

[HGST HUS724030ALA640]
*=/var/fw/disk/Hitachi/MF0PBC50.BD
MF8OAC50=None

[HGST HUS724020ALA640]
*=/var/fw/disk/Hitachi/MF0PBC50.BD
MF6OAC50=None

[HGST HUSMM8020ASS200]
*=/var/fw/disk/Hitachi/SMGNA210.bin
A210=None

[HGST HUSMM8040ASS200]
*=/var/fw/disk/Hitachi/SMGNA210.bin
A210=None

[HGST HUSMM8080ASS200]
*=/var/fw/disk/Hitachi/SMGNA210.bin
A210=None

[HGST HUSMM1620ASS200]
*=/var/fw/disk/Hitachi/SPGNA204.bin
A204=None

[HGST HUSMM1640ASS200]
*=/var/fw/disk/Hitachi/SPGNA204.bin
A204=None

[HGST HUSMM1680ASS200]
*=/var/fw/disk/Hitachi/SPGNA204.bin
A204=None

[HGST HUSMM1680ASS205]
*=/var/fw/disk/Hitachi/SPISD322.bin
d322=None

[HGST HUS726060ALA640]
*=/var/fw/disk/Hitachi/AHIST1EZ.bin
AHIST1EZ=None

[HDS725050KLA360]
*=/var/fw/disk/Hitachi/K2AOCD1A.BD
K2AOAD1A=None

[STEC    MACH8 IOPS]
*=/var/fw/disk/STEC/F2828.bin
2828=None

[STEC MACH8 IOPS]
*=/var/fw/disk/STEC/F2828.bin
2828=None

[STEC    M8ISB2B-200UC]
*=/var/fw/disk/STEC/F2832.bin
2832=None

[STEC M8ISB2B-200UC]
*=/var/fw/disk/STEC/F2832.bin
2832=None

[ST4000NM0033-9ZM170]
*=/var/fw/disk/Seagate/Megalodon-SNG4.lod
SNG4=None

[ST1000NM0033-9ZM173]
*=/var/fw/disk/Seagate/Megalodon-SNG4.lod
SNG4=None

[ST2000NM0033-9ZM175]
*=/var/fw/disk/Seagate/Megalodon-SNG4.lod
SNG4=None

[ST3000NM0033-9ZM178]
*=/var/fw/disk/Seagate/Megalodon-SNG4.lod
SNG4=None

[SEAGATE ST3000NM0063]
*=/var/fw/disk/Seagate/Megalodon-FIPS-0004.lod
0004=None

[SEAGATE ST4000NM0063]
*=/var/fw/disk/Seagate/Megalodon-FIPS-0004.lod
0004=None

[SEAGATE ST33000652SS]
*=/var/fw/disk/Seagate/MantaRay-FIPS-A006.lod
A006=None
 

NickM

Member
Jul 19, 2015
36
7
8
36
Excellent, thanks everyone (and especially Whaaat), firmware updated and this resolved the issues I was seeing

STH is great!
 

NickM

Member
Jul 19, 2015
36
7
8
36
I'm getting some weird responses to hdparm from these drives; no idea if this existed before flashing.

Code:
hdparm /dev/sdm

/dev/sdm:
SG_IO: bad/missing sense data, sb[]:  72 05 20 00 00 00 00 34 00 0a 00 00 00 00 00 00 00 00 00 00 01 0a 00 00 00 00 00 00 00 00 00 00
SG_IO: bad/missing sense data, sb[]:  72 05 20 00 00 00 00 34 00 0a 00 00 00 00 00 00 00 00 00 00 01 0a 00 00 00 00 00 00 00 00 00 00
 HDIO_DRIVE_CMD(identify) failed: Input/output error
 readonly      =  0 (off)
 readahead     = 256 (on)
SG_IO: bad/missing sense data, sb[]:  72 05 20 00 00 00 00 34 00 0a 00 00 00 00 00 00 00 00 00 00 01 0a 00 00 00 00 00 00 00 00 00 00
SG_IO: bad/missing sense data, sb[]:  72 05 20 00 00 00 00 34 00 0a 00 00 00 00 00 00 00 00 00 00 01 0a 00 00 00 00 00 00 00 00 00 00
 HDIO_DRIVE_CMD(identify) failed: Input/output error
 geometry      = 729601/255/63, sectors = 11721045168, start = 0
Is this something I should be concerned about with hdparm throwing errors for SAS drive?

I tried playing with the sdparm MRIE setting to different values, but that didn't seem to help.
 

Whaaat

Active Member
Jan 31, 2020
170
44
28
hdparm is intended for consumer ATA drives, use sdparm to play with mode page parameters if you know what they are related to. MRIE changes how drive will report problems to controller when something unexpected happens during its normal operation, for example mismatch in data while read after write or trouble reading sectors during background surface scan. It hasn't to and will not help hdparm to work correctly with SAS drive.
 
  • Like
Reactions: NickM