server recovery with OS media help !!

[martin_215]

Im trying to recover my boot disk with lvm
specifically bootlif area
i booted thru september 2003 OS media CD1 of 3
and selected the run recovery-recover option
but it gives me an error filesystem full
and the screen flashes so quick that I can exactly identify the message
but i guess the message is
cant load mkboot as filesystem is full

What filesystem is it complaining about
is this the ram filesystem
but I dont make this filesystem for it to get full
it automatically makes the ram filesystem

so could it be that this release of OS has some bugs in the recovery shell?

[Florian Heigl (new acc)]

In this recovery shell, Your / filesystem is only 12MB in size!

You can get along by restoring and rm'ing the specific files You need.
You can 'cheat' by mounting the old /tmp filesystem and working from there.

If You have another hard drive available it is possibly advisable to simply install a small hp-ux setup on that and do the recovery from disk.

[martin_215]

thats okie ,but my understanding is that the hpux recovery option is for use " off the shelf"

the recovery hand book /ignite admin recovery guide says nothing about removing files and tweaking the recovery option to repair the bootlif area

it says to boot from cd.select recovery option,select repair bootlif area

and it should take care of loading the required files

[eran maor]

Hi Martin

you are not doing it o.k ,

please look at this menual and tried to do it like in the menual that i m sending

[melvyn burnard]

It appears that the September 2003 Recovery bits do have an issue with this, you may want to try to use September 2004 media if it is available to you.
You could also take a look at this document if you have a support contract linked to your id:
DKKBRC00006375

[Steven E. Protter]

My thinking is there is a problem with the Core OS cd you are using. Bug or something like that.

I'd look to other sources for recovery:

1) Ignite make_tape_recovery backup of vg00
2) Other Core OS versions.

SEP

[martin_215]

thanks fr all the replies
eran maor -thanks for the doc
one question
the command which u said

loadfile -l RECCMDS ioct

it doesnt find ioct in the archive
i tried to load it from loadfile and from recovery menu-
but it doesnt find the file ioct

any clue?

[martin_215]

Eran,
Where did you find this procedure
did you write it urself

I couldnt find any hint of this in ignite admin or recovery guide

the procedure in ignite admin guide doesnt list any of these commands
thanks

[eran maor]

Hi

this doc is internal doc that i have found in the expert center , so i didnt wrote it just look at the rigth place .


eran maor

[Kent Ostby]

There is a way to increase the size of this memory based file system as noted in the document cited above which is located here:

http://www2.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=DKKBRC00006375

You can also try to remove other files that you dont need as long as this is PRIOR to the chroot (since after the chroot, you are on your disk).

PRIOR to the chroot, I have done: rm /sbin/fs/hfs/*
rm /sbin/Fs/vxfs/*

This will get rid of some files and give you some space. NOTE: This is getting rid of files IN MEMORY not on disk.

Still, if possible, the best route is to re-make the memory file system as listed above.

Best regards,

Kent M. Ostby

[martin_215]

Eran
I dont find this file listed in the expert doc
ioct is not listed in the loadable list of files archive


loadfile -l RECCMDS ioct

[martin_215]

Thanks kent for the doc
I wonder why HP doesnt give a user option to select the size of ram filesystem in recovery menu

I dont think with the 8MB filesystem they make anyone could get the recovery procedure working
bcos fsck,mount,umount and mkboot far exceed this 8MB space limit

[martin_215]

i think I can get it running with making a larger ram filesystem
but out of curiousity in the procedure with Eran sent me-
looks like ,the ioct command is something which cause the kernel to reread the /stand/rootconf file and remap the /dev/dsk/c0t0d0s2lvm to root slice

So it looks like an interesting command
but unfortunately I couldnt find the command ioct anywhere in the archive

Is this really ioct or was there a typo error

can anyone suggest put some light on this