• Are you using the same boot method/configuration you used to create the image?
• Did you verify the name/location of the image file you're pushing?

Set up a network boot disk and try to deploy the image by running rdeploy manually to see if you get the same error.  You may also want to make sure that you can "see" the local drive while in automation by using <path to firm.exe>\FIRM DIR PROD:.

That error sure sounds like what you'd get if RDeploy can't see the local drive. That just doesn't make sense if you were able to pull an image.
Are you trying to deploy the image to the same laptop that you pulled it from? 

I am pushing the image to a different R400 laptop. I am currently trying a different R400 laptop to confirm sectors on the hard drive is not the problem. Thanks

Stil produces the same error. It restarts the laptop with PXE and loads the agent and then shows the rdeploy as though it's about to start imaging and then disappears and gives the error as stated above on the DS server. Thanks

This is from the rdeploy log. Thanks

Error description:
The disk read or write operation referenced an invalid location.
(Note: Current volume is NTFS from source slot 1.)

==================== Technical details ====================

Logfile = created Tue Apr 21 07:08:52 2009
Build = RdeployT.exe 6.9 (9020)
Cmdline = F:\RDeploy\Windows\RdeployT.exe -noprompt -md -f.\Images\xpr400.img -dsstatus:10.0.0.199:402 -mcint:10.0.2.160 -dsconfig:.\Temp\c5000914.cfg

Status = 30 (0x1e)
Source file = imglib\disk\disk.h
Line number = 295 (0x127)
Stack trace = 0x4b4235 0x498867 0x49eda3 0x49f219 0x4973a0 0x41d699 0x41341f 0x413851 0x414185 0x4149ef 0x40352a 0x412294 0x401db0 0x40e42d &Known=0x433e40
Logical block address = 312600440 (0x12a1e778)
Sector count = 112 (0x70)
Note = Current volume is NTFS from source slot 1.
Imaging library revision = 9020 (win32-x86-release build, Sat Oct 11 00:45:03 2008)

What mode is the hard drive running in?

See if you can see the drive from FIRM as I posted above.

While in automation I can run a dir and see the firm.exe. Not certain exactly what you want me to do. Thanks

FIRM is part of the command

In automation, run FIRM.exe with the following:  <path to firm.exe>\FIRM.EXE dir PROD:

That should give you a directory of the c: drive IF the drive can be seen in automation.

I went to the laptop and from the f drive ran firm.exe dir prod and received the message the system cannot find the file f:\firm.exe. Thanks

I don't remember exactly where Firm.exe is in your version of DS, but if you search the express share for it, make sure you are putting in the path to firm.

Perhaps I'm clueless. I'm on the laptop I want to image and I am at the F drive altiris windows pe2 x86 pre-boot automation environment. Everytime I run the command i still get the error message the system cannot find the file. Although when I do a dir for the firm.exe it finds it at the f drive. Thanks

Check to see if you have a firm.exe under \express\rdeploy\windows, but if not, then we're out of luck with my test because the original firm.exe was written for DOS and will not run in PE.  One other option to see if WinPE sees the disk is a PE utility called "diskpart".  That has similar functionality to fdisk in DOS.

Hello, I did find it at rdeploy\windows. The message I receive is the file could not be opened. Here is the information in the firm.log.

Error description:
The file could not be opened.

Possible causes:
A file that was expected to exist does not exist.
You do not have permission for this operation on the file or directory.

Possible resolutions:
Make sure the file exists and is accessible.
If the missing file is part of this program, reinstall the program.
Fix the permissions on the file or directory.

==================== Technical details ====================

Logfile = created Tue Apr 21 10:30:52 2009
Build = firm.exe 6.9 (9020)
Cmdline = F:\rdeploy\windows\firm.exe dir prod

Status = 41 (0x29)
Source file = imglib\fs\native\nativefs.cpp
Line number = 806 (0x326)
Stack trace = 0x44d11c 0x44cb19 0x40646a 0x406324 0x40986d 0x4010ef &Known=0x46d200
Path = prod
Imaging library revision = 9020 (win32-x86-release build, Sat Oct 11 00:45:03 2008)

So that confirms that you are not able to see the HDD in automation.  as Phyrant said earlier, what mode is the HDD in?  You may need to add a mass storage driver to your PE 2.0 to support the controller if it is in SATA mode (not sure what terminology Lenovo (IBM?) uses).

The agent is running in console mode. We have other thinkpad R60 laptops that don't have any problems imaging. Thanks

This doesn't make any sense. Since I was able to create an image from a R400 laptop. These laptops are new out of the box and I'm joining them to the domain and then from the DS pushing the dagent to the laptop successfully.

I will be leaving soon and check back tomorrow. Thanks

Just because you can push AClient or DAgent to the production OS doesn't mean that when you boot into automation for imaging you will be able to see the hard drive. If the hard drive is running in anything other than plain ATA mode you will most likely not be able to see the hard drive in automation without adding mass storage drivers to your boot disk.
I have no explanation as to why you were able to pull an image but that is definitely the reason you aren't able to push the image.

What mass storage drivers would you suggest for me to add to boot disk? Thanks

You'll have to figure out what hard drive controller that laptop uses, then download it and add it to your boot disk.

I am having the exact same problem with the Lenovo R500. I can't seem to find the mass storage drivers? Did this fix your problem, and if so, how did you go about doing this?

IBM Downloads and drivers

I'm not sure exactly which drivers I should download. I am currently putting the firmware update on a bootable cd. I'm not hopeful this will fix the problem. I assume you are referring to a driver that I need to add into my bootworks disk?

You need the Intel Matrix Storage Manager Driver. Can't guarantee it will solve your problem.

I did download those, but there doesn't seem to be any file you can put on a boot disk. It just seems to update the drivers in Windows which wouldn't affect bootworks from a disk, unless I'm missing something.

Then, you can either edit the WinPE Boot file, and select "have disk" and browse to the extracted files. It's not looking for an .exe, but more of .cat, .inf files.

The have disk feature only works if you are at DS6.9 SP2 (a known bug with 6.9SP1).

I think Altiris KB45666 spells out best how to complete this in earlier versions.

I called Altiris tech support and got my problem figured out. We had to tell the image to exclude the hidden restore partition in the deploy job. Thanks for your help.

Can you explain the steps you used to resolve this? We are having the same issue with a Lenovo T400. How did you tell the image to exclude the hidden restore partition?

Thanks in advance.

As I was trying to understand what HSD said how to fix this problem, I finally figured it out myself.  I didn't understand what he mean by "exclude the hidden restore partition in the deploy job."  After thinking about it a little more, I figured it out but I will have to explain the situation. 

My problem began with a Lenovo T400 Laptop.  When I got the T400 laptop I reinstalled windows.  When I did the initial steps of the reinstall I deleted the diagnostic partition of the T400 and then reinstalled Windows XP.  So the only partition that I had on this computer was the main partition for Windows XP.  Once we took an image on this computer we wanted to deploy the image to another T400 that we bought the same time.  This is when our issue began as many have mentioned above.

To solve this issue, what you need to do is go and delete the hidden partition that is default when you buy a new Laptop for most companies.  To do this, I just booted Ubuntu Live CD and used gparted and created a new partition table along with creating one partition that was NTFS.  So now this setup was the same as the other one, but all that I think you have to do is delete the 'hidden' partition on the drive because WinPE can't read Linux based partitions, and therefore doesn't know how to handle it.  That is when you get the "read/write" error in Altiris Deployment Console.  Once I did this, it worked flawlessly!  I hope this helps those out there who come across the same problem!