System crash after mount of lvol

[David Johnson_6]

When ever I try to mount /dev/vg10/lvol system crashes.
first time I tried an ls in /holdit got error:
can't find . file then system crash.

[David Johnson_6]

just found out this disk has bad superblock.
Can I rebuild the superblock?

[melvyn burnard · Accepted solution]

is it an hfs file system, or vxfs?
check /etc/fstab
if hfs, just do a fsck -b 16 on it
if it is vxfs, try running fsck -o full against it

[KapilRaj]

If it is a HFS ,

This message means Superblock copy at block 16 has been corrupted. Hence you can specify an alternate super block and try fsck i.e.

fsck -b

Check in /var/adm/sbtab for a list of alternate super blocks and use the number next to block 16.

If this is JFS ,

Try fsck -o full

NB: Use fstyp command to find out which type of filesystem is this or else , you may have a look at /etc/fstab to find out the type

Regds,

Kaps

[KapilRaj]

melvyn,

u r fast .. i missed to hit submit earlier ..

Kaps

[David Johnson_6]

I am running HP-UX 11.0 on the filesystem is vxfs.
I tried running fsck -o full /dev/vg08/lvol1
says no device found.
also on phone with HP tech and he said to look in /etc/stab but the is no entriesx for /dev/vg08

[KapilRaj]

can u check if this lvol is present in the following o/p ?

vgdisplay -v vg08

Did you ever have a filesystem in it ?, in this case u may need the newfs command to create the filesystems on this logical volume. It could be a bad disk as well. Does syslog finds a problem ?.


Regds,

Kaps

[KapilRaj]

also please post the o/p of lvdisplay -v /dev/vg08/lvol ???

Kaps

[David Johnson_6]

yes I can see the vg, and sam sees it.
I copied data to it earlier.

[KapilRaj]

lvdisplay -v would tell to which alll disks u have Le's distributed and thus u can locate a bad disk ! or else there is no good reason why system should crash.

Regds,

Kaps

[Sridhar Bhaskarla]

Hi,

Make sure the disks in this volume group are not active on some other system. What type of storage do you have on the backend?.

-Sri

[melvyn burnard]

hmm, a little confused here.
You first said it was vg10, now it is vg8
are you certain you are dealing with the correct logical volume?
Also check /dev/vg to make sure you have the block and character device files, and remember fsck should be done against the raw device (rlvol) not block.