Vmunix was corrupt after doing lvreduce at /stand

[JRiggs]

Hi,

Need them fixed asap since i'm running out of time and I was not able to do ignite.

What are my Options?

Can I use my recovery CD?

If yes how?

thanks in advance.

[John Carr_2]

Hi

what hadwareconfiguration do you have and what o/s ?

cheers
John.

[Volker Borowski]

Hello,

- do not reboot !
- Re-create new filesystem on /stand
- Restore backup of /stand

Volker

[Wodisch]

Hi,

very bad idea to lvreduce "/stand", especially since you cannot shrink the filesystem in there (HFS can only be extended, but never shrunk) and hence using lvreduce destroyed the integrity of the whole filesystem...
So, you will have to boot a "recovery shell" from your "core/install" CDROM, do an "mkfs" to that LVOL, mount it (still in your recovery shell) and copy all the files needed to it. Then "umount" and reboot.
Can you "tar" the contents of "/stand" from another, but similiar system to tape for this?
The hardware of the other system should be as similiar as possible (to have all the needed drivers in the kernel you get form there).
Then you boot, single-user should be fine, "mount -a" all filesystems, and then use SAM to create a new kernel. Finally reboot, as SAM tells you.

HTH,
Wodisch
PS: And then use Ignite/UX immediately to create a recovery-tape!

[John Carr_2]

Hi

if the system is still up and running you could try rebuilding the kernel


cd /stand/build

mk_kernel -s system

mv /stand/system /stand/system.old
mv /stand/vmunix /stand/vmunix.old

mv /stand/build/vmunix_test /stand/vmunix

cd /
shutdown -ry now

John.

[Carlos Fernandez Riera]

If after lvreduce you have not run any other lvcomand, then you can run vgcfgrestore using /etc/lvmcong/vgname.conf.old file. It will restore headers on disk. If extents deallocated from /stand have not been used to extend an existing lv or to create a new lv, or even so, if you have not run newfs/extentfs this option would save your problem.

Run pvdisplay -v /dev/dsk/disk_vg00:

/stand is the first lvol created when you install a system, so any extents between lvol1 and lvol2 (primary swap) must own lvol1.

In other words... if extend freed from lvol1 were not overwrite by any other lvol, using vgcfgrestore or lvextend, you shuold be able to allocate again to lvol1.


everyway, make a backup of your current /stand.

Check if vmunix.prev is not corrupted. If not, you can copy to vmunix, to get at least a valid boot.


Good Luck.

[Roger Baptiste]

If possible, try restoring the previous backup copy of /stand from the backup tapes. That should be the first thing to try. If there is not enough space, you can leave out vmunix.prev, since it is a older version of kernel in the backup copy.


HTH
raj