fsck fail

[Yarok]

I rebooted the server, and interrupted the booting.
but how I can bring the ISL prompt?

ISL> hpux -is

all I'v get is the following prompt:

Service Menu: Enter Command>

[Yarok]

OK, I did it - rebooted and intturpted and booted into a single mode than ISL> hpux -is.

Than ran fsck:
isL> /sbin/fsck -F vxfs -o full -y /dev/vg00/lvol0

I'v got:

Invalid super-block
search for auxiliary super-blo? (ynq)y
alternate super-block not found
vxfs fsck: cannot initialize aggregate.

[Yarok]

I attached the bdf results.

I ran /usr/sbin/fsch

# /usr/sbin/fsck
fsck: /dev/vg00/lvol3: root file system
continue (y/n)? y
** /dev/vg00/lvol3
** Last Mounted on /
** Root file system
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
FREE INODE COUNT WRONG IN SUPERBLK
FIX? y

** Phase 5 - Check Cyl groups
8 BLK(S) MISSING
BAD CYLINDER GROUPS
FIX? y

** Phase 6 - Salvage Cylinder Groups
1896 files, 0 icont, 42576 used, 41157 free (557 frags, 5075 blocks)
***** MARKING FILE SYSTEM CLEAN *****

***** FILE SYSTEM WAS MODIFIED *****

***** REBOOT HP-UX; DO NOT SYNC (USE reboot -n) *****
vxfs fsck: /dev/vg01/lvol1 is currently mounted

Please advice.

[Shibin_2]

Was this bdf output taken before doing fsck ?

Could you please repeat the fsck on /dev/vg00/lvol9 similarly as you done on lvol3 ? After that reboot the server as mentioned ( reboot -n )

[Yarok]

Yes, the bdf output taken before doing fsck.

Should I run the following command in order to repeat the fsck to lvol9?
/dev/vg00/lvol9/fsck

[Shibin_2]

Run this command.

/usr/sbin/fsck -o full -y /dev/vg00/lvol9

[Yarok]

I ran:
fsck /dev/vg00/lvol9

Received:

# fsck /dev/vg00/lvol9/
fsck: /etc/default/fs is used for determining the file system type
** /dev/vg00/lvol9/
** Last Mounted on /var
** Phase 1 - Check Blocks and Sizes

CANNOT READ: BLK 212080
CONTINUE? Yes


CANNOT READ: BLK 212080
CONTINUE? YES


CANNOT READ: BLK 212080
CONTINUE? YES

FAILED READ OF BLOCK #212080, RETRIED 2 TIMES
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Cyl groups
SUMMARY INFORMATION (INODE FREE) BAD
BAD CYLINDER GROUPS
FIX? y

** Phase 6 - Salvage Cylinder Groups
17884 files, 0 icont, 328509 used, 632216 free (7096 frags, 78140 blocks)
DISK MEDIA PROBLEMS ENCOUNTERED!
BAD BLOCKS WERE FOUND ON THE DISK.
***** FILE SYSTEM IS NOT CLEAN -- DISK MEDIA PROBLEMS ENCOUNTERED *****

***** FILE SYSTEM WAS MODIFIED *****

[Yarok]

When I run this command:
/usr/sbin/fsck -o full -y /dev/vg00/lvol9


It says:
fsck: illegal option --o
(It is the "o" letter or did you mean to "0" - zero?)

[Shibin_2]

See this errors.

DISK MEDIA PROBLEMS ENCOUNTERED!
BAD BLOCKS WERE FOUND ON THE DISK.
***** FILE SYSTEM IS NOT CLEAN -- DISK MEDIA PROBLEMS ENCOUNTERED *****

you may try to mount the lovol9 .. if it is mounted, you lucky otherwise, it is still having problem.

I think, you need to repeat fsck to fix that issue.

It was letter"o" not digit "0". If you have similar version of HP-UX machine available, read man page of fsck to get options.

[Yarok]

Can you please specify what commands should I use in order to check if the lvol9 is mounted and perform the fsck again?

[Shibin_2]

first, if you are still in single user mode, run fsck ( may be use /sbin/fsck path )

fsck -o full -y /dev/vg00/lvol9

After that, you try to mount lvol9

mount -F vxfs /dev/vg00/lvol9 /var

[Yarok]

I ran the fsck as you recommanded (bye the way Iv already done it before):

isL> /sbin/fsck -F vxfs -o full -y /dev/vg00/lvol0

I'v got:

Invalid super-block
search for auxiliary super-blo? (ynq)y
alternate super-block not found
vxfs fsck: cannot initialize aggregate.

Then I tried to mount as per your offer:

mount -F vxfs/dev/vg00/lvol9 /var
and it says that
vxfs mount: /dev/vg00/lvol9 is not a vxfs file system.

Please advice.

[sarfaraj ahmad]

Hi,
just try to mount as below and see what is the result,

mount /dev/vg00/lvol9 /var

[sarfaraj ahmad]

in addition also check the content of /etc/fstab file for more detail about this volume and filesystem.

[Yarok]

Hi,

mount /dev/vg00/lvol9 /var says that it need to be fsck'ed first.

I attached the /etc/fstab file. (I think it looks ok accept, I don't see the HP machine called hmb3. all other HP machine marke # are there).

I also checked the /etc/mntab and lvol9 wasn't there:

/dev/vg00/lvol3 / hfs defaults 0 1 1295955254
/dev/vg00/lvol1 /stand hfs defaults 0 0 1295955256
/dev/vg00/lvol8 /usr hfs defaults 0 0 1295955654
/dev/vg00/lvol7 /tmp hfs defaults 0 0 1295955655
/dev/vg00/lvol5 /opt hfs defaults 0 0 1295955655
/dev/vg00/lvol4 /home hfs defaults 0 0 1295955655
/dev/vg01/lvol1 /disk2 vxfs delaylog,nodatainlog 0 0 1295955655
hmb3:(pid672) /net ignore ro,intr,port=847,map=-hosts,indirect,dev=0000 0 0 1295955685

Thanks.

[sarfaraj ahmad]

Hi yarok,

As per your fstab output /var is a hfs so try below commands,

/sbin/fsck -F hfs /dev/vg00/lvol9
(go through the fsck man page for other options you may use)

after completion try to mount lvol9

mount /dev/vg00/lvol9
or,
mount -F hfs /dev/vg00/lvol9 /var

Hope it will resolve your issue.

[Yarok]

Ok, thank you.
Should I do it on a single user mode (run level S) or it does not metter?

[Dennis Handly]

>Should I do it on a single user mode (run level S) or it does not matter?

If you are already past single user mode, it doesn't matter.

[Yarok]

Hi,
I ran:
/sbin/fsck -F hfs /dev/vg00/lvol9

Received again the same:

# fsck /dev/vg00/lvol9/
fsck: /etc/default/fs is used for determining the file system type
** /dev/vg00/lvol9/
** Last Mounted on /var
** Phase 1 - Check Blocks and Sizes

CANNOT READ: BLK 212080
CONTINUE? Yes


CANNOT READ: BLK 212080
CONTINUE? YES


CANNOT READ: BLK 212080
CONTINUE? YES

FAILED READ OF BLOCK #212080, RETRIED 2 TIMES
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Cyl groups
SUMMARY INFORMATION (INODE FREE) BAD
BAD CYLINDER GROUPS
FIX? y

** Phase 6 - Salvage Cylinder Groups
17884 files, 0 icont, 328509 used, 632216 free (7096 frags, 78140 blocks)
DISK MEDIA PROBLEMS ENCOUNTERED!
BAD BLOCKS WERE FOUND ON THE DISK.
***** FILE SYSTEM IS NOT CLEAN -- DISK MEDIA PROBLEMS ENCOUNTERED *****

***** FILE SYSTEM WAS MODIFIED *****

Then I treid to
mount -F hfs /dev/vgoo/lvol9 /var
and I been told again to run the fsck first...
Any idea?
Can you point out the problem?
I mean-what excatly is the problem (volume crush? block demege? other?)

[Dennis Handly]

>Then I tried to
>mount -F hfs /dev/vgoo/lvol9 /var

You can only mount it read only. Your disk is junk and must be replaced.

>Can you point out the problem?

As it said:
CANNOT READ: BLK 212080
DISK MEDIA PROBLEMS ENCOUNTERED!
BAD BLOCKS WERE FOUND ON THE DISK.

[Yarok]

Thank you for your reply.
The rest lvol are fine. Consider that, should I replace phisically the whole disk or can I fix onlt the dammaged volume?
Bye the way, we can do the usual work on this HP station.

[Dennis Handly]

>should I replace physically the whole disk or can I fix only the damaged volume?

You can only replace entire physical disks.

>we can do the usual work

And you don't need /var/? I suppose you are using space under /.
If so, you have lost your IPD and you can't install patches. /var/adm/sw/

[Yarok]

Solutions like PV VG LV creat cant halp here?

[sarfaraj ahmad]

hi,
please replace the entire disk. which is the best solution.

so many people has helped you in this regard so don't forget to assign them points.

Thanks.

[Yarok]

Thank you all for the help.

The solutin is pretty diapointed - but nothing alse to do :)

I put the points for each one of you (I dont know if I need to do it as per answer)

BR,

Yaron