Operating System - HP-UX
1753894 Members
7427 Online
108809 Solutions
New Discussion юеВ

Re: file system check failure, aborting ...

 
SOLVED
Go to solution
sreedhar2u
Frequent Advisor

Re: file system check failure, aborting ...

{HP-UX-root}# diskinfo /dev/rdsk/c5t0d0
SCSI describe of /dev/rdsk/c5t0d0:
vendor: HP 36.4G
product id: ST336607LC
type: direct access
size: 35566480 Kbytes
bytes per sector: 512

{HP-UX-root}# diskinfo /dev/rdsk/c5t2d0
SCSI describe of /dev/rdsk/c5t2d0:
vendor: HP 36.4G
product id: ST336607LC
type: direct access
size: 35566480 Kbytes
bytes per sector: 512

{HP-UX-root}# diskinfo /dev/rdsk/c5t4d0
SCSI describe of /dev/rdsk/c5t4d0:
vendor: HP 36.4G
product id: MAP3367NC
type: direct access
size: 35566480 Kbytes
bytes per sector: 512


Bill Hassell
Honored Contributor
Solution

Re: file system check failure, aborting ...

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

The lvol does not exist. It will not exist if the volume is not activated.

> vgdisplay: Volume group not activated.

This is why fsck is failing.

> vgchange: Couldn't activate volume group "vg01":
> Quorum not present, or some physical volume(s) are missing.

The volume cannot be activated since required disks are not found. They are found by reading the LVM header on the disk. Since ioscan reports the disks are present and diskinfo can query the disks, then something has changed the header information. You can use the attached script showLVMinfo to report back what is on each disk:

# showLVMinfo c5t0d0 c5t2d0 c5t4d0

It will either report a valid LVMREC for each disk, or report back that there no LVMREC at all, or report on some other volume group serial numbers. Post the results from the above script.


Bill Hassell, sysadmin
sreedhar2u
Frequent Advisor

Re: file system check failure, aborting ...

it is giving syntax error

{HP-UX-root}# showLVMinfo c5t0d0 c5t2d0 c5t4d0
showLVMinfo[21]: Syntax error at line 29 : `do' is not expected.
хоЛцШОхУ▓
Honored Contributor

Re: file system check failure, aborting ...

that's means Ur Three disk missing the VGRA; Have U Pvcreate these disk from this Server or Other server?
I'm back, water king
sreedhar2u
Frequent Advisor

Re: file system check failure, aborting ...

from the same server
stephen peng
Valued Contributor

Re: file system check failure, aborting ...

you have pvcreate one or all pvs of that vg01? oh, you would miss vg01.
Torsten.
Acclaimed Contributor

Re: file system check failure, aborting ...

You did a pvcreate ???

Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
Bill Hassell
Honored Contributor

Re: file system check failure, aborting ...

> Syntax error at line 29 : `do' is not expected.

When you transferred the file to the HP-UX box, did you specify ASCII and not BINARY?


Bill Hassell, sysadmin
sreedhar2u
Frequent Advisor

Re: file system check failure, aborting ...

Oh, script working now

# ./showLVMinfo c5t0d0 c5t2d0 c5t4d0

Local CPU ID = 1761581075, hex value=0x68ff9813

/dev/rdsk/c5t0d0:
CPUID=0x68ff9813 (1761581075), VGID 0x4194a5e6, PVID 0x4194a5cb

/dev/rdsk/c5t2d0:
CPUID=0x68ff9813 (1761581075), VGID 0x4194a5e6, PVID 0x4194a5d1

/dev/rdsk/c5t4d0:
CPUID=0x68ff9813 (1761581075), VGID 0x4194a5e6, PVID 0x4194a5d7
sudheerch
Frequent Advisor

Re: file system check failure, aborting ...

#pvdisplay -v /dev/rdsk/c5t0d0
#pvdisplay -v /dev/rdsk/c5t2d0
#pvdisplay -v /dev/rdsk/c5t4d0