Get the App
SLTechnology News&Howtos  ›  Servers  › 

Hd5 repair, one of the faults of AIX system

Shulou Source: shulou.com Published: 2022-06-02 08:39:14 10月05日 Update

AIX System Repair hd5

System environment:

Operating System: AIX5308

Fault phenomenon:

HD5 was deleted by mistake, error in cfgmgr execution!

1. View rootvg information

# lsvg -l rootvg

rootvg:LV NAME TYPE LPs PPs PVs LV STATE MOUNT POINThd6 paging 4 4 1 open/syncd N/Ahd8 jfs2log 1 1 1 open/syncd N/Ahd4 jfs2 40 40 1 open/syncd /hd2 jfs2 16 16 1 open/syncd /usrhd9var jfs2 16 16 1 open/syncd /varhd3 jfs2 8 8 1 open/syncd /tmphd1 jfs2 120 120 1 open/syncd /homehd10opt jfs2 1 1 1 open/syncd /optfwdump jfs2 1 1 1 open/syncd /var/adm/ras/platformfslv06 jfs 120 120 1 closed/syncd N/A no hd5 lv

2. Error in executing cfgmgr

# cfgmgr -v

......

Calling savebase

Return code = 1

*** no stdout ****

*** no stderr ****

cfgmgr: 0514-609 Unable to save the base customized information

on /dev/ipldevice.

Fix startup lv:

# bosboot -ad /dev/ipldevice

0301-168 bosboot: The current boot logical volume, /dev/hd5,

does not exist on /dev/hdisk5.

Synchronous LV:

# synclvodm -P -v rootvg

synclvodm: Physical volume data updated.synclvodm: Logical volume hd6 updated.synclvodm: Logical volume hd8 updated.synclvodm: Logical volume hd4 updated.synclvodm: Logical volume hd2 updated.synclvodm: Logical volume hd9var updated.synclvodm: Logical volume hd3 updated.synclvodm: Logical volume hd1 updated.synclvodm: Logical volume hd10opt updated.synclvodm: Logical volume fwdump updated.synclvodm: Logical volume fslv06 updated.

# lsvg -l rootvg

rootvg:LV NAME TYPE LPs PPs PVs LV STATE MOUNT POINThd6 paging 4 4 1 open/syncd N/Ahd8 jfs2log 1 1 1 open/syncd N/Ahd4 jfs2 40 40 1 open/syncd /hd2 jfs2 16 16 1 open/syncd /usrhd9var jfs2 16 16 1 open/syncd /varhd3 jfs2 8 8 1 open/syncd /tmphd1 jfs2 120 120 1 open/syncd /homehd10opt jfs2 1 1 1 open/syncd /optfwdump jfs2 1 1 1 open/syncd /var/adm/ras/platformfslv06 jfs 120 120 1 closed/syncd N/A Missing hd5 lv

Re-create HD5, error:

# mklv -y hd5 -t boot -a e rootvg 1

0516-360 getlvname: The device name is already used; choose a

different name.

0516-822 mklv: Unable to create logical volume.

0516-1734 mklv: Warning, savebase failed. Please manually run 'savebase' before rebooting.

# synclvodm -P -v rootvg

synclvodm: Physical volume data updated.synclvodm: Logical volume hd6 updated.synclvodm: Logical volume hd8 updated.synclvodm: Logical volume hd4 updated.synclvodm: Logical volume hd2 updated.synclvodm: Logical volume hd9var updated.synclvodm: Logical volume hd3 updated.synclvodm: Logical volume hd1 updated.synclvodm: Logical volume hd10opt updated.synclvodm: Logical volume fwdump updated.synclvodm: Logical volume fslv06 updated.

3. Solution:

Remove HD5 via ODM:

# odmdelete -q name=hd5 -o CuDv

1 objects deleted

# odmdelete -q name=hd5 -o CuAt

6 objects deleted

HD5:

# mklv -y hd5 -t boot -a e rootvg 1

hd5

Synchronous LV:

# synclvodm -P -v rootvg

synclvodm: Physical volume data updated.synclvodm: Logical volume hd6 updated.synclvodm: Logical volume hd8 updated.synclvodm: Logical volume hd4 updated.synclvodm: Logical volume hd2 updated.synclvodm: Logical volume hd9var updated.synclvodm: Logical volume hd3 updated.synclvodm: Logical volume hd1 updated.synclvodm: Logical volume hd10opt updated.synclvodm: Logical volume fwdump updated.synclvodm: Logical volume fslv06 updated.synclvodm: Logical volume hd5 updated.

# lsvg -l rootvg

rootvg:LV NAME TYPE LPs PPs PVs LV STATE MOUNT POINThd6 paging 4 4 1 open/syncd N/Ahd8 jfs2log 1 1 1 open/syncd N/Ahd4 jfs2 40 40 1 open/syncd /hd2 jfs2 16 16 1 open/syncd /usrhd9var jfs2 16 16 1 open/syncd /varhd3 jfs2 8 8 1 open/syncd /tmphd1 jfs2 120 120 1 open/syncd /homehd10opt jfs2 1 1 1 open/syncd /optfwdump jfs2 1 1 1 open/syncd /var/adm/ras/platformfslv06 jfs 120 120 1 closed/syncd N/Ahd5 boot 1 1 1 closed/syncd N/Ahd5 Repair successful!

Refix startup lv:

# bosboot -ad /dev/ipldevice

cfgmgr Normal:

# cfgmgr -v...... Calling savebaseReturn code = 0*** no stdout ******* no stderr ****Configuration time: 1 seconds

Tags: System synchronization failure success operating system Information method Times Environment phenomenon Apple Docker Huawei Linux macOS MariaDB Microsoft MySQL NVidia OPPO Reno Huawei OPPO Reno Microsoft MariaDB Shulou Tech Info