|09 Mar 2010||#15|
| || |
A couple of things
I too am having the same problem with my eSata and windows 7 9USB works fine) and will be looking into my BIOS and startup order tonight as well as forcing computer management to locate drives. But what I want to clear up was that eSATA is NOT 3 GigiBYTES per second, it's 3 GigaBITS per second. This effectively makes the throughput about 300 Megabytes per second. Remember, that 1 byte = 8 bits. 3000 Mb = 375 MB. They rounded down to 300.
Now, to make it run the fastest it can, you have to adjust the policies. Go into Device Manager and expand the drives section. Find your eSATA external and right click, then click properties. Click on the policies. Be sure to check all the radio buttons for improved performance. The final checkbox is for drives with their own power supply. This allowed my drive to run roughly about 125 MB/s. Again, the bottle neck are the drives themselves here, but it is twice as fast as it was before adjusting the policies. One policy allows you to just unplug the drive without stopping it first, which slows it down. You do not want this on.
|My System Specs|
|10 Mar 2010||#18|
| || |
***A little background on why my drive dissapeared. I was getting a corrupted file error prior to my enclosure dissapearing. The file conatined some pictures. When I ran chkdsk in windows, it failed. I did a search on the error I was getting (something about "can't access file because it's corrupt" which means you can move it bu not delete it) I found no help other than to run chkdsk. When I ran chkdsk, it failed on the corrupted file and my drive dissapeared, but only for eSATA connections, not USB.***
Last night I went home and shut down my computer. I then hooked up the external enclosure to my eSATA port again and turned it on. I booted my PC and went into BIOS. The external showed up there and I verified it was not the boot drive. I exited BIOS and hit F12 to pick the boot menu anyway. Again, it was my C: drive, so I let the boot continue. Windows 7 Startup splash screen appeared, and right before the log on screen, it went into DOS mode and started a chkdsk of my eSATA enclosure. Sure enough, it located the previously mention corrupted files, deleted all the logs associated with them, then restored my files to original! After that, it proceeded to continue to the logon screen. When I logged on, I clicked on My Computer and sure enough there was my drive! I browsed it and I was able to access the previously corrupted file just fine. I guess the chkdsk utility runs differently in DOS mode than actually in Windows. I was able to run my back up program and write to the drive and everything. There must have been some corrupt system files in the file tables that the computer didn't like via eSATA? I don't know exactly.
|My System Specs|
|Similar help and support threads for2: External Hard Drive attached by eSATA not detected|
|eSATA drive not detected--can CrystalDiskInfo damage an eSATA drive||BSOD Help and Support|
|Why won't my external hard drive work in IDE mode through eSATA?||Hardware & Devices|
|External eSata drive stopped being detected||Hardware & Devices|
|ESATA hard drive not detected||Hardware & Devices|
|eSATA hard disk drive not detected when hotplugged||Hardware & Devices|
|External Hard Drive Not Recognized in eSATA||Hardware & Devices|
|Hard Drive attached by eSATA is not detected||Hardware & Devices|
|Our Sites ||Site Links ||About Us ||Find Us |
© Designer Media Ltd
All times are GMT -5. The time now is 01:03 PM.