|
|
Sponsored Content
03-07-2008
Quote:
- if you migrated the whole rootvg disk to another disk then you will have to do bosboot plus a bootlist -m normal. However, in this case I'd prefer a mirrorvg follwed by an unmirrorvg...
- if you migrated /home only by issuing a migratepv -l /home AND you keep your original disk you do not have to do bosboot as an empty disk with just /home and no /hd5 device is not meant for booting from anyway.
Having said that one could say that it boils down to whether you migrate the hd5 device. Only then using the bosboot command makes sense. Getting to the nitty-gritty then I should add that with lslv -l hd5 you can see on what disk a hd5 device is located. But to find out whether you can boot from it you need to issue an ipl_varyon -i
|
|
3 More Discussions You Might Find Interesting
1. AIX
HI all,
I have changed chldev command for just one hitachi lun and I moved data from EMC to hitachi
extendvg VolumeGroupName hdisk_new
migratepv hdisk_bad hdisk_new
reducevg -d VolumeGroupName hdisk_EMC
that vg has only one EMC_lun
now i have more than one lun in one vg. i want to do... (1 Reply)
Discussion started by: nibiru78
1 Replies
2. AIX
Hi
I need to do the migratepv for the rootvg disks of the vio servers ? The current rootvg disks are on DMX3 storage and the new disks will be given from VMAX. Our setup is dual vio servers with multipathing to the vio clients.
What is the command to do the migratepv for the vio rootvg disks... (5 Replies)
Discussion started by: newtoaixos
5 Replies
3. AIX
We have 3PVs, now we want to migrate it to new 2PVs.
OLD PVS
hdisk1 ---- /u01
hdisk2 ------ /u01
hdisk 3 ----- /u02, /u01
new PVs
hdisk4 ---- Free
hdisk5 ---- Free
I check man, it doesn't say anything about offline/online thing, do i need downtime to migrate pv ? also, what i... (6 Replies)
Discussion started by: Fracker
6 Replies
LEARN ABOUT SUNOS
installboot
installboot(1M) installboot(1M) NAME
installboot - install bootblocks in a disk partition SYNOPSIS
installboot bootblk raw-disk-device The boot(1M) program, ufsboot, is loaded from disk by the bootblock program which resides in the boot area of a disk partition. The ufs boot objects are platform-dependent, and reside in the /usr/platform/platform-name/lib/fs/ufs directory. The platform name can be found using the -i option of uname(1). The installboot utility is a SPARC only program. It is not supported on the architecture. users should use installgrub(1M) instead. bootblk The name of the bootblock code. raw-disk-device The name of the disk device onto which the bootblock code is to be installed; it must be a character device which is read- able and writable. Naming conventions for a SCSI or IPI drive are c?t?d?s? and c?d?s? for an IDE drive. Example 1: Installing UFS Boot Block To install a ufs boot block on slice 0 of target 0 on controller 1 of the platform where the command is being run, use: example# installboot /usr/platform/`uname -i`/lib/fs/ufs/bootblk /dev/rdsk/c1t0d0s0 /usr/platform/platform-name/lib/fs/ufs directory where ufs boot objects reside. /platform/platform-name/ufsboot second level program to boot from a disk or CD See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ od(1), uname(1), boot(1M), init(1M), kadb(1M), kernel(1M), monitor(1M), reboot(1M), rpc.bootparamd(1M), init.d(4), attributes(5) WARNINGS
The installboot utility fails if the bootblk or openfirmware files do not exist or if the raw disk device is not a character device. 11 Apr 2005 installboot(1M)