• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

MSI x58 Pro eSATA port not reading my WD MyBook

In2Photos

Platinum Member
I can not get my MSI x58 Pro to recognize my WD 500GB ES edition. It works fine via USB. In the BIOS it shows "not detected". The cable is plugged in and I unplugged and reinstalled just to make sure. I will be picking another cable just in case but was wondering if anyone else had any insight.

thanks!
 
I believe that your eSata port is driven by the JMicron JMB363 chip. Make sure you have the drivers installed for that.
 
Thanks Binky, I'll check it out. I would have thought though, that if the drivers were not installed then I would have seen something amiss in Device Manager. And if I needed the drivers they should have also been on the install DVD, right? Anything is possible though, so I'll try the drivers to see if that works.
 
No luck with the drivers. As I suspected I think they were already installed as I had no conflicts or problems in Device Manager.

I checked with WD and of course they say there is nothing to download, if there is a problem it is with the mobo or Windows. I am going to try a SATA to eSATA cable as well as another eSATA to eSATA cable to see if that works.
 
Sorry that you're having trouble, I have the same motherboard and my Seagate Freeagent Xtreme 1.5tb works over eSata, although a little quirky. Sometimes it doesn't turn on with the OS, I have to take the power cord out and put it back in to have it work. I am using the latest drivers listed on the website, although I am using the latest x58 Pro SLI bios instead of the regular one 😛
 
Well that's not good. I assume you can see the deivce in device manager.

Have you tried the drive with eSata on another system? Is there any way to jumper the drive to the slower speed (is it SATA1? 150 or something...)? I've seen this fix work before, but it wasn't with pre-packages esata drives.

Also, I've seen problems on some systems with esata hot-swapping, although the same system might work if you boot with the drive attached. It's worth a shot.
 
Originally posted by: Binky
Well that's not good. I assume you can see the deivce in device manager.

Have you tried the drive with eSata on another system? Is there any way to jumper the drive to the slower speed (is it SATA1? 150 or something...)? I've seen this fix work before, but it wasn't with pre-packages esata drives.

Also, I've seen problems on some systems with esata hot-swapping, although the same system might work if you boot with the drive attached. It's worth a shot.

I can not see the My Book anywhere. But there are no other conflicts in Device Manager so all drivers appear to be installed. I don't have any other systems with eSATA to test.

Drive should be SATA II so I shouldn't need to adjust any jumpers, but I'll check to see.

I have tried booting with the MyBook on and off, unplugging the drive while machine is on as well. No go. I have some new cables on the way (both eSATA to eSATA and eSATA to SATA) hoping that is my problem and not the Mobo.

Thanks again for your help guys!
 
Looks like it was a bad cable. I plugged in the new one from Newegg today and it powered on by itself and I can see it in My Computer. All is good, thanks for everyone's help!
 
Originally posted by: In2Photos
Looks like it was a bad cable. I plugged in the new one from Newegg today and it powered on by itself and I can see it in My Computer. All is good, thanks for everyone's help!

Now tell your motherboard you're sorry.
 
Originally posted by: WaitingForNehalem
Originally posted by: In2Photos
Looks like it was a bad cable. I plugged in the new one from Newegg today and it powered on by itself and I can see it in My Computer. All is good, thanks for everyone's help!

Now tell your motherboard you're sorry.

LOL, I never blamed the mobo. in fact in my first post I thought it was the cable!

Good mobo! 🙂
 
Back
Top