Ignite-UX

Re: Error installing from make_tape_recovery

 
dictum9
Super Advisor

Error installing from make_tape_recovery

rx8640 running 11.31.

I successfully made a make_tape_recovery tape.  When I booted off the tape and attempted to install, I got this:

Why does / demand 727 GB instead of just 3.6GB which is what /  is on the source machine? 

I have the same problem with /data3, it will not go forward no matter what I set it to. 

==============================================================

xxxx ERROR: The size specified for volume: "/" (3648MB) is not large xxx
xxxx enough to accommodate the amount of software to be loaded into it xxx
xxxx (744492MB). xxx
xxxx xxx
xxxx ERROR: The disk capacity available is not sufficient to create the xxx
xxxx volume "/data3" with the size specified (disk space is short by xxx
xxxx 39744Mb). Reduce the size of this volume (or other volumes that share xxx
xxxx the same disk group), or use additional/larger disks.

 

5 REPLIES 5
Bill Hassell
Honored Contributor

Re: Error installing from make_tape_recovery

3.6 GB  is very unusual for the "/" lvol.

Post a copy of bdf -l for the source system.

Also, post a copy of the error messages from the tape backup session.



Bill Hassell, sysadmin
dictum9
Super Advisor

Re: Error installing from make_tape_recovery

 

Filesystem kbytes used avail %used Mounted on
/dev/vg00/lvol3 3719168 452024 3242848 12% /
/dev/vg00/lvol1 1032192 666312 363152 65% /stand
/dev/vg00/lvol8 25165824 12992592 12146664 52% /var
/dev/vg00/lvol7 10240000 3743224 6446104 37% /usr
/dev/vg00/lvol6 25853952 3270560 22425664 13% /tmp
/dev/vg00/lvol5 15368192 9904608 5420936 65% /opt
/dev/vg00/lvol4 2572288 1822320 744888 71% /home
/dev/vg00/lvol9 5128192 18662 4790512 0% /.secure

 

dictum9
Super Advisor

Re: Error installing from make_tape_recovery

The initial error I get is this below.    It complains about several /data directories and saying nothing about /.

When I delete a non-essential directory to be recovered, it starts complaining about / at that point. 

 

 

xxxx The following errors occurred while trying to apply the current file xxx
xxxx system layout to the available physical disk space. One possible xxx
xxxx reason for the errors is that you have selected a root disk which is xxx
xxxx too small in size. xxx
xxxx xxx
xxxx ERROR: The disk capacity available is not sufficient to create the xxx
xxxx volume "/data3" with the size specified (disk space is short by xxx
xxxx 33472Mb). Reduce the size of this volume (or other volumes that share xxx
xxxx the same disk group), or use additional/larger disks. xxx
xxxx xxx
xxxx ERROR: The disk capacity available is not sufficient to create the xxx
xxxx volume "/data4" with the size specified (disk space is short by xxx
xxxx 83840Mb). Reduce the size of this volume (or other volumes that share xxx
xxxx the same disk group), or use additional/larger disks.

dictum9
Super Advisor

Re: Error installing from make_tape_recovery

I moved past the above error by removing some extra disks. 

 

Now I am getting this error, any idea what it means? 

 

insf: Installing special files for pseudo driver diag2
insf: Installing special files for pseudo driver root
insf: Installing special files for pseudo driver escsi
* Boot device is: 0/0/0/3/1.0x5.0x0
* Will install B.11.31 onto this system.
* Using LVM for disk 0/0/14/1/0/4/0.0x500143801136f009.0x4001000000000000 (disk26_p2), group: vg00
* Using LVM for disk 0/0/12/1/0/4/0.0x500143801136f009.0x4001000000000000 (disk26_p2), group: vg00
* Using LVM for disk 0/0/14/1/0/4/0.0x500143801136f00d.0x4001000000000000 (disk26_p2), group: vg00
* Using LVM for disk 0/0/12/1/0/4/0.0x500143801136f00d.0x4001000000000000 (disk26_p2), group: vg00
* Using LVM for disk 0/0/14/1/0/4/0.0x500143801136f00f.0x4001000000000000 (disk26_p2), group: vg00
* Using LVM for disk 0/0/12/1/0/4/0.0x500143801136f00f.0x4001000000000000 (disk26_p2), group: vg00
* Using LVM for disk 0/0/14/1/0/4/0.0x500143801136f009.0x4002000000000000 (disk27), group: /dev/vg01_eva
* Using LVM for disk 0/0/12/1/0/4/0.0x500143801136f009.0x4002000000000000 (disk27), group: /dev/vg01_eva
* Using LVM for disk 0/0/14/1/0/4/0.0x500143801136f00d.0x4002000000000000 (disk27), group: /dev/vg01_eva
* Using LVM for disk 0/0/12/1/0/4/0.0x500143801136f00d.0x4002000000000000 (disk27), group: /dev/vg01_eva
* Using LVM for disk 0/0/14/1/0/4/0.0x500143801136f00f.0x4002000000000000 (disk27), group: /dev/vg01_eva
* Using LVM for disk 0/0/12/1/0/4/0.0x500143801136f00f.0x4002000000000000 (disk27), group: /dev/vg01_eva
* Creating LVM physical volume "/dev/rdisk/disk27" (0/0/14/1/0/4/0.0x500143801136f009.0x4002000000000000).
* Creating LVM physical volume "/dev/rdisk/disk26_p2" (0/0/14/1/0/4/0.0x500143801136f009.0x4001000000000000).
* Creating volume group "/dev/vg01_eva" with physical volume group "PVG0".
* Creating volume group "vg00".
* Creating logical volume "/dev/vg01_eva/lvol1" (/oracle).
lvcreate: "/dev/vg01_eva/group": not a character device.
ERROR: Command "/sbin/lvcreate -A n -n lvol1 -C n /dev/vg01_eva" failed.


The configuration process has incurred an error, choose one of the following options

1) abort and reboot
2) ignore error and continue
3) push a shell for troubleshooting the problem
(At any time within the shell, type "exit" to return to this menu)


Choose an option from above [1 by default] :

Bill Hassell
Honored Contributor

Re: Error installing from make_tape_recovery

The error message indicates that the requsite /dev/vg01_eva/group file is invalid. What does: ls -l vg01_eva/group show? 

We are really missing a lot of information including the errors from make_tape _recovery.

What is the model of the target machine (where you are installing from the backup tape)?

Can you provide the output from the machine where you created the tape:

 

# cat /var/opt/ignite/recovery/latest/recovery.log
# uname -a
# model
# cat /opt/ignite/data/Version

There has been a limit on the size of lvol1, and primary swap, but without information on your version of HP-UX, the hardware you are backing up and restoring, most suggestions are just guesses.

 

 



Bill Hassell, sysadmin