corrupt filesystem

[Sherif A. Louis]

i have a server with hpux 11.11 installed. i did an lvextend to the root "/" filesystem on maintenance mode "hpux -lm". This is the procedure i followed:
1- interrupt BCH
2- bo
3- interact with IPL/ISL: y
hpux -lm
4- pvmove /dev/dsk/c0t5d0 /dev/dsk/c0t6d0 /dev/vg00/lvol4
where lvol4 is the "/tmp" and both disk belong to the same volume group vg00
5- lvextend -L 500 /dev/vg00/lvol3
6- extendfs /dev/vg00/lvol3
7- i was forced to run an fsck and it said filesystem clean and all is well, and it was successfully extended, i moved up to run level 3 and made an lvdisplay and lvlnboot -v and found everything normal and mounted.
when i made a reboot "shutdown -ry 0" the system crashed made a crash dump and displayed several errors and warnings one of the is that the super block size is wrong and a full fsck need to be run. and the server reboots.
i tried logging in single user mode but i couldn't. is there any way i can log in to the system and fix this? thank you.

[Ivan Krastev]

You can recover it and extend root (/) with the latest Ignite archive.


regards,
ivan

[Sherif A. Louis]

it was a fresh installation, and i installed oracle and was preparing for the OVO installation. but needed to extend the root for the OVO. i know i should of taken an ignite!!
any other solution?

[Robert-Jan Goossens]

Hi,

You could try to boot from dvd and try to repair the root filesystem, but it could be faster to reinstall from scratch. I would go for the second option.

Regards,
Robert-Jan

[Sherif A. Louis]

i am preparing for the second option!!

so what went exactly wrong? did i corrupt the superblock data by initiating an init 3?
or was it something in the extension steps?

[Torsten.]

You should never boot from LM mode to any higher level - do always a reboot.
Did you run any lvlnboot (-d -r -b) command?

Maybe this is the problem.

IMHO you should start over now.

[chris huys_4]

Hi Louis,

Booting to lvm maintenance mode, hpux -lm, is only done in very specific (recovery) cases and not developed with "increasing" the rootfilesystem in mind, ignite on the otherhand was specifically developed as a way to increase the rootfilesystem in a supported way.

So yeah, ignite is, the way to go..

Greetz,
Chris