_____________________________________________________________________________________________
For AIX Version 3, choose the limited function maintenance shell (option 5 for AIX 3.1, option 4 for AIX 3.2).
If you only have one disk on the system, then hdisk0 will be used in the execution of the getrootfs or /etc/continue commands, which follow. If you have more than one disk, determine which disk contains the boot logical volume in this manner:
AIX 3.2.4 or AIX 3.2.5:
Run getrootfs; the output will indicate which disk contains the hd5 logical volume.
AIX 3.1 to AIX 3.2.3e:
Run lqueryvg -Ltp hdisk# for each hdisk. You can obtain a listing of these with the command lsdev -Cc disk. Repeat this command until you get output similar to the following:
Now, access the rootvg volume group by running one of the following commands, using the disk you obtained in the preceding step:
Example:
Example:
Now you may select one of two options: Access this volume group and start a shell , option 1, or Access this volume group and start a shell before mounting file systems , option 2. Option 2 allows you to perform file system maintenance on /, /usr, /tmp, and /var before mounting them.
NOTE: If you intend to use SMIT or vi, set your terminal type in preparation for editing the file. xxx stands for a terminal type such as lft, ibm3151, or vt100.
_____________________________________________________________________________________________
lspv
hdisk0 00cd95149e2914b0 rootvg active
-bash-3.2# mount
node mounted mounted over vfs date options
-------- --------------- --------------- ------ ------------ ---------------
/dev/hd4 / jfs2 Jan 07 09:22 rw,log=/dev/hd8
/dev/hd2 /usr jfs2 Jan 07 09:22 rw,log=/dev/hd8
/dev/hd9var /var jfs2 Jan 07 09:22 rw,log=/dev/hd8
/dev/hd3 /tmp jfs2 Jan 07 09:22 rw,log=/dev/hd8
/dev/hd1 /home jfs2 Jan 07 09:22 rw,log=/dev/hd8
/dev/hd11admin /admin jfs2 Jan 07 09:22 rw,log=/dev/hd8
/proc /proc procfs Jan 07 09:22 rw
/dev/hd10opt /opt jfs2 Jan 07 09:22 rw,log=/dev/hd8
/dev/livedump /var/adm/ras/livedump jfs2 Jan 07 09:22 rw,log=/dev/ hd8
En la PMUX1LABO no existe el disco hdisk0, en su lugar aparecen los listados de los cuatro discos
hdisk0
hdisk4
hdisk8
hdisk12
con el mismo identificador 00cd95149cc1f8dd
Si hago un lsdev -Cc adapter se ve que falta el dispositivo fcs0
solo nos muestra el fcs1 el cual nos da acceso a los discos hdisk8 y hdisk12
/SPOT/usr/sbin/cfgmgr
Para volver a configurar el dispositivo fcs0 ejecute esto
cfgmgr -l fcs0
y al hacer lsdev -Cc adapter quedó visible
Para ver los detalles lqueryvg -p hdisk8 -Avt
Borro de la odm a fcs0
odmdelete -o CuDv -q name=fcs0
Si hago un lsdev -Cc adapter ya no tengo fcs0
ahora ejecuto cfgmgr -l fcs0
Para ver todas las definiciones en la ODM
odmget CuDv
lqueryvg -Ltp hdisk#
Busco getrootfs con find / -name getrootfs
/SPOT/usr/lib/boot/getrootfs
Accessing rootvg and mounting file systems
For AIX Version 3, choose the limited function maintenance shell (option 5 for AIX 3.1, option 4 for AIX 3.2).
If you only have one disk on the system, then hdisk0 will be used in the execution of the getrootfs or /etc/continue commands, which follow. If you have more than one disk, determine which disk contains the boot logical volume in this manner:
AIX 3.2.4 or AIX 3.2.5:
Run getrootfs; the output will indicate which disk contains the hd5 logical volume.
AIX 3.1 to AIX 3.2.3e:
Run lqueryvg -Ltp hdisk# for each hdisk. You can obtain a listing of these with the command lsdev -Cc disk. Repeat this command until you get output similar to the following:
00005264feb3631c.2 hd5 1If more than one disk contains this output, use any disk when running getrootfs.
Now, access the rootvg volume group by running one of the following commands, using the disk you obtained in the preceding step:
AIX 3.1: /etc/continue hdisk# AIX 3.2.0-3.2.3e: getrootfs -f hdisk# AIX 3.2.4-3.2.5: getrootfs hdisk#NOTE: If you want to leave the primary OS file systems (/, /usr, /tmp, and /var) unmounted after this command has completed, to run fsck, for instance, place a space and the letters sh after the hdisk in the preceding command. For example:
getrootfs hdisk0 shFor AIX Version 4, choose Start Maintenance Mode for System Recovery , option 3. The next screen will be called Maintenance; select option 1, Access a Root Volume Group. At the next screen, type 0 to continue, and select the appropriate volume group by typing the number next to it. A screen like the following will display.
Example:
Access a Root Volume GroupType the number for a volume group to display the logical volume information and press Enter.
1) Volume Group 0073656f2608e46a contains these disks: hdisk0 2063 04-C0-00-4,0Once a volume group has been selected, information will be displayed about that volume group.
Example:
Volume Group Information ------------------------------------------------------------------------------ Volume Group ID 0073656f2608e46a includes the following logical volumes: hd6 hd5 hd8 hd4 hd2 hd9var hd3 hd1 ------------------------------------------------------------------------------Type the number of your choice and press Enter.
1) Access this Volume Group and start a shell 2) Access this Volume Group and start a shell before mounting filesystems 99) Previous MenuIf the logical volumes listed do not include logical volumes like hd4, hd2, hd3, and so on, you may have selected the wrong volume group. Press 99 to back up one screen and select again.
Now you may select one of two options: Access this volume group and start a shell , option 1, or Access this volume group and start a shell before mounting file systems , option 2. Option 2 allows you to perform file system maintenance on /, /usr, /tmp, and /var before mounting them.
NOTE: If you intend to use SMIT or vi, set your terminal type in preparation for editing the file. xxx stands for a terminal type such as lft, ibm3151, or vt100.
TERM=<xxx> export TERMErrors from these steps may indicate failed or corrupt disks in rootvg. These problems should be corrected. For additional assistance, contact your vendor, your local branch office, or your AIX support center.
_____________________________________________________________________________________________
lspv
hdisk0 00cd95149e2914b0 rootvg active
-bash-3.2# mount
node mounted mounted over vfs date options
-------- --------------- --------------- ------ ------------ ---------------
/dev/hd4 / jfs2 Jan 07 09:22 rw,log=/dev/hd8
/dev/hd2 /usr jfs2 Jan 07 09:22 rw,log=/dev/hd8
/dev/hd9var /var jfs2 Jan 07 09:22 rw,log=/dev/hd8
/dev/hd3 /tmp jfs2 Jan 07 09:22 rw,log=/dev/hd8
/dev/hd1 /home jfs2 Jan 07 09:22 rw,log=/dev/hd8
/dev/hd11admin /admin jfs2 Jan 07 09:22 rw,log=/dev/hd8
/proc /proc procfs Jan 07 09:22 rw
/dev/hd10opt /opt jfs2 Jan 07 09:22 rw,log=/dev/hd8
/dev/livedump /var/adm/ras/livedump jfs2 Jan 07 09:22 rw,log=/dev/ hd8
En la PMUX1LABO no existe el disco hdisk0, en su lugar aparecen los listados de los cuatro discos
hdisk0
hdisk4
hdisk8
hdisk12
con el mismo identificador 00cd95149cc1f8dd
Si hago un lsdev -Cc adapter se ve que falta el dispositivo fcs0
solo nos muestra el fcs1 el cual nos da acceso a los discos hdisk8 y hdisk12
/SPOT/usr/sbin/cfgmgr
Para volver a configurar el dispositivo fcs0 ejecute esto
cfgmgr -l fcs0
y al hacer lsdev -Cc adapter quedó visible
Para ver los detalles lqueryvg -p hdisk8 -Avt
Borro de la odm a fcs0
odmdelete -o CuDv -q name=fcs0
Si hago un lsdev -Cc adapter ya no tengo fcs0
ahora ejecuto cfgmgr -l fcs0
Para ver todas las definiciones en la ODM
odmget CuDv
lqueryvg -Ltp hdisk#
Busco getrootfs con find / -name getrootfs
/SPOT/usr/lib/boot/getrootfs
Comentarios
Publicar un comentario