Package Details: samsung_magician-consumer-ssd 1.0-1

Git Clone URL: (read-only, click to copy)
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: 21
Popularity: 0.002764
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! For 983 ZET, 983 DCT, 883 DCT and 860 DCT (and potentially other models) you may try this package:

Latest Comments

« First ‹ Previous 1 2 3 Next › Last »

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! :)

mrlamud commented on 2016-12-10 22:12

oberon2007, singlot and all,

I apology that I can't verify the source files given since it's been such a long time I keep these 2 files.

Please feel free to use some other trustworthy sources if available.

oberson2007, I'm very sorry if my files cause you in difficult time.

oberon2007 commented on 2016-12-10 21:24

@siglot, I have done some more research and found another source on this site:
It states "A less recent version – no longer mentioned on or linked to from the main page, but still available on a separate page – doesn't have the same limitation. (I've mirrored it in case Samsung removes page or file.)"
Well Samsung has infact meanwhile removed the old file, but the mirror mentioned here is still working:
The binary in the linked mirror is also 4MB and the checksums matches with mrlamud's file. Of course this is still not 100% proof that the file is legit but I'd say it's quite reassuring, don't you think? Maybe there was an update at one point from your version to this one here?

oberon2007 commented on 2016-12-10 18:45

Will do. Also see the original discussion about v1.0 here:

siglot commented on 2016-12-10 18:35

@oberon2007 can you ask him about this difference and origin of his package? Putting your name under bin file which you know nothing about isn't great idea.

oberon2007 commented on 2016-12-10 17:53

@siglot, I don't know. kindly provides of the old binary.