Operating System - HP-UX
1825756 Members
2331 Online
109687 Solutions
New Discussion

Re: file system check failure, aborting ...

 
SOLVED
Go to solution
Deeos
Regular Advisor

Re: file system check failure, aborting ...

Hi ,


Could you do following stepsand give output once more:

#more /etc/mnttab

#mv /etc/lvmtab /etc/lvmtab.oldd

#vgscan -v

#vgdisplay -v

#vgdisplay -v vg01

#mount -a

#more /etc/mnttab


Regards
Deeos
Deepak
Deeos
Regular Advisor

Re: file system check failure, aborting ...

after

#vgscan -v

#strings /etc/lvmtab

Deepak
sreedhar2u
Frequent Advisor

Re: file system check failure, aborting ...

Hi Bill,

I am getting the below error, while running vgimport

# vgimport -s -m vg01.map vg01
vgimport: Couldn't open MAPFILE "vg01.map".
vgimport: vg01.map: No such file or directory

sreedhar2u
Frequent Advisor

Re: file system check failure, aborting ...


Hi Bill,

came to the same stage, where we started.

# vgimport -s -m vg01.map vg01
# cd /dev/vg01
# ls
group lvol13 lvol15 rlvol13 rlvol15
lvol11 lvol14 rlvol11 rlvol14
# vgchange -a y vg01
vgchange: Couldn't activate volume group "vg01":
Quorum not present, or some physical volume(s) are missing.

# mount -a
vxfs mount: Cannot open /dev/vg01/lvol15: No such device or address
vxfs mount: Cannot open /dev/vg01/lvol14: No such device or address
mount: /dev/vg02/lvol201 is already mounted on /oradumps2
vxfs mount: Cannot open /dev/vg01/lvol13: No such device or address
vxfs mount: Cannot open /dev/vg01/lvol11: No such device or address
mount: /dev/vg00/lvol9 is already mounted on /apps
mount: /dev/vg00/lvol8 is already mounted on /var
mount: /dev/vg00/lvol7 is already mounted on /usr
mount: /dev/vg00/lvol6 is already mounted on /opt
mount: /dev/vg00/lvol5 is already mounted on /tmp
mount: /dev/vg00/lvol4 is already mounted on /local
mount: /dev/vg02/tarot2_2 is already mounted on /tarot2_2
mount: /dev/vg00/lvol1 is already mounted on /stand



Bill Hassell
Honored Contributor

Re: file system check failure, aborting ...

> # vgimport -s -m vg01.map vg01
> vgimport: Couldn't open MAPFILE "vg01.map".
> vgimport: vg01.map: No such file or directory

There was a missing step. Normally, the system administrator will create map files for all the current volume groups. This must be done manually and I suspect that there aren't any map files in /etc/lvmconf.

So you'll need to create one. From your listings above, it appears that vg01 has 4 lvols numbered 11 12 13 and 14. Ans since we can see the serial number information from showLVMinfo, you can create the map file which will look like this:

cat /etc/lvmconf/vg01.map
VGID 0x68ff98134194a5e6
1 lvol11
2 lvol13
3 lvol14
4 lvol15

DISCLAIMER: I am assuming that this was the order of the lvols when they were first created. Without a map file, I am just guessing. After you use vgimport, vgchange and mount -a, you'll need to verify that the files are in the correct mount points.

Now you should be able to use vgimport:

(create /dev/vg01 and /etc/vg01/group with nothing else in the directory)
vgexport -s -m vg01.map vg01
vgchange -a y
mount -a

If the mount point names have the wrong files, make a list of which lvol has the required files for the destination mount point, then change /etc/fstab and remount the volumes.


Bill Hassell, sysadmin
Torsten.
Acclaimed Contributor

Re: file system check failure, aborting ...

Please post the exact vgexport command you did!

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!   
sreedhar2u
Frequent Advisor

Re: file system check failure, aborting ...

Hi Bill,

I have this file
# strings /etc/lvmconf/vg01.conf
CONFIG01
/dev/vg01
/dev/rdsk/c5t0d0
/dev/rdsk/c5t2d0
/dev/rdsk/c5t4d0
LVMREC01h
LVMREC01h
LVMREC01h
1VVGDA0001
VGSA0001F
sreedhar2u
Frequent Advisor

Re: file system check failure, aborting ...

Hi Torsten,

I have run the vgexport command as below

# vgexport -s -m vg01.map vg01
sreedhar2u
Frequent Advisor

Re: file system check failure, aborting ...

Hi Torsten/Bill,

Thanks for all the support provided. This problem is due to SCSI terminator, which was broken. I replaced the SCSI terminator. I am able to mount few lvm's which are on external storage.

Now I have the below issue. I am not able to mount /dev/vg01/lvol14 and lvol15.

vxfs mount: read of super-block on /dev/vg01/lvol15 failed: I/O error
vxfs mount: /dev/vg01/lvol14 is corrupted. needs checking
mount: /dev/vg01/lvol13 is already mounted on /oradumps
mount: /dev/vg01/lvol11 is already mounted on /tarot
mount: /dev/vg00/lvol9 is already mounted on /apps
mount: /dev/vg00/lvol8 is already mounted on /var
mount: /dev/vg00/lvol7 is already mounted on /usr
mount: /dev/vg00/lvol6 is already mounted on /opt
mount: /dev/vg00/lvol5 is already mounted on /tmp
mount: /dev/vg00/lvol4 is already mounted on /local
mount: /dev/vg00/lvol1 is already mounted on /stand
Bill Hassell
Honored Contributor

Re: file system check failure, aborting ...

> vxfs mount: read of super-block on /dev/vg01/lvol15 failed: I/O error
> vxfs mount: /dev/vg01/lvol14 is corrupted. needs checking

For lvol15, there is a bad spot on the disk which cannot be read. You can verify this with dd:

dd if=/dev/vg01/rlvol15 of=/dev/null bs=1024k

You can try to fix this with fsck. Run the command:

fsck -o full /dev/vg01/rlvol15

Because there is a bad spot on the disk, fsck may not be able to fix the problem. If it reports I/O errors, the disk is damaged and will have to be replaced. This means that all the data on vg01 will have to be restored from your backup tapes. To determine which disk is bad, run dd on each of the disks (will take a few minutes):

dd if=/dev/rdsk/c5t0d0 of=/dev/null bs=1024k
dd if=/dev/rdsk/c2t0d0 of=/dev/null bs=1024k
dd if=/dev/rdsk/c4t0d0 of=/dev/null bs=1024k

The second error is probably recoverable. Use a similar command:

fsck -o full /dev/vg01/rlvol14

If you don't have a backup of these lvols, don't start any applications. Instead, backup all the lvols on vg01 immediately.


Bill Hassell, sysadmin
sreedhar2u
Frequent Advisor

Re: file system check failure, aborting ...

Hi Bill,

please see the output as below

{HP-UX-root}# fsck -o full /dev/vg01/rlvol14
file system is larger than device
vxfs fsck: cannot initialize aggregate
file system check failure, aborting ...

{HP-UX-root}# dd if=/dev/vg01/rlvol15 of=/dev/null bs=1024k
dd read error: I/O error
0+0 records in
0+0 records out
sreedhar2u
Frequent Advisor

Re: file system check failure, aborting ...

{HP-UX-root}# dd if=/dev/rdsk/c5t0d0 of=/dev/null bs=1024k
34732+1 records in
34732+1 records out
{HP-UX-root}# dd if=/dev/rdsk/c2t0d0 of=/dev/null bs=1024k
34732+1 records in
34732+1 records out
{HP-UX-root}# dd if=/dev/rdsk/c4t0d0 of=/dev/null bs=1024k
/dev/rdsk/c4t0d0: No such file or directory
dd: cannot open /dev/rdsk/c4t0d0
sreedhar2u
Frequent Advisor

Re: file system check failure, aborting ...

Hi Bill,

I have reinserted the disks.Everything is working fine now.

Thanks a lot Bill