One fix for "S.M.A.R.T. not supported by drive" In Acronis Drive Monitor

By Bret A. Bennett 10/10/2013


 

Environment:

Asus F1A75-V PRO motherboard (SATA III / SATA 3 capable).

Seagate ST3250410AS hard drive, 250GB (SATA II / SATA 2 capable).
 

Scenario:

I previously had this hard drive on a Gigabyte Intel motherboard (SATA II capable) and Acronis Drive Monitor (aka ADM) saw it’s S.M.A.R.T capability as expected. I then upgraded the PC, using a Asus F1A75-V PRO AMD motherboard. Since then, ADM reports, "S.M.A.R.T not supported by drive".
 

Unsuccessful Corrective Actions Tried:

  • I made sure the SATA setup in the BIOS was set to AHCI and not RAID. It was AHCI. No joy here.
  • I tried a different ST3250410AS and also received, "S.M.A.R.T not supported by drive". No joy here. So I put the original drive back in place.
  • I moved the SATA drive's data cable from the SATA4 port to the SATA0 port. No joy here either.
     

Successful Corrective Action:

I noticed in Windows 7’s Device Manager, under Disk Drives, that the drive was being reported as ST3250410AS SCSI disk drive. Seeing "SCSI" there, is not always surprising, because some motherboard/controller/disk combinations do report SATA disks on that branch as "SCSI".

Still in Device Manager, I look on down the list for "IDE ATA/ATAPI controllers". I’m surprised that branch is not there. Btw, this motherboard has no legacy PATA controller port.

So I look further down the list and see the familiar "Storage Controllers" branch. That’s where we typically see our SCSI disk controller(s) enumerated. To my surprise, I see both "AMD AHCI Compatible RAID Controller" and "AMD RAID Console".

  • First action is to right click on "AMD RAID Console", and select to Uninstall. When prompted, select to delete the drivers from the PC.
  • Second action is to right click on "AMD AHCI Compatible RAID Controller" and select to Uninstall. Btw, here there is no prompt to delete the drivers from the PC.
  • Third action is to restart the PC (as prompted by the driver uninstall). After logging back in to Windows 7, I see that it’s detecting the drive once again as a SCSI disk. I click on the "Installing Devices" flag at the bottom of the screen to open that up, and I see that it’s trying to find "AMD RAID Console" on the Windows Update site. I hit the Cancel option at the end of that "AMD RAID Console" line. I get a warning that this may cause problems (ignore that warning). It finally completes the driver(s) install and prompts for another restart.
  • After logging in to Windows 7 again, I see it’s detecting new devices once more. I click on the driver installation flag pop-up down near the Windows System Tray (ie. where the time & date are usually displayed), and to my joy, I see it’s installing SATA0 through SATA5 ports. I’m prompted for a restart again.

After logging into Windows 7 this third time, I see that the ADM notification icon in the System Tray has its happy little green checkmark (with no yellow error check mark). I open ADM and there’s the disk with all the S.M.A.R.T. info as desired.

Next I open up Device Manager. As desired, under the Disk Drives branch I see:
"ST3250410AS ATA device" (no more "SCSI" there!).

There’s now an "IDE ATA/ATAPI controllers" branch. In there I see "ATA Channel 0" through "ATA Channel 5", and Standard "AHCI 1.0 Serial ATA Controller". Btw, that’s Microsoft’s native SATA controller driver and it works perfectly well.

Under the Storage Controllers branch, the "AMD AHCI Compatible RAID Controller" and "AMD RAID Console" leafs are gone. Only "Asmedia 106x SATA Controller" remains (that’s for the one blue SATA III port on the motherboard and the SATA III port on the back I/O panel).
 

Conclusion:

I was able to get Acronis Drive Monitor’s S.M.A.R.T. reporting functioning properly by uninstalling/removing the AMD SCSI driver components. My guess is that these drivers were automatically installed when the new Asus F1A75-V PRO motherboard was installed. This is one case where simply putting in the motherboard vendor’s CD and running "Install/Setup" was probably the reason an undesired driver was installed.

Imho, with Windows Visa forward, it’s better to just let the Windows OS installation find the drivers on the Windows installation media and/or Windows Update site. Then later, point the yellow unknown devices in Device Manager to the motherboard vendor’s installation media to find the vendor specific devices.

 


 

Did my work help you solve a problem, save time or save money?
Please show your appreciation with a PayPal donation you consider reasonable.


Copyright © 2013 by Bret A. BENNETT. All rights reserved.
Reprints by permission only: Please contact bret@bretabennett.com .
(Reprints for personal use do not require permission)
(Comments and corrections are welcome)

 


Legal Notice
Last modified: 10/14/2018 12:23 PM -0400
Copyright © 1997-2018 BRET A. BENNETT, All rights reserved.
Lost in space? Click here to return to our doorway at www.bretabennett.com
Click this link to contact us with questions or comments about this web site.