10 More Discussions You Might Find Interesting
1. AIX
Hi,
when I boot I get an E1DC error code. I've looked it up and it says that this error occurs during the firmware check. But the error is called "Dynamic Console Selection" .
1- Machine stopped at LCD led display = E1DC = CA00E1DC
E1DC Dynamic console selection. (maybe cable or keyboard)... (3 Replies)
Discussion started by: filosophizer
3 Replies
2. AIX
Hi guys,
My company just bought pseries server from ibm,
would like to ask , if first i need to install HMC for creating lpars ?
or first i need to install aix , and then install hmc?
Thx, (3 Replies)
Discussion started by: prpkrk
3 Replies
3. AIX
Hello,
I'm very rookie to AIX and attempting to install AIX. I have vio ready on the machine and don't know how to install OS? Inserted Volume 1 DVD into the ROM, don't know what to do next. Searched many forum but cant find the this basic thing. Please let me know how to install AIX on this... (4 Replies)
Discussion started by: pjeedu2247
4 Replies
4. AIX
Hello,
I installed PowerVM IVM Virtual I/O on P-550 but later found out that the machine isn't activated for CoD VET code for virtualization.
So when booted , it goes into OPEN Firmware
I/O Hosting requires a hosting partition boot not permitted exit called
> ok
Panel shows > IO... (3 Replies)
Discussion started by: filosophizer
3 Replies
5. AIX
Hello,
Lets say for simplicity that I do not use any vlan config inside my server - one lpar group use hea physical port1, another group hea physical port2. Physical port1 configured as vlan1 on external switch, physical port2 as vlan2.
What is the common practice - should I isolate my vios... (0 Replies)
Discussion started by: vilius
0 Replies
6. Linux
Anyone can help me answer the question.
Why does they use Linux on IBM pSeries not AIX.
I can't understand why, cause AIX is the best supporting from IBM pSeries.
Tks you. (3 Replies)
Discussion started by: quan0509
3 Replies
7. AIX
Hello Gurus,
i'm quite new person in AIX world, actually i'm SAP consultant. But due to my job faced with AIX.
Trying to configure new server for installation SAP. We have 4 disks one of them (hdisk3) has VG rootvg. How i can extend rootvg with another disk?
i tried:
# extendvg rootvg hdisk0... (2 Replies)
Discussion started by: sapbcer
2 Replies
8. AIX
Hi All --
I have an old 7028-6C1 which I'm using to learn AIX. The system didn't include a graphics card, so I connected via the serial port and performed a fresh install of AIX 5L V5.3.
Later, I purchased a GXT135P (2849) graphics card, and added it to the system. When I ran diag, I was able... (2 Replies)
Discussion started by: i386tech
2 Replies
9. UNIX for Dummies Questions & Answers
I'm new with UNIX, i have a pseries server from IBM and i need to install AIX 4.3, i never used wyse terminal or AIX, i need help to know how to install it, i have the server and the wyse i get in into the aixterm, over com1 but i don't know wich command use or what to do to install it..... ... (0 Replies)
Discussion started by: Juan-ito
0 Replies
10. AIX
I have been given some pSeries AIX servers to maintain. One of the servers wont come up after a shutdown and the following code is showing on the server:
10118401
How do I look up the error code? (2 Replies)
Discussion started by: dangral
2 Replies
voldiskadd(8) System Manager's Manual voldiskadd(8)
NAME
voldiskadd - Adds one or more disks for use with the Logical Storage Manager
SYNOPSIS
/usr/sbin/voldiskadd disk-address-list
DESCRIPTION
The voldiskadd utility sets up new disks that are added to the system after the initial system installation and configures the disks for
use by the Logical Storage Manager. A valid disk label must exist on the disk before using the voldiskadd utility.
One or more disks may be specified using a disk-address-list. Disk addresses in the list have the form dskn (for the entire disk) or dsknp
(for a specific partition). When specifying multiple disks, use a space between entries. Disk address names relate directly to device names
in the /dev/disk directory.
For example, here are some valid voldiskadd disk-address-list specifications: # voldiskadd dsk1 # voldiskadd dsk2 dsk3a
The file, /etc/vol/disks.exclude, may be used to exclude disks from use by voldiskadd. Each line of the file specifies the name of a disk
to exclude (for example, dsk5).
The voldiskadd utility prompts the user for a disk group name and disk media name for the disks. If a new disk group name is specified,
that disk group is created for the new disks. If no disk group name is specified, the disks are left as unassigned replacement disks for
future use. If an existing disk group name is specified, the user is prompted for whether the disks should be designated as spares for the
disk group.
If a disk is found to already contain non-Logical Storage Manager partitioning, the user is asked whether the disk should be encapsulated.
Encapsulation turns each partition of the disk into a volume. A disk should be encapsulated if it contains file systems or data that should
not be overwritten. If encapsulation is not desired for a disk, the disk can be initialized as a new disk for use by the Logical Storage
Manager. For new disks, all space on the disk becomes free space in the disk's disk group.
Context-sensitive help is available at every prompt by typing ?. Also, a list option can be used to get information on available target
disks for an operation.
The voldiskadd utility supports the following general classes of actions: Initializing a disk with reserved regions and partitions.
Disk initialization is performed by calling voldisksetup command. Adding a disk to an existing disk group.
This operation can be performed independently of the initialization of the disk drive to add a disk's storage space to a disk
group's free space pool. The volassist command may subsequently allocate from that free space. The disk can also be added as a hot
spare device. Creating new disk groups in which to import new disks.
If no disk group exists for importing disks, the option of creating the disk group is offered. Encapsulating disks that have exist-
ing contents.
This is the default action for disks that do not have a valid, existing Logical Storage Manager private region, but that do have a
disk label. Encapsulation is performed by calling volencap. Reconnecting a drive that was temporarily inaccessible.
This situation is detected automatically, by noting that the specified drive has a disk ID that matches a disk media record with no
currently associated physical disk. After reconnection, any stale plexes referring the disk are reattached, and any stopped volumes
referring the disk are restarted. This reattach action is performed by calling the volrecover script.
ERRORS
You may receive the following messages when using the voldiskadd command:
Initialization of disk device special-device failed. Error: special-device or an overlapping partition is open.
This message indicates that the partition you specified or an overlapping partition on the disk is actively in use. The partition could be
a mounted UFS or AdvFS filesystem, initialized as an LSM disk or used as a swap device.
special-device is marked in use for fstype in the disklabel. If you continue with the operation you can possibly destroy existing data.
Would you like to continue?? [y,n,q,?] (default: n)
This message indicates that the fstype of a partition or an overlapping partition is set in the disk label. The voldiskadd command prints
this message to warn that a disk partition may have valid data which could be destroyed.
If you are sure that the disk partition does not have valid data and that the partition can be added to LSM, you can ignore the warning
message by entering y at the prompt. The voldiskadd command will proceed to initialize the disk partition and add it to LSM.
FILES
A list of disks to exclude from use by voldiskadd.
SEE ALSO
disklabel(8), volassist(8), voldisk(8), voldiskadm(8), voldisksetup(8), voldg(8), volintro(8)
voldiskadd(8)