/stand directory logical volume was removed.

[Jai Harikrishnan]

Hi All,

I inadvertantly removed the /stand directory logical volume, and hence the entire contents of the /stand directory.

I recreated the /stand directory and associated this with a newly created logical volume (HFS).

Has anyone encountered the problem. What are the effects due to this and what should I do to mitigate this problem.

Unfortunately, as this is a new install, we have not taken a backup yet.

Thanks a lot in advance!

[A. Clay Stephenson]

First, you will notice that a few commands like ps or adb are going to give very strange results. That's the least of your problems. You will not be able to reboot. The system must have the files in /stand (especially /stand/vmunix - the kernel file) to bootstrap itself.

You might as well start over with your OS install. If you've done anything that you would like to save, you should tar them off to tape before the install.

[Michael Tully]

You'll be better off starting your system install over again. There is nothing you can do. *ALWAYS* create an ignite backup immediately after creating a system. If there is a problem, recovering from this will be quicker than starting again. As Clay as suggested, unless you have the /stand/vmunix or /stand/vmunix.prev file(s) you will not be able to reboot.

[Arockia Jegan]

Oops.... your kernel files stored under /stand have gone. Your system can't boot with out those files. If you have backup you can restore them. Else.... one more installation...

[Ester Saez]

Ups!

It's ocurred to me. You can recreate /stand, but there is another condition than be an HFS filesystem; all filesystem extensions or blocks must be contigous. If they not, system will not be able to start.
The best way to recover your system in the mininum time is to reinstall system.
I learned very well lesson and in our OS installations we always include Ignite software in order to have at least one version og Ignite tape, while we are deploying system into server.

Good luck!