Error on mounting: unrecognized file system

[vz7r1x]

I am trying to mount a file system but it errors out.

# mount /dev/vga02/lvol05 /ar2
/dev/vga02/lvol05: unrecognized file system

# ls -l *vol05*
brw-r----- 1 root sys 64 0x050005 May 12 19:22 lvol05
crw-r----- 1 root sys 64 0x050005 Apr 13 2002 rlvol05

I am running HP 9000 with 11.00 HP-UX OS on it.

Any ideas please? Thanks

[Geoff Wild]

It means it either doesn't have a filesystem on it (IE - hasn't been newfs's yet) - or it is a filesystem that was created on a newer version of HP-UX.

Rgds...Geoff

[Geoff Wild]

BTW - is it in /etc/fstab ?

Rgds...Geoff

[vz7r1x]

Jeff
this fs is part of /etc/fstab. This FS was giving me errors, I could cd into it but could not see any files in it so I dismounted it using umount command. Now I can not mount it back on. This file system has been there for a long time. I do not have access to hardware and manage it remotely.

[Geoff Wild]

What is interesting is the timestamps of the files - looks like it was created back in 2002 - yet lvol05 was changed May 12 @19:22.

Try fsck

fsck -F vxfs /dev/vga02/rlvol05


or

fsck -F vxfs -o full /dev/vga02/rlvol05


Otherwise, you may have to rebuild it and restore the data.

Rgds...Geoff

[Torsten.]

Hi,

if it is in /etc/fstab, try only

mount /ar2

Of course you can "cd" into the mountpoint when it is not mounted - there is nothing.
This is pretty normal.

[vz7r1x]

Thanks Torsten.

When I do mount, I get another error:
# mount /ar2
mount - read of super-block on /dev/vga02/lvol05 failed: I/O error

I am suspecting hardware failure. I may have to rebuild that slice.

Reply to Jeff's Q: There are too many cooks out there on that server.

[Torsten.]

Try to run a "dd" on the disk. If this gives no error, continue with the fsck.
In case of I/O errors, refer to this document:
http://docs.hp.com/en/5991-1236/When_Good_Disks_Go_Bad.pdf

[Yogeeraj_1]

hi,

any errors in the /var/adm/syslog.log?

it could be a failing hardware...

revert

kind regards
yogeeraj

[vz7r1x]

Error seen in syslog is:

May 16 07:59:30 fse vmunix: vxfs: mesg 008: vx_direrr - /ar2 file system inode 2 block 129631 error 5

Thanks

[vz7r1x]

Jeff
DD output is pointing to HW failure:

# dd if=/dev/vga02/lvol05 of=/dev/null bs=1024k count=64
dd read error: I/O error
0+0 records in
0+0 records out
#
Thanks you all for vey helpful input.

[Geoff Wild]

As I said above - run:

fsck -F vxfs -o full /dev/vga02/rlvol05

Rgds...Geoff

[vz7r1x]

Geoff

I have already run that comand. Here is output from that command:
# fsck -F vxfs -o full /dev/vga02/rlvol05
cannot open device /dev/vga02/rlvol05
file system check failure, aborting ...
#

Thanks

[Geoff Wild]

Ah - okay - then it's dead Jim....

You will need to have it replaced and then restored - sorry.

Rgds...Geoff

[vz7r1x]

Thanks to everyone for helpful input.

[vz7r1x]

I just found out that more than 1 file sysem is affected. Here is the output from lvlnboot command:
/usr/sbin/lvlnboot -v
lvlnboot: Volume group not activated.
Cannot display volume group "/dev/vg01".
lvlnboot: Volume group not activated.
Cannot display volume group "/dev/vg03".
lvlnboot: Volume group not activated.
Cannot display volume group "/dev/vg04".
lvlnboot: Volume group not activated.
Cannot display volume group "/dev/vg06".
lvlnboot: Volume group not activated.
Cannot display volume group "/dev/vg07".
lvlnboot: Volume group not activated.
Cannot display volume group "/dev/vg09".

Also,

# /usr/sbin/ioscan -fk|grep -i lan
lan 0 0/0/0/0 btlan3 CLAIMED INTERFACE HP PCI 10/100Base-TX Core

lan 1 0/5/0/0 btlan5 UNCLAIMED UNKNOWN PCI Ethernet (10110019)

lan 2 0/10/0/0 gelan CLAIMED INTERFACE HP A4929A PCI 1000Base-T Adapter

lan 3 1/8/0/0 gelan CLAIMED INTERFACE HP A4929A PCI 1000Base-T Adapter

Nothing has changed on HW or SW or drivers. What could make Ethernet Card go wrong?

[Geoff Wild]

Looks like you may have something more (or other) then just a bad disk - could be a pci board...

Check syslog.log

Check EMS alerts.

Rgds...Geoff

[vz7r1x]

Where are EMS alerts located/stored to look for?

[Geoff Wild]

Usually you run a command from syslog....something like:

/opt/resmon/bin/resdata -R 409337859 -r /system/events/core_hw/core_hw -n 409337860 -a

Note: that was an example from one of my systems...

man ems
for more info

Rgds...Geoff