Samsung Magician Software Does Not Recognize Samsung SSD 830

Posted on 2012-04-12
Last Modified: 2016-11-23
I recently purchased a Samsung 830 SSD drive to breath some new life into a Dell Dimension 8400 running Windows XP. On the bright side, the drive works great.  I cloned my existing C drive (the original Western Digital hard drive) using a USB-SATA adapter, plugged the new drive into the SATA port where the prior drive was plugged in, and everything ran fine.  I then installed the software which comes with the drive, known as Samsung Magician.  It promises to maintain the performance of the drive over time in light of the fact that Windows XP does not have any capabilities with regard to using TRIM or garbage collection.  Neither concept is one I fully understand, other than they seem to be important issues in the SSD world and without them the drive is doomed to get slower and slower.

Much to my surprise, the Samsung software indicates it cannot find the Samung 830 SSD, which it chooses to refer to as a "Promise 1+0 JBOD SCSI Disk Device." Maybe not a surprise, as that is how my Windows XP device manager sees it. (Actually, that is how Windows XP device manager sees the old Western Digital hard drive as well.)

I thought I could trick the software by moving the SSD to a USB port, but then Samsung Magician refuses to even acknowledge it as a drive of any kind. I called Samsung support. I was informed that Samsung Magician won't recognize any SSD drive using a RAID interface or on a USB port. My operating system does seem to think I am using a RAID interface for the drives, although in reality I have never set up any RAID system for my drives (the system originally shipped with only one drive, which makes RAID not a possibility anyway to my understanding.)

The system BIOS, on the other hand, can correctly identify the drive as a Samsung 830 SSD, and also admits that both the new and old drives are  both "Non-RAID disks." I can't even disable RAID on them in the BIOS, because it insists they are not RAID devices to begin with, so you can't turn off something which is not on to begin with apparently.

Is there any strategy for getting the Samsung software to recognize it's own drive? I tried third party software to see if it would work, Solid State Doctor, and Solid State Life. Neither can see the SSD as an SSD when it is hooked up to a SATA port.  Solid State Doctor will see the drive as an SSD when it is hooked up to a USB port, so the first light of any kind in this process. Not sure I can see trying to permanently run my operating system off a USB port though, or periodically removing the drive from inside the computer so that I can hook it up to a USB and manually issue TRIM commands to it.

Any thoughts would be appreciated.
Question by:bapetersen
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions

Accepted Solution

asher-is-me earned 500 total points
ID: 37841010
Have you updated your motherboard's BIOS?  It's possible that Windows doesn't understand what's going on because your motherboard reports the SSD incorrectly.

For the Dell Dimension 8400, version A09 is the latest BIOS and is available here.

You may also want to install the Intel Application Accelerator, application and driver.  Sometimes, this helps.

Finally, update the chipset driver and any other system specific drivers you can find.

Dell's driver website:
LVL 47

Expert Comment

ID: 37841026
When you bridge a SATA device behind a USB chip you are changing the device from a SATA disk to a SCSI drive.  Also you kill performance unless this is USB 3.0. This protocol conversion affects all management software.  For example, a SCSI device has a 16-char product name, 8 char vendor name.  A SATA disk has a 40-character combined vendor/product ID.

So how can the software possibly covert 40 chars into 24 chars?  The software can't recognize the HDD because of the protocol conversion.  Sorry, you need to hook it up to a SATA controller if you want it to work.

Author Closing Comment

ID: 37845287
I like the theory that the BIOS needs updating.  I am running the Dell Dimension 8400 A01 BIOS at this point, and probably not designed in 2004 to run an SSD drive. Have always been afraid of updating the BIOS, but I am going to study the precautions that need to be taken and bite the bullet and do it. Thanks for giving me the push to do it.

Featured Post

Database Solutions Engineer FAQs

In this series, we will discuss common questions received as a database Solutions Engineer at Percona. In this role, we speak with a wide array of MySQL and MongoDB users responsible for both extremely large and complex environments to smaller single-server environments.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Employees depend heavily on their PCs, and new threats like ransomware make it even more critical to protect their important data.
No single Antivirus application (despite claims by manufacturers) will catch or protect you from all Virus / Malware or Spyware threats. That doesn't stop you from further protecting yourself however - and this article is to show you how.
This video Micro Tutorial explains how to clone a hard drive using a commercial software product for Windows systems called Casper from Future Systems Solutions (FSS). Cloning makes an exact, complete copy of one hard disk drive (HDD) onto another d…
The viewer will learn how to successfully create a multiboot device using the SARDU utility on Windows 7. Start the SARDU utility: Change the image directory to wherever you store your ISOs, this will prevent you from having 2 copies of an ISO wit…

627 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question