Changing block size IBM branded Micron S650DC-800 SSD

sephallen

New Member
Jan 22, 2021
13
0
1
I'm not 100% sure, but I'm positive enough that your case is completely similar as far as I can see ;)
That's good enough for me! I've ordered one from eBay, it should by Friday.
I'll keep you posted and thanks so much for all your efforts so far!
 

sephallen

New Member
Jan 22, 2021
13
0
1
@Whaaat bit of an update:

The H700 arrived and I put it into my server. However, it is unable to detect the IBM SAS SSD, in PD Mgmt it displays the message "No PD Present". So I tried with an old 200gb SATA HDD and it detects the drive successfully.

My next thought was to update the firmware on the controller and I noticed from your screenshot that you were running a new version that me. Firstly, I tried the Linux update binary from Dell, but this fails due to incompatible hardware (I presume because my server is not a PowerEdge). So I tried putting the controller into a desktop machine which has Windows installed on a spare drive in order to use the Windows based update tool.
Unfortunately, my desktop machine failed to POST with the controller inserted, but after some googling, I found out that SMBus pins needed to be covered on the controller for my machine to be able to POST.
After covering the two pins, running the firmware update tool in Windows was successful, but sadly, the IBM SAS SSD is still not detected by the H700.

I'm not sure how to progress from here, do you have any more suggestions?
 

Whaaat

Active Member
Jan 31, 2020
142
39
28
Most likely it's because of 528 sector size. Every disk with non 512 sector size didn't work at first with any of my RAID controllers. I had to plug them into HBA to reformat first. The fun thing is no vendor incompatibility involved here: my IBM M5110 didn't want to work with IBM 00VJ568 SAS drives (520 bps, SED capable but luckily arrived unsecured) until I reformatted them from 520 to 512 bps on an HBA. Although these drive were displayed in MSM and storcli as unsupported with M5110. What you can try to do next is to load Windows with your drive attached to H700 and see how perccli (or MegaCli for older controllers) will show this drive. There is a chance that perccli will let you perform 'secureerase' command on unsupported drive.

perccli.PNG
If this fails too there was a post somewhere in other topic that sedutil fails into linux but works correctly into TrueNas. Try this (with HBA) into TrueNas.

I was curious what are those controllers that initially work with 520-528 bps drives in VD and found that they are crazy expensive pieces of hardware even in used untested condition that will definitely not work in ordinary computer under common OS.
 

sephallen

New Member
Jan 22, 2021
13
0
1
What you can try to do next is to load Windows with your drive attached to H700 and see how perccli (or MegaCli for older controllers) will show this drive.
perccli can detect the H700, but it fails to show the IBM SAS SSD (I assume this is to be expected considering the drive is not detected in the controller's BIOS either). I did attach another drive to the H700 so I could confirm the commands work. Even though perccli would not display the IBM SAS SSD, I ran the 'secureerase' command at the location I knew it was physically attached too, but this ultimately failed.

If this fails too there was a post somewhere in other topic that sedutil fails into linux but works correctly into TrueNas. Try this (with HBA) into TrueNas.
This showed some promise, which surprises me as the sedutil for FreeBSD appears to be a port of the Linux tool.
Here are some outputs of the commands I ran:
Bash:
Scanning for Opal compliant disks
/dev/ada0  E  IBM SSG IBM  SSGSVW800  7201

Which seems great, sedutil is at least acknowledging encryption is available. Running the following commands all report success:

Bash:
sedutil-cli --yesIreallywanttoERASEALLmydatausingthePSID redacted /dev/da0
revertTper completed successfully

sedutil-cli --PSIDrevert redacted /dev/da0
revertTper completed successfully
(sedutil-cli --PSIDrevertAdminSP redacted /dev/da0 was not recognised)

I didn't run the above commands all after each other, I tried each one after the next steps failed.

sg_format -v --format --size=512 /dev/da0 returns the same failure messages as before.

and attempting to wipe the drive with dd if=/dev/zero of=/dev/da0 bs=1m count=32 or via the TrueNAS UI results in the same error as described here.

I feel as if we got much closer, but not quite there!
 

Whaaat

Active Member
Jan 31, 2020
142
39
28
I feel as if we got much closer, but not quite there!
Good, if PSID revert was succesful, LBA ranges has to be unlocked now. Format commands may fail now because those LBA ranges are unclaimed and drive has zero available capacity for format. Can you please list the output of smartctl utility to prove of deny this assumption?
sg_format -v --format --size=512 /dev/da0 returns the same failure messages as before.
Try sg_format --resize --count=-1 /dev/da0 prior to format
 

sephallen

New Member
Jan 22, 2021
13
0
1
Can you please list the output of smartctl utility to prove of deny this assumption?
Bash:
smartctl 7.1 2019-12-30 r5022 [FreeBSD 12.2-RELEASE-p2 amd64] (local build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Vendor:               IBM-SSG
Product:              IBM-SSGMSVW800
Revision:             7201
Compliance:           SPC-4
User Capacity:        800,166,073,344 bytes [800 GB]
Logical block size:   528 bytes
Physical block size:  4224 bytes
LU is resource provisioned, LBPRZ=1
Rotation Rate:        Solid State Device
Form Factor:          2.5 inches
Logical Unit id:      0x5000c500ad704fd8
Serial number:        redacted
Device type:          disk
Transport protocol:   SAS (SPL-3)
Local Time is:        Mon Feb  8 23:46:24 2021 PST
SMART support is:     Available - device has SMART capability.
SMART support is:     Enabled
Temperature Warning:  Enabled

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

Percentage used endurance indicator: 0%
Current Drive Temperature:     33 C
Drive Trip Temperature:        65 C

Elements in grown defect list: 0

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:   248218036        0  12261420  248218036          0       6173.867    0
write:         0        0         0         0          0       5079.482  0

Bash:
smartctl 7.1 2019-12-30 r5022 [FreeBSD 12.2-RELEASE-p2 amd64] (local build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Vendor:               IBM-SSG
Product:              IBM-SSGMSVW800
Revision:             7201
Compliance:           SPC-4
User Capacity:        800,166,073,344 bytes [800 GB]
Logical block size:   528 bytes
Physical block size:  4224 bytes
LU is resource provisioned, LBPRZ=1
Rotation Rate:        Solid State Device
Form Factor:          2.5 inches
Logical Unit id:      0x5000c500ad704fd8
Serial number:        redacted
Device type:          disk
Transport protocol:   SAS (SPL-3)
Local Time is:        Mon Feb  8 23:54:27 2021 PST
SMART support is:     Available - device has SMART capability.
SMART support is:     Enabled
Temperature Warning:  Enabled
Read Cache is:        Enabled
Writeback Cache is:   Disabled

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

Percentage used endurance indicator: 0%
Current Drive Temperature:     33 C
Drive Trip Temperature:        65 C

Elements in grown defect list: 0

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:   248218036        0  12261420  248218036          0       6173.867    0
write:         0        0         0         0          0       5079.482  0
verify:        0        0         0         0          0       3200.664  0

Non-medium error count:        0

No Self-tests have been logged

Background scan results log
  Status: waiting until BMS interval timer expires
    Accumulated power on time, hours:minutes 321:51 [19311 minutes]
    Number of background scans performed: 34,  scan progress: 0.00%
    Number of background medium scans performed: 0

Protocol Specific port log page for SAS SSP
relative target port id = 1
  generation code = 0
  number of phys = 1
  phy identifier = 0
    attached device type: SAS or SATA device
    attached reason: power on
    reason: loss of dword synchronization
    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 = 0x5000c500ad704fd9
    attached SAS address = 0x5000ea62a0058d00
    attached phy identifier = 4
    Invalid DWORD count = 5
    Running disparity error count = 5
    Loss of DWORD synchronization = 2
    Phy reset problem = 0
    Phy event descriptors:
     Invalid word count: 5
     Running disparity error count: 5
     Loss of dword synchronization count: 2
     Phy reset problem count: 0
relative target port id = 2
  generation code = 0
  number of phys = 1
  phy identifier = 1
    attached device type: no device attached
    attached reason: unknown
    reason: unknown
    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 = 0x5000c500ad704fda
    attached SAS address = 0x0
    attached phy identifier = 0
    Invalid DWORD count = 0
    Running disparity error count = 0
    Loss of DWORD synchronizati

Try sg_format --resize --count=-1 /dev/da0 prior to format
Bash:
    IBM-SSG   IBM-SSGMSVW800    7201   peripheral_type: disk [0x0]
      Unit serial number: redacted
      LU name: 5000c500ad704fd8
Mode Sense (block descriptor) data, prior to changes:
  Number of blocks=1515466048 [0x5a542d40]
  Block size=528 [0x210]
Resize operation seems to have been successful

The resize looked good, however, I am still unable to change the sector size:

Bash:
    IBM-SSG   IBM-SSGMSVW800    7201   peripheral_type: disk [0x0]
      PROTECT=0
      Unit serial number: redacted
      LU name: 5000c500ad704fd8
    mode sense(10) cdb: [5a 00 01 00 00 00 00 00 fc 00]
Mode Sense (block descriptor) data, prior to changes:
  Number of blocks=1515466048 [0x5a542d40]
  Block size=528 [0x210]
    mode select(10) cdb: [55 11 00 00 00 00 00 00 1c 00]
mode select(10):
Fixed format, current; Sense key: Illegal Request
Additional sense: Invalid field in parameter list
  Field replaceable unit code: 17
  Sense Key Specific: Error in Data parameters: byte 13 bit 7
Try MODE SELECT again with SP=0 this time
    mode select(10) cdb: [55 10 00 00 00 00 00 00 1c 00]
 

sephallen

New Member
Jan 22, 2021
13
0
1
How about --six option?
I did actually try this under FreeBSD (TrueNAS) previously, though I didn't list it above. Here is the same command under Linux though:

Bash:
    IBM-SSG   IBM-SSGMSVW800    7201   peripheral_type: disk [0x0]
      PROTECT=0
      Unit serial number: redacted
      LU name: 5000c500ad704fd8
    mode sense(6) cdb: [1a 00 01 00 fc 00]
Mode Sense (block descriptor) data, prior to changes:
  Number of blocks=1515466048 [0x5a542d40]
  Block size=528 [0x210]
    mode select(6) cdb: [15 11 00 00 18 00]
mode select(6):
Fixed format, current; Sense key: Illegal Request
Additional sense: Invalid field in parameter list
  Field replaceable unit code: 17
  Sense Key Specific: Error in Data parameters: byte 9 bit 7
Try MODE SELECT again with SP=0 this time
    mode select(6) cdb: [15 10 00 00 18 00]
mode select(6):
Fixed format, current; Sense key: Illegal Request
Additional sense: Invalid field in parameter list
  Field replaceable unit code: 17
  Sense Key Specific: Error in Data parameters: byte 9 bit 7
MODE SELECT command: Illegal request, type: sense key, apart from Invalid opcode

Have you tried to change the firmware this time?
I have just tried this now, however the outcome is the same as the previous attempts, for example:

Bash:
Write buffer: pass-through os error: Invalid argument
Write buffer failed: Invalid argument
sg_write_buffer failed: Invalid argument

again, this attempt was under Linux, though I am happy to try under FreeBSD again (it may take me a few days, I like to try to limit server downtime as much as possible!).
 

Whaaat

Active Member
Jan 31, 2020
142
39
28
Sometimes things simply do not work as intended with those SAS drives. Even for drives with original firmware. I received another HGST drive last week which is different only in firmware version from what I had earlier, and guess what, it refused to be formatted after I 'securely erased' it. H700 displayed it as 'ready', but it was 'unconfigured bad' on any other controller.
uBAD.PNG
I tried all I could imagine to no avail, and eventually I had to create RAID0 consisting of a single drive on H700 and only after this action drive became operational. Strange, but even two disks of the same model with slightly different firmware version behave in a different manner. Not to mention that HPE H240 doesn't detect those drives at all.))
So the sequence of operations is trial and error unfortunately.
In your case I would still try to find the right order of commands this drive requires to be formatted. What sg_format will tell if you try to format the drive with current sector size first? Try hitachi HUGO tool also, who knows maybe it will work.)
 

daniel.kovacs

New Member
Feb 28, 2021
6
0
1
I'm just got two IBM SSD drives. One is a Micron S630DC 3.8T (MTFDJAL3T8MBT), the other one is a Seagate Nytro 7.68T (XS7680SE70014).
I tried all of the possible methods listen in this topic to format from 528 byte to 512 byte but no success yet :(
I'm also tried to format in Avago (LSI) configuration utility with an LSI SAS2008 HBA (in IT mode). The format successed within a minute, but the the drive stays in 528 byte :(
And the same when I format with sg_format to the origianl (528 byte sector size):
root@r1u01-02:/home/ubuntu# sg_format --format --size=528 /dev/sg2
IBM-SSG IBM-SSGMSVT3P8 7214 peripheral_type: disk [0x0]
Unit serial number: ZAT1573Z0000822150Z3
LU name: 5000c500ad71fe60
Mode Sense (block descriptor) data, prior to changes:
<<< longlba flag set (64 bit lba) >>>
Number of blocks=7274159057 [0x1b192dbd1]
Block size=528 [0x210]

A FORMAT UNIT will commence in 15 seconds
ALL data on /dev/sg2 will be DESTROYED
Press control-C to abort

A FORMAT UNIT will commence in 10 seconds
ALL data on /dev/sg2 will be DESTROYED
Press control-C to abort

A FORMAT UNIT will commence in 5 seconds
ALL data on /dev/sg2 will be DESTROYED
Press control-C to abort

Format unit has started
FORMAT UNIT Complete


Do I have any chance to flash the factory firmware? (I hope it could help me to format to 512 byte format)

If I have any good news I'll update you ASAP! :)
 
Last edited:

daniel.kovacs

New Member
Feb 28, 2021
6
0
1
Of course, but no luck :(

root@r1u03-04:/home/ubuntu/Linux/Lin64# ./SeaChest_Format_140_11923_64 -d /dev/sg3 --setSectorSize 512 --confirm this-will-erase-data
==========================================================================================
SeaChest_Format - Seagate drive utilities - NVMe Enabled
Copyright (c) 2014-2019 Seagate Technology LLC and/or its Affiliates, All Rights Reserved
SeaChest_Format Version: 1.4.0-1_19_23 X86_64
Build Date: Jun 10 2019
Today: Mon Mar 1 07:57:30 2021
==========================================================================================

/dev/sg3 - IBM-SSGSSHU7P6 - HLM047370000822150Z3 - SCSI
Set Sector Size to 512
Setting sector size not supported on this device
For SCSI Drives, try a format unit operation
 

Whaaat

Active Member
Jan 31, 2020
142
39
28
wrong option, --formatUnit is what you need, --setSectorSize is fast format change from 512e to 4096 and will not work for your case even if the drive supports it.
 

daniel.kovacs

New Member
Feb 28, 2021
6
0
1
wrong option, --formatUnit is what you need, --setSectorSize is fast format change from 512e to 4096 and will not work for your case even if the drive supports it.
formatUnit not working either, enabled verbose mode to get more info :(

root@r1u03-04:/home/ubuntu/Linux/Lin64# ./SeaChest_Format_140_11923_64 -v4 -d /dev/sg3 --formatUnit 512 --confirm this-will-erase-data
==========================================================================================
SeaChest_Format - Seagate drive utilities - NVMe Enabled
Copyright (c) 2014-2019 Seagate Technology LLC and/or its Affiliates, All Rights Reserved
SeaChest_Format Version: 1.4.0-1_19_23 X86_64
Build Date: Jun 10 2019
Today: Mon Mar 1 11:23:09 2021
==========================================================================================
Sending SCSI Inquiry

CDB:

0 1 2 3 4 5
0x00 12 00 00 00 60 00

Sending command with send_IO

Sense Data Buffer:

0 1 2 3 4 5 6 7
0x00 00 00 00 00 00 00 00 00


Sense Key: 0h = No Error
ASC & ASCQ: 0h - 0h = No Additional Sense Information
FRU: 0h = No Additional Information
Information: 0000000000000000h
Command Specific Information: 0000000000000000h
Command Time (us): 546.82

Data Buffer being returned:

0 1 2 3 4 5 6 7 8 9 A B C D E F
0x00 00 00 07 32 9F 00 10 02 49 42 4D 2D 53 53 47 20 ...2....IBM-SSG
0x10 49 42 4D 2D 53 53 47 53 53 48 55 37 50 36 20 20 IBM-SSGSSHU7P6
0x20 45 31 41 30 48 4C 4D 30 34 37 33 37 45 31 41 30 E1A0HLM04737E1A0
0x30 45 31 41 30 45 31 41 30 00 20 20 20 20 20 20 20 E1A0E1A0.
0x40 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20
0x50 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20


Inquiry returning: SUCCESS

Sending SCSI Inquiry, VPD = 00h

CDB:

0 1 2 3 4 5
0x00 12 01 00 00 60 00

Sending command with send_IO

Sense Data Buffer:

0 1 2 3 4 5 6 7
0x00 00 00 00 00 00 00 00 00


Sense Key: 0h = No Error
ASC & ASCQ: 0h - 0h = No Additional Sense Information
FRU: 0h = No Additional Information
Information: 0000000000000000h
Command Specific Information: 0000000000000000h
Command Time (us): 501.13

Data Buffer being returned:

0 1 2 3 4 5 6 7 8 9 A B C D E F
0x00 00 00 00 18 00 03 80 83 86 87 88 8A 8D 90 91 B0 ................
0x10 B1 B2 B7 C0 C1 C3 C4 C7 C8 C9 D1 D2 50 36 20 20 ............P6
0x20 45 31 41 30 48 4C 4D 30 34 37 33 37 45 31 41 30 E1A0HLM04737E1A0
0x30 45 31 41 30 45 31 41 30 00 20 20 20 20 20 20 20 E1A0E1A0.
0x40 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20
0x50 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20


Inquiry returning: SUCCESS

Sending SCSI Inquiry, VPD = 80h

CDB:

0 1 2 3 4 5
0x00 12 01 80 00 18 00

Sending command with send_IO

Sense Data Buffer:

0 1 2 3 4 5 6 7
0x00 00 00 00 00 00 00 00 00


Sense Key: 0h = No Error
ASC & ASCQ: 0h - 0h = No Additional Sense Information
FRU: 0h = No Additional Information
Information: 0000000000000000h
Command Specific Information: 0000000000000000h
Command Time (us): 491.09

Data Buffer being returned:

0 1 2 3 4 5 6 7 8 9 A B C D E F
0x00 00 80 00 14 48 4C 4D 30 34 37 33 37 30 30 30 30 ....HLM047370000
0x10 38 32 32 31 35 30 5A 33 822150Z3


Inquiry returning: SUCCESS

Sending SCSI Inquiry, VPD = 83h

CDB:

0 1 2 3 4 5
0x00 12 01 83 00 60 00

Sending command with send_IO

Sense Data Buffer:

0 1 2 3 4 5 6 7
0x00 00 00 00 00 00 00 00 00


Sense Key: 0h = No Error
ASC & ASCQ: 0h - 0h = No Additional Sense Information
FRU: 0h = No Additional Information
Information: 0000000000000000h
Command Specific Information: 0000000000000000h
Command Time (us): 509.67

Data Buffer being returned:

0 1 2 3 4 5 6 7 8 9 A B C D E F
0x00 00 83 00 48 01 03 00 08 50 00 C5 00 A1 81 F3 38 ...H....P......8
0x10 61 93 00 08 50 00 C5 00 A1 81 F3 39 61 94 00 04 a...P......9a...
0x20 00 00 00 01 61 A3 00 08 50 00 C5 00 A1 81 F3 38 ....a...P......8
0x30 03 28 00 18 6E 61 61 2E 35 30 30 30 43 35 30 30 .(..naa.5000C500
0x40 41 31 38 31 46 33 33 38 00 00 00 00 20 20 20 20 A181F338....
0x50 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20


Inquiry returning: SUCCESS

Sending SCSI Inquiry, VPD = B1h

CDB:

0 1 2 3 4 5
0x00 12 01 B1 00 40 00

Sending command with send_IO

Sense Data Buffer:

0 1 2 3 4 5 6 7
0x00 00 00 00 00 00 00 00 00


Sense Key: 0h = No Error
ASC & ASCQ: 0h - 0h = No Additional Sense Information
FRU: 0h = No Additional Information
Information: 0000000000000000h
Command Specific Information: 0000000000000000h
Command Time (us): 492.68

Data Buffer being returned:

0 1 2 3 4 5 6 7 8 9 A B C D E F
0x00 00 B1 00 3C 00 01 00 53 01 00 00 00 00 00 00 00 ...<...S........
0x10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0x20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0x30 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................


Inquiry returning: SUCCESS

Sending SCSI Read Capacity 10 command

CDB:

0 1 2 3 4 5 6 7 8 9
0x00 25 00 00 00 00 00 00 00 00 00

Sending command with send_IO

Sense Data Buffer:

0 1 2 3 4 5 6 7
0x00 00 00 00 00 00 00 00 00


Sense Key: 0h = No Error
ASC & ASCQ: 0h - 0h = No Additional Sense Information
FRU: 0h = No Additional Information
Information: 0000000000000000h
Command Specific Information: 0000000000000000h
Command Time (us): 492.94

Data Buffer being returned:

0 1 2 3 4 5 6 7
0x00 FF FF FF FF 00 00 02 10 ........


Read Capacity 10 returning: SUCCESS

Sending SCSI Read Capacity 16 command

CDB:

0 1 2 3 4 5 6 7 8 9 A B C D E F
0x00 9E 10 00 00 00 00 00 00 00 00 00 00 00 20 00 00

Sending command with send_IO

Sense Data Buffer:

0 1 2 3 4 5 6 7
0x00 00 00 00 00 00 00 00 00


Sense Key: 0h = No Error
ASC & ASCQ: 0h - 0h = No Additional Sense Information
FRU: 0h = No Additional Information
Information: 0000000000000000h
Command Specific Information: 0000000000000000h
Command Time (us): 486.88

Data Buffer being returned:

0 1 2 3 4 5 6 7 8 9 A B C D E F
0x00 00 00 00 03 63 25 67 77 00 00 02 10 00 03 C0 00 ....c%gw........
0x10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................


Read Capacity 16 returning: SUCCESS


/dev/sg3 - IBM-SSGSSHU7P6 - HLM047370000822150Z3 - SCSI
Format Unit
Requesting SCSI Supported Op Codes

CDB:

0 1 2 3 4 5 6 7 8 9 A B
0x00 A3 0C 01 04 00 00 00 00 00 0A 00 00

Sending command with send_IO

Sense Data Buffer:

0 1 2 3 4 5 6 7
0x00 00 00 00 00 00 00 00 00


Sense Key: 0h = No Error
ASC & ASCQ: 0h - 0h = No Additional Sense Information
FRU: 0h = No Additional Information
Information: 0000000000000000h
Command Specific Information: 0000000000000000h
Command Time (us): 493.68

Data Buffer being returned:

0 1 2 3 4 5 6 7 8 9
0x00 00 03 00 06 04 FF C0 FF FF 00 ..........


Supported Op Codes returning: SUCCESS

Sending SCSI Mode Sense 10, page 0x00

CDB:

0 1 2 3 4 5 6 7 8 9
0x00 5A 10 00 00 00 00 00 00 18 00

Sending command with send_IO

Sense Data Buffer:

0 1 2 3 4 5 6 7
0x00 00 00 00 00 00 00 00 00


Sense Key: 0h = No Error
ASC & ASCQ: 0h - 0h = No Additional Sense Information
FRU: 0h = No Additional Information
Information: 0000000000000000h
Command Specific Information: 0000000000000000h
Command Time (us): 913.09

Data Buffer being returned:

0 1 2 3 4 5 6 7 8 9 A B C D E F
0x00 00 28 00 10 01 00 00 10 00 00 00 03 63 25 67 78 .(..........c%gx
0x10 00 00 00 00 00 00 02 10 ........


Mode Sense 10 returning: SUCCESS

Sending SCSI Mode Select 10

CDB:

0 1 2 3 4 5 6 7 8 9
0x00 55 01 00 00 00 00 00 00 18 00

Data Buffer being sent:

0 1 2 3 4 5 6 7 8 9 A B C D E F
0x00 00 28 00 10 01 00 00 10 FF FF FF FF FF FF FF FF .(..............
0x10 00 00 00 00 00 00 02 00 ........


Sending command with send_IO

Sense Data Buffer:

0 1 2 3 4 5 6 7 8 9 A B C D E F
0x00 72 05 26 00 00 00 00 1C 02 06 00 00 8F 00 15 00
0x10 03 02 00 11 80 0E 00 00 05 26 00 11 FF FF FF FF
0x20 FF FF 00 00


Sense Key: 5h = Illegal Request
ASC & ASCQ: 26h - 0h = Invalid Field In Parameter List
FRU: 11h = Vendor Specific
Information: 0000000000000000h
Command Specific Information: 0000000000000000h
Sense Key Specific Information:
Invalid field in Parameter byte 21 bit 7
Command Time (ms): 1.19

Mode Select 10 returning: FAILURE

Format Unit Failed!

Can I flash back it to the OEM (seagate) firmware? When I put the serial number in Seagate's fimware finder it shows me that it's an IBM branded Nytro 3331 SSD and no firmware available. I find an OEM Nytro 3331 model's serial number, and I got fw for the SSD. But I'm not sure that it could be working or not :/

FunFact I got specs (and it shows that it has 512 sector...) for my SSD by serial in Seagate's website:

Product Brand Seagate
Model Number XS7680SE70014
Part Number (PN) 2LZ216-039
Marketing Name NYTRO 3331
Family NYTRO 3331
Interface SAS
Encryption Type SED BASE
Capacity 7680 GB
Form Factor 2.5S
Product Type DRIVE SS
Market Segment Flash
Sub-market Segment SSD
Application Segment Enterprise SSD
Performance
Interface Transfer Rate 12
Access Time .1
Physical
Sector Size 512
Height 15MM
Weight .1653 kg
Zero G Sensor N
 
Last edited:

Whaaat

Active Member
Jan 31, 2020
142
39
28
Bad, drive requires vendor specific fields to be filled with only IBM knows what. Try to format using Iprutils, I've nowhere to test it, but if you can make it work in linux with your HBA, it will do whatever required to a drive loaded with IBM firmware
 

daniel.kovacs

New Member
Feb 28, 2021
6
0
1
Bad, drive requires vendor specific fields to be filled with only IBM knows what. Try to format using Iprutils, I've nowhere to test it, but if you can make it work in linux with your HBA, it will do whatever required to a drive loaded with IBM firmware
Thank for the correction! :) I've just cloned the iprutils git repo. After the build I can run it without any errors, but cant find any controllers/disks :( Do I need to make some extra steps to get it work? I tried with LSI SAS2008 and LSI 3108 also
 

daniel.kovacs

New Member
Feb 28, 2021
6
0
1
Thank for the correction! :) I've just cloned the iprutils git repo. After the build I can run it without any errors, but cant find any controllers/disks :( Do I need to make some extra steps to get it work? I tried with LSI SAS2008 and LSI 3108 also
Not the ~170 USD makes me sad, what I paid for the 8TB drive. The fact that I can't use a very cheap 8TB SSD :( Moreover it has only two hours and a few MB(!!) TBW... So it's actualy unused...

As for the firmware flashing I saw the somebody flash back OEM (seagate) firmware for HP sas drives (HDD). Whats the difference in my case? I think the vendor specific fields need to be filled every time. Am I wrong?
 

Whaaat

Active Member
Jan 31, 2020
142
39
28
As for the firmware flashing I saw the somebody flash back OEM (seagate) firmware for HP sas drives (HDD). Whats the difference in my case?
The difference is that IBM hdds are not locked for reformatting from 520bps, so you wouldn't need to update firmware. SSD is a different story and you can find firmware download port is locked as well, but it worth trying anyway
 

daniel.kovacs

New Member
Feb 28, 2021
6
0
1
The difference is that IBM hdds are not locked for reformatting from 520bps, so you wouldn't need to update firmware. SSD is a different story and you can find firmware download port is locked as well, but it worth trying anyway
If the IBM SSDs locked for formatting, we are wasting time for the reformatting with sg_format, seachest, etc... :(
Am I wrong if I say I have two expensive beer coaster? :(

My last chance is to get a server with power processor and reformat them from AIX. I've already have AIX iso but to find a server seems to be a difficult task for me :/