From: Antonio R. (arv@VODAFONE.ES)
Date: Mon Mar 15 2004 - 06:56:17 EST
Problem continue ....
# synclvodm -v rootvg hd5
synclvodm: Physical volume data updated.
0516-532 synclvodm: logical volume hd5 not found in volume group rootvg.
#
# lslv hd5
LOGICAL VOLUME: hd5 VOLUME GROUP: rootvg
LV IDENTIFIER: 000002183308e6b7.1 PERMISSION: ?
VG STATE: active/complete LV STATE: ?
TYPE: boot WRITE VERIFY: ?
MAX LPs: ? PP SIZE: ?
COPIES: ? SCHED POLICY: ?
LPs: ? PPs: ?
STALE PPs: ? BB POLICY: ?
INTER-POLICY: minimum RELOCATABLE: no
INTRA-POLICY: edge UPPER BOUND: 32
MOUNT POINT: N/A LABEL: None
MIRROR WRITE CONSISTENCY: ?
EACH LP COPY ON A SEPARATE PV ?: yes
#
> Try "synclvodm rootvg hd5", or "synclvodm rootvg".
>
> If the boot information exists in the right physical location, on a disk
> that is in the bootlist then it will get used before LVM gets involved
> and notices that your rootvg is damaged. Once it's booted, it doesn't
> need it again.
>
> --
> Simon Green
> Altria ITSC Europe Ltd
>
> AIX-L Archive at https://new-lists.princeton.edu/listserv/aix-l.html
>
> New to AIX? http://publib-b.boulder.ibm.com/redbooks.nsf/portals/UNIX
>
> N.B. Unsolicited email from vendors will not be appreciated.
> Please post all follow-ups to the list.
>
> > -----Original Message-----
> > From: Antonio R. [mailto:arv@VODAFONE.ES]
> > Sent: 15 March 2004 10:07
> > To: aix-l@Princeton.EDU
> > Subject: Boot confoguration problem
> >
> >
> > Hi sysadmins,
> >
> > I have a 4.3.3 system with this rootvg defined logical volumes:
> > # lsvg -l rootvg
> > rootvg:
> > LV NAME TYPE LPs PPs PVs LV STATE
> > MOUNT POINT
> > hd6 paging 64 128 2 open/syncd N/A
> > hd8 jfslog 1 2 2 open/syncd N/A
> > hd4 jfs 2 4 2 open/syncd /
> > hd2 jfs 77 154 2 open/syncd /usr
> > hd9var jfs 4 8 2 open/syncd /var
> > hd3 jfs 3 6 2 open/syncd /tmp
> > hd1 jfs 1 2 2 open/syncd /home
> > hd7b sysdump 4 4 1 open/syncd N/A
> > hd7 sysdump 4 4 1 open/syncd N/A
> > lv00 jfs 32 64 2 open/syncd
> > /informix
> > #
> >
> > As you can see, there isn't hd5 lv.... and no boot logical volume.
> > If I execute lslv hd5:
> > # lslv hd5
> > LOGICAL VOLUME: hd5 VOLUME GROUP: rootvg
> > LV IDENTIFIER: 000002183308e6b7.1 PERMISSION: ?
> > VG STATE: active/complete LV STATE: ?
> > TYPE: boot WRITE VERIFY: ?
> > MAX LPs: ? PP SIZE: ?
> > COPIES: ? SCHED POLICY: ?
> > LPs: ? PPs: ?
> > STALE PPs: ? BB POLICY: ?
> > INTER-POLICY: minimum RELOCATABLE: no
> > INTRA-POLICY: edge UPPER BOUND: 32
> > MOUNT POINT: N/A LABEL: None
> > MIRROR WRITE CONSISTENCY: ?
> > EACH LP COPY ON A SEPARATE PV ?: yes
> > #
> >
> > But if I try to recover it:
> > # bosboot -ad /dev/hdisk0
> > 0516-022 lslv: Illegal parameter or structure value.
> >
> > 0301-168 bosboot: Current boot logical volume, /dev/hd5,
> > doesn't exist in /dev/hdisk0.
> > #
> >
> > That would be normal, because hd5 doesn't exist.
> > But, I can't create new hd5 nor new logical volume into rootvg.
> >
> >
> > Mysteriously, I've reboot the system... and it can do it.
> > Where is it finding boot device?
> >
> > This is my bootlist:
> > # bootlist -m normal -o
> > hdisk0
> > hdisk1
> > #
> >
> > How can I fix it, and redefine hd5?
>
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 22:17:42 EDT