Fsck Query

[Jim Adamson]

I am have a problem fixing a hfs file system using fsck on hp-ux 10.20. When I run fsck manually on vg01/lvol1 I receive the following error messages -

CANNOT READ BLOCK 70224
CANNOT READ BLOCK 70240
CANNOT READ BLOCK 100336
Phase 5 - BAD CYLINDER GROUPS
Phase 6 - DISK MEDIA PROBLEMS ENCOUNTERED, BAD BLOCKS WERE FOUND ON THE DISK.

Once fsck is finished the file system will still not mount.

I have a full dump of this logical volume. Is there any way to fix this volume without having to delete it, then recreate it and restore the files from back up. Maybe its a disk fault?

Any help will be greatly appreciated
Jim

[Rainer_1]

examine the lvol

lvdisplay -v /dev/vg00/lvol1

and look for any stale extents.

[Carol Garrett · Accepted solution]

There is no way to recover it. You have bad blocks on it which fsck cannot fix. You need to delete it, re-initialise it and recover what you can.

only thing you could try is create another lvol the exact same size and dd the one you cant fsck to the new one. If the dd works your in luck, you have a copy of your data, if not, your dead. (ie. dd if=/dev/vgXX/rlvolXX of=/dev/vgXX/rvlolXY bs=64k)

[Dan Hetzel]

Hi Jim,

Good news first: you said you had a full dump of this volume
;-))

Bad news: if fsck claims that there are bad blocks, you'll never be able to mount this volume again, as fsck won't fix anything.
The only solution is a low level format of your disk.
:-((

Good luck

Dan

[CHRIS_ANORUO]

I will advice that you get a new disk, if you can backup information on this do so and restore on another disk.

[federico_3]

I think you have to delete this file system, then recreate it and restore the files from back up.

federico

[Paula J Frazer-Campbell]

Hi
Check out
http://europe-support.external.hp.com/cki/bin/doc.pl/sid=b021e3930f8bf0cd15/screen=ckiDisplayDocument?docId=400000000247125

[Harish Kumar Sudhamalal]

Hi

lvol1 normally refers to the root. I hope you are running fsck manually in single user mode.

Also I hope you are using the character device file name while doing fsck.

As fsck is pointing that it has bad blocsk on the disk, I would recommend that either you change your disk or recreate the file system.

(You have the backup and the data recovery should not be a problem)

- Bye

[Jim Adamson]

Thanks everyone, its going to be a new disk and restore.

Jim.