I suppose it goes back to "When you try to boot what will you see?" If you are using a partitioned server or a whole physical server it should not matter either way. If you can get the console opened and then power on/activate you would (if there are no usable boot devices) drop into the SMS menus. You can then probe to see what devices are visible. You can force this by pressing the appropriate key at the right time during the start-up. Do you know how to do that?
I suppose one question to ask is "Do you have a mirrored pair of disks for your root volume group?" which should give you some resilience. If you don't know, then the output from the following would be useful:-
As has been commented, you really need to force the mksysb off the server you may need to recover such that you can boot from it, so tape, DVD or NIM server (yes, I know you haven't got NIM) because then you can select that device from the SMS menus to boot from and (hopefully) it will all recover.
If you have other volume groups, then we can work on how to save the structure and/or contents. If you have Networker backing up data over the network , then you will probably just want the structure so you can recover that then restore your data.
The output from:-
Code:
lsvg
lsvg | grep -v rootvg | while read vg
do
lsvg -p $vg
lsvg -l $vg
done
.... will help us plan. The best place to store the structure information is somewhere in the root volume group so that it is recovered from a mksysb when you really need it.
if you can elaborate on what you have then I'm sure we can help. It would also be useful to know if the recovery would be to the same/similar server or if there are going to be differences, e.g. do you have LVM mirrored disks and the recovery server has hardware mirrors so you only have half the storage etc.
Don't worry if you don't have all the answers yet. We can work on them later.
hello
i saved my system this morning, mksysb tape, and i have the message: "boot.image exceeded the size....." i have not the end because the message is disappeared.
where can i find the mksysb message in a log ?
the message is scary ?
thank you (6 Replies)
Hi all,
I have a SCSI hard disk drive (2GB) I'm installing on it solaris 5 and some other applications on a sun sparc workstation, I made an image file of this H.D using Norton Ghost 6, then I restored this image file on another H.D.D (4GB), I tried to boot the sun sparc workstation with this new... (0 Replies)
I have a whole bunch of solaris machines. How do i create an image so i dont have to keep doing a reload and. In the pC world we have ghost what about the solaris world? (3 Replies)
I have several systems which require software maintenance several times a year. After the software maintenance, it is required that we make two system tapes for DR purposes. The creation of these system tapes takes anywhere from 1-1.5 hours because of the performance of the tape drives. What I... (7 Replies)
when i made image of my fedora9 disk it had 18 GB. my new drive has 60GB. How can i expand the installed image to fit the entire new disk?. (2 Replies)
Hello,
I have an mksysb image in my disk, created like:
# mksysb -i /mnt/backup/lpar2.image
I want to know if this image could be copied to a tape and make it a boot image.
Thanks
Enzote (3 Replies)
Hi,
Can any one please tell me the method to check whether a mksysb image which is in the server is bootable or not. :confused:
Thanks in advance,
Anoop (1 Reply)
i have been given a bootable cd/dvd, that i install a ibm aix 185 workstation with, i want to make a nim mksysb resource from that,
the following is a listing for the root file structure of the cd/dvd, seems someone took a mksysb of a built ibm aix machine and did mkcd -L -S -I and setup the... (2 Replies)
Hi Folks,
How to restore mksysb image on LPAR which is already having cloned AIX OS installed on hdisk0 (nothing configured, only full partition image is sitting on hdisk0)
Let me know.
Thank a lot. (1 Reply)
Hi Experts,
I am very new to AIX, I have a mksysb image in one of my aix server (V6), I would like to install this mksysb image on newly lpar. Is it possible without tape and NIM?
Advice would be appreciated.
Regards,
Rockie (11 Replies)
Discussion started by: aix.rockie
11 Replies
LEARN ABOUT HPUX
lvmadm
lvmadm(1M)lvmadm(1M)NAME
lvmadm - display limits associated with a volume group version
SYNOPSIS
vg_vers]
DESCRIPTION
The command is used to perform the actions below:
o Display the limits associated with a volume group version.
o Display the LVM configuration that is contained in and files for the indicated volume group version.
o Update the entries of the bootable volume group and the boot information present in the boot disk either during or after boot.
With the boot disk's physical location changing prior to reboot or when the system is booted with a cloned disk, the entries of the
bootable volume group and the boot information present in the boot disk may be out of sync with the kernel. In such a situation, follow-
ing root volume group activation (either during boot or post boot) use the command in migrate mode option) to update the information
present in the file and the boot information present in the boot disk with the kernel. See lvm(7) for more details.
Options and Arguments
recognizes the following options:
Display a table of limits for the indicated
volume group version.
Display limits or configuration for volume group version
vg_vers. The default is to display limits for all supported volume group versions.
Display the LVM configuration that is contained in the
and files.
Produce a compact listing of fields described in
The output is a list of colon separated fields formatted as:
Update the information present in the
file for the bootable volume group and the boot information present in the boot disk, with the information present in the
kernel, if there is any mismatch.
Display With -t Option
For each volume group version to be displayed (one if is specified, all if is omitted) displays the following.
VG Version The volume group version.
Max VG Size (Tbytes) The maximum size of a volume group in terabytes.
Max LV Size (Tbytes) The maximum size of a logical volume in terabytes.
Max PV Size (Tbytes) The maximum size of a physical volume in terabytes.
Max VGs The maximum number of volume groups this volume group version supports on a system.
Max LVs The maximum number of logical volumes in a volume group.
Max PVs The maximum number of physical volumes in a volume group.
Max Mirrors The maximum number of mirrors for a logical volume.
Max Stripes The maximum number of stripes for a logical volume.
Max Stripe Size (Kbytes) The maximum stripe size for a logical volume in kilobytes.
Max LXs per LV The maximum number of extents in a logical volume.
Max PXs per PV The maximum number of extents in a physical volume.
Max Ext Size (Mbytes) The maximum size of an extent in megabytes.
Display with -l Option
For each volume group version to be displayed (one if is specified, all if is omitted) displays the following:
o The list of volume groups that exist on the system, and
o The list of physical volumes belonging to each of the volume groups.
The LVM configuration displayed by this option is from data contained in the and files. The command fails if these files are missing or
corrupt.
Compact Listing (-F Option)
The option generates a compact and parsable listing of the command output in colon separated fields formatted as
The option is designed to be used by scripts. The resulting command output may be split across multiple lines. The output may include new
keys and/or values in the future. If a key is deprecated, its associated value is set to
Compact Listing for -t option
Below is a sample output:
Compact Listing for -l option
Below is a sample output:
EXTERNAL INFLUENCES
Environment Variables
determines the language in which messages are displayed.
If is not specified or is null, it defaults to "C" (see lang(5)).
If any internationalization variable contains an invalid setting, all internationalization variables default to "C" (see environ(5)).
EXAMPLES
Display a table of limits for volume group version 2.0.
Display the LVM configuration file contents for volume group version 1.0.
AUTHOR
was developed by HP.
SEE ALSO vgcreate(1M), lvm(7).
lvmadm(1M)
07-08-2015
, then you will probably just want the structure so you can recover that then restore your data.