Windows 10: Since 1909 my Startech eSata Multiplier card does not work

The Startech PEXESAT322Ihttps://www.startech.com/au/Search?search_term=esata&page=2


This allowed me to plug in a ext box with 4 drives in it using one eSata connection to the card in the Dell 9020.


It worked in 1903 until 1909 and the stopped. Still stopped in 2004.

Startech do not know about any driver changes in 1990 update from 1903.


Where can I find out what changes were made to stop it from working.


It is not the card or the box. It works in another 1903 box still.


Thanks

:)

 

Only one drive is showing up in Windows 10, connected using eSATA port multiplier

Hi Guido,



Thank you for writing to Microsoft Community Forums.



We understand that you are facing issue of hard drive not recognizing using eSATA port multiplier. Since the issue is related to Silicon Image sil3726 based eSATA port multiplier using RAID1, we would suggest you to post your query in

IT Pro TechNet Forums where we have our support professionals who are well equipped with the knowledge on this issue to assist you with your query.





Regards,

 

eSATA seems incompatible with Windows 10

When I first installed Startech eSATA card in 1505 windows did not natively recognize it until I installed the driver. It has since updated flawlessly to every version including 1909

 

Windows 10 Pro - eSATA port Multiplier - multiple hdds

I have a new Lenovo AMD desktop PC i've converted into a server by function while waiting on the Win10 server published build; it was originally a Win10 Home and I upgraded via MSFT link. I've converted the pc to a dedicated small scale DB server with software
removal and installations.

Generally speaking the PC has got great cpu and memory management capabilities and has yet to have a problem with any performance issues of any devices. I've even had to deal with DNS attacks and potential China based db hacks all successfully thanks to
good advice from several blogs and forums.

I initially was going to put internal drive expansions into the box but found it only had two provisional spaces within the case for additional drives. This led me to using one or more external drive arrays. Because its working as a DB server for our business
tech team I wanted to find a fault tolerant approach using storage or some other RAID or RAID simulator.

I have a PROBOX 4 bay 3.5" HD drive housing that provides a backplane for working with an eSATA port multiplier or USB 3 connection. For this box I chose the USB 3 connection and had Windows structure 3 of the 4 1TB drives as a single storage container;
this left me with 1 2TB and 1 1TB drive representing two devices through Device Manager/Storage Manager. These all formatted and are working fine without bumps in performance. The combination allows the drives to act as RAID 10 in the Microsoft Storage
Space plus a logging file system. This part is working fine.

I needed to expand the system to support another array for another purpose and decided to go with a StarTech PEXESATA2 card which is an eSATA II port multiplier card. When I initially installed the card connected to a VenusT5 mini drive box (it has its
own onboard software configuration for creating a RAID system), the Windows 10 Storage Manager recognized all 5 drives in the housing. I went to set up the Storage Space and accidentally chose 4 not all 5 drives. As soon as I did that I no longer saw (see)
the 5th drive. I have since removed the storage space for the 4 drives hoping it would solve the problem but it didn't. Now no matter what I do the 5th drive doesn't exist for Windows.

So I then ran the StarTech and VenusT5 mini software managers and both of them see the 5 drives, but Windows10 only sees 4 of the 5 drives.

This seems wholly weird in that from Windows Storage Manager I can see each of 4 drives individually or as a single available drive but I can no longer see the 5th drive. The drive is simply not visible to the Windows system, but both device controller
programs outside of Windows sees the 5th drive.

Incase someones going to ask, yes I've rebooted the system several times during the install and updates to see if anything changes; .. no luck.

Does anyone have an idea how or why Windows would not see 1 of several drives in this type of scenario. (BTW I have reached out to both the drive housing and StarTech support teams while trying to solve this problem and am hoping to find a solution rather
than waste the purchase of a 1TB HD).

Ideas?