ProLiant Deployment and Provisioning
1753945 Members
8322 Online
108811 Solutions
New Discussion юеВ

Re: RDeploy: The disk read operation failed.

 
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
pasquino bocci_1
Trusted Contributor

Re: RDeploy: The disk read operation failed.

Hi,

how many Vg do you have? 1 or 2, or 1 across 2 disks?
pasquino
Gordon Leonard
Honored Contributor

Re: RDeploy: The disk read operation failed.

Few more questions.

How did you install RH 4u4?

How many logical drives do you have (as seen by the RAID controller)?

Did you modify the kickstart file? [if so please send it]

Also you see the error message "The volume is invalid" when you try to capture the image? By default you should not need any switches since we will capture the first drive by default.

Thanks

Todd Schelin
Valued Contributor

Re: RDeploy: The disk read operation failed.

Installed RedHat from the iso cd's and did not modify the kickstart file.

I understand that is should work by default but it doesn't. This machine has LVM installed on it.
Gordon Leonard
Honored Contributor

Re: RDeploy: The disk read operation failed.

Install RH using the RDP "Server Deployment".
pasquino bocci_1
Trusted Contributor

Re: RDeploy: The disk read operation failed.

Hi,

the capture image should work! We're missing something!
What about your raid config? It seems you have two luns or 2 mirrors. Please, more infos!
thanks.
Pasquino