IBM 1.8" 400 GB SAS SSD for $50 OBO + Shipping

Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.
D

dontwanna

Member
Dec 22, 2016
90
20
8
Will these work in a regular desktop/server, or are they formatted with some weird size (like 520B or smth)?
 
D

dontwanna

Member
Dec 22, 2016
90
20
8
But how do you format Sata drives? I've bought a couple of Samsung EMC MZ3S9200XACP-000C3 drives, and I've no idea how to format them to 512B. The only guide I've found describes how to use sg_format, but it only works for sas drives apparently and didn't work for those sata Samsung drives from EMC. So I've still got those 2 laying around doing nothing, and too scared to buy any more sata drives.. :)
 
N

nthu9280

Well-Known Member
Feb 3, 2016
1,628
498
83
San Antonio, TX
@dontwanna lookup hdparm and fdisk for linux. Drive manufacturer may have tools for different OSes. For ex: Intel has SSD Tool Box as well as Data Center SSD Tool. If the drive has custom FW it may get tricky.
 
  • Like
Reactions: dontwanna
J

jinto36

New Member
Sep 11, 2018
5
1
3
(longtime lurker, first time poster)

I picked up one of these since I haven't ever had issues with getting OEM drives to work, but I realize the SSDs might be different territory. Through a microSATA adapter the drive is detected in Windows, but tools are definitely having a hard time with it- Disk Management locks up, CrystalDiskInfo doesn't launch, and Minitool is threadlocked trying to format it. It shows up as TX21B10400GECIBM so it definitely looks like custom firmware and I can't find any info on use of this model/series outside of the IBM server context.

I can try Linux, but before booting up a different system, I wanted to check if anyone else picked these up and had any success in getting them to work outside of an IBM server. Thanks!
 
D

dontwanna

Member
Dec 22, 2016
90
20
8
jinto36 said:
I can try Linux, but before booting up a different system, I wanted to check if anyone else picked these up and had any success in getting them to work outside of an IBM server. Thanks!
Click to expand...
It's probably not 512B. :( I also picked up two of these, but still waiting for the shipping (overseas). We're probably screwed, :D if it's not 512B then it's likely to be the same thing as I've had with those Samsung EMC sata drives.
 
F

fpm1703

New Member
Jun 29, 2013
6
9
3
dontwanna said:
But how do you format Sata drives? I've bought a couple of Samsung EMC MZ3S9200XACP-000C3 drives, and I've no idea how to format them to 512B. The only guide I've found describes how to use sg_format, but it only works for sas drives apparently and didn't work for those sata Samsung drives from EMC. So I've still got those 2 laying around doing nothing, and too scared to buy any more sata drives.. :)
Click to expand...
They're SAS, not SATA, drives. I connected mine to an Dell H200 (LSI Logic IT firmware) on a Fedora 27 Linux system and determined that the drive was formatted with 528 byte sectors. I then formatted the drive for 512 byte sectors with:

sg_format --format --size=512 --six /dev/sg0
​
The format operation completed in roughly 2 minutes and the drive now has 512 byte sectors.:)
 
  • Like
Reactions: dontwanna and warlockedyou
F

fpm1703

New Member
Jun 29, 2013
6
9
3
dontwanna said:
Wait, are we talking about the IBM drives from the first post, or the Samsung drives I mentioned before? These IBM drives have "SATA" written on them: IBM DS8800 Series 400GB Flash SSD SATA Drive 98Y4524 98Y4317 | eBay Or is it some kind of adapter (left half of the picture) and the actual drives (right half) are SAS?
Click to expand...
I'm talking about the IBM 400GB flash drive assembly. This consists of a SAS to SATA bridge which connects to a 400GB SATA SSD. After reformatting the drive for 512 byte sectors via the SAS bridge, I separated the SATA SSD from the bridge and now have a 1.8" 400GB SATA drive with 512 byte sectors.

Here's the smartctl -x of the SSD with the SAS to SATA bridge in place (after reformatting to 512 bytes/sector):
Code: 
smartctl 6.5 2016-05-07 r4318 [x86_64-linux-4.17.19-100.fc27.x86_64] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Vendor:               IBM
Product:              V2-TX21B10400G
Revision:             0TS8
User Capacity:        400,088,457,216 bytes [400 GB]
Logical block size:   512 bytes
Rotation Rate:        Solid State Device
Logical Unit id:      0x50011731000c1694
Serial number:        F0403MZH
Device type:          disk
Transport protocol:   SAS (SPL-3)
Local Time is:        Fri Sep 14 20:55:51 2018 PDT
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

Current Drive Temperature:     54 C
Drive Trip Temperature:        65 C

Manufactured in week 37 of year 2013
Specified cycle count over device lifetime:  0
Accumulated start-stop cycles:  0
Read defect list: asked for grown list but didn't get it
Vendor (Seagate) cache information
  Blocks sent to initiator = 0
  Blocks sent to initiator = 0
  Blocks sent to initiator = 0
  Blocks sent to initiator = 0
  Blocks sent to initiator = 0
  Blocks sent to initiator = 0
  Blocks sent to initiator = 0
  Blocks sent to initiator = 0
  Blocks sent to initiator = 0
  Blocks sent to initiator = 0
  Blocks sent to initiator = 0
  Blocks sent to initiator = 0
  Blocks sent to initiator = 0
  Blocks sent to initiator = 0
  Blocks sent to initiator = 0
  Blocks sent to initiator = 0
  Blocks sent to initiator = 0
  Blocks sent to initiator = 0
  Blocks sent to initiator = 0
  Blocks sent to initiator = 0
  Blocks sent to initiator = 0
  Blocks sent to initiator = 0
  Blocks sent to initiator = 0
  Blocks sent to initiator = 0
  Blocks sent to initiator = 0
  Blocks sent to initiator = 0
  Blocks sent to initiator = 0
  Blocks sent to initiator = 0
  Blocks sent to initiator = 0
  Blocks sent to initiator = 0

Vendor (Seagate/Hitachi) factory information
  number of hours powered up = 25309.82
  number of minutes until next internal SMART test = 39

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       54         0         0          0          2.850           0
write:         0        0         0         0          0          1.325           0

Non-medium error count:        3

No self-tests have been logged

Background scan results log
  Status: no scans active
    Accumulated power on time, hours:minutes 416:39 [24999 minutes]
    Number of background scans performed: 0,  scan progress: 0.00%
    Number of background medium scans performed: 0

Protocol Specific port log page for SAS SSP
relative target port id = 2
  generation code = 0
  number of phys = 1
  phy identifier = 0
    attached device type: no device attached
    attached reason: unknown
    reason: unknown
    negotiated logical link rate: phy enabled; 3 Gbps
    attached initiator port: ssp=0 stp=0 smp=0
    attached target port: ssp=0 stp=0 smp=0
    SAS address = 0x50011731000c1695
    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
relative target port id = 0
  generation code = 0
  number of phys = 1
  phy identifier = 1
    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 = 0x50011731000c1696
    attached SAS address = 0x590b11c037252c00
    attached phy identifier = 7
    Invalid DWORD count = 4
    Running disparity error count = 4
    Loss of DWORD synchronization = 1
    Phy reset problem = 0
    Phy event descriptors:
     Invalid word count: 4
     Running disparity error count: 4
     Loss of dword synchronization count: 1
     Phy reset problem count: 0
Here's the smartctl -x of the SATA SSD without the SAS bridge (also after reformatting to 512 bytes/sector):
Code: 
smartctl 6.5 2016-05-07 r4318 [x86_64-linux-4.17.19-100.fc27.x86_64] (local build)

Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     SandForce Driven SSDs
Device Model:     TX21B10400GECIBM    98Y4317  98Y4317IBM
Serial Number:    F0403MZH
LU WWN Device Id: 5 001173 1000c1694
Firmware Version: PRO6SWS8
User Capacity:    400,088,457,216 bytes [400 GB]
Sector Sizes:     512 bytes logical, 8192 bytes physical
Rotation Rate:    Solid State Device
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ACS-2 T13/2015-D revision 3
SATA Version is:  SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Fri Sep 14 22:05:55 2018 PDT
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
AAM feature is:   Unavailable
APM level is:     254 (maximum performance)
Rd look-ahead is: Enabled
Write cache is:   Enabled
ATA Security is:  Disabled, NOT FROZEN [SEC1]
Wt Cache Reorder: Unavailable

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x00)    Offline data collection activity
                    was never started.
                    Auto Offline Data Collection: Disabled.
Self-test execution status:      (   0)    The previous self-test routine completed
                    without error or no self-test has ever
                    been run.
Total time to complete Offline
data collection:         (    0) seconds.
Offline data collection
capabilities:              (0x7b) SMART execute Offline immediate.
                    Auto Offline data collection on/off support.
                    Suspend Offline collection upon new
                    command.
                    Offline surface scan supported.
                    Self-test supported.
                    Conveyance Self-test supported.
                    Selective Self-test supported.
SMART capabilities:            (0x0003)    Saves SMART data before entering
                    power-saving mode.
                    Supports SMART auto save timer.
Error logging capability:        (0x01)    Error logging supported.
                    General Purpose Logging supported.
Short self-test routine
recommended polling time:      (   1) minutes.
Extended self-test routine
recommended polling time:      (  48) minutes.
Conveyance self-test routine
recommended polling time:      (   2) minutes.
SCT capabilities:            (0x1021)    SCT Status supported.
                    SCT Data Table supported.

SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAGS    VALUE WORST THRESH FAIL RAW_VALUE
  1 Raw_Read_Error_Rate     PO--CK   120   120   050    -    0/0
  5 Retired_Block_Count     PO--CK   099   099   003    -    0
  9 Power_On_Hours_and_Msec -O--CK   000   000   000    -    24999h+29m+36.750s
 12 Power_Cycle_Count       -O--CK   100   100   000    -    62
 13 Soft_Read_Error_Rate    -O--CK   120   120   000    -    1079/0
 32 Unknown_Attribute       ------   100   000   000    -    2459
 33 Unknown_Attribute       ------   100   000   000    -    1000
100 Gigabytes_Erased        ------   000   000   000    -    1255776256
161 Unknown_Attribute       ------   000   000   000    -    134395
162 Unknown_SandForce_Attr  ------   000   000   000    -    1175844531
170 Reserve_Block_Count     POSR-K+  000   000   000    -    69888
171 Program_Fail_Count      -O-R--   000   000   000    -    0
172 Erase_Fail_Count        -O--CK   000   000   000    -    0
174 Unexpect_Power_Loss_Ct  ----CK   000   000   000    -    66
177 Wear_Range_Delta        ------   000   000   000    -    0
184 IO_Error_Detect_Code_Ct ------   100   100   090    -    0
187 Reported_Uncorrect      --SRC-   100   100   000    -    0
190 Airflow_Temperature_Cel ------   060   045   029    -    40 (Min/Max 21/55)
194 Temperature_Celsius     -O---K   040   055   000    -    40 (Min/Max 21/55)
195 ECC_Uncorr_Error_Count  --SRC-   100   100   000    -    0/0
196 Reallocated_Event_Count PO--CK   100   100   003    -    0
198 Uncorrectable_Sector_Ct ----C-   120   120   000    -    0/0
199 SATA_CRC_Error_Count    --S---   200   200   000    -    0
230 Life_Curve_Status       PO--C-   100   100   000    -    100
231 SSD_Life_Left           PO--C-   092   092   010    -    30064771073
232 Available_Reservd_Space -O--CK   000   000   000    -    136
233 SandForce_Internal      -O--CK   000   000   000    -    1175844531
234 SandForce_Internal      -O--CK   000   000   000    -    1324574208
241 Lifetime_Writes_GiB     ------   000   000   000    -    1324574208
242 Lifetime_Reads_GiB      ------   000   000   000    -    7145422336
                            ||||||_ K auto-keep
                            |||||__ C event count
                            ||||___ R error rate
                            |||____ S speed/performance
                            ||_____ O updated online
                            |______ P prefailure warning

General Purpose Log Directory Version 1
SMART           Log Directory Version 1 [multi-sector log support]
Address    Access  R/W   Size  Description
0x00       GPL,SL  R/O      1  Log Directory
0x03       GPL     R/O     16  Ext. Comprehensive SMART error log
0x04       GPL,SL  R/O      1  Device Statistics log
0x07       GPL     R/O      1  Extended self-test log
0x09           SL  R/W      1  Selective self-test log
0x10       GPL     R/O      1  SATA NCQ Queued Error log
0x11       GPL,SL  R/O      1  SATA Phy Event Counters log
0x80-0x9f  GPL,SL  R/W     16  Host vendor specific log
0xa8       GPL,SL  VS      16  Device vendor specific log
0xb0       GPL,SL  VS       1  Device vendor specific log
0xb1       GPL,SL  VS      16  Device vendor specific log
0xb7       GPL,SL  VS      16  Device vendor specific log
0xd0       GPL     VS   65535  Device vendor specific log
0xd0       SL      VS     255  Device vendor specific log
0xe0       GPL,SL  R/W      1  SCT Command/Status
0xe1       GPL,SL  R/W      1  SCT Data Transfer

SMART Extended Comprehensive Error Log Version: 1 (16 sectors)
No Errors Logged

SMART Extended Self-test Log Version: 1 (1 sectors)
No self-tests have been logged.  [To run self-tests, use: smartctl -t]

SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

SCT Status Version:                  3
SCT Version (vendor specific):       0 (0x0000)
SCT Support Level:                   1
Device State:                        Active (0)
Current Temperature:                    40 Celsius
Power Cycle Min/Max Temperature:     21/55 Celsius
Lifetime    Min/Max Temperature:     21/55 Celsius
Under/Over Temperature Limit Count:   0/0
Vendor specific:
00 00 00 00 a7 61 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

SCT Temperature History Version:     2
Temperature Sampling Period:         1 minute
Temperature Logging Interval:        10 minutes
Min/Max recommended Temperature:      ?/ ? Celsius
Min/Max Temperature Limit:            ?/ ? Celsius
Temperature History Size (Index):    478 (7)

Index    Estimated Time   Temperature Celsius
   8    2018-09-11 14:30     ?  -
 ...    ..(469 skipped).    ..  -
   0    2018-09-14 20:50     ?  -
   1    2018-09-14 21:00    53  **********************************
   2    2018-09-14 21:10    54  ***********************************
   3    2018-09-14 21:20    54  ***********************************
   4    2018-09-14 21:30    54  ***********************************
   5    2018-09-14 21:40    51  ********************************
   6    2018-09-14 21:50    40  *********************
   7    2018-09-14 22:00     ?  -

SCT Error Recovery Control command not supported

Device Statistics (GP Log 0x04)
Page  Offset Size        Value Flags Description
0x01  =====  =               =  ===  == General Statistics (rev 2) ==
0x01  0x008  4              64  ---  Lifetime Power-On Resets
0x01  0x010  4           24999  ---  Power-on Hours
0x01  0x018  6    169545525767  ---  Logical Sectors Written
0x01  0x028  6    914614063112  ---  Logical Sectors Read
0x04  =====  =               =  ===  == General Errors Statistics (rev 1) ==
0x04  0x008  4               0  ---  Number of Reported Uncorrectable Errors
0x04  0x010  4              95  ---  Resets Between Cmd Acceptance and Completion
0x06  =====  =               =  ===  == Transport Statistics (rev 1) ==
0x06  0x008  4              95  ---  Number of Hardware Resets
0x06  0x010  4              41  ---  Number of ASR Events
0x06  0x018  4               0  ---  Number of Interface CRC Errors
0x07  =====  =               =  ===  == Solid State Device Statistics (rev 1) ==
0x07  0x008  1             255  ---  Percentage Used Endurance Indicator
                                |||_ C monitored condition met
                                ||__ D supports DSN
                                |___ N normalized value

SATA Phy Event Counters (GP Log 0x11)
ID      Size     Value  Description
0x0001  2            0  Command failed due to ICRC error
0x0003  2            0  R_ERR response for device-to-host data FIS
0x0004  2            0  R_ERR response for host-to-device data FIS
0x0006  2            0  R_ERR response for device-to-host non-data FIS
0x0007  2            0  R_ERR response for host-to-device non-data FIS
0x0008  2            0  Device-to-host non-data FIS retries
0x0009  2            0  Transition from drive PhyRdy to drive PhyNRdy
0x000a  2            1  Device-to-host register FISes sent due to a COMRESET
0x000f  2            0  R_ERR response for host-to-device data FIS, CRC
0x0010  2            0  R_ERR response for host-to-device data FIS, non-CRC
0x0012  2            0  R_ERR response for host-to-device non-data FIS, CRC
0x0013  2            0  R_ERR response for host-to-device non-data FIS, non-CRC
0x0002  2            0  R_ERR response for data FIS
0x0005  2            0  R_ERR response for non-data FIS
0x000b  2            0  CRC errors within host-to-device FIS
0x000d  2            0  Non-CRC errors within host-to-device FIS
 
  • Like
Reactions: dontwanna
D

dontwanna

Member
Dec 22, 2016
90
20
8
Thanks! I wonder whether it means that I could also reformat my Samsung sata drives by connecting them with a similar SATA to SAS bridge and using sg_utils.
 
J

jinto36

New Member
Sep 11, 2018
5
1
3
Just to add to this, I haven't been successful in attempts to update the firmware- the Sandisk scli utility reports the drive as "compatible" with the firmware I'm trying to load, but then reports "unknown error" with the Linux version of scli (CloudSpeed Ultra SSD Drive Firmware). So it looks like I'll have to try the SAS bridge approach.

What's a (very) cheap SAS board that will work for this? My only SAS-supporting device right now is an HP SmartArray P410 in an active server, and I imagine that is not going to work for this purpose due to the RAID abstraction?
 
D

dontwanna

Member
Dec 22, 2016
90
20
8
jinto36 said:
What's a (very) cheap SAS board that will work for this?
Click to expand...
I don't have much experience with SAS, and someone might suggest a more affordable option, but the cheapest (yet still not useless for something like a small file server with sata/sas mechanical drives) SAS controller I know of is Dell H200. They usually go for $20-25 on ebay.
 
S

Samir

Post Liker and Deal Hunter Extraordinaire!
Jul 21, 2017
3,306
1,481
113
49
HSV and SFO
jinto36 said:
What's a (very) cheap SAS board that will work for this? My only SAS-supporting device right now is an HP SmartArray P410 in an active server, and I imagine that is not going to work for this purpose due to the RAID abstraction?
Click to expand...
I don't see any issue in you attaching it to the p410 unless it physically won't connect. Generally I've found sas devices play quite well together in the older stuff I have, including a p400 in older dl360/380s and perc 5i in a 2950.
 
J

jinto36

New Member
Sep 11, 2018
5
1
3
Samir said:
I don't see any issue in you attaching it to the p410 unless it physically won't connect. Generally I've found sas devices play quite well together in the older stuff I have, including a p400 in older dl360/380s and perc 5i in a 2950.
Click to expand...
I would try the p410 but the system its in has all the bays full and so I'd have to break an array to test it...
 
S

Samir

Post Liker and Deal Hunter Extraordinaire!
Jul 21, 2017
3,306
1,481
113
49
HSV and SFO
jinto36 said:
I would try the p410 but the system its in has all the bays full and so I'd have to break an array to test it...
Click to expand...
I've had to do that before and just removed all the drives and let the controller clear the configuration. Be sure to know exactly which drives go in which slots. I cannot stress this part enough.

Then remove one of the drives and test your drive. After your test is done, you should be able to put all the drives back in and then import the configuration if the controller doesn't automatically recognize it again.
 
S

sovking

Member
Jun 2, 2011
84
9
8
So, these are SATA drives with SAS bridge.
I've a LSI 3008 and a SAS3 Supermicro backplane... there is any way to connect these drive to the backplane via the attached sata bridge to format them ? I will need some adapter or converter to connect them ??
 
S

Samir

Post Liker and Deal Hunter Extraordinaire!
Jul 21, 2017
3,306
1,481
113
49
HSV and SFO
sovking said:
So, these are SATA drives with SAS bridge.
I've a LSI 3008 and a SAS3 Supermicro backplane... there is any way to connect these drive to the backplane via the attached sata bridge to format them ? I will need some adapter or converter to connect them ??
Click to expand...
I don't have one of these, but looking at the picture (the original picture, not the ebay bait-n-switch 'similar item'), it looks like it would connect to a regular sata connector which means it should work with any sas controller as well.
 
You must log in or register to reply here.
Top Bottom