Problems arising after AIX recovers the file system 0516-013

After AIX is re-installed due to power failure or damage, use resotre to restore the backup file system. First, the problem occurs. rootvg cannot be varyon. Of course, because it is a root volume group, it cannot be exportvg: 0516-013 The volume group cannot be varied
On because there are no good copies of the descriptor Area

An error similar to unable to find device ID 0066657d00004c00000000dc65c5cbc6 in the device configuration database is reported during the operation,The original error message and operation procedure are not recorded, but the error message is similar to the message. Please keep a record when you resolve the problem the next time.
.

 

Solution:

Delete data in ODM

 
Odmdelete-Q name = volumegroupname-O cuat


When the ODM database is synchronized, the following error occurs:
 

1. # Synclvodm-p-V rootvg
2. 0516-010: volume group must be varied on; Use varyonvg command.

Varyonvg also reports the following error:

1. # Varyonvg rootvg
2. 0516-008 varyonvg: LVM system call returned an unknown error code (3 ).

Solve the problem by using a brother:

Redefine the volume group and then varyon.

1. #Redefinevg-D hdisk0-I 0066657d3164c00001_dc65c5cbc6 rootvg
2. #Varyonvg-B rootvg

Perform the following three steps to solve the problem.

 

Finally, you may need to execute the synchronized volume group command. After completing the above operations, there is a problem with adding the additional language environment: 0506-907 cannot get volume group partition size

 

Synclvodm-v-F rootvg

 

---------------------------------------------------------------

 

Reference a brother'sArticle:

 

 

The problem that the AIX rootvg ODM library is not synchronized

 

There is a bad machine (I'm sorry to say). I want to add oneHard Disk
As an image.

1. # Extendvg rootvg hdisk1 reports an error saying that rootvg requires varyon.

CopyCode

If rootvg cannot be varyonSystem
The error 0555-0557 must be reported at startup, but the system is running normally and reboot is normal. The output results of the following commands are also weird.

1. # Lspv
2. Hdisk0 0066657dc6092c0b none
3. Hdisk1 none
4. # Lsvg-o
5. 0516-304 lsvg: unable to find device ID 0066657d00004c00000000dc65c5cbc6 in the device configuration database.
6. # Lsvg rootvg
7. 0516-010: volume group must be varied on; Use varyonvg command.

Copy code

Later, I used history to find someone used odmchange to change the ODM library. In my heart, synclvodm won't be OK.

1. # Synclvodm-p-V rootvg
2. 0516-010: volume group must be varied on; Use varyonvg command.
3. # Varyonvg rootvg
4. 0516-008 varyonvg: LVM system call returned an unknown error code (3 ).

Copy code

This is depressing ~ This error can be reported. If it is not rootvg, this case is also very easy. After the export is used, re-import it.
I used odmget to take a look at the ODM classes starting with several Cus. It seems very troublesome to start from here. I need a normal ODM database for comparison and it is easy to make mistakes.
Later I came up with a good idea, hehe.
Note that the preceding lsvg
-O's output contains a string of numbers (0066657d00004c00001_dc65c5cbc6), which must be a vgid and the system only has one VG.
It is the vgid of rootvg. When the system starts, it needs to read the vgid instead of the rootvg name. Therefore, the system can start normally.
The solution here is that the vgid does not correspond to the real rootvg.

1. # Redefinevg-D hdisk0-I 0066657d3164c00001_dc65c5cbc6 rootvg
2. # Varyonvg-B rootvg

Copy code

Use redefinevg to force the establishment of rootvg ing, and then use varyonvg-B to force the activation of rootvg (I am too lazy to restart, not recommended, it is better to save this reboot step)
Then, perform the following steps to create an image:

1. # Extendvg rootvg hdisk1
2. # Chvg-Qn rootvg
3. # Mirrorvg rootvg
4. # Bosboot-a-d/dev/hdisk1
5. # Bootlist-M normal hdisk0 hdisk1

Copy code