Showing results for 
Search instead for 
Do you mean 

Not able to do fsck

SOLVED
Go to Solution
Advisor

Not able to do fsck

I am not able to mount /var partition. when I am doing fsck I am getting below error. please help me to resolve the issue.


# fsck -F vxfs -o full /dev/vg00/lvol33
vxfs fsck: file system had I/O error(s) on meta-data.
intent log marked bad in super-block
cannot perform log replay
pass0 - checking structural files
pass1 - checking inode sanity and blocks
pass2 - checking directory linkage
pass3 - checking reference counts
pass4 - checking resource maps
au 40 state file incorrect - fix? (ynq)y
OK to clear log? (ynq)y
vxfs fsck: error writing LOG inode
file system check failure, aborting ...
1 ACCEPTED SOLUTIONS
Honored Contributor Honored Contributor

Re: Not able to do fsck

Hi,

Use the raw device.

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

Regards,
Robert-Jan
5 REPLIES
Honored Contributor Honored Contributor

Re: Not able to do fsck

Hi,

Use the raw device.

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

Regards,
Robert-Jan
Highlighted
Regular Advisor Regular Advisor

Re: Not able to do fsck

Hi,

To Repair the file system

# fsck -F vxfs -o full -y /dev/vg00/rlvol33

( yes to all )

Then try to mount the file system


Regards,
Subodh
Advisor

Re: Not able to do fsck

I tried raw device but that also is not working so I tried to ignite the server, then I am getting below error.

Main Menu: Enter command or menu > bo lan.XXXXXXXX install
Interact with IPL (Y, N, or Cancel)?> n

Booting...
Failed to initialize.

ENTRY_INIT
Status = -4

00000000 00000000 00000000 00000000 00000000 00000030 00000000 6E48E7BC
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000005 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000007 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000

Failed to initialize.
Honored Contributor Honored Contributor

Re: Not able to do fsck

Hi,

well it seems like the hard disk is damaged.
Replace it, then use ignite.

HTH
Volkmar

P.S.
A copy test 'dd' to /dev/null would also be a test to verify if the disk is damaged.
*** Say 'Thanks' with Kudos ***
Honored Contributor Honored Contributor

Re: Not able to do fsck

Check the bad blocks on your disk to be sure:
lvdisplay -v /dev/vg00/lvol33

and then put disk dev below;

echo 2400?20X | adb /dev/dsk/cXtYd0