1752720 Members
5572 Online
108789 Solutions
New Discussion

Who Me Too'd this topic

Ken_152
Frequent Visitor

11.31 Recovery Shell giving errors

Hello all.
I am attempting to rebuild an 11.31 kernel by booting the HP-UX Recovery Shell from an Ignite Server (Ignite C.7.5.142) and I get getting errors:
Transcript follows:
*************************************************
***************************************************************************
HP-UX NETWORK 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: r
Getting into recovery mode...




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 c3t6d0.
The hardware path to disk is 1/0/1/1/0/1/1.6.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: a
Setting boot and root device file for c3t6d0...
Loading /sbin/umount...


HP-UX Recovery MENU

Use this menu to select the level of recovery desired.

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.

m. Return to 'HP-UX Recovery Media Main Menu'.
x. Exit to the shell.

Selection: a
Entering file system checking...






FILE SYSTEM CHECK MENU

The file system check 'fsck -y /dev/rdsk/c3t6d0'
will now be executed.

Select one of the following:
a. Run fsck -y.
b. Prompt for the fsck execution string on c3t6d0.

m. Return to the 'HP-UX Recovery MENU.'

Selection: a
Loading /sbin/fsck...




** /dev/rdsk/c3t6d0
BAD SUPER BLOCK: MAGIC NUMBER WRONG
USE -b OPTION TO FSCK TO SPECIFY LOCATION OF AN ALTERNATE SUPER-BLOCK TO SUPPLY NEEDED INFORMATION; SEE fsck(1M).
'fsck' could not fix all customer file system errors with the options and answers specified. You may wish to run 'fsck' again with different options or attempt to repair the file system with the 'fsck -b' option to use a redundant superblock. Automatic recovery cannot be completed unless the target file system can be successfully 'fsck'ed.
***********************************************

It does look strange to me that the fsck is running against /dev/rdsk/c3t6d0. Surely it should be fsck'ing the O/S partition?
Upgrading the Ignite server may be an obvious potential solution, but is not an option at the moment.

Any ideas appreciated.
Thanks...
Who Me Too'd this topic