Machine cannot comes up

[Yaroki]

Hello,

This is the first time I compose a message here so please correct me if I do something wrong.

I hold an HP UX c- 8000 b.11.11 machine.

I tried to create more disk space. Thought this, I move into "init s" (single mode)  and then to "init 0 (reboot) state.

When the os tried to come up I noticed that few processes are failed:

HP Gigabit

HP Ethernet

nfs core

nfs client/server

and few more...

and the os couldn't be brought up for several tries.

I interrupted the reboot process and entered to HPUX -is (s mode) and stooped nfs core, client and server, but it didn't help.

Please advice,

[Yaroki]

I have should notinced that I received some more messages:

command is reapawning too rapidlly will try in 5 minutes check for possible errors:

/opt/wbem/sbin/cimserverd

/usr/sam/lbin/samd

/usr/sbin/getty/ console console console

[V. Nyga]

>I tried to create more disk space. Thought this ....

Maybe you can tell us more exactly what you tried?
Where did you want to create more space?

Maybe it's more easy to use the last backup/ignite backup?

V.

[Yaroki]

Hello,

I tried to create disk space on /dev/vg00/lvol9 (i am not sure it was 9), it is one directory above the home directory / .

If you need more information please let me know.

Thank you,

Yali

[Patrick Wallek]

>>I tried to create disk space on /dev/vg00/lvol9 (i am not sure it was 9), it is one directory above the home directory /

How?  What exactly did you do?  What errors did you receive?

[Yaroki]

Hello,

I used sam -> Disk and File sys -> logical volumes -> increase size.

Then, I could not perform the action because the lvol was mounted. I went into run level S in order to unmount the lvol but couldn’t unmount it (bye the way how can I unmount a busy lvol?). so I press init 0 - to reboot.

from this stage the problem I described before occurred.

[Dennis Handly]

>I went into run level S in order to unmount the lvol but couldn’t unmount it (by the way how can I unmount a busy lvol?).

Run level s or S typically isn't good enough.  I.e. Not all processes are killed.

For / and /etc /tmp /var you probably have to reboot to single user mode.

[Yaroki]

Ok, and then what should I do?

[Yaroki]

I think I find out a problematic vlome disk.

I reboot the system into single mode and run fsck:

fsck -F vxfs -y -o full /dev/vg00/*

then I received some error messages:

invalid supper block

search for AUX supper block

failer in block 33554432

in addition I received: " no lost+found on directory fileset..." for lvol3

I run fstyp and found that dev/vg00/lvol2 cannot be identified - unknown_fstyp.

also a specific fsck on this vol shows the same.

How can I overcome the problem?

BR,

Yali.

[pradeep m]

Probably the file system is corrupted in the root volume group..
If there is an alternate boot path.. try to boot from it else restore from Ignite-UX backup image..