ProLiant Deployment and Provisioning
cancel
Showing results for 
Search instead for 
Did you mean: 

RDeploy: The disk read operation failed.

 
Todd Schelin
Valued Contributor

RDeploy: The disk read operation failed.

When attempting to create an image of a DL585 running RedHat Linux OS I get the error "RDeploy: The disk read operation failed." Error code 35. I have disabled any HBA's on the system and still receive the same error. The server is running a LVM as well on the OS. Is there something I am missing as this should work. Any help would be greatly appreciated.
32 REPLIES 32
Gordon Leonard
Honored Contributor

Re: RDeploy: The disk read operation failed.

Disconnect the SAN connections. Then give it a try.
Todd Schelin
Valued Contributor

Re: RDeploy: The disk read operation failed.

Gordon,
Even though I have disabled to HBA's I still need to disconnect the Fiber from the server? I will give it a try. If this works this is something that needs some work from Altiris, otherwise it defeats the whole purpose of automation.
Gordon Leonard
Honored Contributor

Re: RDeploy: The disk read operation failed.

I suspect it will lead you to this type of message..

http://h18004.www1.hp.com/products/servers/management/rdp/knowledgebase/00000178.html

Even with the HBA "disabled" do you see the LUNs via showdisk utility?

pasquino bocci_1
Trusted Contributor

Re: RDeploy: The disk read operation failed.

Hi,

LVM is only supported with RDP 3.5 8altiris 6.8). What version are you using?
Pasquino
Todd Schelin
Valued Contributor

Re: RDeploy: The disk read operation failed.

I am running RDP 3.5 with Altiris 6.8. After disconnecting the Fiber cables I am now getting an error "The volume is invalid". Are there parameters that I need to put in the RDeploy section of the job to indicate which disk I need to image?
Todd Schelin
Valued Contributor

Re: RDeploy: The disk read operation failed.

Ok, now I have verified that attempting to image Red Hat Linux is not working in RDP 3.5. The disks are running LVM and it is supposed to be supported in RDP 3.5, but I have tried 3 different machines and consistently get the same error.

"The volume is invalid."

Any help would be greatly appreciated.
Gordon Leonard
Honored Contributor

Re: RDeploy: The disk read operation failed.

Todd,

Have you reviewed the document called "RDP_UserGuide.pdf" page 10? (I don't know your setup but this deals with when you have more than 1 drive).

For imaging of a target with Red Hat Linux and LVM, the Distribute Disk Image task will need to be modified to indicate the first and last drive if the LVM volume spans ultiple logical drives.

To specify which drives to use for installation:
1. From the Deployment Server Console, copy, rename, and edit the job to be used for this deployment.
2. Modify the Distribute Disk Image task.
3. Select Advanced, and click the Additional Options tab.
4. In the Additional command-line switches field, add the -dy switch, where y is comma separated integers
representing the disk numbers that the LVM volume will span. For example, to deploy an LVM image to two
drives, use -d1,2.
Todd Schelin
Valued Contributor

Re: RDeploy: The disk read operation failed.

Gordon,
I just want to create the image, so I am guessing I need to do the same thing? But from what I can tell it is only on a Mirror set. That is one physical disks, but could be multiple VM's. I will look at the user guide and see what else is in there.
Todd Schelin
Valued Contributor

Re: RDeploy: The disk read operation failed.

Gordon,
I just got off of the phone with HP and apparently Creating a Disk Image of Linux running LVM is not supported in Altiris 6.8. Altiris is currently working on the issue, but currently is not supported at this time.

You can distribute an OS installation and then add LVM to the OS, but you cannot create a disk image of Linux running LVM.

Thanks for you help.
pasquino bocci_1
Trusted Contributor

Re: RDeploy: The disk read operation failed.

Hi,

HP is not the bible!!!

look here, from HP:

How To Use Data From The Altiris Showdisk Utility Produced From The Read Hardware Configuration Job


Article: 178

Applies to: Release 3.00 or greater


The Read Hardware Configuration job includes output from the Altiris showdisk utility. This output can be used to determine how drives are enumerated under automation which is how rdeploy sees the drives for imaging.

This information is beneficial when deploying an operating system to a SAN-attached environment, a direct-attached storage environment with multiple logical drives, or when USB is used as the boot media method. In these environments, rdeploy may read or write image files to or from the secondary disks. The showdisk information can be used to determine the appropriate -dX parameter to the Create Disk Image or Distribute Disk Image tasks in a scripted or image install job. For scripted installs, a NTFS.IMG or GRUB.IMG image file is landed to start the operating system installation process.

For servers installed with Red Hat Linux and Logical Volume Manager (LVM), showdisk shows the data differently. Showdisk will display a disk for LVM and one or more disks for the logical drives. Using the disk number for the disk with LVM, the image capture will capture the LVM volume which may span more than one logical drive. If deploying this image back to a server with more than one logical drive, the Distribute Disk Image task will need to be modified to use more than one disk parameter, for example, -d1,2 to deploy the LVM image to disk 1 and disk 2. The disks indicated with -d are comma separated.

Important: The -d1,2 syntax for rdeploy is only valid for LVM deployments. This syntax cannot be used for capturing and deploying multiple storage drives for other operating systems or non-LVM setups.

If the disk number for the physical/logical drive is used to capture an image in place of capturing the LVM disk, the image will be read in raw mode. Reading a drive in raw mode, reads the entire drive which could take extra time to read the drive and creates many large image files on the Deployment Server.

Todd Schelin
Valued Contributor

Re: RDeploy: The disk read operation failed.

I only have one question, where does the output from the Showdisk utility end up and or how do you use it? I have looked in the Rdeploy/Linux/Logs directory and that doesn't tell me much.
Todd Schelin
Valued Contributor

Re: RDeploy: The disk read operation failed.

Never mind I just figured out how to get output from Showdisk. Running the job now and will let you know if that works in helping me create an image of the Linux system.
Todd Schelin
Valued Contributor

Re: RDeploy: The disk read operation failed.

Here is the output from my Linux system running LVM..

ShowDisk 6.8 (8297)
Copyright (C) 2003-2007 Altiris, Inc. All rights reserved.

Disk 1 (Unknown): 2186/1024/64, 143273870 sectors, 68.32 GB (LVM)

Type Boot Begin Size
----------------------------------------------------------------------------
1 Ext3 0 0/0/1 208782 (101.94 MB)
2 Ext3 208782 3/190/15 41943040 (20.00 GB)
3 Linux Swap 42151822 643/190/15 16777216 (8.00 GB)

Disk 2 (SCSI): 17562/255/32, 143305920 sectors, 68.33 GB (MBR, sig=00056f46)

Type Boot Begin Size
----------------------------------------------------------------------------
1 Ext3 * 63 0/1/32 208782 (101.94 MB)
2 0x8e 208845 25/151/14 143090955 (68.23 GB)


* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *


Disk /dev/cciss/c0d0: 73.3 GB, 73372631040 bytes
255 heads, 63 sectors/track, 8920 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/cciss/c0d0p1 * 1 13 104391 83 Linux
/dev/cciss/c0d0p2 14 8920 71545477+ 8e Linux LVM


So, how do I correlate this to a setting in the parameters so, I can capture the image?
Gordon Leonard
Honored Contributor

Re: RDeploy: The disk read operation failed.

Todd,

What is your case number?
Todd Schelin
Valued Contributor

Re: RDeploy: The disk read operation failed.

Here is the case number that I had opened and was informed from HP engineer that it is not supported. So, I think the case was closed.

3218604354
Gordon Leonard
Honored Contributor

Re: RDeploy: The disk read operation failed.

Todd,

The only thing I see is you said your using RH 4u3 - HP supports RH 4u4. Could you build a server using RH 4u4? Let me know - sorry about the run around. I'm working on the LVM "not supported" message.
Todd Schelin
Valued Contributor

Re: RDeploy: The disk read operation failed.

What about Update 5 is that supported? I can get to update 5 easy, but don't know about 4 may take some more time.
Gordon Leonard
Honored Contributor

Re: RDeploy: The disk read operation failed.

Sorry - We need to keep to the RDP Support Matrix (found in the DOC directory). Lets get you at the "expected" OS and see if you still have issues. HP *does* support LVM.
Todd Schelin
Valued Contributor

Re: RDeploy: The disk read operation failed.

Installing Update 4 now will reply when I am done. Once there is there anything specific I need to do, or just run the Create Disk Image job against it.
pasquino bocci_1
Trusted Contributor

Re: RDeploy: The disk read operation failed.

Hi,

from altiris 6.8SP1 doc:


RapiDeploy Command-line Switches (Continued)
Switch [parameters] Details
-d[hard disk number] Function Specifies which hard disk to read from or write to,
depending on whether you are uploading or downloading. This
switch is used for computers that have more than one hard disk.
Examples
To download an image to disk 2, combine with the -md switch
and type
rdeploy -d2 -md -f[filename]
To create an image from disk 2, combine with the -mu switch
and type
rdeploy -d2 -mu -f[filename]
See also -m[mode], -f[path & file name]
Disk to Disk
A colon indicates disk-to-disk imaging.
-d1:2 (disk to disk mode, source is disk 1, destination is disk 2)
-d3:2 (Source is disk 3, destination is disk 2)
Linux Software Raid and LVM
When using a Linux software raid or LVM, a comma specifies the
disks in the set.
rdeploy -d1,2 -md -f[filename]
If using a hardware raid, this syntax might not be required if the
disk set is recognized as a single drive. Use the firm drives
command to determine how the drives are recoginized.
1-2] Function Specifies the disk location to set if the imaged disk will
be removed after imaging.
filename] Function Specifies the Deployment Agent configuration file to
copy to the computer when the imaging job completes.
-f[path & file name] Function Used with the -m switch. In upload mode, it specifies
the filename and location for storing an image file. In download
mode it specifies which image file to restore.
To create (upload) a regular image file, use an .img extension.
To create a self-extracting executable image file, use an .exe
extension.
Examples
zTo upload an image file to disk g:, type
rdeploy -mu -fg:\images\win98.img
To upload a self-extracting executable image file, type
rdeploy -mu -fg:\images\win98.exe
See also -m[mode], -f[path & file name]
Gordon Leonard
Honored Contributor

Re: RDeploy: The disk read operation failed.

Pasquino,

You would think that he need only use -d1,2 and all would be fine. Kind of wondering if the RH version has something to do with it...we'll see.
Todd Schelin
Valued Contributor

Re: RDeploy: The disk read operation failed.

Ok, the system is updated and running RHU4 and still getting the same problem. Here is a screen shot of the parameters that I have set and the location of the image. From what I can tell the Linux boot loader is located on Disk 1. I provided the output from the showdisk command.
Gordon Leonard
Honored Contributor

Re: RDeploy: The disk read operation failed.

Ok.

You built the server from the ground up on the local drives (no SAN connections - *no* cables connecting to the SAN). Yes???

From the RAID controller view you have how many drives?

Please send me an update ShowDisk output (attach a TXT file or just cut/paste to message).

Thanks!
Todd Schelin
Valued Contributor

Re: RDeploy: The disk read operation failed.

Here is the capture from Showdisk.

# Showdisk provides a view of how rdeploy sees the drives.
# This information can be used to determine the appropriate
# -dX parameter to use in the Create/Distribute Disk Image tasks.
#
# For servers installed with Red Hat Linux and Logical Volume Manager (LVM),
# showdisk will display a disk representing the LVM volume and disks for
# the logical drives. When deploying a captured LVM image, a modification
# to the Distribute Disk Image task may be required to use one or more disk
# parameter.
# For example, use -d1,2 to deploy the LVM image to disk 1 and disk 2.
# This rdeploy -dx,y syntax is only valid for LVM deployments.



ShowDisk 6.8 (8297)
Copyright (C) 2003-2007 Altiris, Inc. All rights reserved.

Disk 1 (Unknown): 2186/1024/64, 143273870 sectors, 68.32 GB (LVM)

Type Boot Begin Size
----------------------------------------------------------------------------
1 Ext3 0 0/0/1 208782 (101.94 MB)
2 Ext3 208782 3/190/15 138870784 (66.22 GB)
3 Linux Swap 139079566 2122/190/15 4063232 (1.94 GB)

Disk 2 (SCSI): 17562/255/32, 143305920 sectors, 68.33 GB (MBR, sig=00056f46)

Type Boot Begin Size
----------------------------------------------------------------------------
1 Ext3 * 63 0/1/32 208782 (101.94 MB)
2 0x8e 208845 25/151/14 143090955 (68.23 GB)


* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *


Disk /dev/cciss/c0d0: 73.3 GB, 73372631040 bytes
255 heads, 63 sectors/track, 8920 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/cciss/c0d0p1 * 1 13 104391 83 Linux
/dev/cciss/c0d0p2 14 8920 71545477+ 8e Linux LVM