Package Details: samsung_magician-consumer-ssd 1.0-1

Git Clone URL: (read-only)
Package Base: samsung_magician-consumer-ssd
Description: CLI tool for Samsung Consumer SSDs including 470, 750, 830, 840, 850, 950 and 960 series
Upstream URL:
Licenses: custom
Conflicts: samsung_magician
Submitter: oberon2007
Maintainer: oberon2007
Last Packager: oberon2007
Votes: 19
Popularity: 0.296324
First Submitted: 2016-12-10 16:44
Last Updated: 2017-11-27 10:47

Pinned Comments

oberon2007 commented on 2016-12-10 16:48

Samsung has stopped providing a Linux version of the 'Magician' for Consumer SSDs. The newer v2.0 only works with Enterprise PM863 and SM863 Series. So this is the older version v1.0. It should still be working with most Consumer SSDs but be aware that this is not the latest updated version of this software!

Latest Comments

1 2 Next › Last »

FrederickZh commented on 2018-04-11 07:13

Does not work for me...

$ sudo nvme list Node SN Model Namespace Usage Format FW Rev


/dev/nvme0n1 S2GMNXXXXXXXXXX Samsung SSD 950 PRO 512GB 1 229.79 GB / 512.11 GB 512 B + 0 B 2B0QBXX7 $ sudo magician --list ================================================================================================ Samsung(R) SSD Magician DC Version 1.0 Copyright (c) 2014 Samsung Corporation ================================================================================================


| Disk | Model | Serial | Firmware | Capacity | Drive | Total Bytes | | Number | | Number | | | Health | Written |


No Samsung SSD found!

I guess the only workaround now is to have a copy of Windows on your machine :(

oberon2007 commented on 2017-11-27 10:50

@steadybright , I got confused. The situation is as described in the pinned comment. Samsung has discontinued Linux support for consumer models and there are no updates. So I'm afraid we cannot do much there.

steadybright commented on 2017-11-27 01:21

This version still fails to recognize the Samsung 840. (See details in my 2017-07-12 comment below. The results are identical to the earlier version of this package)

oberon2007 commented on 2017-11-25 23:58

Updated to v2.0
Please try again with the new version @Pietro_Pizzi !

Pietro_Pizzi commented on 2017-11-25 22:01

My two 850 EVO and one 960 EVO don't get recognized.

steadybright commented on 2017-07-12 14:25


$ sudo magician --list

results in

No Samsung SSD found!


$ sudo hdparm -I /dev/sda

shows that I have a Samsung 840 installed:

Model Number: Samsung SSD 840 Series
Serial Number: S14[............]
Firmware Revision: DXT09B0Q

Please help!

Thank you,


agusl88 commented on 2017-07-04 23:30

May be will be good idea to remove the 850 from the list of supported disks because it doesn't recognize it.

siglot commented on 2016-12-11 12:02

# Maintainer: Berhard Landauer <>

pkgdesc="CLI tool for Samsung Consumer SSDs including 470, 750, 830, 840, 850, 950 and 960 series"
arch=('x86_64' 'i686')
depends=('jsoncpp' 'hdparm')
md5sums=('b7e88ecac15adddaa5bfae3f679ee2ca' '138596cfbe00f6b9ead1829b300f5e83')
source=("" "LICENSE")

package() {

if [[ $CARCH = i686 ]]; then
cd ${srcdir}/samsung_magician_dc-v1.0_rtm_p2/32bin/

if [[ $CARCH = x86_64 ]]; then
cd ${srcdir}/samsung_magician_dc-v1.0_rtm_p2/64bin/

install -Dm 755 magician ${pkgdir}/usr/bin/magician
install -D -m644 ${srcdir}/LICENSE "${pkgdir}/usr/share/licenses/${_pkgname}/LICENSE"

siglot commented on 2016-12-11 00:56

Ok, I investigated further and found that samsung still hosts the original file:

It has same md5sum (b7e88ecac15adddaa5bfae3f679ee2ca) as in original pkgbuild

The sum of archive differs from one from but inside bins are the same. It means that original pkgbuild ( could be still legit with little link fix. You can consider switching back to it as long as samsung won't mess it again.

After makepkg the binary is trimmed from 4,0 mb to 2,8 mb (could be my system specific) so mystery resolved.

Example of working PKGBUILD above.

oberon2007 commented on 2016-12-10 22:17

Not to worry @mrlamud. The checksum match, so I consider it safe to use them. I think it's great that you still had the files in the first place! :)