fsck fail

[Yarok]

Hello
When trying to run the fsck it finally bring the message: cannot red blk 212080.
It seems that Vol 19 is crushed.

The OS is up but without the normal GUI (like init 3).

Please see the attached rc.log file.

Please advice.

[Shibin_2]

You need to unmount the file system on /dev/vg00/lvol9 then do fsck

I think, it is /usr file system.

If any application running, please stop and unmount /usr . Otherwise, boot into single user mode ( this is safe option ) and do fscsk on /usr

fsck -F vxfs -o full

[Yarok]

Hello,

Thanks for the reply,

I rebooted the system into Singel mode.
When I tried to umount /dev/vg00/lvol19, it says that /dev/vg00/lvol19 cannot find in /etc/mnttab.

Should I run the fsck -F vxfs -o anyway ?

BR,

Yaron

[Shibin_2]

Single user mode ( in maintenance ), it won't mount all file system. You can start straight away to do fsck.

You may have to give full path.

/sbin/fsck -F vxfs -o full

[Yarok]

sorry, but what is the 'vxfs' and what vol should I check? (the problematic one - 19) ?

[Ismail Azad]

Hi,

Vxfs there is the type of filesystem that is being mentioned at the time of execution of fsck and an lvol19 will not be mounted in runlevel s. Yes the logical volume that is corrupted should be mentioned as the argument on the execution of fsck.

Regards
Ismail Azad

[Yarok]

Sorry, but I still cannot run it correctly.
I tried:

/sbin/fsck -F vxfs -o full /dev/vg00/lvol19

received:

fsck vxfs cannot stat /dev/vg00/lvol19

What does it mean?

Thanks,

Yaron

[Dennis Handly]

>fsck vxfs cannot stat /dev/vg00/lvol19

Are you using the raw/character device?

>Shibin: I think, it is /usr file system.

It seems to be /var/?

[Matti_Kurkela · Accepted solution]

Not "Vol 19" but LVOL 9:

---from the attachment:---
mount: /dev/vg00/lvol9 needs to be fsck'ed before mounting
----end----

Depending on the font used on your display, the second lowercase L in default-style LV names (pattern "lvolN", N = number) can be easy to confuse with number 1.

You aren't the first to make this mistake, and probably won't be the last one either.

Based on the error messages in your attached rc.log, looks like your /dev/vg00/lvol9 probably contains your /var. As a result of the failed mount, several system daemons have failed to start.

You also have an exportfs error message about /scc: is this symlinked to some sub-directory within your /var? If not, this might be a separate issue.

If /scc does not exist at all, it might be a remnant of some old configuration: while the /scc directory may have been removed, /etc/exports seems to still refer to it.

MK

[Shibin_2]

// Have you checked that this is mounted ?

bdf /dev/vg00/lvol19 ?

If mounted, then need to unmount it first, then do fsck.