topic Re: can't mount a file system in Operating System - HP-UX

can't mount a file system

hp admin — Wed, 31 Mar 2004 10:09:35 GMT

I tried to mount /dev/vg00/lvol9, but the system displays some errors.

jupiter,sys,root > mount /dev/vg00/lvol9
mount: /dev/vg00/lvol9 needs to be fsck'ed before mounting
mount: warning: if device /dev/vg00/lvol9 is mounted to another system
then do not run fsck
jupiter,sys,root >

Then I launched a fsck on this partition but the problem still here:jupiter,sys,root > fsck /dev/vg00/lvol9
** /dev/vg00/lvol9
** Last Mounted on /mnt
** Phase 1 - Check Blocks and Sizes

CANNOT READ: BLK 1368256
CONTINUE? y

CANNOT READ: BLK 1368256
CONTINUE? y

CANNOT READ: BLK 1368256
CONTINUE? y

FAILED READ OF BLOCK #1368256, 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
41254 files, 0 icont, 4336026 used, 216134 free (2334 frags, 26725 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 *****
jupiter,sys,root >

Can you help me, please ?
And is the pvmove command can solve this problem ?

Re: can't mount a file system

Kent Ostby — Wed, 31 Mar 2004 10:16:50 GMT

CANNOT READ: BLK almost always means that you've got a bad disk drive.

While I haven't done a lot with the pvmove, if fsck can't read the blk then pvmove probably wont be able to read the blk either.

In the past this was always a disk replacement situation.

Best regards,

Kent M. Ostby

Re: can't mount a file system

Robert-Jan Goossens — Wed, 31 Mar 2004 10:35:09 GMT

Looks like your disk is broken, you could try to mount the filesystem read only, and copy the data to an other file system. This way you won't loose ALL your data.

You will need to call HP and get the disk changed.

# mount -o ro /dev/vg00/lvol9 /mnt
# find /mnt | cpio -pcmudv /copy

HTH,
Robert-Jan

Re: can't mount a file system

Fabio Ettore — Wed, 31 Mar 2004 10:35:55 GMT

Hi,

I agree with Kent.

DISK MEDIA PROBLEMS ENCOUNTERED

After that I faced this error on fsck three times and solution was only the replacement of disk....well I would say to substitute the disk as soon as possible, also it is about vg00!

Best regards,
Ettore

Re: can't mount a file system

hp admin — Wed, 31 Mar 2004 11:25:42 GMT

Thanks to all for answers,

Even if I tried to mount the lvol file system, the error is submitted, and the system implies to fsck'ed the partition.

And as in my first message I can't fsck'ed it.

It's really a problem to lose data.

Re: can't mount a file system

Robert-Jan Goossens — Wed, 31 Mar 2004 11:40:25 GMT

Hi,

force the mount and copy the data as soon as possible.

HFS
# mount -f /dev/vg00/lvol4 /mnt

VXFS
# mount -o ro /dev/vg00/lvol4 /mnt

Regards,

Robert-Jan

Re: can't mount a file system

SureshKumar_2 — Fri, 02 Apr 2004 07:14:53 GMT

Hi

if u could get all the lv's (lvdisplay -v /dev/dsk/lvol9) certainly you can able to move the data thru' pvmove

Add an additional/spare Harddisk.

Try moving only this volume by issuing the following command....

pvmove -n dev/vg00/lvol9

If this has completed successfully, u may try with other volumes to new hdd..

I hope certainly pvmove will help...

All the best

suresh

Re: can't mount a file system

doug mielke — Fri, 02 Apr 2004 09:01:10 GMT

It does look like a disk failure. Try looking for lbolt errors in syslog to confirm. If good backups are available, that's the ticket.

if not, remember that fsck does not always clean fs on 1st try.
fsck -o full -y
for 4 or 5 times could be required.

also, I've never tried, but have been told there is an occasional quick fix in

fsdb.

Re: can't mount a file system

hp admin — Fri, 02 Apr 2004 10:20:18 GMT

I have added a new disk, then create a new LV (lvoltmp) in which I did a copy of all data that were on the old LV (lvol9) with the command:
dd if=/dev/vg00/rlvol9 of=/dev/vg00/rlvoltmp bs=1024k conv=noerror,sync

NB: the conv option is very interessant (look man pages)
noerror: Do not stop processing on an input error. If the sync conversion symbol is also specified, missing input is replaced with null bytes and processed normally; otherwise, the input block is omitted from the output.

Now, I'll try to reformat my old LV and return data on it.

Thank you all for your help.

Re: can't mount a file system

hp admin — Thu, 08 Apr 2004 05:06:20 GMT

Hello,

I recreate my lvol9 with -r n (see man page for info)

Just have a look on the link,
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=542133

After that, I reformat my original LV (lvol9)and I have copied data from the newly LV (lvoltmp)

But, I get a problem, my lvol9 becomes full (100%), after verification I found that the lost+found directory contain too files which have about 110 Mo each, and efectively some other files.

Now my question, If I delete files on lost+found directory to get free space, will I have any problem ?

Please your help.