mount error

[MarkW_1]

Just had a drive replaced by HP field tech.
I am getting the following error when trying to do a mount -a:

vxfs mount: /dev/vg01/lvol11 is corrupted. needs checking

[A. Clay Stephenson]

Well, did yoy follow all the steps? Assuming this was a mirrored disk, did you, for example, do a vgcfgrestore. Did you do a vgchange -a y and a vgsync?

[MarkW_1]

The field tech went though the steps to create the volume. The disk is not mirrored

[A. Clay Stephenson]

There is not enough data to solve this yet. For example was a newfs command run to create the filesystem? Is there an /etc/fstab entry for this logical volume. If so, it's possible thast the filetype the tech created (e.g. hfs) does not match the /etc/fstab entry type (e.g. vxfs). I suggest that you use the fstyp command to first determine the filesystem type.
Man fstyp for details.

[MarkW_1]

The file type is vxfs. The tech used the correct newfs command.

Question: this disk has a single volume on it. Would I be better off deleting the volume in sam and recreating it.

[Patrick Wallek]

Check out this document on the ITRC:
Doc ID: LVMKBRC00005130
http://support1.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000060744801

It goes through all the steps that need to taken to replace an unmirrored data disk in HP-UX 10.X and 11.X

[Sridhar Bhaskarla]

Hi Mark,

1. How many disks are there in vg01?.
2. There is a possibility that lvol11 might have spread across multiple disks. If so, it is better to 'lvremove' the entire lvol11 as you already lost data.
3. Your tech might have followed vgcfgrestore to restore the LVM structures on the disk. After doing an lvremove, do a vgreduce and take out the disk from the volume group.
4. Add the disk into the volume group and then create the logical volume and mount it so that it will be clean.

-Sri

[A. Clay Stephenson]

It's also possible that you actually need to do an fsck -F vxfs -o full,nolog. Man fsck_vxfs for details.

You could use sam to delete the lvol and recreate it but I urge you to only use SAM after you know how to do all the step manually.
It's more important that you become familiar all the steps involveds so that you will better know how to fix this in the future.

By the way, this is the very reason why you should purchase Mirror/UX and OnlineJFS. If you have hot-plug disks, your system could then keep right on chugging while the fixes are done.

[PIYUSH D. PATEL]

Hi,

If you can give the original configuration of the vg01 and how many disks it contained previously...it would have been better.

After the HP engg replaced the disk and created the filesystem, did it mount atleast once ??

You need to run a fsck on the lvol11 and then find out what errors it gives.

Or you can remove the lvol and recreate it.

Piyush

[George Abraham_1]

hai

try the full fsck and if that fails.. you will be better off if you can recreate it.. command line will be better than SAM in these kind of situations


keep smiling
george

[MarkW_1]

Sorry Clay, I ended up using SAM to delete and recreate the logical volume. I have restore the OB2 database and am back in business.