[g4u-help] Slow performance with g4u after changing motherboard
Brought to you by:
hubertf
From: Brian H. <bri...@bh...> - 2012-01-21 15:47:37
|
Hi, I first attempted to post this with an image attachment, but it bounced, so trying again by typing in my g4u information below. This week, my motherboard was replaced. So as I rebuilt the system and everything is back to normal again, I began a clone of the system drive using g4u 2.4. Normally, cloning my 500 Gb system drives takes about 96 minutes. But last nights clone from a 500 Gb disk to another of the same size was still not finished after 6 hours. I am cloning locally from one SATA drive to another using the command: copydisk wd0 wd1 Since I just did a clone before my old motherboard died on these same disks in 96 minutes, I can only assume something is changed on my new motherboard or processor causing the problem. Is there anything I can do to correct this? The info below isn't the 6 hour copy, but another attempt that I started and hit ctrl-c to cancel. That's why you see the ^C^ stuff in there. But you can see the 1.53 MiB/s speed, which is very slow I believe. I have written down on my last clone, this speed was 82.77 MiB/s g4u> disks wd0 at atabus1 drive0: <ST3500418AS> wd0: quirks 0x2<FORCE_LBA48> wd0: drive supports 16-sector PIO transfers, LBA48 addressing wd0: 465 GB, 962021 cyl, 16 head, 63 sec, 512 bytes/sect x 976773168 sectors wd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 6 (Ultra/133) wd1 at atabus2 drive 0: <ST3500320AS> wd1: quirks 0x2<FORCE_LBA48> wd1: drive supports 16-sector PIO transfers, LBA48 addressing wd1: 465 GB, 962021 cyl, 16 head, 63 sec, 512 bytes/sect x 976773168 sectors wd1: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 6 (Ultra/133) g4u> copydisk wd0 wd1 1375 MiB 1.53 MiB/s ^C^1376+0 recofds in 2818048+0 records out 1442840576 bytes transferred in 896.182 seconds (1609986 bytes/sec) g4u> Here's my system info as well. Windows 7 Pro, SP1 Processor: Intel i7-2600K CPU @ 3.40 GHz RAM: 16 GB Thanks in advance for any advice to help! - Brian |