HP-UX 11.0 Mount point not working

[Doug_85]

We migrated about a year ago from a K server to a new L class server. A mount point was established for the old system and the old system files were placed on our SAN. The mount point is still on our system but we are unable to mount the filesystem. When we try to mount the file system it states /dev/emcvg01/Ksytem/
device not found. I checked in SAM and the mount point structure is still intact. It appears that we may need to recreate the device setting. Any suggestions on re-establishing or troubleshooting a mount point would be helpful. Also, I looked at the /etc/fstab file and noticed # signs in front of the non-working mount point. I thought it might be similiar to a REM in front of the line. Once I removed these # signs the structure to our EMC appeared on the system. Unfortunately, their just empty structures.

Thanks,
Doug

[Sridhar Bhaskarla]

Hi Doug,

Is it a syntax error?

/dev/emcvg01/Ksystem/ ?

For a logical volume you wouldn't see a trailing /.

Can you do a "vgdisplay -v emcvg01|grep "LV Name" and see if you get the logical volumes out of it?.

If it returns the error, then make sure the VG is activated 'vgchange -a y emcvg01" and then try. If it does not return error but the logical volumes, then make sure you are using the correct lv names. You will do something like

mount /dev/emcvg01/lvol1 /mount_point.

If you can post your /etc/fstab and vgdisplay -v emcvg01 we can be able to find the issue.

-Sri

[Doug_85]

The vgdisplay -v option displays the following error.

root[/] >vgdisplay -v emcvg01
vgdisplay: Volume group not activated.
vgdisplay: Cannot display volume group "emcvg01".
root[/] >


Also, the added / was a syntax error on my part.

Thanks,
Doug

[Patrick Wallek]

It sounds like the VG isn't getting activated for some reason. Try doing a:

# vgchange -a y /dev/emcvg01

If that succeeds then try mounting your LV and then troubleshoot the reason the VG is not being activated automatically. If it doesn't work, you may have VG troubles and just need to recreate and restore.

[Sridhar Bhaskarla]

Well, I wonder why the VG didn't get activated at boot time. You might have rebooted the server as it's been a year?. Try 'vgchange -a y emcvg01' and see if you get any errors. If it is activated, then you can mount the mount point. Make sure /etc/lvmrc is updated with this VG if the AUTO_VG_ACTIVATE has been set to 0.

-Sri

[Steven E. Protter]

strings /etc/lvmtab

There is probably a minor number conflict between this older volume group and one of the new ones.

Check the minor numbers on the /dev/vg##/group files.

I think if you resolve the conflict, you should be able to activate the vg with instructions already in the thread.

SEP

[Doug_85]

I'm currently making an ignite tape and will try out your suggestions shortly.

Thanks,
Doug

[Doug_85]

All of your solutions have been helpful. I will apply the simplest method first and then work my way up. Unfortunatly, I cannot reboot the server until tomorrow morning when noone is on the system. This may re-establish itself especially since the system has not been rebooted in several months. Also, taking the SAN on and off line in the last couple months due to new hardware and software configurations may have severed the connection.

Thanks,
Doug