From: JOSEPH KREMBLAS (JKREMBLAS@REDHEARTGIFTS.COM)
Date: Mon Mar 15 2004 - 12:43:00 EST
Antonio,
I duplicated your problem and here's what I did to fix it:
Script: doit_create_blv
------------------------------------------------
#!/bin/ksh
rmlv -f hd5
mkboot -d /dev/hdisk0 -c
mklv -y hd5 -t boot rootvg 1
echo ":C:C:C" | /usr/lpp/bosinst/blvset -d /dev/hdisk0
bosboot -a -d /dev/hdisk0
Send output results.
--joseph
-----Original Message-----
From: IBM AIX Discussion List [mailto:aix-l@Princeton.EDU] On Behalf Of
Antonio R.
Sent: Monday, March 15, 2004 9:32 AM
To: aix-l@Princeton.EDU
Subject: Re: Boot confoguration problem
Here is what you want:
# lqueryvg -Lp /dev/ipldevice
000002183308e6b7.2 hd6 1
000002183308e6b7.3 hd8 1
000002183308e6b7.4 hd4 1
000002183308e6b7.5 hd2 1
000002183308e6b7.6 hd9var 1
000002183308e6b7.7 hd3 1
000002183308e6b7.8 hd1 1
000002183308e6b7.9 hd7b 1
000002183308e6b7.10 hd7 1
000002183308e6b7.11 lv00 1
#
> Antonio,
>
> Execute the following command to determine if the boot logical
> volume is stored in the boot record:
>
> lqueryvg -Lp /dev/ipldevice
>
> Send output of command.
>
> --joseph
>
> Example:
> --------
> [root:suzkre]/bin>lqueryvg -Lp /dev/ipldevice
> 0010600bc3e7d4f2.1 hd5 1
> 0010600bc3e7d4f2.2 hd6 1
> 0010600bc3e7d4f2.3 hd8 1
> 0010600bc3e7d4f2.4 hd4 1
> 0010600bc3e7d4f2.5 hd2 1
> 0010600bc3e7d4f2.6 hd9var 1
> 0010600bc3e7d4f2.7 hd3 1
> 0010600bc3e7d4f2.8 hd1 1
> 0010600bc3e7d4f2.9 paging00 1
> [root:suzkre]/bin>
>
>
>
>
> -----Original Message-----
> From: IBM AIX Discussion List [mailto:aix-l@Princeton.EDU] On Behalf
> Of Antonio R.
> Sent: Monday, March 15, 2004 3:07 AM
> 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?
>
>
> Thanks in advance
>
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 22:17:42 EDT