Operating System - HP-UX
1752781 Members
6647 Online
108789 Solutions
New Discussion юеВ

file system check failure, aborting ...

 
SOLVED
Go to solution
sreedhar2u
Frequent Advisor

file system check failure, aborting ...


I have file systems attached to storage (DAS) to my HP-UX11i system. it is not mount the fie systems after root of the server. Please help me in addressing this issue.

Server1{HP-UX-root}# mountall
mountall: /dev/vg01/lvol11 has to be fsck'd
mountall: diagnostics from fsck
vxfs fsck: Cannot open /dev/vg01/lvol11: No such device or address
mountall: cannot fsck /dev/vg01/lvol11
mountall: diagnostics from fsck
file system check failure, aborting ...
No such device or address
mountall: /dev/vg01/lvol11 failed in fsck
mountall: /dev/vg01/lvol11 cannot be mounted
mountall: /dev/vg01/lvol13 has to be fsck'd
mountall: diagnostics from fsck
vxfs fsck: Cannot open /dev/vg01/lvol13: No such device or address
mountall: cannot fsck /dev/vg01/lvol13
mountall: diagnostics from fsck
file system check failure, aborting ...
No such device or address
mountall: /dev/vg01/lvol13 failed in fsck
mountall: /dev/vg01/lvol13 cannot be mounted
mountall: /dev/vg01/lvol15 has to be fsck'd
mountall: diagnostics from fsck
vxfs fsck: Cannot open /dev/vg01/lvol15: No such device or address
mountall: cannot fsck /dev/vg01/lvol15
mountall: diagnostics from fsck
file system check failure, aborting ...
No such device or address
mountall: /dev/vg01/lvol15 failed in fsck
mountall: /dev/vg01/lvol15 cannot be mounted
mountall: /dev/vg01/lvol14 has to be fsck'd
mountall: diagnostics from fsck
vxfs fsck: Cannot open /dev/vg01/lvol14: No such device or address
mountall: cannot fsck /dev/vg01/lvol14
mountall: diagnostics from fsck
file system check failure, aborting ...
No such device or address
mountall: /dev/vg01/lvol14 failed in fsck
mountall: /dev/vg01/lvol14 cannot be mounted

Regards,
Sreedhar
37 REPLIES 37
Torsten.
Acclaimed Contributor

Re: file system check failure, aborting ...

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


First do a

# vgdisplay -v vg01

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 ...

I am getting the below

{HP-UX-root}# vgdisplay -v vg01
vgdisplay: Volume group not activated.
vgdisplay: Cannot display volume group "vg01".
Torsten.
Acclaimed Contributor

Re: file system check failure, aborting ...

Try

# vgchange -a y vg01

If in cluster, check from other nodes.

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 ...

It is giving this error

{HP-UX-root}# vgchange -a y vg01
vgchange: Couldn't activate volume group "vg01":
Quorum not present, or some physical volume(s) are missing.
Torsten.
Acclaimed Contributor

Re: file system check failure, aborting ...

OK, a missing (dead) disk.

Try

# vgchange -a y -q n vg01

# vgdisplay -v vg01

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 ...

still the same result

{HP-UX-root}# vgchange -a y -q n vg01
vgchange: Couldn't activate volume group "vg01":
Quorum not present, or some physical volume(s) are missing.
Torsten.
Acclaimed Contributor

Re: file system check failure, aborting ...

Let's try something different:

# strings /etc/lvmtab

# ioscan -fn

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 ...

{HP-UX-root}# strings /etc/lvmtab
/dev/vg00
/dev/dsk/c2t0d0
/dev/vg01
/dev/dsk/c5t0d0
/dev/dsk/c5t2d0
/dev/dsk/c5t4d0
/dev/vg02
/dev/dsk/c2t1d0

{HP-UX-root}# ioscan -fn
Class I H/W Path Driver S/W State H/W Type Description
=============================================================================
root 0 root CLAIMED BUS_NEXUS
ioa 0 0 sba CLAIMED BUS_NEXUS System Bus Adapter (880)
ba 0 0/0 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (783)
usb 0 0/0/1/0 hcd CLAIMED INTERFACE NEC USB Interface
usbhub 0 0/0/1/0.1 hub CLAIMED DEVICE USB Root Hub
usb 1 0/0/1/1 hcd CLAIMED INTERFACE NEC USB Interface
usbhub 1 0/0/1/1.1 hub CLAIMED DEVICE USB Root Hub
/dev/hub
usb 2 0/0/1/2 ehci CLAIMED INTERFACE NEC USB Interface
sideba 0 0/0/2/0 side_ba CLAIMED INTERFACE CMD IDE controller
ext_bus 0 0/0/2/0.0 side CLAIMED INTERFACE IDE
target 0 0/0/2/0.0.0 tgt CLAIMED DEVICE
disk 0 0/0/2/0.0.0.0 sdisk CLAIMED DEVICE TEAC DV-28E-C
/dev/dsk/c0t0d0 /dev/rdsk/c0t0d0
target 1 0/0/2/0.0.7 tgt CLAIMED DEVICE
ctl 0 0/0/2/0.0.7.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c0t7d0
ext_bus 1 0/0/2/0.1 side CLAIMED INTERFACE IDE
target 2 0/0/2/0.1.7 tgt CLAIMED DEVICE
ctl 1 0/0/2/0.1.7.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c1t7d0
ba 1 0/1 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (783)
ext_bus 2 0/1/1/0 c8xx CLAIMED INTERFACE SCSI C1010 Ultra160 Wide LVD
target 3 0/1/1/0.0 tgt CLAIMED DEVICE
disk 1 0/1/1/0.0.0 sdisk CLAIMED DEVICE HP 36.4GST336753LC
/dev/dsk/c2t0d0 /dev/rdsk/c2t0d0
target 4 0/1/1/0.1 tgt CLAIMED DEVICE
disk 6 0/1/1/0.1.0 sdisk CLAIMED DEVICE HP 146 GST3146707LC
/dev/dsk/c2t1d0 /dev/rdsk/c2t1d0
target 5 0/1/1/0.7 tgt CLAIMED DEVICE
ctl 2 0/1/1/0.7.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c2t7d0
ext_bus 3 0/1/1/1 c8xx CLAIMED INTERFACE SCSI C1010 Ultra160 Wide LVD
target 6 0/1/1/1.7 tgt CLAIMED DEVICE
ctl 3 0/1/1/1.7.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c3t7d0
lan 0 0/1/2/0 igelan CLAIMED INTERFACE HP PCI 1000Base-T Core
ba 2 0/2 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (783)
ba 3 0/3 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (783)
ext_bus 5 0/3/1/0 c8xx CLAIMED INTERFACE SCSI C1010 Ultra160 Wide LVD A6828-60101
target 7 0/3/1/0.0 tgt CLAIMED DEVICE
disk 2 0/3/1/0.0.0 sdisk CLAIMED DEVICE HP 36.4GST336607LC
/dev/dsk/c5t0d0 /dev/rdsk/c5t0d0
target 8 0/3/1/0.2 tgt CLAIMED DEVICE
disk 3 0/3/1/0.2.0 sdisk CLAIMED DEVICE HP 36.4GST336607LC
/dev/dsk/c5t2d0 /dev/rdsk/c5t2d0
target 9 0/3/1/0.4 tgt CLAIMED DEVICE
disk 4 0/3/1/0.4.0 sdisk CLAIMED DEVICE HP 36.4GMAP3367NC
/dev/dsk/c5t4d0 /dev/rdsk/c5t4d0
target 10 0/3/1/0.7 tgt CLAIMED DEVICE
ctl 5 0/3/1/0.7.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c5t7d0
ba 4 0/4 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (783)
ba 5 0/6 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (783)
ba 6 0/7 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (783)
tty 0 0/7/1/0 asio0 CLAIMED INTERFACE PCI SimpleComm (103c1290)
/dev/diag/mux0 /dev/mux0 /dev/tty0p0
tty 1 0/7/1/1 asio0 CLAIMED INTERFACE PCI Serial (103c1048)
/dev/GSPdiag1 /dev/mux1 /dev/tty1p2
/dev/diag/mux1 /dev/tty1p0 /dev/tty1p4
unknown -1 0/7/2/0 UNCLAIMED UNKNOWN PCI Display (10025159)
memory 0 8 memory CLAIMED MEMORY Memory
ipmi 0 16 ipmi CLAIMED INTERFACE IPMI Controller
/dev/ipmi
processor 0 128 processor CLAIMED PROCESSOR Processor
processor 1 129 processor CLAIMED PROCESSOR Processor

Torsten.
Acclaimed Contributor

Re: file system check failure, aborting ...

Disks are there, try

# diskinfo /dev/rdsk/c5t0d0
# diskinfo /dev/rdsk/c5t2d0
# diskinfo /dev/rdsk/c5t4d0

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!