Speed difference between Dell models

[dcol]

Hi all,

I am using Acronis TI corporate WS (latest build) for my deploys and I notice that the Dell Latitude 600 is much faster than the Latitude 610 during restores. I restore a 2GB image on the 600 in under 10 minutes. A 3.5GB image on the 610 takes 1 hour and 15 minutes. I would expect it to be under 20 minutes.

All images are stored on a GB speed local network. The only difference is in the laptops.

I only use the restore CD, so I am using Acronis drivers. Both models use the Broadcom GB NIC.

Any ideas?

[Acronis Support]

Hello dcol,

Thank you for choosing Acronis Workstation Disk Backup Software.

First of all, please try booting with "acpi=off noapic" parameter as it is described in Acronis Help Post.

If that does not help then please do the following:

- Boot your Dell Latitude 610 laptop from Bootable Rescue CD created using the latest build (1213) of Acronis True Image 8.0 Corporate Workstation and press F11 key when "Staring Acronis Loader..." message appears;

- After you get the "Linux Kernel Settings" prompt, please remove the "quiet" word, click on the OK button and wait for # prompt to appear.

- Issue the following commands:

asamba dhcp -n
asamba masters

- Write down the output after each of the commands or use a digital camera to make a shots of the output screens;

cd tmp
mkdir mntdir
mount /devfs/floppy/0 mntdir
cat /proc/net/dev > mntdir/net.txt
sysinfo > mntdir/sysinfo.txt
umount mntdir

- Collect the net.txt and sysinfo.txt files from the diskette.

Please also provide us with the following information:

- What is the exact size of the data that you are imaging?

- What is the exact size of the resulting image archive?

- How much time does it take exactly to restore this image on your Dell Latitude 610 laptop?

Please submit a request for technical support. Attach all the collected files and information to your request along with the step-by-step description of the actions taken before the problem appears and the link to this thread. We will investigate the problem and try to provide you with the solution.

Thank you.
--
Alexey Popov

[dcol]

Took a while to get to this, but I cannot do the steps you requested because these laptops do not have floppy drives.

One other note, It only takes 10 minutes to create an image, but 1 hour and 50 minutes to do a restore.

When I do asamba dhch -n, I get the following:
client started
SIOCDELRT: Unknown error 3
eth0: using PCI INTX interuppt
sending discover
BM5700: eth0 NIC link is up 1000 Mbps full duplex, receive tranmit flow control on
SIOCDELRT: Unknown error 3

asamba masters listed all my shares (do want want to disclose them on a public forum)

Here are some specs:
Using TI Corporate Bootable rescue media ver 1213
Dell Laptop D610 Latitude, latest revision.
Data size to image is 5.5GB
Image size is 3.75 GB
Create Image time is 10:50 (min:sec)
Restore Image time is 1:51:30 (hr:min:sec)

Please Help!

[bobdat]

The reason for speed variance is because TrueImage uses freebie Linux drivers which provide USB1-like speed for most modern chipsets like those in your Dell's.

To bypass this glaring deficiency in TI, create a BartPE CD which will use your native Windows drivers and give you the speed you should be getting from TI.

Unfortunately, you'll have to create a unique BartPE CD for each machine that has a different chipset.

The other disadvantage of using the TI plugin with BartPE is that you can't create or restore form removable media (not a big deal for most).

[Acronis Support]

Hello dcol,

Could you please let us know how much time it takes to restore an image located on any local hard drive (any internal or external hard drive connected to your Dell Latitude 610 locally)?

Please also do the following in order to save Linux system information (sysinfo.txt) to the USB flash drive (if any). Flash disk needs to be formatted to one of the following file systems: ext2, ext3 or FAT32.

Please boot from the Acronis True Image rescue disc and press F11 key after the "Starting Acronis Loader..." message appears and you get to the selection screen advising you to select either "Full", "Safe" or "Boot into Windows" option appears. After you get the "Linux Kernel Settings" prompt, please remove the word "quiet", click on the "OK" button and select the Full version menu item to boot. Wait for # prompt to appear.

Please insert a Flash disk to a USB port and issue the following commands:

# cat /proc/partitions

This will give you the list of partitions/drives available in your system.

For example:

8 0 127744 scsi/host0/bus0/target0/lun0/disc
8 1 127744 scsi/host0/bus0/target0/lun0/part1
3 0 80417183 ide/host0/bus0/target0/lun0/disc
3 1 10241406 ide/host0/bus0/target0/lun0/part1
3 2 20482875 ide/host0/bus0/target0/lun0/part2
3 3 1020127 ide/host0/bus0/target0/lun0/part3

Flash drive is visible as 'scsi'. If there are some scsi devices in your system you may find your flash by partition/drive size. If the flash is partitioned it will bring the list of partitions as well.

Then you need to create a mount point for your flash and mount it.

# mkdir /mnt/tmp
# mount -t auto /devfs/scsi/host0/bus0/target0/lun0/part1 /mnt/tmp

There can be some warning messages but it is safe to ignore them. If mount fails you may try to use 'vfat' (if the flash is formatted to FAT file system) or 'ext3fs' or 'ext2fs' (if its formatted to ext3 or ext2) parameter instead of 'auto'.

Make a directory on your flash drive to save files to it:

# mkdir /mnt/tmp/sysinfo

Check whether the drive is mounted correctly for writing access:

#ls /mnt/tmp

This will give a list of files/folders located on the drive.

Save 'sysinfo' and unmount the flash drive:

# sysinfo > /mnt/tmp/sysinfo/sysinfo.txt
# umount /mnt/tmp

Boot into Windows and collect the created sysinfo.txt file from the flash drive.

Please send us all the collected information in the way I have described in my previous post. We will certainly investigate the problem and try to provide you with the solution.

P.S. If you are not able to create Linux system information (sysinfo.txt) for some reason then please contact us by submitting a request for technical support anyway.

Thank you.
--
Alexey Popov

[thomasjk]

Originally Posted by bobdat

The reason for speed variance is because TrueImage uses freebie Linux drivers which provide USB1-like speed for most modern chipsets like those in your Dell's.

To bypass this glaring deficiency in TI, create a BartPE CD which will use your native Windows drivers and give you the speed you should be getting from TI.

Unfortunately, you'll have to create a unique BartPE CD for each machine that has a different chipset.

The other disadvantage of using the TI plugin with BartPE is that you can't create or restore form removable media (not a big deal for most).

A different BartPe CD for each machine is not necessarily needed. There are a couple of ways around this. One option is the: http://ubcd4win.com/ another is Reatgo using Mustang's plugin at: http://www.911cd.net/forums//index.php?showforum=32. Also see the following thread in this forum: http://www.wilderssecurity.com/showt...ghlight=bartpe.

The main issue with varying machines is Chipsets and hardware drivers. Both solutions above offer a wide variety of drivers.

[dcol]

I will try the Bart CD, but I do not normally use USB. If I do the same restore from the USB drive it actually takes a little longer.

Acronis- will get those files via thumb drive tomorrow.

Dan

[Jallen]

This is also an issue with the new Dell Latitude D510 which uses the Broadcom 440x chipset.

Is there any plan to natively support these adaptors?

[Acronis Support]

Hello Jallen,

Thank you for choosing Acronis Disk Backup Software.

Please accept our apologies for the delay with the response.

Please collect all the files and information requested above by Alexey and submit a request for technical support. Attach all the collected files and information to your request along with the step-by-step description of the actions taken before the problem appears and the link to this thread. We will investigate the problem and try to provide you with the solution.

Thank you.
--
Kirill Omelchenko