12-27-2012
re: your other story - sounds as if you have been very busy!
I would only add that if you are not seeing console AFTER doing the ASMI reset you might have a motherboard issue.
Happy New Year!
This User Gave Thanks to MichaelFelt For This Post:
10 More Discussions You Might Find Interesting
1. 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
2. SuSE
Hi.
I was wondering if there was a way to get the PVIDs from the disks on a SuSE Enterprise 9 box. I have 2 hdisks from a VIO setup that have specific PVIDs. I'd like to match those 2 disk to the disks within the Linux box. Any tips?
thanks. (0 Replies)
Discussion started by: Stephan
0 Replies
3. 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
4. AIX
Hello,
I successfully entered VET activation key through HMC -> capacity on demand (CoD) -> advanced power virtualization -> activate VET Key .
But the option for VIOS creation is still not appearing.
VET information gives this :
Type de système : 8203
Numéro de série du système : XX-XXXX
CCIN... (2 Replies)
Discussion started by: astjen
2 Replies
5. AIX
Hi all please give me a link for IBM PowerVM (4 Replies)
Discussion started by: babinlonston
4 Replies
6. AIX
Hi,
When I try to login on my vios ivm website http://vios through the browser -- all three of them -- firefox , chrome , Internet Explorer , i get this error
http://vioserver/j_security_check
I have java installed on the machine from where i am trying to open up the IVM/VIOS webpage.
I... (2 Replies)
Discussion started by: filosophizer
2 Replies
7. AIX
I am facing problems in moving CD-ROM from one lpar to another.
CDROM can be seen on the POWERVM (IVM) server , but through the web-access if I move it ( assign it ) to LPAR it will be assigned. I run cfgmgr , and the cdrom does not show up in the LPAR. I firmly believe this is the reason why I... (2 Replies)
Discussion started by: filosophizer
2 Replies
8. AIX
A team member installed the wrong version of License Code on a Power 740 system used in our Development environment.
The system will no longer boot.
Does anyone have IBM documentation or experience to share on recovering a system that currently reports "Unsupported License Code version... (1 Reply)
Discussion started by: kevinedailey
1 Replies
9. AIX
coming from this thread: https://www.unix.com/aix/211107-ibm-power-pseries-open-firmware-boot-vios-powervm-vet-code.html
PowerVM, formerly known as Advanced Power Virtualization (APV), is a chargeable feature of IBM POWER5, POWER6, POWER7, POWER8, and POWER9 servers and is required for support... (0 Replies)
Discussion started by: filosophizer
0 Replies
10. AIX
Hello,
After installing on P6 which is POWERVM IVM VIOS enabled (VET CODE D21C77ACD9229817CA1F00002C10004164 )
i get this message
"I/O hosting requires a hosting partition - boot not permitted".
HMC was connected to the machine
then HMC was removed through ASMI
Searching on... (2 Replies)
Discussion started by: filosophizer
2 Replies
LEARN ABOUT REDHAT
pivot_root
PIVOT_ROOT(8) Maintenance Commands PIVOT_ROOT(8)
NAME
pivot_root - change the root file system
SYNOPSIS
pivot_root new_root put_old
DESCRIPTION
pivot_root moves the root file system of the current process to the directory put_old and makes new_root the new root file system. Since
pivot_root(8) simply calls pivot_root(2), we refer to the man page of the latter for further details.
Note that, depending on the implementation of pivot_root, root and cwd of the caller may or may not change. The following is a sequence for
invoking pivot_root that works in either case, assuming that pivot_root and chroot are in the current PATH:
cd new_root
pivot_root . put_old
exec chroot . command
Note that chroot must be available under the old root and under the new root, because pivot_root may or may not have implicitly changed the
root directory of the shell.
Note that exec chroot changes the running executable, which is necessary if the old root directory should be unmounted afterwards. Also
note that standard input, output, and error may still point to a device on the old root file system, keeping it busy. They can easily be
changed when invoking chroot (see below; note the absence of leading slashes to make it work whether pivot_root has changed the shell's
root or not).
EXAMPLES
Change the root file system to /dev/hda1 from an interactive shell:
mount /dev/hda1 /new-root
cd /new-root
pivot_root . old-root
exec chroot . sh <dev/console >dev/console 2>&1
umount /old-root
Mount the new root file system over NFS from 10.0.0.1:/my_root and run init:
ifconfig lo 127.0.0.1 up # for portmap
# configure Ethernet or such
portmap # for lockd (implicitly started by mount)
mount -o ro 10.0.0.1:/my_root /mnt
killall portmap # portmap keeps old root busy
cd /mnt
pivot_root . old_root
exec chroot . sh -c 'umount /old_root; exec /sbin/init'
<dev/console >dev/console 2>&1
SEE ALSO
chroot(1), mount(8), pivot_root(2), umount(8)
Linux Feb 23, 2000 PIVOT_ROOT(8)