11-07-2009
Quote:
Originally Posted by
rwesterik
[..] When starting the partition to the SMS menu you can see the correct (rootvg) devices being scanned, but the devices are NOT listed as a possible boot device.
When booting off a NIM server and trying to restore an mksysb, the entire rootvg (all disks in it) is invisible and cannot be selected. Some user-defined volume groups are also "missing".[...]
Being able to see a device but being unable to access the data area sounds like a SCSI disk reservation problem.
10 More Discussions You Might Find Interesting
1. AIX
We have a frame the uses 2 vios that assign disk storage to LPAR's. We have a LPAr with multiple disk and I want to know how do I tell which vio is serving the disk. For example the LPAr has hdisk 0, 1, 2, 3 all the same size. I want to know which vio is serving hdisk0, 1. (4 Replies)
Discussion started by: daveisme
4 Replies
2. Solaris
My current situation is like this, I have a v440 connected to a netapp central storage 3140 via fiber channel, my OS and oracle is installed in the internal drive of the v440.
What I would like to do is to advertise another LUN in netapp to the v440 and let my v440 boot from it so I can start... (3 Replies)
Discussion started by: q8devilish
3 Replies
3. AIX
Hi,
Is there a way to dynamically increase the size of virtual disk on the LPAR. The virtual disk is coming from my VIO Server. From my SAN I have allocated a disk to VIO Server and from VIO Server to my LPAR....If I increase the space of the logical SAN DISK (DS 4700 using IBM TotalStorage... (0 Replies)
Discussion started by: filosophizer
0 Replies
4. AIX
hello Folks,
my vio:
$ lsmap -all
SVSA Physloc Client Partition ID
--------------- -------------------------------------------- ------------------
vhost0 U9117.MMA.6534BE4-V2-C11 0x00000003
VTD ... (0 Replies)
Discussion started by: filosophizer
0 Replies
5. Solaris
How to identify the server is BOOT FROM SAN.
Also how one can find from which device it is booted?
Thanks
Rahul
Double post, continued here (0 Replies)
Discussion started by: rahul.kurumkar
0 Replies
6. AIX
:wall::wall::wall:
1. I have created an LPAR in the HMC.
2. I have allocated the storage from an Hitachi AMS2500 and assigned it to the host group.
3. I have zoned the LPAR and Storage on a Brocade 5100. (The zone sees the AMS)
Next I activated the LPAR in the HMC, SMS mode for the mksysb... (3 Replies)
Discussion started by: Dallasguy7
3 Replies
7. AIX
hi all i have entered Aix environment 4 months had experienced in linux
what i am facing is i am unable to do sort of RnD with aix like
installation on my own, creating vgs managing networks, the VIOS, storage,lpars,
So we have a setup here almost all are in live production environment
with... (4 Replies)
Discussion started by: vax
4 Replies
8. AIX
Dear All,
I created a new partition through "Integrated Virtualization Manager" but there have an error when I added a new disk to the partition. The disk already created without any issue,
Below error is to add the disk to the partition
An error occured while modifying the assignments... (5 Replies)
Discussion started by: lckdanny
5 Replies
9. AIX
Hi all,
In my system, I have HMC 7 with Power Machine 6 & 7. On the managed system, we have many lpars.
In some lpars, I can see they are using virtual fiber channel to connect to DS8K storage. In search with google, I understand that it is configured with VIOS server to share the physical FC... (7 Replies)
Discussion started by: Phat
7 Replies
10. UNIX for Beginners Questions & Answers
We have 2 LPAR. LPAR #1 have a Application, Database Server process (ctree Server) and SAN+Physical Table. LPAR#2 has only Application.
Both Application process are connected to Database via C-tree Server Process (Running on LPAR #1..
We want to keep one Active C-tree Server and one Backup... (1 Reply)
Discussion started by: gabhanes
1 Replies
LEARN ABOUT OPENDARWIN
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)