unexpected inconsistency on root filesystem at boot

[Danial Howard]

I have HP B1000 workstation that I shut down this morning to attach a new monitor. Upon bootup, I get this message:

Checking root file system.
/dev/rroot: UNALLOCATED I=20745 OWNER=root MODE=0
/dev/rroot: SIZE=0 MTIME=Jun 20 11:51 2002
/dev/rroot: NAME=/tcb/files/auth/r/root
/dev/rroot: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
Root check done.
.
.
.
/sbin/ioinitrc:
mount: file system table may be corrupt
Unable to mount /stand - please check entries in /etc/fstab


How can I run fsck if I can't boot to single-user mode? Of all the files, why is the problem in root's tcb entry?

I'd like to discuss any options besides a cold install of HP-UX 11.0 and restore from tape.

[Paula J Frazer-Campbell]

Hi

Boot from ignite tape and then fsck files system.

Paula

[Arockia Jegan]

Boot from ignite tape. Go to the shell mode. And then run fsck to fix the issue.

[Martin Johnson]

Boot from the Maintenance CD.

Marty

[PIYUSH D. PATEL · Accepted solution]

Hi,

Try to boot into the single user mode by interrupting the boot sequence.

ISL > hpux -is -lm

Then see whether the root file system and /stand gets mounted or not.

Or else then Use the recovery CD ( Core Media CD ) and go to the recovery shell and see if you can try some repair.

Piyush

[Sanjay_6]

Hi,

you can boot into lvm maintainance mode and try,

at the boot prompt type "bo pri" to boot from the primary disk and select "y" to interact with ipl. At the ipl prompt type,

hp -lm (;0)/stand/vmunix

This will bring you to the lvm maintainance prompt. do a interactive fsck of the root filesystem, do not use shutdown to shutdown the system once done. Use reboot command.

Hope this helps.

Regds

[Danial Howard]

Thank you for your suggestions. I will award points soon.

I followed the suggestion to boot from the Core OS Install CD and use the Repair Shell option. I was able to fsck the root file system and fix the inconsistency. The system will now mount the root filesystem and boot into single user mode.

The remaining problem is that the system refuses to mount any other filesystem (specifically /stand) saying that the filesystem table may be corrupt. I created a new /etc/fstab while in the recovery shell, but this hasn't helped.

Any ideas?

[Peter Kloetgen]

Hi Danial,

if you boot from a recovery shell, you have a read only access to the file systems. You will have to remount them with read/write access.

Allways stay on the bright side of life!

Peter

[Tim D Fulford]

vgchange -a y vg00
mountall

[Danial Howard]

Well, with your help I was able to get the system back to normal.

Here's the summary:
I could boot into single-user mode, but couldn't mount the other filesystems. I fixed that with

vgchange -a y /dev/vg00

I rebooted and the system came up in single-user mode again. I could now do a mountall successfully. In my original post on this topic, I mentioned that /tcb/files/auth/r/root had problems. It turns out that this file was completely missing as a result of the fsck.The missing file caused the single-user mode.

I did a authck -pv and it reported that root was missing an entry in the trusted database. I fixed that with pwconv, edited the file /tcb/files/auth/r/root to remove the asterisk * in the encrypted password field, and set a new password. A reboot now brings up the system to the runlevel 3 like normal.

Thanks very much for your help.