topic Re: invalid super-block in Operating System - HP-UX

invalid super-block

TYP3R — Wed, 05 Nov 2008 16:55:10 GMT

Hi Guys

We have a customer who having some error when booting up there RP3410, I've attached a copy of the errors thats they have on there screen, Can you tell me if they do an:

#fsck -F vxfs -y -o full /dev/vg01/lvol1

Fixs this problem ?? Any help would be great

William

Re: invalid super-block

Marco A. — Wed, 05 Nov 2008 17:05:37 GMT

Hello William,

That could be a good idea, normally that fix the issue.

In addition, it's important to know the OS that you have as well as the patch level, also the vxfs patches are good for some problems like that, but the first step is that one that you are suggesting.

Regards,

Marc'o

Re: invalid super-block

Ganesan R — Wed, 05 Nov 2008 17:14:09 GMT

Hi,

I faced the same kind of issue once and fsck fixed that. Hopefully will do the same for you as well...

Re: invalid super-block

TYP3R — Thu, 06 Nov 2008 14:19:09 GMT

Hi

I got the customer to run the command:

#fsck -F vxfs -y -o full /dev/vg01/lvol1

but that didnt work, He have booted up the server in single user mode and this is what he got back

INIT: SINGLE USER MODE
INIT: Running /sbin/sh

# fsck -F vxfs -y -o full /dev/vg01/lvol1

vxfs fsck: Cannot open /dev/vg01/lvol1: No such device or address

file system check failure, aborting ...

Is there a step that we missed out ?

William

Re: invalid super-block

OldSchool — Thu, 06 Nov 2008 18:57:49 GMT

I'm not sure if you have to activate the volume group before you run the fsck or not.

try a

vgchange -a y /dev/vg01

followed by the fsck again.

the message makes me wonder if you have a dead drive. what does ioscan report?

anything in syslog?

Re: invalid super-block

Bill Hassell — Fri, 07 Nov 2008 01:37:52 GMT

> # fsck -F vxfs -y -o full /dev/vg01/lvol1
> vxfs fsck: Cannot open /dev/vg01/lvol1: No such device or address
> file system check failure, aborting ...

> Is there a step that we missed out ?

The primary errors are:

> vxfs fsck: /dev/vg01/lvol1:not a valid vxfs file system
> /dev/vg01/lvol1:invalid super-block

This would indicate that vg01/lvol1 has been trashed. Someone with root capability copied a file onto lvol1. Just exit from bcheckrc and see if anything else on vg01 is working. You may only have corruption with lvol1.

Re: invalid super-block

Adam W. — Fri, 07 Nov 2008 16:19:11 GMT

OldSchool, I think you may be on it there. I think it has to be activated first.

Re: invalid super-block

TYP3R — Fri, 07 Nov 2008 16:27:21 GMT

HI Guys

I've did activate the volume group and ran fsck but this is what came back now

#fsck -F vxfs -o full /dev/vg00/lvlo1

vxfs fsck: not a valid vxfs file system

invalid super-block

search for auxiliary super-block? (ynq)y

vxfs fsck: read failure at 36420124672

file system check failure, aborting ...

Still no luck there

Re: invalid super-block

Marco A. — Fri, 07 Nov 2008 16:29:34 GMT

Do you have a backup for this filesystem ?

I think you will need to use this backup.

Regards,

Marc'o

Re: invalid super-block

Adam W. — Fri, 07 Nov 2008 16:31:47 GMT

http://forums11.itrc.hp.com/service/forums/questionanswer.do?admit=109447626+1226075476776+28353475&threadId=872695

May help.

Re: invalid super-block

TYP3R — Fri, 07 Nov 2008 16:33:59 GMT

Oops it was

fsck -F vxfs -o full /dev/vg01/lvlo1

i even tried running it on the whole disk but still came back with the same error, I'll ask the customer to see if they have a backup of the filesystem

Will