Samsung SM963 960GB M.2 to 1GB issue!

[Kev]

So I have been running windows server core (headless) on ESXI 6.5 with a Samsung SM963 960GB M.2 NVME (MZ1LW960HMJP | Samsung Enterprise SSD | Samsug Semiconductor) passed-through to each instance. The main motivation was to try out starwind virtual san with two nodes. I shut down one of the servers and when I brought it back up, I found out starwind did not properly present the iscsi share and upon further investigation, the storage for the starwind image that is on the SM963 was not present.

Since I just formatted the NVME as one large NTFS drive, I passed the drive to a windows 10 installation and found the same thing. The SM963 drive is now detected as a 1GB drive.

DISKPART> list disk

  Disk ###  Status         Size     Free     Dyn  Gpt
  --------  -------------  -------  -------  ---  ---
  Disk 0    Online           30 GB      0 B
  Disk 1    Online         1024 MB  1024 MB

If I don't enable passthrough and let ESXI detect the drive, ESXI detects the drive as 1GB as well!

Has anyone experienced this and how can I fix??

 

[rune-san]

I've seen this happen with various SSDs before, including some Intel ones in some Flash Storage Platforms. I'm afraid in all cases I've seen it happen it means the SSD is done for. It's going to need RMA'd or replaced. Secure Erase hasn't fixed it in any of the attempts I've seen.

 

[Kev]

That's what I was afraid How's samsung's warranty for enterprise SSDs?

 

[Aestr]

That's what I was afraid How's Samsung's warranty for enterprise SSDs?

That depends. Is it a retail drive or an OEM that you bought used. If OEM it's unlikely you'll get much support. If you bought it from eBay how long ago was the purchase? You might be able to work something out with the seller.

 

[Miki]

Hi, have you collected any additional insights about this problem or solutions now?

I talked to Philipp who says the 1GB thing (in my case correlated with the ERRORMOD firmware error status) means the SSD's firmware has run into problems and is now giving you 1GB of its own RAM as disk space, and I understand next step is going to physical data recovery like detaching NAND chips to do manual data extraction. My experience of this 1GB issue has been on a 3.84TB PM983 M.2 specifically model MZ1LB3T8HMLA-00007.

 

[istqian]

I would love to share an experience for repairing this faulty state SSD of PM953.
Recently I bought two cheap PM953 SSDs from ebay, and it is NOT WORKING and FOR PARTS only!
I am not seeing that sentences when I bought them.
when they arrive today, of course, as expected, not working!

But they can recorgize by OS, which is FreeBSD 12.0. Below is the output of nvmecontrol

root@nec:~ # nvmecontrol devlist
 nvme0: SAMSUNG MZ1LV960HCJH-000MU
    nvme0ns1 (1024MB)
 nvme1: SAMSUNG MZ1LV960HCJH-000MU
    nvme1ns1 (1024MB)

capacity shown as 1024MB. and the FIRMWARE version is shown ERRORMOD

As I google and found nothing can solve this problem. at first I am thinking the firmware is corrputed by something during firmware update. so I can update the firmware to solve the problem. The problem is I cannot find firmware anywhere since these are OEM SSDs.

After I output nvmecontrol identify nvme0

Controller Capabilities/Features
================================
Vendor ID:                   144d
Subsystem Vendor ID:         144d
Serial Number:               S2C2NA0H945644
Model Number:                SAMSUNG MZ1LV960HCJH-000MU
Firmware Version:            ERRORMOD
Recommended Arb Burst:       2
IEEE OUI Identifier:         00 25 38
Multi-Path I/O Capabilities: Not Supported
Max Data Transfer Size:      Unlimited
Controller ID:               0x01
Version:                     0.0.0

Admin Command Set Attributes
============================
Security Send/Receive:       Not Supported
Format NVM:                  Supported
Firmware Activate/Download:  Supported
Namespace Managment:         Supported
Device Self-test:            Not Supported
Directives:                  Not Supported
NVMe-MI Send/Receive:        Not Supported
Virtualization Management:   Not Supported
Doorbell Buffer Config       Not Supported
Abort Command Limit:         8
Async Event Request Limit:   4
Number of Firmware Slots:    3
Firmware Slot 1 Read-Only:   Yes
Per-Namespace SMART Log:     Yes
Error Log Page Entries:      64
Number of Power States:      1

NVM Command Set Attributes
==========================
Submission Queue Entry Size
  Max:                       64
  Min:                       64
Completion Queue Entry Size
  Max:                       16
  Min:                       16
Number of Namespaces:        1
Compare Command:             Supported
Write Uncorrectable Command: Supported
Dataset Management Command:  Supported
Write Zeroes Command:        Supported
Save Features:               Supported
Reservations:                Not Supported
Timestamp feature:           Supported
Fused Operation Support:     Not Supported
Format NVM Attributes:       Crypto Erase, Per-NS Erase, Per-NS Format
Volatile Write Cache:        Not Present

Namespace Drive Attributes
==========================
NVM total cap:               0
NVM unallocated cap:         0

and query the firmware slots.

root@nec:~ # nvmecontrol logpage -p 3 nvme0
Firmware Slot Log
=================
Slot 1: [  Active] BXV76M8Q
Slot 2: Empty
Slot 3: Empty

As above output, I found firmware slot has 3 slots. and slot 1 is readonly and can show the correct firmware version! slot 2 and 3 are empty. that will lead to firmware corrupt is impossible since
this slot is readonly, normal person cannot override it without special vendor tool.

When I type nvmecontrol, the output shows their is a subcommand format. I try it for the normal SSD, it didn't work and output error message.
while using this command for the faulty SSD, it did works! did't return any error message.
after I type nvme reset nvme0 for a warm reset. from dmesg, I found nvd0 is detaching.

OK, something happens I dont know it is good or not, but better than nothing.
I reboot, and the SSD is shows normal!!!!
nvmecontrol devlist shows normal capacity of 960GB.
And I using zpool create a new pool on it, it works! I can write data on it without error!!!

Since I have another faulty SSD, I process same commands. it works too.

That it is! you can have a try when you have a nvme SSD with ERRORMOD firmware version!
I don't know Windows or Linux has equal command or not. You better try FreeBSD 12.0 first.

 

[hmartin]

I don't know Windows or Linux has equal command or not. You better try FreeBSD 12.0 first.

istqian, thank you so much for this tip. I had a drive I thought was dead, but this procedure has rescued it.

I can confirm this process works on Linux using the nvme utility.

# smartctl --all /dev/nvme0n1 
smartctl 6.6 2017-11-05 r4594 [x86_64-linux-4.19.41-0-vanilla] (local build)
Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Number:                       SAMSUNG MZ1LV960HCJH-000MU
Serial Number:                      *MASKED*
Firmware Version:                   ERRORMOD
PCI Vendor/Subsystem ID:            0x144d
IEEE OUI Identifier:                0x382500
Controller ID:                      1
Number of Namespaces:               1
Namespace 1 Size/Capacity:          1,073,741,824 [1.07 GB]
Namespace 1 Formatted LBA Size:     512
Namespace 1 IEEE EUI-64:            002538 2482220652
Local Time is:                      Wed Dec 25 11:03:51 2019 CET
Firmware Updates (0x07):            3 Slots, Slot 1 R/O
Optional Admin Commands (0x000e):   Format Frmw_DL NS_Mngmt
Optional NVM Commands (0x005f):     Comp Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat Timestmp

Supported Power States
St Op     Max   Active     Idle   RL RT WL WT  Ent_Lat  Ex_Lat
 0 +     8.00W       -        -    0  0  0  0       30      30

Supported LBA Sizes (NSID 0x1)
Id Fmt  Data  Metadt  Rel_Perf
 0 +     512       0         0

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

SMART/Health Information (NVMe Log 0x02, NSID 0x1)
Critical Warning:                   0x00
Temperature:                        34 Celsius
Available Spare:                    0%
Available Spare Threshold:          10%
Percentage Used:                    255%
Data Units Read:                    ~21267649834034552833065489312776192
Data Units Written:                 ~156502406691541351771447126512369664
Host Read Commands:                 ~21045056226890630090352230400
Host Write Commands:                ~65493139554225515155447061425598496768
Controller Busy Time:               ~97221540568695410225449100057667174400
Power Cycles:                       ~332787601315152639685718100849914281984
Power On Hours:                     ~129002868980418140308175384297408036864
Unsafe Shutdowns:                   ~188288398581393670862864483318702800896
Media and Data Integrity Errors:    ~2824609491042946229920590003095732224
Error Information Log Entries:      ~1334420929254122986588868227952017408
Warning  Comp. Temperature Time:    2117904159
Critical Comp. Temperature Time:    1640465925
Temperature Sensor 1:               -209 Celsius
Temperature Sensor 2:               -272 Celsius
Temperature Sensor 5:               7919 Celsius
Temperature Sensor 6:               -241 Celsius
Temperature Sensor 7:               -269 Celsius
Temperature Sensor 8:               16115 Celsius

Error Information (NVMe Log 0x01, max 64 entries)
Num   ErrCount  SQId   CmdId  Status  PELoc          LBA  NSID    VS
  0 276070544846     0  0x0012  0x4004  0x000            0     0     -

Run the format command:

# nvme format /dev/nvme0n1
Success formatting namespace:1

Power cycle the host (reboot is insufficient).

The drive appears to be alive again!

# smartctl --all /dev/nvme0n1
smartctl 6.6 2017-11-05 r4594 [x86_64-linux-4.19.41-0-vanilla] (local build)
Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Number:                       SAMSUNG MZ1LV960HCJH-000MU
Serial Number:                      *MASKED*
Firmware Version:                   BXV76M8Q
PCI Vendor/Subsystem ID:            0x144d
IEEE OUI Identifier:                0x382500
Controller ID:                      1
Number of Namespaces:               1
Namespace 1 Size/Capacity:          960,197,124,096 [960 GB]
Namespace 1 Utilization:            0
Namespace 1 Formatted LBA Size:     512
Namespace 1 IEEE EUI-64:            002538 2482220652
Local Time is:                      Wed Dec 25 11:15:31 2019 CET
Firmware Updates (0x07):            3 Slots, Slot 1 R/O
Optional Admin Commands (0x000e):   Format Frmw_DL NS_Mngmt
Optional NVM Commands (0x005f):     Comp Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat Timestmp

Supported Power States
St Op     Max   Active     Idle   RL RT WL WT  Ent_Lat  Ex_Lat
 0 +     8.00W       -        -    0  0  0  0       30      30

Supported LBA Sizes (NSID 0x1)
Id Fmt  Data  Metadt  Rel_Perf
 0 +     512       0         0

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

SMART/Health Information (NVMe Log 0x02, NSID 0x1)
Critical Warning:                   0x00
Temperature:                        38 Celsius
Available Spare:                    100%
Available Spare Threshold:          10%
Percentage Used:                    0%
Data Units Read:                    7 [3.58 MB]
Data Units Written:                 0
Host Read Commands:                 102
Host Write Commands:                0
Controller Busy Time:               0
Power Cycles:                       1
Power On Hours:                     0
Unsafe Shutdowns:                   1
Media and Data Integrity Errors:    0
Error Information Log Entries:      2
Warning  Comp. Temperature Time:    60
Critical Comp. Temperature Time:    41

Error Information (NVMe Log 0x01, max 64 entries)
Num   ErrCount  SQId   CmdId  Status  PELoc          LBA  NSID    VS
  0          2     0  0x001c  0x4004  0x000            0     0     -
  1          1     0  0x0015  0x4004  0x000            0     0     -

 

[alexherreraz]

istqian, thank you so much for this tip. I had a drive I thought was dead, but this procedure has rescued it.

I can confirm this process works on Linux using the nvme utility.

# smartctl --all /dev/nvme0n1
smartctl 6.6 2017-11-05 r4594 [x86_64-linux-4.19.41-0-vanilla] (local build)
Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Number:                       SAMSUNG MZ1LV960HCJH-000MU
Serial Number:                      *MASKED*
Firmware Version:                   ERRORMOD
PCI Vendor/Subsystem ID:            0x144d
IEEE OUI Identifier:                0x382500
Controller ID:                      1
Number of Namespaces:               1
Namespace 1 Size/Capacity:          1,073,741,824 [1.07 GB]
Namespace 1 Formatted LBA Size:     512
Namespace 1 IEEE EUI-64:            002538 2482220652
Local Time is:                      Wed Dec 25 11:03:51 2019 CET
Firmware Updates (0x07):            3 Slots, Slot 1 R/O
Optional Admin Commands (0x000e):   Format Frmw_DL NS_Mngmt
Optional NVM Commands (0x005f):     Comp Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat Timestmp

Supported Power States
St Op     Max   Active     Idle   RL RT WL WT  Ent_Lat  Ex_Lat
0 +     8.00W       -        -    0  0  0  0       30      30

Supported LBA Sizes (NSID 0x1)
Id Fmt  Data  Metadt  Rel_Perf
0 +     512       0         0

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

SMART/Health Information (NVMe Log 0x02, NSID 0x1)
Critical Warning:                   0x00
Temperature:                        34 Celsius
Available Spare:                    0%
Available Spare Threshold:          10%
Percentage Used:                    255%
Data Units Read:                    ~21267649834034552833065489312776192
Data Units Written:                 ~156502406691541351771447126512369664
Host Read Commands:                 ~21045056226890630090352230400
Host Write Commands:                ~65493139554225515155447061425598496768
Controller Busy Time:               ~97221540568695410225449100057667174400
Power Cycles:                       ~332787601315152639685718100849914281984
Power On Hours:                     ~129002868980418140308175384297408036864
Unsafe Shutdowns:                   ~188288398581393670862864483318702800896
Media and Data Integrity Errors:    ~2824609491042946229920590003095732224
Error Information Log Entries:      ~1334420929254122986588868227952017408
Warning  Comp. Temperature Time:    2117904159
Critical Comp. Temperature Time:    1640465925
Temperature Sensor 1:               -209 Celsius
Temperature Sensor 2:               -272 Celsius
Temperature Sensor 5:               7919 Celsius
Temperature Sensor 6:               -241 Celsius
Temperature Sensor 7:               -269 Celsius
Temperature Sensor 8:               16115 Celsius

Error Information (NVMe Log 0x01, max 64 entries)
Num   ErrCount  SQId   CmdId  Status  PELoc          LBA  NSID    VS
  0 276070544846     0  0x0012  0x4004  0x000            0     0     -

Run the format command:

# nvme format /dev/nvme0n1
Success formatting namespace:1

Power cycle the host (reboot is insufficient).

The drive appears to be alive again!

# smartctl --all /dev/nvme0n1
smartctl 6.6 2017-11-05 r4594 [x86_64-linux-4.19.41-0-vanilla] (local build)
Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Number:                       SAMSUNG MZ1LV960HCJH-000MU
Serial Number:                      *MASKED*
Firmware Version:                   BXV76M8Q
PCI Vendor/Subsystem ID:            0x144d
IEEE OUI Identifier:                0x382500
Controller ID:                      1
Number of Namespaces:               1
Namespace 1 Size/Capacity:          960,197,124,096 [960 GB]
Namespace 1 Utilization:            0
Namespace 1 Formatted LBA Size:     512
Namespace 1 IEEE EUI-64:            002538 2482220652
Local Time is:                      Wed Dec 25 11:15:31 2019 CET
Firmware Updates (0x07):            3 Slots, Slot 1 R/O
Optional Admin Commands (0x000e):   Format Frmw_DL NS_Mngmt
Optional NVM Commands (0x005f):     Comp Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat Timestmp

Supported Power States
St Op     Max   Active     Idle   RL RT WL WT  Ent_Lat  Ex_Lat
0 +     8.00W       -        -    0  0  0  0       30      30

Supported LBA Sizes (NSID 0x1)
Id Fmt  Data  Metadt  Rel_Perf
0 +     512       0         0

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

SMART/Health Information (NVMe Log 0x02, NSID 0x1)
Critical Warning:                   0x00
Temperature:                        38 Celsius
Available Spare:                    100%
Available Spare Threshold:          10%
Percentage Used:                    0%
Data Units Read:                    7 [3.58 MB]
Data Units Written:                 0
Host Read Commands:                 102
Host Write Commands:                0
Controller Busy Time:               0
Power Cycles:                       1
Power On Hours:                     0
Unsafe Shutdowns:                   1
Media and Data Integrity Errors:    0
Error Information Log Entries:      2
Warning  Comp. Temperature Time:    60
Critical Comp. Temperature Time:    41

Error Information (NVMe Log 0x01, max 64 entries)
Num   ErrCount  SQId   CmdId  Status  PELoc          LBA  NSID    VS
  0          2     0  0x001c  0x4004  0x000            0     0     -
  1          1     0  0x0015  0x4004  0x000            0     0     -

Hi! Im a guy from México that Is suffering this stuff AND i havent manage to maje It work again! I dont know anything about Linux so i really need tour help!! Can you help me with this? I can Pay you ir you want to But PLEASE help me!

He're Is my email: alexherreraz@hotmail.com

I beg you, im desperate trying to fix this and i cant!

 

[alexherreraz]

I would love to share an experience for repairing this faulty state SSD of PM953.
Recently I bought two cheap PM953 SSDs from ebay, and it is NOT WORKING and FOR PARTS only!
I am not seeing that sentences when I bought them.
when they arrive today, of course, as expected, not working!

But they can recorgize by OS, which is FreeBSD 12.0. Below is the output of nvmecontrol

root@nec:~ # nvmecontrol devlist
nvme0: SAMSUNG MZ1LV960HCJH-000MU
    nvme0ns1 (1024MB)
nvme1: SAMSUNG MZ1LV960HCJH-000MU
    nvme1ns1 (1024MB)

capacity shown as 1024MB. and the FIRMWARE version is shown ERRORMOD

As I google and found nothing can solve this problem. at first I am thinking the firmware is corrputed by something during firmware update. so I can update the firmware to solve the problem. The problem is I cannot find firmware anywhere since these are OEM SSDs.

After I output nvmecontrol identify nvme0

Controller Capabilities/Features
================================
Vendor ID:                   144d
Subsystem Vendor ID:         144d
Serial Number:               S2C2NA0H945644
Model Number:                SAMSUNG MZ1LV960HCJH-000MU
Firmware Version:            ERRORMOD
Recommended Arb Burst:       2
IEEE OUI Identifier:         00 25 38
Multi-Path I/O Capabilities: Not Supported
Max Data Transfer Size:      Unlimited
Controller ID:               0x01
Version:                     0.0.0

Admin Command Set Attributes
============================
Security Send/Receive:       Not Supported
Format NVM:                  Supported
Firmware Activate/Download:  Supported
Namespace Managment:         Supported
Device Self-test:            Not Supported
Directives:                  Not Supported
NVMe-MI Send/Receive:        Not Supported
Virtualization Management:   Not Supported
Doorbell Buffer Config       Not Supported
Abort Command Limit:         8
Async Event Request Limit:   4
Number of Firmware Slots:    3
Firmware Slot 1 Read-Only:   Yes
Per-Namespace SMART Log:     Yes
Error Log Page Entries:      64
Number of Power States:      1

NVM Command Set Attributes
==========================
Submission Queue Entry Size
  Max:                       64
  Min:                       64
Completion Queue Entry Size
  Max:                       16
  Min:                       16
Number of Namespaces:        1
Compare Command:             Supported
Write Uncorrectable Command: Supported
Dataset Management Command:  Supported
Write Zeroes Command:        Supported
Save Features:               Supported
Reservations:                Not Supported
Timestamp feature:           Supported
Fused Operation Support:     Not Supported
Format NVM Attributes:       Crypto Erase, Per-NS Erase, Per-NS Format
Volatile Write Cache:        Not Present

Namespace Drive Attributes
==========================
NVM total cap:               0
NVM unallocated cap:         0

and query the firmware slots.

root@nec:~ # nvmecontrol logpage -p 3 nvme0
Firmware Slot Log
=================
Slot 1: [  Active] BXV76M8Q
Slot 2: Empty
Slot 3: Empty

As above output, I found firmware slot has 3 slots. and slot 1 is readonly and can show the correct firmware version! slot 2 and 3 are empty. that will lead to firmware corrupt is impossible since
this slot is readonly, normal person cannot override it without special vendor tool.

When I type nvmecontrol, the output shows their is a subcommand format. I try it for the normal SSD, it didn't work and output error message.
while using this command for the faulty SSD, it did works! did't return any error message.
after I type nvme reset nvme0 for a warm reset. from dmesg, I found nvd0 is detaching.

OK, something happens I dont know it is good or not, but better than nothing.
I reboot, and the SSD is shows normal!!!!
nvmecontrol devlist shows normal capacity of 960GB.
And I using zpool create a new pool on it, it works! I can write data on it without error!!!

Since I have another faulty SSD, I process same commands. it works too.

That it is! you can have a try when you have a nvme SSD with ERRORMOD firmware version!
I don't know Windows or Linux has equal command or not. You better try FreeBSD 12.0 first.

Hi! Im a guy from México that Is suffering this stuff AND i havent manage to maje It work again! I dont know anything about Linux so i really need tour help!! Can you help me with this? I can Pay you ir you want to But PLEASE help me!



He're Is my email: alexherreraz@hotmail.com



I beg you, im desperate trying to fix this and i cant!

 

[yelley]

Hello All,

Just my 2cents to this subject.
I've come across a similar situation on a PM863a Samsung SSD 3,8TB with a Firmware version 'ERRORMOD' and a size reported of 1GB.
I use a HP Z840 with LSI controller to attach the SSD.

The SSD could not be used and is not recognized by the standard tools form Samsung, like Magician v 6.21.

However, I could find an older version of this software, V2 and 32 bits, at:
Enterprise SSD Products | Download | Samsung V-NAND SSD

With this version you have the ability using the following flags in a command window run as Administrator:

c:\Users\admin\Downloads>Samsung_Magician_DC_Windows_32bit.exe -L
================================================================================================
Samsung(R) SSD Magician DC Version 2.0
Copyright (C) 2015 SAMSUNG Electronics Co. Ltd. All rights reserved.
================================================================================================
----------------------------------------------------------------------------------------------------
| Disk | Model | Serial | Firmware | Capacity | Drive | Total Bytes |
| Number | | Number | | | Health | Written |
----------------------------------------------------------------------------------------------------
| 2 |SAMSUNG MZ7LM3T8HMLP-000AZ |Serialnr |ERRORMOD | 0 GB | POOR | 0.00 TB |
----------------------------------------------------------------------------------------------------

c:\Users\admin\Downloads>.\Samsung_Magician_DC_Windows_64bit.exe -V
================================================================================================
Samsung(R) SSD Magician DC Version 2.0
Copyright (C) 2015 SAMSUNG Electronics Co. Ltd. All rights reserved.
================================================================================================
------------------------------------------------------------------------------------------------
Usage:

magician -d [diskindex] -V [ --vendor-utility ] [parameter-list]
Example:
magician --disk 1 --vendor-utility --FAlog-dump [or]
magician -d 1 -V -fa
magician --disk 1 --vendor-utility --PLP-log [or]
magician -d 1 -V -p
magician --disk 1 --vendor-utility --Escape [or]
magician -d 1 -V -e
magician --disk 1 --vendor-utility --DSLR [or]
magician -d 1 -V -dslr

-d [ --disk ] Disk-Number of the disk to execute Vendor Utility command
-fa [ --FAlog-dump ] Enables the user to extract the log data from a coreview block of the
SSD
-p [ --PLP-log ] Enables the user to extract the PLP log data from a coreview block of the
SSD
-e [ --Escape ] Attempts to escape the device from the ERROR MODE state
-dslr [ --DSLR ] Extracts DSLR from the SSD

------------------------------------------------------------------------------------------------

c:\Users\admin\Downloads>Samsung_Magician_DC_Windows_32bit.exe -d 2 -V -e
================================================================================================
Samsung(R) SSD Magician DC Version 2.0
Copyright (C) 2015 SAMSUNG Electronics Co. Ltd. All rights reserved.
================================================================================================
------------------------------------------------------------------------------------------------
Disk Number: 2 | Model Name: SAMSUNG MZ7LM3T8HMLP-000AZ | Firmware Version: ERRORMOD
------------------------------------------------------------------------------------------------
Successfully issued ERROR MODE escape command to the device.
It may take up to 1 minute for the device to be ready.
------------------------------------------------------------------------------------------------

after approx. 1 minute:

c:\Users\admin\Downloads>Samsung_Magician_DC_Windows_32bit.exe -L
================================================================================================
Samsung(R) SSD Magician DC Version 2.0
Copyright (C) 2015 SAMSUNG Electronics Co. Ltd. All rights reserved.
================================================================================================
----------------------------------------------------------------------------------------------------
| Disk | Model | Serial | Firmware | Capacity | Drive | Total Bytes |
| Number | | Number | | | Health | Written |
----------------------------------------------------------------------------------------------------
| 2:0:1 |SAMSUNG MZ7LM3T8HMLP-000AZ |Serialnr |GXT51W3Q | 3576 GB | GOOD | 0.00 TB |
----------------------------------------------------------------------------------------------------

And the SSD is usable again!


Remark: Later versions of Magician CLI command does not seem to have those -e flag anymore.
Hope this helps for others in the same situation

 

[nahueef11]

Hello All,

Just my 2cents to this subject.
I've come across a similar situation on a PM863a Samsung SSD 3,8TB with a Firmware version 'ERRORMOD' and a size reported of 1GB.
I use a HP Z840 with LSI controller to attach the SSD.

The SSD could not be used and is not recognized by the standard tools form Samsung, like Magician v 6.21.

However, I could find an older version of this software, V2 and 32 bits, at:
Enterprise SSD Products | Download | Samsung V-NAND SSD

With this version you have the ability using the following flags in a command window run as Administrator:

c:\Users\admin\Downloads>Samsung_Magician_DC_Windows_32bit.exe -L
================================================================================================
Samsung(R) SSD Magician DC Version 2.0
Copyright (C) 2015 SAMSUNG Electronics Co. Ltd. All rights reserved.
================================================================================================
----------------------------------------------------------------------------------------------------
| Disk | Model | Serial | Firmware | Capacity | Drive | Total Bytes |
| Number | | Number | | | Health | Written |
----------------------------------------------------------------------------------------------------
| 2 |SAMSUNG MZ7LM3T8HMLP-000AZ |Serialnr |ERRORMOD | 0 GB | POOR | 0.00 TB |
----------------------------------------------------------------------------------------------------

c:\Users\admin\Downloads>.\Samsung_Magician_DC_Windows_64bit.exe -V
================================================================================================
Samsung(R) SSD Magician DC Version 2.0
Copyright (C) 2015 SAMSUNG Electronics Co. Ltd. All rights reserved.
================================================================================================
------------------------------------------------------------------------------------------------
Usage:

magician -d [diskindex] -V [ --vendor-utility ] [parameter-list]
Example:
magician --disk 1 --vendor-utility --FAlog-dump [or]
magician -d 1 -V -fa
magician --disk 1 --vendor-utility --PLP-log [or]
magician -d 1 -V -p
magician --disk 1 --vendor-utility --Escape [or]
magician -d 1 -V -e
magician --disk 1 --vendor-utility --DSLR [or]
magician -d 1 -V -dslr

-d [ --disk ] Disk-Number of the disk to execute Vendor Utility command
-fa [ --FAlog-dump ] Enables the user to extract the log data from a coreview block of the
SSD
-p [ --PLP-log ] Enables the user to extract the PLP log data from a coreview block of the
SSD
-e [ --Escape ] Attempts to escape the device from the ERROR MODE state
-dslr [ --DSLR ] Extracts DSLR from the SSD

------------------------------------------------------------------------------------------------

c:\Users\admin\Downloads>Samsung_Magician_DC_Windows_32bit.exe -d 2 -V -e
================================================================================================
Samsung(R) SSD Magician DC Version 2.0
Copyright (C) 2015 SAMSUNG Electronics Co. Ltd. All rights reserved.
================================================================================================
------------------------------------------------------------------------------------------------
Disk Number: 2 | Model Name: SAMSUNG MZ7LM3T8HMLP-000AZ | Firmware Version: ERRORMOD
------------------------------------------------------------------------------------------------
Successfully issued ERROR MODE escape command to the device.
It may take up to 1 minute for the device to be ready.
------------------------------------------------------------------------------------------------

after approx. 1 minute:

c:\Users\admin\Downloads>Samsung_Magician_DC_Windows_32bit.exe -L
================================================================================================
Samsung(R) SSD Magician DC Version 2.0
Copyright (C) 2015 SAMSUNG Electronics Co. Ltd. All rights reserved.
================================================================================================
----------------------------------------------------------------------------------------------------
| Disk | Model | Serial | Firmware | Capacity | Drive | Total Bytes |
| Number | | Number | | | Health | Written |
----------------------------------------------------------------------------------------------------
| 2:0:1 |SAMSUNG MZ7LM3T8HMLP-000AZ |Serialnr |GXT51W3Q | 3576 GB | GOOD | 0.00 TB |
----------------------------------------------------------------------------------------------------

And the SSD is usable again!


Remark: Later versions of Magician CLI command does not seem to have those -e flag anymore.
Hope this helps for others in the same situation

hi! can you help me whith my SSD?. I have the same problem and cant find the old version of the Magician.
My mail is nahuee.f@hotmail.com.

 

[netswitch]

Hello

Just a bump up of the tread with one other occurence on the issue :
Drive : Samsung MZ-1LB9600 960Go ( PM963)
OS : Almalinux / CentOS 8.4
Recognised without issue on Asrockrack X470
Recognised showing only 1GB Asrockrack X570

Ran the command :
# nvme format /dev/nvme0n1

Cold rebooted

and drive reported 960Gb on the X570.

Beware that it wipes all data / partitions on the drive.

 

[alexherreraz]

Hello

Just a bump up of the tread with one other occurence on the issue :
Drive : Samsung MZ-1LB9600 960Go ( PM963)
OS : Almalinux / CentOS 8.4
Recognised without issue on Asrockrack X470
Recognised showing only 1GB Asrockrack X570

Ran the command :
# nvme format /dev/nvme0n1

Cold rebooted

and drive reported 960Gb on the X570.

Beware that it wipes all data / partitions on the drive.

Thanks! can i try it via Oracle VirtualBox?