 |
» |
|
|
|
Expert recovery enables you to recover a root disk or root volume group with software
damage. With this method, you repair the boot/root disk and root volume
group from your Ignite-UX server or HP-UX core media. Once the recovery
system has been booted, you can: Expert recovery does not require that you complete
any preparation before you use it. The media used is supplied by HP
so it does not contain any customization you may have on your system.
In addition to using boot media, you can also
boot from your Ignite-UX server. Depending on the failure cause, expert recovery
gives you enough capabilities to recover HP-UX onto your system. At
that point, you need to recover your data files using a restore tool
to completely recover your system to the state it was in before the
problem occurred. Expert recovery is not useful in recovering from
hardware failures. Expert Recovery Using the Core Media | |
If your system
should become compromised or corrupt and will not boot to a login
prompt, or the system boots but critical operating system files are
corrupted, adversely affecting overall system operation, it may be
useful to restore system elements with core recovery media. The more you know about the system disk and its
partitioning scheme before you encounter major damage or
corruption, the easier it will be for you to recover. Much of this information, including file system types, can be obtained by accessing your
online system manifest, either using Ignite-UX
or by reading the hardcopy that came with your system. Before you attempt to recover an HP-UX system,
you should have the following information about your system disk available: The hardware path of the root file system on the disk (that is, what file system
you will be checking/repairing using fsck.) The address of the LIF volume (bootlif) path of that disk. What the AUTO file in the LIF volume should contain. Whether you have an LVM,
VxVM, or whole-disk system.
The procedures that follow assume that both fsck and mount can be run successfully
on the system disk; otherwise, the following procedures are not applicable. Automated Recovery Procedures There
are two possible expert recovery situations that occur after a system
problem. Each has an associated recovery procedure: The system does not boot
to the HP-UX boot loader prompt (ISL for PA-RISC
systems and EFI Boot Manager for Itanium-based
systems) from a known good root file system. Procedure: On the system disk, rebuild the LIF
volume on PA-RISC systems or the EFI, HP Service Partition, and HP-UX
partitions on Itanium-based systems. Then, install all critical operating
system files required to boot on the root file
system. See "Recovering the LIF/EFI Volume and Critical HP-UX Files " below. The system boots to the
HP-UX boot loader prompt, but cannot boot vmunix. This means that the kernel cannot be found,
is corrupted or the file systems are corrupt
or damaged. Procedure: Install only the
critical operating system files required to boot on the root file system. See “Recovering Critical HP-UX Files Only ”. If you believe the kernel is corrupted,
then replace only the kernel on the root file
system. See “Recovering the Kernel Only ”.
Recovering the LIF/EFI Volume and Critical HP-UX Files Following is an example of the procedure for rebuilding
the LIF volume of the system disk and for installing all the critical
operating system files necessary to boot from the root file system. | | | |  | NOTE: The following example requires the use of the
core operating system media for the appropriate version of HP-UX. | | | | |
Boot
your system from the media device to begin the recovery process. For
specific information regarding how to boot your system from an alternate
boot source, see the HP-UX System Administrator’s
Guide for HP-UX 11i v3, or the Managing Systems
and Workgroups: A Guide for HP-UX System Administrators manual. The following menu appears once
the booting process from the media device is complete: Welcome to the HP-UX installation/recovery process!
Use the <tab> key to navigate between fields, and the arrow keys
within fields. Use the <return/enter> key to select an item.
Use the <return/enter> or <space-bar> to pop-up a choices list. If the
menus are not clear, select the "Help" item for more information.
Hardware Summary: System Model: ia64 hp server rx2600
+---------------------+----------------+-------------------+ [ Scan Again ]
| Disks: 2 ( 67.8GB) | Floppies: 0 | LAN cards: 4 |
| CD/DVDs: 1 | Tapes: 0 | Memory: 2036Mb |
| Graphics Ports: 0 | IO Buses: 4 | CPUs: 2 |[ H/W Details ]
+---------------------+----------------+-------------------+
[ Install HP-UX ]
[ Run a Recovery Shell ]
[ Advanced Options ]
[ Reboot ] [ Help ] |
Select Run a Recovery Shell. The next prompt is: Would you like to start up networking at this time? [n] |
Unless
you need networking to be able to ftp files to
or from other systems, press n. Ignite-UX installs the commands and mounts the file
systems necessary to the recovery. Upon completion, the HP-UX Core
Media System Recovery menu appears: HP-UX CORE MEDIA SYSTEM RECOVERY
MAIN MENU
s. Search for a file
b. Reboot
l. Load a file
r. Recover an unbootable HP-UX system
x. Exit to shell
This menu is for listing and loading the tools contained on the
core media. Once a tool is loaded, it may be run from the shell.
Some tools require other files to be present in order to
successfully execute.
Select one of the above: |
To
install a file or files, enter l at the prompt. NOTE: Loading some files may require other files/libraries to be
loaded.
If an attempt is made to load a file, and an error message is
encountered when the command is invoked, it may be useful to use
the chatr command (on a system that is up and running) to ensure
that dependencies are met. See chatr(1) for more details.
For some commands (vi, ftp, rcp), the dependent files will be
automatically loaded. For others, you need to load them
manually.
If you specify a filename of "all" a list of all the files
available will be displayed.
Filesystem kbytes used avail %cap iused ifree iused Mounted on
/ 33980 15499 18481 46% 172 8468 2% ? |
Enter
the names of the damaged or corrupted files you want to install or
files that you need to repair the system. For example: ftp vi date grep | | | | | NOTE: In order to use ftp, networking
would have had to have been enabled in Step 3. | | | | |
The following example lists two files (ex and libm.so.1) that must be installed
before the files vi and grep can be installed. It also lists a file (date) that is not in the installation list. Adding dependent files to the list
NOTE :
Since ./usr/lib/hpux32/libm.so is linked to ./usr/lib/hpux32/libm.so.1
'./usr/lib/hpux32/libm.so.1' will be added to the list to load.
Adding dependent libraries for vi to the list
NOTE :
Since ./usr/bin/vi is linked to ./usr/bin/ex
'./usr/bin/ex' will be added to the list to load.
******** THE REQUESTED FILE(S): ***********
./usr/bin/ex ./usr/lib/hpux32/libm.so.1 ./usr/bin/ftp ./etc/inetsvcs.conf
./usrp
Is the above load list correct? [y/(n)] |
If
yes, the following messages appear: ********* downloading the files *******
x ./usr/lib/hpux32/libelf.so.1, 180044 bytes, 352 tape blocks
x ./usr/lib/hpux32/libm.so symbolic link to ./libm.so.1
x ./usr/lib/hpux32/libm.so.1, 1469944 bytes, 2871 tape blocks
x ./usr/lib/hpux32/libxcurses.so.1, 531640 bytes, 1039 tape blocks
x ./usr/lib/hpux32/libgss.so, 132132 bytes, 259 tape blocks
x ./usr/lib/hpux32/libcom_err.so, 22376 bytes, 44 tape blocks
x ./usr/lib/hpux32/libk5crypto.so, 177872 bytes, 348 tape blocks
x ./usr/lib/hpux32/libkrb5.so, 903932 bytes, 1766 tape blocks
x ./usr/bin/grep, 44572 bytes, 88 tape blocks
x ./usr/bin/ftp, 257816 bytes, 504 tape blocks
x ./usr/bin/ex, 553808 bytes, 1082 tape blocks
./usr/bin/vi linked to ./usr/bin/ex
x ./sbin/date, 542412 bytes, 1060 tape blocks
x ./etc/inetsvcs.conf, 15 bytes, 1 tape blocks
<Press return to continue> |
Press Enter and the Main Menu appears. To search for a file you
want to install, press s. Either enter the filename(s) to be searched for,or 'all' for a total
listing. |
Enter
the following command: vi awk /sbin/sh
date The following messages appear: ../usr/bin/vi linked to ./usr/bin/ex
./sbin/awk
./sbin/sh
./sbin/date
<Press return to continue> |
Press Enter to return to the HP-UX Core Media System Recovery
menu: HP-UX CORE MEDIA SYSTEM RECOVERY
MAIN MENU
s. Search for a file
b. Reboot
l. Load a file
r. Recover an unbootable HP-UX system
x. Exit to shell
This menu is for listing and loading the tools contained on the
core media. Once a tool is loaded, it may be run from the shell.
Some tools require other files to be present in order to
successfully execute.
Select one of the above: |
To
begin the system recovery, press r. DEVICE FILE VERIFICATION MENU
This menu is used to specify the path of the root file system.
When the information is correct, select ’a’.
INFORMATION to verify:
Device file used for ’/’(ROOT) is c1t15d0
The hardware path to disk is 0/0/1/1.15.0
Select one of the following:
a. The above information is correct.
b. WRONG!! The device file used for ’/’(ROOT) is incorrect.
m. Return to the ’HP-UX Recovery MENU.’
x. Exit to the shell.
Selection: |
Since c1t15d0 is the correct root device
filename, press a. |
HP-UX Recovery MENU
Select one of the following:
a. Mount the root disk and exit to a shell only.
b. Recover the bootlif/os partitions.
c. Replace the kernel on the root file system.
d. Both Options: b and c
v. Read information about VxVM Recovery (VXVM.RECOVER)
m. Return to ’HP-UX Recovery Media Main Menu’.
x. Exit to the shell.
Use this menu to select the level of recovery desired.
Selection: |
To
repair both the LIF/EFI volume (bootlif) and critical operating system files, press d. If your system is PA-RISC,
the following message appears: BOOTLIF PATH VERIFICATION MENU
This menu must be used to determine the path to the bootlif
(ISL, HPUX and the AUTO file).
When the information is correct, select 'a'.
INFORMATION to verify:
Path to the bootlif is 0/0/1/1.15.0
Select one of the following:
a. The above information is correct.
b. WRONG!!Prompt user for a new bootlif path.
m. Return to the 'HP-UX Recovery MENU.'
x. Exit to the shell.
Selection: |
Assuming the bootlif path
displayed is correct, press a. For both PA-RISC and Itanium-based systems, the
following message appears next: BOOT STRING VERIFICATION MENU
This menu must be used to verify the system's boot string.
When the information is correct, select 'a'.
The system's boot string is currently: 'boot vmunix'
When correct this string will be placed in the AUTO file.
Select one of the following:
a. The above information is correct.
b. WRONG!! Prompt the user for a new system's boot string.
m. Return to the 'HP-UX Recovery MENU.'
x. Exit to the shell.
Selection: |
Assuming
that the boot string is correct, press a. FILE SYSTEM CHECK
MENU
The file system check '/sbin/fs/vxfs/fsck -y /dev/rdsk/c2t0d0s4'
will now be run.
Select one of the following:
a. Run fsck -y.
b. Prompt for the fsck run string on c2t0d0s4.
m. Return to the 'HP-UX Recovery MENU.'
Selection: |
Press a to execute fsck -y to check your file systems for corruption. Loading /sbin/fs/vxfs/fsck...
Doing fsck on /ROOT file system
Loading /sbin/fs/vxfs/fsck...
/sbin/fs/vxfs/fsck -y /dev/rdsk/c2t0d0s5
file system is clean - log replay is not required
Mount /ROOT file system
/sbin/fs/vxfs/mount /dev/dsk/c2t0d0s5 /ROOT
Loading mount commands ...
Mount /ROOT/stand again
/sbin/fs/vxfs/mount -F vxfs /dev/dsk/c2t0d0s4 /ROOT/stand
vxfs mount: Cannot open portal device: No such file or directory
Entering loading kernel....
Filesystem kbytes used avail %cap iused ifree iused Mounted on
/ROOT 1024000 316688 702120 31% 5109 22091 19% ?
Filesystem kbytes used avail %cap iused ifree iused Mounted on
/ROOT/stand 311296 118008 191824 38% 112 6032 2% ?
The default action is to keep the existing kernel /stand/vmunix.
If you want to replace the old kernel (/stand/vmunix) with downloading
a kernel,the /stand/vmunix will be saved to /stand/vmunixBK.
Do you want to download a new kernel? [y/(n)] |
Assuming
your file system is not corrupted, and you want to continue with the
system recovery, press Return to mount your root
file system under the / (root) directory. To
overwrite the existing kernel with the new kernel, press y at the prompt. '/stand/vmunix' has been saved as '/stand/vmunixBK'
Downloading IINSTALL to /stand/vmunix
=================================================================
The root disk has been mounted under /ROOT, if you want to chroot
to this directory type the commands:
loadfile chroot
chroot /ROOT /sbin/sh
# |
Complete
the recovery process by entering reboot at the
shell prompt. NOTE: System rebooting...
NOTE: run_cmd: Process: 84 (/sbin/sh): killed by signal: 9.
sync'ing disks (0 buffers to flush):
0 buffers not flushed
0 buffers still dirty
Closing open logical volumes...
Done
.
.
.
Console Login: |
Your Itanium-based system might not
be configured to automatically boot to multiuser
mode. If this is the case you will be booted to single-user mode,
and the boot sequence must be completed manually. Enter init 3 to bring a single-user mode Itanium-based system
to multiuser mode: .
.
.
INIT: Overriding default level with level ’s’
INIT: SINGLE USER MODE
INIT: Running /sbin/sh
# init 3 |
For detailed information regarding the boot sequence,
see the HP-UX System Administrator’s Guide for HP-UX 11i v3, or Managing Systems and Workgroups:
A Guide for HP-UX System Administrators, and the hardware
documentation for your system. | | | |  | IMPORTANT: If your PA-RISC system
is running VxVM, the system will boot to single-user mode. You must
execute the following steps to bring a single-user mode PA-RISC system
to multiuser mode:To start the VxVM configuration daemon, at the shell prompt enter vxconfigd List the contents of the
root disk, enter: vxdisk list Messages similar to the following appear: DEVICE TYPE DISK GROUP STATUS
c2t0d0 simple - - online
c2t1d0 simple - - online
c3t2d0 simple rootdisk01 rootdg online |
Start all of the disabled
volumes, execute vxvol -g rootdg
startall Mount all VxVM volumes,
execute mountall Update the boot program
on the root disk, enter: mkboot
-l /dev/rdsk/c1t15d0 Update the information
contained in the LABEL file for the LIF disk,
enter: vxvmboot -v /dev/rdsk/c3t2d0 Messages similar to the following appear: LIF Label File @ (1k) block # 834 on LVM Disk /dev/rdsk/c3t2d0:
Label Entry: 0, Boot Volume start: 2912; length: 140011 MB |
For systems executing
HP-UX 11i v1 (B.11.11) only, execute the following
commands: mv /etc/resolv.conf /etc/resolv.conf.save
/sbin/rc1.d/S320hostname start
/sbin/rc2.d/S008net.init start
swagentd
mv /etc/resolv.conf.save /etc/resolv.conf Configure the system boot
information on the boot disk, enter: /etc/vx/bin/vxbootsetup -g rootdg rootdisk01 Update the LABEL file once again, enter: vxvmboot
-v /dev/rdsk/c3t2d0 Complete the PA-RISC recovery
process by entering reboot. The system will now
boot correctly to multiuser mode.
| | | | |
This completes the process for rebuilding the
LIF volume and installing critical operating system files. Recovering Critical HP-UX Files Only The following example is the procedure for installing
all the critical operating system files necessary to boot on the client root file system. Boot
your system from the media device to begin the recovery process. For
specific information regarding how to boot your system from an alternate
boot source, see the HP-UX System Administrator’s
Guide for HP-UX 11i v3, or Managing Systems
and Workgroups: A Guide for HP-UX System Administrators manual. The following menu appears once
the booting process from the media device is complete: Welcome to the HP-UX installation/recovery process!
Use the <tab> key to navigate between fields, and the arrow keys
within fields. Use the <return/enter> key to select an item.
Use the <return/enter> or <space-bar> to pop-up a choices list. If the
menus are not clear, select the "Help" item for more information.
Hardware Summary: System Model: ia64 hp server rx2600
+---------------------+----------------+-------------------+ [ Scan Again ]
| Disks: 2 ( 67.8GB) | Floppies: 0 | LAN cards: 4 |
| CD/DVDs: 1 | Tapes: 0 | Memory: 2036Mb |
| Graphics Ports: 0 | IO Buses: 4 | CPUs: 2 |[ H/W Details ]
+---------------------+----------------+-------------------+
[ Install HP-UX ]
[ Run a Recovery Shell ]
[ Advanced Options ]
[ Reboot ] [ Help ] |
Select Run a Recovery Shell. The display clears, and
the following query appears: Would you like to start up networking at this time? [n] |
Unless
you need networking to be able to ftp files to
or from other systems, press n. Ignite-UX installs the commands and mounts the file
systems necessary to the recovery. Upon completion, the HP-UX Core
Media System Recovery menu appears: HP-UX CORE MEDIA SYSTEM RECOVERY
MAIN MENU
s. Search for a file
b. Reboot
l. Load a file
r. Recover an unbootable HP-UX system
x. Exit to shell
This menu is for listing and loading the tools contained on the
core media. Once a tool is loaded, it may be run from the shell.
Some tools require other files to be present in order to
successfully execute.
Select one of the above: |
To
begin the actual system recovery, press r. DEVICE FILE VERIFICATION MENU
This menu is used to specify the path of the root file system.
When the information is correct, select ’a’.
INFORMATION to verify:
Device file used for ’/’(ROOT) is c1t15d0
The hardware path to disk is 0/0/1/1.15.0
Select one of the following:
a. The above information is correct.
b. WRONG!! The device file used for ’/’(ROOT) is incorrect.
m. Return to the ’HP-UX Recovery MENU.’
x. Exit to the shell.
Selection: |
If
the root device is correct, press a (press b to provide the correct root device.) HP-UX Recovery MENU
Select one of the following:
a. Mount the root disk and exit to a shell only.
b. Recover the bootlif/os partitions.
c. Replace the kernel on the root file system.
d. Both Options: b and c
v. Read information about VxVM Recovery (VXVM.RECOVER)
m. Return to ’HP-UX Recovery Media Main Menu’.
x. Exit to the shell.
Use this menu to select the level of recovery desired.
Selection: |
To
install critical operating system files only, press b. Loading commands needed for boot recovery...
Entering boot area repairing ....
Loading commands needed for boot recovery...
Verification of partitions on /dev/rdsk/c2t0d0 completed OK.
Running mkboot to verify/repair boot areas
Ignore the following question, and wait a few seconds...
BOOT STRING VERIFICATION MENU
This menu must be used to verify the system's boot string.
When the information is correct, select 'a'.
The system's boot string is currently: 'boot vmunix'
When correct this string will be placed in the AUTO file.
Select one of the following:
a. The above information is correct.
b. WRONG!! Prompt the user for a new system's boot string.
m. Return to the 'HP-UX Recovery MENU.'
x. Exit to the shell.
Selection: |
Assuming
that the system’s boot string is correct, press a. HPUX.EFI 4/11/2005 536124
The disk is LVM
Setting boot and root device file for c2t0d0...
Loading /sbin/umount ......
HP-UX Recovery MENU
Select one of the following:
a. Mount the root disk and exit to a shell only.
b. Recover the bootlif/os partitions.
c. Replace the kernel on the root file system.
d. Both Options: b and c
v. Read information about VxVM Recovery (VXVM.RECOVER)
m. Return to ’HP-UX Recovery Media Main Menu’.
x. Exit to the shell.
Use this menu to select the level of recovery desired.
Selection: |
Exit
to the shell by pressing x. Loading /sbin/umount ......
# |
Complete
the recovery process by entering reboot at the
shell prompt. NOTE: System rebooting...
NOTE: run_cmd: Process: 84 (/sbin/sh): killed by signal: 9.
sync'ing disks (0 buffers to flush):
0 buffers not flushed
0 buffers still dirty
Closing open logical volumes...
Done
.
.
.
Console Login: |
Your system might not be configured to automatically
boot to multiuser mode. If this is the case, you must complete the
boot sequence manually. For detailed information regarding the boot
sequence, see the HP-UX System Administrator’s Guide for HP-UX 11i v3, or Managing Systems and Workgroups:
A Guide for HP-UX System Administrators, and the hardware
documentation for your system.
This completes the process for recovering critical
operating system files only. Recovering the Kernel Only It may be necessary to recover only the kernel if all kernels in the /stand directory were removed inadvertently and then the system was rebooted.
If the current kernel fails to boot and backup kernels exist, you
should attempt to boot from those kernels before replacing the current
kernel. | | | | | NOTE: Replacing the kernel removes any tunable settings
that existed for the old kernel. When you have booted the system from
the replaced kernel, create a new kernel and reapply any tunable changes
you have previously made, or recover a kernel from your backups that
was known to work. You must reboot the system from the new or recovered
kernel to begin using that kernel. | | | | |
The following example is the detailed procedure
for recovering the kernel in the client root file
system. Boot
your system from the media device to begin the recovery process. For
specific information regarding how to boot your system from an alternate
boot source, see the HP-UX System Administrator’s
Guide for HP-UX 11i v3, or Managing Systems
and Workgroups: A Guide for HP-UX System Administrators manual. The following menu appears when
the booting process from the media device is complete: Welcome to the HP-UX installation/recovery process!
Use the <tab> key to navigate between fields, and the arrow keys
within fields. Use the <return/enter> key to select an item.
Use the <return/enter> or <space-bar> to pop-up a choices list. If the
menus are not clear, select the "Help" item for more information.
Hardware Summary: System Model: ia64 hp server rx2600
+---------------------+----------------+-------------------+ [ Scan Again ]
| Disks: 2 ( 67.8GB) | Floppies: 0 | LAN cards: 4 |
| CD/DVDs: 1 | Tapes: 0 | Memory: 2036Mb |
| Graphics Ports: 0 | IO Buses: 4 | CPUs: 2 |[ H/W Details ]
+---------------------+----------------+-------------------+
[ Install HP-UX ]
[ Run a Recovery Shell ]
[ Advanced Options ]
[ Reboot ] [ Help ] |
Select Run a Recovery Shell. The display clears, and
the following query appears: Would you like to start up networking at this time? [n] |
Unless
you need networking to be able to ftp files to
or from other systems, press n. Ignite-UX installs the commands and mounts the file
systems necessary to the recovery. Upon completion, the HP-UX Core
Media System Recovery menu appears: HP-UX CORE MEDIA SYSTEM RECOVERY
MAIN MENU
s. Search for a file
b. Reboot
l. Load a file
r. Recover an unbootable HP-UX system
x. Exit to shell
This menu is for listing and loading the tools contained on the
core media. Once a tool is loaded, it may be run from the shell.
Some tools require other files to be present in order to
successfully execute.
Select one of the above: |
To
begin the actual system recovery, press r. DEVICE FILE VERIFICATION MENU
This menu is used to specify the path of the root file system.
When the information is correct, select ’a’.
INFORMATION to verify:
Device file used for ’/’(ROOT) is c1t15d0
The hardware path to disk is 0/0/1/1.15.0
Select one of the following:
a. The above information is correct.
b. WRONG!! The device file used for ’/’(ROOT) is incorrect.
m. Return to the ’HP-UX Recovery MENU.’
x. Exit to the shell.
Selection: |
If
the root device is correct, press a (press b to provide the correct root device). HPUX.EFI 4/11/2005 536124
The disk is LVM
Setting boot and root device file for c2t0d0...
Loading /sbin/umount ......
HP-UX Recovery MENU
Select one of the following:
a. Mount the root disk and exit to a shell only.
b. Recover the bootlif/os partitions.
c. Replace the kernel on the root file system.
d. Both Options: b and c
v. Read information about VxVM Recovery (VXVM.RECOVER)
m. Return to ’HP-UX Recovery Media Main Menu’.
x. Exit to the shell.
Use this menu to select the level of recovery desired.
Selection: |
Press c to rebuild only the kernel. FILE SYSTEM CHECK
MENU
The file system check '/sbin/fs/vxfs/fsck -y /dev/rdsk/c2t0d0s4'
will now be run.
Select one of the following:
a. Run fsck -y.
b. Prompt for the fsck run string on c2t0d0s4.
m. Return to the 'HP-UX Recovery MENU.'
Selection: |
Press a to execute fsck -yto check your file systems for corruption. Loading /sbin/fs/vxfs/fsck...
Doing fsck on /ROOT file system
Loading /sbin/fs/vxfs/fsck...
/sbin/fs/vxfs/fsck -y /dev/rdsk/c2t0d0s5
file system is clean - log replay is not required
Mount /ROOT file system
/sbin/fs/vxfs/mount /dev/dsk/c2t0d0s5 /ROOT
Loading mount commands ...
Mount /ROOT/stand again
/sbin/fs/vxfs/mount -F vxfs /dev/dsk/c2t0d0s4 /ROOT/stand
vxfs mount: Cannot open portal device: No such file or directory
Entering loading kernel....
Filesystem kbytes used avail %cap iused ifree iused Mounted on
/ROOT 1024000 316688 702120 31% 5109 22091 19% ?
Filesystem kbytes used avail %cap iused ifree iused Mounted on
/ROOT/stand 311296 118008 191824 38% 112 6032 2% ?
The default action is to keep the existing kernel /stand/vmunix.
If you want to replace the old kernel (/stand/vmunix) with downloading
a kernel,the /stand/vmunix will be saved to /stand/vmunixBK.
Do you want to download a new kernel? [y/(n)] |
To
overwrite the existing kernel with the new kernel, press y at the prompt. '/stand/vmunix' has been saved as '/stand/vmunixBK'
Downloading IINSTALL to /stand/vmunix
=================================================================
The root disk has been mounted under /ROOT, if you want to chroot
to this directory type the commands:
loadfile chroot
chroot /ROOT /sbin/sh
# |
Complete
the recovery process by entering reboot at the
shell prompt. NOTE: System rebooting...
NOTE: run_cmd: Process: 84 (/sbin/sh): killed by signal: 9.
sync'ing disks (0 buffers to flush):
0 buffers not flushed
0 buffers still dirty
Closing open logical volumes...
Done
.
.
.
Console Login: |
Your system might not be configured to automatically
boot to multiuser mode. If this is the case, complete the boot sequence
manually. For detailed information regarding the boot sequence, see
the HP-UX System Administrator’s Guide for HP-UX 11i v3, or Managing Systems and Workgroups:
A Guide for HP-UX System Administrators, and the hardware
documentation for your system.
This completes the process for rebuilding the
kernel only. |
Printable version
