Changing block size IBM branded Micron S650DC-800 SSD

[Whaaat]

Sense Key Specific Information:
Invalid field in Parameter byte 21 bit 7
Command Time (ms): 1.19

If the IBM SSDs locked for formatting, we are wasting time for the reformatting with sg_format, seachest, etc...

Drive is waiting for valid value in byte 21 bit 7 of format request. In case of hdd this field can be left empty. If you have firmware file, try to update it with seachest and see how ssd will react.

 

[sephallen]

What sg_format will tell if you try to format the drive with current sector size first?

I have actually done this a few times, it appears to work and does not report any errors.

Try hitachi HUGO tool also, who knows maybe it will work.

My Google-fu must be weak as I can't find any reference to download this tool.

 

[Whaaat]

My Google-fu must be weak as I can't find any reference to download this tool.

HUGO

I have actually done this a few times, it appears to work and does not report any errors.

it is clear now that IBM has embedded some modification into firmware for changing block size. Firmware requires some additional fields into format request to be filled with correct values and there is no way to find them out without having at least an IBM HBA controller.

 

[sephallen]

it is clear now that IBM has embedded some modification into firmware for changing block size. Firmware requires some additional fields into format request to be filled with correct values and there is no way to find them out without having at least an IBM HBA controller.

Ah OK, I suppose HUGO won't help me here anyway!
It's a shame about the drive, but I will re-sell it on eBay (clearly stating the block size issue of course!).
I really appreciate all the advice from yourself and other members on the forum, it has been a fun ride and I have definitely learnt a thing or two - which at the end of the day is what it is all about.

 

[Thurbin]

This link might be something to try,

How to reformat 520 byte drives to 512 bytes (usually)

So a lot of cool hardware uses 520 byte sectors instead of 512 byte sectors (or 4* sector size in the case of SSDs). There is a lot of misinformation out there. Prettymuch anything since 2012 that supports 520 byte sectors will support 512 byte sectors if you know the right magic commands...

forum.level1techs.com

Michael

 

[ioan]

Sector size must be changed on this drives with iprconfig utility (which is open source). When IBM drive are in IBM proprietary raid array - it have sector size 528 bytes. When it converted to JBOD mode - it must change sector size to 512 bytes. iprconfig works only with IBM branded SAS adapters. iprconfig changes sector size with MODE SELECT ioctl. I've modified source code to work with generic LSI HBA, but no success - it accepts only 528 bytes value - when i'm specifying 512 bytes - ioctl returns error (S650DC ibm-branded ssd).

 

[kdub]

Sector size must be changed on this drives with iprconfig utility (which is open source). When IBM drive are in IBM proprietary raid array - it have sector size 528 bytes. When it converted to JBOD mode - it must change sector size to 512 bytes. iprconfig works only with IBM branded SAS adapters. iprconfig changes sector size with MODE SELECT ioctl. I've modified source code to work with generic LSI HBA, but no success - it accepts only 528 bytes value - when i'm specifying 512 bytes - ioctl returns error (S650DC ibm-branded ssd).

So are you saying you were actually able to change block from 528 to 512 on these drives using iprconfig and an IBM adapter like the M5015?

 

[ioan]

So are you saying you were actually able to change block from 528 to 512 on these drives using iprconfig and an IBM adapter like the M5015?

i don't have ibm branded sas adapter
i wasn't able to change sector size using LSI HBA and some code ported from iprconfig utility.
according to IBM documentation when you are formatting SSD for JBOD, iprconfig will change sector size to 512/4096 bytes.
iprconfig works with linux (it's open sourced), but it supports only IBM-branded sas adapters.

 

[Whaaat]

So are you saying you were actually able to change block from 528 to 512 on these drives using iprconfig and an IBM adapter like the M5015?

M5015 doesn't support 520/528 bps drives. You would need a 57B5 or similar controller that has 520-byte virtual disk support.

 

[ioan]

M5015 doesn't support 520/528 bps drives. You would need a 57B5 or similar controller that has 520-byte virtual disk support.

iprconfig changes sector size with simple MODE SELECT request, which can be issued with any controller. I can't find out why MODE SELECT not working when i specify non-528 value. May be some other request must be sent previously to move drive out of raid array. I've decided to return drives to seller.

 

[gtcdma]

Hi! I've got a couple of IBM 00WV995 / ST800FM0203 SSDs with the same problem. Nothing seems to work for changing the sector size to 512.

 

[ioan]

Hi! I've got a couple of IBM 00WV995 / ST800FM0203 SSDs with the same problem. Nothing seems to work for changing the sector size to 512.

you can try buying iprconfig-compatible sas controller (list of supported controllers you can find in source code)
and then use iprconfig to convert them to jbod mode

 

[Whaaat]

I've got a couple of IBM 00WV995 / ST800FM0203 SSDs

What adapter or backplane are you using to get the connectivity?

 

[gtcdma]

What adapter or backplane are you using to get the connectivity?

I'm using "1.8 Micro SATA 16pin SSD to 2.5 SATA 22pin" adapters I found on Amazon (Amazon.com: Cablecc 1.8 Micro SATA 16pin SSD to 2.5 SATA 22pin 7+15 Hard Disk case Enclosure White 7mm Height: Computers & Accessories) in an HP DL380p Gen8 server with 420i controller switched to HBA mode.

I've successfully formatted a number of other HDDs and SSDs to 512e with this set up, these are the only ones that just won't accept the MODE SELECT command, as pointed out by the other users in this thread.

 

[gtcdma]

you can try buying iprconfig-compatible sas controller (list of supported controllers you can find in source code)
and then use iprconfig to convert them to jbod mode

Are you sure that it's going to work? I'm afraid that iprconfig may fail like the other tools.

 

[ioan]

Are you sure that it's going to work? I'm afraid that iprconfig may fail like the other tools.

this is single documented (by IBM) way to change block size in their drives
i don't know will it work on non-IBM computer with IBM-branded SAS adapter

 

[gtcdma]

this is single documented (by IBM) way to change block size in their drives
i don't know will it work on non-IBM computer with IBM-branded SAS adapter

I can't find the controller list in the source code (bjking1/iprutils). There are only some old PCI SCSI cards mentioned in the README. Do you know of any specific model?

 

[ioan]

IPR Linux device driver

Download IPR Linux device driver for free. This project is a development area for a Linux Device driver for IBM Power Linux RAID SCSI HBA's, including the ipr driver and iprutils packages.

sourceforge.net

here is latest iprutils
can't recommend anything - you need to google IBM documentation for SAS adapters, compatible with yours drives

 

[drace]

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 :/

Hi Daniel,

have you found anything useful? I have the same 3.8TB disk and still finding a way to solve this.
Actually an HP H240 is reporting the disk 520 bytes block size.

Best,
drace

 

[sand_storm]

I am also got a couple IBM branded Micron SSD( MTFDJAK800MBS-2AN ) with 528/b sector. And reformatted it in HP DL360e with P420 wihout any issues:

root@kubuntu:/home/kostya# smartctl -a /dev/sg1
smartctl 6.5 2016-01-24 r4214 [x86_64-linux-4.4.0-116-generic] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Vendor: IBM
Product: MTFDJAK800MBS
Revision: 5039
Compliance: SPC-4
User Capacity: 800,166,073,344 bytes [800 GB]
Logical block size: 528 bytes
LU is resource provisioned, LBPRZ=1
Rotation Rate: Solid State Device
Form Factor: 2.5 inches
Logical Unit id: 0x5000c500ad72bc1f
Serial number: ZAZ169390000822150Z3
Device type: disk
Transport protocol: SAS (SPL-3)
Local Time is: Mon Nov 15 19:05:52 2021 +04
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: 1%
Current Drive Temperature: 32 C
Drive Trip Temperature: 65 C

root@kubuntu:/home/kostya# sg_format --format --size=512 /dev/sg1 -v
IBM MTFDJAK800MBS 5039 peripheral_type: disk [0x0]
PROTECT=0
Unit serial number: ZAZ169390000822150Z3
LU name: 5000c500ad72bc1f
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

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

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

A FORMAT will commence in 5 seconds
ALL data on /dev/sg1 will be DESTROYED
Press control-C to abort
format cdb: 04 18 00 00 00 00

Format has started
FORMAT Complete
root@kubuntu:/home/kostya# smartctl -a /dev/sg1
smartctl 6.5 2016-01-24 r4214 [x86_64-linux-4.4.0-116-generic] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Vendor: IBM
Product: MTFDJAK800MBS
Revision: 5039
Compliance: SPC-4
User Capacity: 800,166,076,416 bytes [800 GB]
Logical block size: 512 bytes
LU is resource provisioned, LBPRZ=1
Rotation Rate: Solid State Device
Form Factor: 2.5 inches
Logical Unit id: 0x5000c500ad72bc1f
Serial number: ZAZ169390000822150Z3
Device type: disk
Transport protocol: SAS (SPL-3)
Local Time is: Mon Nov 15 19:08:49 2021 +04
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: 1%
Current Drive Temperature: 33 C
Drive Trip Temperature: 65 C

tested it in standalone and mirror mode - all seems to be ok