• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2263
  • Last Modified:

AIX VG hdisk Issue

I have a VG with with 6 disks in it and look like 2 disks are having issues from past 1 weeks, The disk# are hdisk19 and hdisk20, When I run a LSVG then here is the output

# lsvg -p corpstg
corpstg:
PV_NAME           PV STATE          TOTAL PPs   FREE PPs    FREE DISTRIBUTION
hdisk19           active            541         0           00..00..00..00..00
hdisk20            active            541         104         05..00..00..00..99
hdisk34           active            67          19          14..00..00..00..05

These volumes are not accessible

$ lqueryvg -Ptp /dev/hdisk19
0516-062 lqueryvg: Unable to read or write logical volume manager
        record. PV may be permanently corrupted. Run diagnostics
$ lqueryvg -Ptp /dev/hdisk20
0516-062 lqueryvg: Unable to read or write logical volume manager
        record. PV may be permanently corrupted. Run diagnostics


Now We add 2 more disks to our VIO client and looks like the 2 new disks have hdisk19 and hdisk20, So what must have happened to the old disks..???
0
mnis2008
Asked:
mnis2008
  • 3
1 Solution
 
mnis2008Author Commented:
SO did AIX drop hdisk19 and hdisk20 from ODM due to disk issues from a long time and when the new disks came in it gave hdisk19 and hdisk20
0
 
woolmilkporcCommented:
I think I don't understand quite well ...

You say that you have a VG with 6 disks, but lsvg -p shows just 3.

What do you see with "lspv"?

AIX never removes devices permanently from ODM. It will give them "Defined" status in case of serious trouble, that's all.
The only way to get rid of obsolete devices is "rmdev -d ...".

What do you see with "lsdev -Ccdisk"?

Did  you add the new disks to any/this VG already?

If you didn't, what do you get with "varyonvg corpstg"?

Generally, what does "errpt" say?

Please describe chronologically what you did and which output of which command you saw at which point in time inbetween.
0
 
mnis2008Author Commented:
Looks like storage has accidentally drop these disks and that is why we were not able to access
0
 
mnis2008Author Commented:
With the above checks I was able to find the root cause
0

Featured Post

Important Lessons on Recovering from Petya

In their most recent webinar, Skyport Systems explores ways to isolate and protect critical databases to keep the core of your company safe from harm.

  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now