![]() ![]() If the PVID on the drive is in the VGDA, but not in the ODM, the ODM can be updated by forcing a re-read of the PVID from the drive using the chdev command.ĭo NOT run this command unless you have verified that there is a PVID on the drive AND that PVID is in the VGDA also on the drive.Īfter this check to see if the physical volume shows up with no errors:ģ. The PVIDs in the VGDA can be viewed easiest using lqueryvg: If a PVID is returned but does not match what lspv or the ODM show, then does it exist in the VGDA? It's possible after this you may need to try the varyonvg again.Ģ. If varyonvg does not go out and find the disk, we may have to force it into an available state so LVM will check it. ![]() ![]() Which should force the volume group to go out and probe all physical volumes belonging to it.ġb. ![]() If yes then it's possible there was some temporary problem accessing the disk. In the above output the PVID is the 2nd and 3rd columns combined.ĭoes the PVID returned match the output from lspv ?ġ. You will need to be root or su'ed to root to run this command and many of the ones that follow.Ġ0000080 00050A85 A9B17061 00000000 00000000 |.pa.| This technique uses a lower-level command that bypasses the ODM and will print out information recorded on the disk. Try to read the PVID directly off the drive. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |