HPE Community read-only access December 15, 2018
This is a maintenance upgrade. You will be able to read articles and posts, but not post or reply.
Hours:
Dec 15, 4:00 am to 10:00 am UTC
Dec 14, 10:00 pm CST to Dec 15, 4:00 am CST
Dec 14, 8:00 pm PST to Dec 15, 2:00 am PST
cancel
Showing results for 
Search instead for 
Did you mean: 

controller changed

 
SOLVED
Go to solution
himacs
Super Advisor

controller changed

Hi Admins,



Storage team changed the controller of LUNS c9t#d# and c10t#d# . Now it became c21t#d# and c22t#d# .But during the activity VG was active in server.

Now ioscan shows both - new and old device files.Now we cant deactivate the VG.If we try to unmount any LV,it throws error. - no entry found in /etc/mnttab .
please suggest .

Regards
himacs

4 REPLIES
Manix
Honored Contributor
Solution

Re: controller changed

Are you on 11.31..in that case device files
can be kept persistent.

>>If we try to unmount any LV,it throws error. - no entry found in /etc/mnttab


Regarding your /etc/mnttab file being out of sync with your /etc/fstab file
# mv /etc/mnttab /etc/mnttab.old
# mount -a

Please run vgscan -a -v -p preview mode and
check the results if VGs are able to detect new device files. ( send output )

We may need to recreate lvmtab file and then
import the VGs back with new device files & then start the cluster.
HP-UX been always lovable - Mani Kalra
Ismail Azad
Esteemed Contributor

Re: controller changed

Hi,

Do u need the old device file?? If not, remove it with rmsf.

Inconsistency of /etc/mnttab with the kernel data structures is a common issue. That can be one or interms of /etc/mnttab, maybe it's not present at all. Some malicious user would have deleted it!

For that you can do what Manix suggested as the command mount -a internally recreates /etc/mnttab. This approach is a common approach for getting out of the troubleshooting loop in terms of "mounting".

And if you are trying out what Manix suggested, I also suggest you remove the file you have renamed for /etc/mnttab with mv.

Regards
Ismail Azad
Read, read and read... Then read again until you read "between the lines".....
shanmuhanandam
Regular Advisor

Re: controller changed

Hi,

If you have only 2 paths to the PV's then, you can't access your VG's. bcoz the instance number has been changed. And you are able to access the new device files, so you need to the vgscan (as said earlier) in preview mode, confirm the vg details, then do the vgscan -a, and mountall. you will be able to access the lv's.

Thanks,
Shan.
I am an HPE Employee
Torsten.
Acclaimed Contributor

Re: controller changed

>> Storage team changed the controller of LUNS c9t#d# and c10t#d# . Now it became c21t#d# and c22t#d# .But during the activity VG was active in server.



If you are the admin of the server and you did not know about this change - bad planning!


However, have you still access over other paths to this VG?


If you are on 11.23 or below, consider to vgreduce the c9... and c10... devices and vgextend to c21... and c22...


Ask the team what they have done.

Changed switch ports?

Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!