Six days for 30gigs???

[imported_Com80787]

I am trying to copy 30 gigabytes from one SATA drive to another SATA drive. These are two seperate drives not even the same drive. I am using an MSI P6N system board with 3gigs of RAM and a core 2 duo. I am using Windows Vista. I am using the SATA ports on the system board. No add-in card. I am using Seagate 7200RPM drives both with 16MB cache.

It is taking FOREVER to copy these files. I came back 5 hours later and the estimated time to finish was over 6 DAYS.

Surely that can't be right? Yet it is moving that slow. What could possibly be causing this issue? This is on a nearly clean install of Vista as well.

 

[Fullmetal Chocobo]

It's an issue with Vista, as I've been reading anyway. Google it and check out the latest. Some people are having issues with it, some aren't. I have my machine dual booted XP & Vista. I actually use XP to do a lot of file moving. Also, I had issues with Kaspersky, as therei s a bug in Vista when using Kaspersky Anti-Virus that caps how many files you can copy (16,435 I believe).

Link 1

Link 2 @ Slashdot -- this one is short, but has links to places with good info

 

[n7]

I copied about 350 GB of stuff from one SATA HDD to another in a couple hours or less last night (didn't really pay attention).

I haven't heard much about this issue...maybe chipset related?

 

[Fullmetal Chocobo]

Originally posted by: n7
I copied about 350 GB of stuff from one SATA HDD to another in a couple hours or less last night (didn't really pay attention).

I haven't heard much about this issue...maybe chipset related?

Quite possible. I have a few issues, but nothing like what some (including the OP) are describing, and that's quite likely a result of my choice of an external (non mobo based) RAID controller.

 

[imported_Com80787]

It is rediculous. I also can confirm the issue does not exist on my WinXP dual boot.

Vista is saying it is copying at less than 500kb/sec. What a joke. And this is two different drives not even the same drive, it should be WAY WAY faster.

 

[Fullmetal Chocobo]

What is really funny is that the hard drives benchmark just fine, as file reading is not affected. Just file copying and moving.

 

[Comdrpopnfresh]

If you are doing it while in windows, and there are programs or swap in or around the files in question windows might be having to tippy-toe around. I'd get an external esata or plug in a spare drive, put the files on that, and from that to the third if you don't have time to diagnose the cause

 

[VirtualLarry]

It could be the BIOS bug with the MSI P6N. If you have more than 2GB of RAM installed, it runs very slowly. L2 cache speeds benchmark at 1/10 of what they are supposed to. There is a beta BIOS that supposedly fixes the problem.
Search for "MSI P6N 4GB bug"

 

[Matthias99]

1) Check your chipset drivers. Make sure you have the latest Vista drivers for the motherboard and that everything looks good in Device Manager.

2) Run something like HDTach to see that at least you're getting reasonable read/write speeds.

3) Make sure you haven't somehow gotten into PIO mode (easy way to check: see if your CPU usage is maxed out while copying the files. In DMA mode it should use something like 5%).

4) Try the hotfix described above for the Vista file move/copy issue, and the updated BIOS mentioned by VirtualLarry above.

 

[Roguestar]

Jeez. I can download 30 gigabytes quicker than that off my cable connection. I have heard a lot of people having that problem with Vista, but it seems only to affect random people and not their XP boots.

http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=1358057&SiteID=17

 

[Puffnstuff]

This is a known problem with vista. Go into programs and features and select turn windows features on or off. Then find the box that says remote differential compression and uncheck it. This works for some however it didn't work for me. Files take forever when moving from one internal drive to another. If I move to and from and external drive via usb/firewire it flies compared to the internal transfer and it upsets me plus wastes lots of time. MS is supposed to release a patch to correct the problem however I'm not holding my breathe waiting for it.