fsck doesn't work - not even run?

[Morhoo]

Hi,

please consider, I'm pretty new to HP-UX, thanks.

Our server (rp7420 with HP-UX 11.31) has crashed due to disk write error (not boot partition). So I replaced damaged device with the new one of the same size and performed dd copy 1:1 to restore data - vxfs partition "/dev/vg01/lvol1" mounted as "/data" and some raw devs. After reboot system wrote this error: "vxfs mount: V-3-21268: /dev/vg01/lvol1 is corrupted. needs checking". So I wanted to run fsck command to fix filesystem, logged as root, but to my surprise nothing happened. No error, no output, no result. Just like if it wouldn't run. I'm sure I was able to run fsck many times before and I tried many variants of parameters, no deal. Any suggestions how to fix FS without using fsck? Or better, how to repair fsck to run properly? Thanks for every advice.

Add: Disc was replaced directly by HP technician. Unfortunately that server is not further under any support licence from HP. I just wonder why fsck is failing to run now and has no response.

Thanks

[melvyn burnard · Accepted solution]

when you say "does nothing", what do you get?
Just a prompt back?
If so, sounds like you have an empty executable file.

[Torsten.]

From where did you restore the data? Sure it isn't corrupted too?

[Morhoo]

This is example of output:

root@rp7420:/usr/sbin> mount -a
vxfs mount: V-3-21268: /dev/vg01/lvol1 is corrupted. needs checking
mount: /dev/vg00/lvol8 is already mounted on /var
mount: /dev/vg00/lvol7 is already mounted on /usr
mount: /dev/vg00/lvol6 is already mounted on /opt
mount: /dev/vg00/lvol5 is already mounted on /home
mount: /dev/vg00/lvol4 is already mounted on /tmp
mount: /dev/vg00/lvol1 is already mounted on /stand
root@rp7420:/usr/sbin> fsck -m /dev/vg01/lvol1
root@rp7420:/usr/sbin>

fsck seems to do noting.

[Morhoo]

Source of restore was damaged disc itself. Data may be truly corrupted, but why fsck behaves like that? Could it be damaged too?

Thanks.

[Dennis Handly]

>Could it be damaged too?

Which disk was damaged?
What does "ls -l /sbin/fs_wrapper" show?

This seems to look at /sbin/lib/mfsconfig.d and /usr/lbin/fs/*.

[Bill Hassell]

Since the data seems to be corrupted, you may want to run newfs on one of the vg01 lvols (or create a new small lvol), then run fsck on the (empty) filesystem. If fsck works OK, the dd copy may not have worked correctly or may have copied bad data. Was the source disk for dd part of a mirrored pair? You may have to restore from your backup tapes.

[Morhoo]

root@rp7420:/> ls -l /sbin/fs_wrapper
-r-xr-xr-x 1 bin bin 0 Nov 3 18:23 /sbin/fs_wrapper

(zero size??)

root@rp7420:/>ls -l /sbin/lib/mfsconfig.d
total 64
-r--r--r-- 1 bin bin 695 Jan 12 2007 cachefs
-r--r--r-- 1 bin bin 984 Feb 15 2007 hfs
-rw-r--r-- 1 root sys 0 Nov 4 02:51 ls
-r--r--r-- 1 bin bin 924 Jan 12 2007 vxfs
-r--r--r-- 1 bin bin 3448 Jun 26 2007 vxfs5.0

root@rp7420:/>ls -l /usr/lbin/fs
total 32
dr-xr-xr-x 2 bin bin 8192 Dec 5 2007 hfs
dr-xr-xr-x 2 bin bin 8192 Dec 5 2007 vxfs
dr-xr-xr-x 2 bin bin 96 Dec 5 2007 vxfs5.0

Bad disk was standalone and was not mirrored. I can use backup tape, but i can't create new filesystem as long as fsck doesn't work at all. :-(

[Torsten.]

I would start over - remove LVOL and VG, pvcreate the disks, create the VG and LVOL again, then the file system. Restore your data now.

[Dennis Handly]

>-r-xr-xr-x 1 bin bin 0 Nov 3 18:23 /sbin/fs_wrapper
>(zero size??)

Yes, that's enough to explain why nothing happens. Do you have another machine where you can try extracting fs_wrapper?

Was it the root disk that went bad?