HDs connected via eSATA not detected; Storage Controllers absent

[yanagawa]

Hi. This is a longish one. I will try to be as informative and clear as possible.

Brief summary of problem: Hard drives connected externally via eSATA are not "seen" by Windows. There are no storage controllers in the device manager. This is the result of trying to install a hard disk controller that would allow monitoring of HDs connected by eSATA.

Long version:

I have been using software to monitor HD performance, temperature, errors, etc. This has worked for USB connected drives. I use Vantec Nexstar 3 enclosures and a Thermaltake BlacX Duet dock. These are standard WD Black and Blue drives, and Seagate Barracudas.

However, recently I started using eSATA connections with my external drives, and noticed that the software could not monitor them (no temp, SMART data, etc.). I contacted the developer for assistance.

He informed me that the controller — Marvell 61xx — was the issue. The current version does not provide HD status information. He directed me to replace it with a driver that I could download from his site. I attempted to install the driver via the Device Manager. I located the Storage Controllers section, found the Marvell 61xx controller, and tried to update by browsing to the proper driver file. This did not work: a dialog box told me that the best driver software for my device was already installed and up-to-date.

At this point he told me the alternate method would be to go to the Storage Controllers section, choose update, browse, and then "let me pick from a list of device drivers", and then choose the "standard dual channel PCI controller" driver, which is a generic Windows driver. The idea here, I believe, was that this would allow the software to monitor the drive, and also might be a workaround to eventually get the desired "better" driver installed.

After doing this and rebooting, the drive was detected and also recognized by the monitoring software. However it reported the drive as having 100% performance and 0% health, because the threshold value for Reallocated Sectors was reported incorrectly as 207, with the current value being 200. I reinstalled the monitor, and it seemed to report the disk as 100% for both, but with some odd threshold values.

I then ejected the drive (via the Windows Safely Remove utility on taskbar), and reconnected. The PC no longer saw the drive through eSATA, but did when I connected via USB. I rebooted again, and the computer did not detect any drives connected by eSATA. This continues to be the case.

I looked in the Device Manager, and realized that there is no longer a section for Storage Controllers. This continues to be so, even after hard and soft reboots and even in Safe Mode.

I have also tried scanning for hardware changes -- no dice, and just straight installing the driver that the developer suggested in the first place. All that did was make a folder called "Marvell" in the Program Files (x86) folder, and I have no idea what to do with that.

I have not tried any System Repair nor System Restore, mainly because neither of them have ever worked for me. I do have Restore Points from earlier this week.

At this point, all I want is for my computer to be able to detect and use drives connected via eSATA. I don't really care if they can be monitored or not (though if there were a way to make that happen, that would be nice).

Any ideas or guidance would be greatly appreciated.

Thanks

 

[pbcopter]

I would perform a system restore to a time before you replaced the driver.

 

[RPmtl]

I frequently find HDs connected via eSATA fail to auto-mount properly get a drive letter assigned and appear absent. When I load up the Disk Management tool within Computer Management I can see the drive without a drive letter. After assigning a drive letter the drive then appears properly with its correct drive label.

Some have suggested commands that will enable/repair auto-mounting of hard disks but I still see the problem popping up and simply assign a drive letter in Disk Management when it occurs.

This might or might not be relevant to the problem you're experiencing. But ya never know ....

 

[townsbg]

rpmtl how is the drive suppose to be mounted without a drive letter if the OP doesn't have drivers? I suggest that you download the chipset drivers for your computer from the manufacturer's website.

 

[RPmtl]

Perhaps the controller is there but hidden as it's no longer recognized a device to control?

Here are the instructions I keep on hand to display hidden devices in the Device Manager:

At a command prompt, type the following command , and then press ENTER:
set devmgr_show_nonpresent_devices=1

Type the following command a command prompt, and then press ENTER:
start devmgmt.msc

When the device Manager loads you can choose View -> Hidden Devices

If the controller then appears you could then choose to uninstall it (perhaps even remove the driver if that option is offered) or use the Update Driver option and install the appropriate Marvell 61xx driver for your system.

Just a thought ....

 

[yanagawa]

Hi, everyone

Thanks for the replies. Sorry I did not respond earlier, but having static IRL.

I was able to determine which one of my standard dual channel PCI controllers was the one I had changed to from the Marvell driver. I did an update and pointed it to an inf file in the drivers supplied by the developer. This successfully installed the older Marvell 61xx driver, the one that is supposed to enable SMART reading via eSATA.

Once I rebooted, the Storage Controllers reappeared in the Device Manager. I connected an HD via eSATA, it was detected, and I did get SMART and temp data.

However, any subsequent attempts to connect any drive through eSATA does not work. Windows does not see the drive, even after scanning for new hardware, and connecting seems to freeze up my system for several seconds.

I guess at this point, I will try to use the Update Driver option (as suggested by RPmtl). I don't know if I should let Windows search for the correct driver, or to download the one from the ASUS page for my motherboard. Which course of action is better?

If this fails, I will follow pbcopter's advice and try System Restore next.

I will update the thread probably tomorrow, once I have attempted the above. In the meantime, if anyone has any new ideas, I am eager and grateful to hear them.

Thanks

 

[RPmtl]

I don't know if I should let Windows search for the correct driver, or to download the one from the ASUS page for my motherboard. Which course of action is better?

I would install the ASUS driver rather than let Windows install something generic. If, after the ASUS driver is installed, Windows suggests that there's a recommended update then I'd probably let it do that.

Good luck in setting things right!

 

[townsbg]

I don't use drivers suggested by Windows update.

 

[yanagawa]

Hi, everyone. Well, I installed the driver from ASUS, but the behaviour continued. So then I did a System Restore to a date several days before the first driver change, and now the drives are being detected by Windows.

However, I have been using my Thermaltake X Duet dock to transfer files between HDs. I have two drives in the dock, and transfers go fine, but twice I have come back from leaving them idle and found my system frozen, and I have to push the reset button on the desktop to get things moving again.

So I guess the original problem is fixed!

Thanks to pbcopter, PRmtl, and townsbg for your kind assistance.