@zumoshi, fixed. Thanks for the report!

@andrej: Try this:

# magician --disk 2:c --nvme-get-log-pages --smart
# magician -d A -NG --smart

See manual for more examples. The disc detail feature may not be available on your device (pay attention to the Features on p. 13).

@MarsSeed: You don't need to comment on all my packages that should be -bin, I know. Please let me know if you're willing to help convert them. I've emailed you. You can stop spamming me.

@andrej: Well, obviously Samsung doesn't even support this tool. They haven't updated it years and don't care.

Quite surprisingly it does support WD SSDs, but not Samsung SSDs. Example:

# magician -L
================================================================================================
Samsung DC Toolkit Version 2.1.L.Q.0
Copyright (C) 2017 SAMSUNG Electronics Co. Ltd. All rights reserved.
================================================================================================
----------------------------------------------------------------------------------------------------------------------------------------
| Disk   | Path       | Model                   | Serial          | Firmware | Optionrom | Capacity | Drive  | Total Bytes | NVMe Driver |
| Number |            |                         | Number          |          | Version   |          | Health | Written     |             |
----------------------------------------------------------------------------------------------------------------------------------------
| 2      | /dev/sdc   | WDC  WDS400T1R0A-68A4W0 | 203572800209    | 411000WR | N/A       |  3726 GB | N/A    | 0.00 TB     | N/A         |
----------------------------------------------------------------------------------------------------------------------------------------
| 3      | /dev/sdd   | WDC  WDS400T1R0A-68A4W0 | 203572800290    | 411000WR | N/A       |  3726 GB | N/A    | 0.00 TB     | N/A         |
----------------------------------------------------------------------------------------------------------------------------------------
| 4      | /dev/sde   | WDC  WDS400T1R0A-68A4W0 | 203572800247    | 411000WR | N/A       |  3726 GB | N/A    | 0.00 TB     | N/A         |
----------------------------------------------------------------------------------------------------------------------------------------
| 5      | /dev/sdf   | WDC  WDS400T1R0A-68A4W0 | 2045BD800375    | 411000WR | N/A       |  3726 GB | N/A    | 0.00 TB     | N/A         |
----------------------------------------------------------------------------------------------------------------------------------------
| 6      | /dev/sdg   | WDC  WDS400T1R0A-68A4W0 | 2045BD800380    | 411000WR | N/A       |  3726 GB | N/A    | 0.00 TB     | N/A         |
----------------------------------------------------------------------------------------------------------------------------------------
| 7      | /dev/sdh   | WDC  WDS400T1R0A-68A4W0 | 2045A5800377    | 411000WR | N/A       |  3726 GB | N/A    | 0.00 TB     | N/A         |
----------------------------------------------------------------------------------------------------------------------------------------
| 8      | /dev/sdi   | WDC  WDS400T1R0A-68A4W0 | 203572800265    | 411000WR | N/A       |  3726 GB | N/A    | 0.00 TB     | N/A         |
----------------------------------------------------------------------------------------------------------------------------------------
| 9      | /dev/sdj   | WDC  WDS400T1R0A-68A4W0 | 2045BD800371    | 411000WR | N/A       |  3726 GB | N/A    | 0.00 TB     | N/A         |
----------------------------------------------------------------------------------------------------------------------------------------
| 2:c    | /dev/nvme2 | Samsung SSD 980 PRO 2TB | S69ENX0T719547K | 5B2QGXA7 | N/A       |  1863 GB | GOOD   |  0.00 TB    | Unknown     |
----------------------------------------------------------------------------------------------------------------------------------------

The problem is, as already noted by @yochananmarqos, in the bogus disk number. It is 2:c in my case. (No asterisk involved.)

Now interestingly enough, this works:

# magician -d 2:c -ID
================================================================================================
Samsung DC Toolkit Version 2.1.L.Q.0
Copyright (C) 2017 SAMSUNG Electronics Co. Ltd. All rights reserved.
================================================================================================

IDENTIFY data ouput: /usr/local/DCToolkit/VendorUtility/S69ENX0T719547K_Log_NVME_CONTROLLER_IDENTIFY.bin

IDENTIFY data ouput: /usr/local/DCToolkit/VendorUtility/S69ENX0T719547K_Log_NVME_NAMESPACE_IDENTIFY.bin

The output is:

# strings /usr/local/DCToolkit/VendorUtility/S69ENX0T719547K_Log_NVME_CONTROLLER_IDENTIFY.bin /usr/local/DCToolkit/VendorUtility/S69ENX0T719547K_Log_NVME_NAMESPACE_IDENTIFY.bin
S69ENX0T719547K     Samsung SSD 980 PRO 2TB                 5B2QGXA7
nqn.1994-11.com.samsung:nvme:980PRO:M.2:S69ENX0T719547K

Now that^ looks promising! Yes, 2:c means something.

However, using just -I will fail:

# magician -d 2:c -I
================================================================================================
Samsung DC Toolkit Version 2.1.L.Q.0
Copyright (C) 2017 SAMSUNG Electronics Co. Ltd. All rights reserved.
================================================================================================
------------------------------------------------------------------------------------------------
Usage:
  magician -d [diskindex] -I [ --info ]

Example:
  magician --disk 1 --info [or] magician -d 1 -I

Sub Options:
  -d [ --disk ] Disk-Number of the disk whose details has to be displayed.
------------------------------------------------------------------------------------------------

No luck there. So, why does -ID work, unlike -I, with the bogus 2:c disk “number”?

And why are WD SSDs on SATA supported (as in: -I works), but not Samsung SSDs on PCIe via Thunderbolt? Is it because of the Thunderbolt?

Also, the machine has 2 more PCIe SSDs from Seagate, but those don’t appear in -L at all, so one can’t easily tell if Thunderbolt (as opposed to a direct M.2 connection to the motherboard) is causing the 2:c weirdness; the M.2 Seagates are hidden.

Hi,

Please kindly fix the LICENSE location. Currently it's being put in the wrong directory:

/usr/share/licenses/LICENSE

@fedgyma: Same here:

================================================================================================
Samsung DC Toolkit Version 2.1.L.Q.0
Copyright (C) 2017 SAMSUNG Electronics Co. Ltd. All rights reserved.
================================================================================================
--------------------------------------------------------------------------------------------------------------------------------------------------
| Disk   | Path       | Model                        | Serial               | Firmware | Optionrom | Capacity | Drive  | Total Bytes | NVMe Driver |
| Number |            |                              | Number               |          | Version   |          | Health | Written     |             |
--------------------------------------------------------------------------------------------------------------------------------------------------
| *0:c   | /dev/nvme0 | Samsung SSD 970 EVO Plus 1TB | S59ANM0NB10302Y      | 2B2QEXM7 | N/A       |   931 GB | GOOD   |  0.00 TB    | Unknown     |
--------------------------------------------------------------------------------------------------------------------------------------------------

I own a Samsung SSD 970 EVO 250GB and on the output of the --list param, the Disk Number show up as *0:c. Can't manage to update firmware since its not a valid number.

The license is erroneously installed in /usr/share/licenses/ instead of /usr/share/licenses/samsung-ssd-dc-toolkit/ because the $_pkgname variable is not defined.