Corrupted DCD/ODM, LVM problems with hdisk

[A. Gordon Lyph]

Hello-

I have an issue on a p650 where I can't rmdev -dl hdisk4. Here is the
error message:

Method error (/etc/methods/ucfgdevice):
0514-043 Error getting or assigning a minor number.

This disk was previously mounted in a VG/LV from a SAN over FC. The
SAN was modified and hdisk4 became an issue. At some point, I
believe, the VG was exported, and then the trail gets fuzzy.

At any rate, here is what I've tried so far today to get rid of the

lsvg -o

0516-304 : Unable to find device id 0000bdda00004c00000000fbcaaac1f5
in the Device
Configuration Database.
vgid=0000bdda00004c00000000fbcaaac1f5
tst2vg
tstvg
rootvg

lsvg -o | lsvg -i -l

0516-304 : Unable to find device id 0000bdda00004c00000000fbcaaac1f5
in the Device
Configuration Database.
0516-306 : Unable to find volume group
vgid=0000bdda00004c00000000fbcaaac1f5 in the Device
Configuration Database.

varyonvg -m1 testingvg

0516-310 varyonvg: Unable to find attribute lock in the Device
Configuration Database. Execute synclvodm to attempt to
correct the database.

synclvodm testingvg

0516-306 : Unable to find volume group testingvg in the Device
Configuration Database.
0516-502 synclvodm: Unable to access volume group testingvg.

lqueryvg -Pp /dev/hdisk4

0516-062 lqueryvg: Unable to read or write logical volume manager
record. PV may be permanently corrupted. Run diagnostics

ldeletepv -g <vgid copied from earlier lsvg -o output> -p hdisk4

0516-062 ldeletepv: Unable to read or write logical volume manager
record. PV may be permanently corrupted. Run diagnostics

odmget CuAt | grep hdisk4

<returns nothing>

odmget CuDvDr | grep hdisk4

<returns nothing>

odmget CuAt | grep testingvg

<returns nothing>

odmget CuDvDr | grep testingvg

<returns nothing>

rmdev -l hdisk4 -SR

hdisk4 Available

rmdev -l hdisk4 -d

Method error (/etc/methods/ucfgdevice):
0514-043 Error getting or assigning a minor number.

It looks to me like any reference to hdisk4 explicitly in the ODM is
gone, while at the same time, there are some phantom references to
testingvg hanging around 'somewhere' (VGDA?) but I can't seem to get
rid of them.

Any suggestions, hints, thoughts greatly appreciated.

AG

[Tom Van Overbek]

Post by A. Gordon Lyph
Hello-
I have an issue on a p650 where I can't rmdev -dl hdisk4. Here is the
0514-043 Error getting or assigning a minor number.
This disk was previously mounted in a VG/LV from a SAN over FC. The
SAN was modified and hdisk4 became an issue. At some point, I
believe, the VG was exported, and then the trail gets fuzzy.

try running synclvodm without any parameters at all ?

Tom.

[A. Gordon Lyph]

Post by Tom Van Overbek
try running synclvodm without any parameters at all ?

Tom-

Thanks for the suggestion, but running synclvodm with out params or
flags only gives the usual return:

Usage: synclvodm [-v] [-P] VGname [LVname...]

When I run synlvodm -v testingvg, I get:

0516-306 : Unable to find volume group testingvg in the Device
Configuration Database.
0516-502 synclvodm: Unable to access volume group tetsingvg.

Which indicates to me that the ODM seems to not know about testingvg
anymore.

Thanks again,

AG

[Claudiu Costin]

Hi Gordon,

Post by A. Gordon Lyph
Hello-
I have an issue on a p650 where I can't rmdev -dl hdisk4. Here is the
0514-043 Error getting or assigning a minor number.
This disk was previously mounted in a VG/LV from a SAN over FC. The
SAN was modified and hdisk4 became an issue. At some point, I
believe, the VG was exported, and then the trail gets fuzzy.

1) Have you tried a cfgmgr or cfgmgr -l fcs0 first?
2) Have you tried a reboot? (may be is a garbage in kernel)

Post by A. Gordon Lyph
At any rate, here is what I've tried so far today to get rid of the

lsvg -o

0516-304 : Unable to find device id 0000bdda00004c00000000fbcaaac1f5
in the Device
Configuration Database.
vgid=0000bdda00004c00000000fbcaaac1f5
tst2vg
tstvg
rootvg

lsvg -o | lsvg -i -l

0516-304 : Unable to find device id 0000bdda00004c00000000fbcaaac1f5
in the Device
Configuration Database.
0516-306 : Unable to find volume group
vgid=0000bdda00004c00000000fbcaaac1f5 in the Device
Configuration Database.

varyonvg -m1 testingvg

0516-310 varyonvg: Unable to find attribute lock in the Device
Configuration Database. Execute synclvodm to attempt to
correct the database.

synclvodm testingvg

0516-306 : Unable to find volume group testingvg in the Device
Configuration Database.
0516-502 synclvodm: Unable to access volume group testingvg.

lqueryvg -Pp /dev/hdisk4

0516-062 lqueryvg: Unable to read or write logical volume manager
record. PV may be permanently corrupted. Run diagnostics

ldeletepv -g <vgid copied from earlier lsvg -o output> -p hdisk4

0516-062 ldeletepv: Unable to read or write logical volume manager
record. PV may be permanently corrupted. Run diagnostics

odmget CuAt | grep hdisk4

<returns nothing>

odmget CuDvDr | grep hdisk4

<returns nothing>

odmget CuAt | grep testingvg

<returns nothing>

odmget CuDvDr | grep testingvg

<returns nothing>

rmdev -l hdisk4 -SR

hdisk4 Available

rmdev -l hdisk4 -d

0514-043 Error getting or assigning a minor number.
It looks to me like any reference to hdisk4 explicitly in the ODM is
gone, while at the same time, there are some phantom references to
testingvg hanging around 'somewhere' (VGDA?) but I can't seem to get
rid of them.
Any suggestions, hints, thoughts greatly appreciated.
AG

[A. Gordon Lyph]

Post by Claudiu Costin
1) Have you tried a cfgmgr or cfgmgr -l fcs0 first?
2) Have you tried a reboot? (may be is a garbage in kernel)

Claudiu-

Yes, I've tried #1 and it doesn't change anything. I still have
hdisk4 hanging about (interestingly enough, if I do an ls in /dev, it
doesn't show there, though).

I will have to schedule an outage for #2...the developers will love
that. Something about being behind schedule... :)

AG