I was trying the mksysb installation of the new OS ( AIX 5.3 ) . The
rootvg always gets mounted on different hdisk??? numbers where as it
should be on hdisk0 and hdisk1 which are the internal disks for the
LPAR. Is there anyway i can get it mounted back on hdisk0 and hdisk1.

Why weird numbers are showing as the disks for the rootvg. We do have
SAN connectivity and rest of the hdisk... devices are showing as SAN
devices. Is there any way we can have the rootvg mounted on hdisk0 and
hdisk1 and rest of the hdisk.. as SAN disks.
----------------------------------------------------------------------------------------------------
hdisk0 Available 05-08-02 EMC CLARiiON FCP LUNZ Disk
hdisk1 Available 05-08-02 EMC CLARiiON FCP RAID 5 Disk
hdisk2 Available 05-08-02 EMC CLARiiON FCP RAID 5 Disk
hdisk3 Available 05-08-02 EMC CLARiiON FCP RAID 5 Disk
hdisk4 Available 05-08-02 EMC CLARiiON FCP RAID 5 Disk
hdisk5 Available 05-08-02 EMC CLARiiON FCP RAID 5 Disk
hdisk6 Available 05-08-02 EMC CLARiiON FCP RAID 5 Disk
hdisk7 Available 05-08-02 EMC CLARiiON FCP RAID 5 Disk
hdisk8 Available 05-08-02 EMC CLARiiON FCP RAID 5 Disk
hdisk9 Available 05-08-02 EMC CLARiiON FCP RAID 5 Disk
hdisk10 Available 05-08-02 EMC CLARiiON FCP RAID 5 Disk
hdisk11 Available 05-08-02 EMC CLARiiON FCP RAID 5 Disk
hdisk12 Available 05-08-02 EMC CLARiiON FCP RAID 5 Disk
hdisk13 Available 05-08-02 EMC CLARiiON FCP RAID 5 Disk
hdisk14 Available 05-08-02 EMC CLARiiON FCP RAID 5 Disk
hdisk15 Available 05-08-02 EMC CLARiiON FCP RAID 5 Disk
hdisk16 Available 05-08-02 EMC CLARiiON FCP RAID 5 Disk
hdisk17 Available 05-08-02 EMC CLARiiON FCP RAID 5 Disk
hdisk18 Available 05-08-02 EMC CLARiiON FCP RAID 5 Disk
hdisk19 Available 05-08-02 EMC CLARiiON FCP RAID 5 Disk
hdisk20 Available 05-08-02 EMC CLARiiON FCP RAID 5 Disk
hdisk21 Available 05-08-02 EMC CLARiiON FCP RAID 5 Disk
hdisk22 Available 05-08-02 EMC CLARiiON FCP RAID 5 Disk
hdisk23 Available 05-08-02 EMC CLARiiON FCP RAID 5 Disk
hdisk24 Available 05-08-02 EMC CLARiiON FCP RAID 5 Disk
hdisk25 Available 05-08-02 EMC CLARiiON FCP RAID 5 Disk
hdisk26 Available 05-08-02 EMC CLARiiON FCP RAID 5 Disk
hdisk27 Available 05-08-02 EMC CLARiiON FCP RAID 5 Disk
hdisk28 Available 05-08-02 EMC CLARiiON FCP RAID 5 Disk
hdisk29 Available 05-08-02 EMC CLARiiON FCP RAID 5 Disk
hdisk30 Available 05-08-02 EMC CLARiiON FCP RAID 5 Disk
hdisk31 Available 05-08-02 EMC CLARiiON FCP RAID 5 Disk
hdisk32 Available 05-08-02 EMC CLARiiON FCP RAID 5 Disk
hdisk33 Available 05-08-02 EMC CLARiiON FCP RAID 5 Disk
hdisk34 Available 05-08-02 EMC CLARiiON FCP LUNZ Disk
hdisk35 Available 06-08-00-4,0 16 Bit LVD SCSI Disk Drive
hdisk36 Available 06-08-00-5,0 16 Bit LVD SCSI Disk Drive
hdisk37 Available 07-08-02 EMC CLARiiON FCP LUNZ Disk
hdisk38 Available 07-08-02 EMC CLARiiON FCP LUNZ Disk
hdisk39 Available 07-08-02 EMC CLARiiON FCP RAID 5 Disk
hdisk40 Available 07-08-02 EMC CLARiiON FCP RAID 5 Disk
hdisk41 Available 07-08-02 EMC CLARiiON FCP RAID 5 Disk
hdisk42 Available 07-08-02 EMC CLARiiON FCP RAID 5 Disk
hdisk43 Available 07-08-02 EMC CLARiiON FCP RAID 5 Disk
hdisk44 Available 07-08-02 EMC CLARiiON FCP RAID 5 Disk
hdisk45 Available 07-08-02 EMC CLARiiON FCP RAID 5 Disk
hdisk46 Available 07-08-02 EMC CLARiiON FCP RAID 5 Disk
hdisk47 Available 07-08-02 EMC CLARiiON FCP RAID 5 Disk
hdisk48 Available 07-08-02 EMC CLARiiON FCP RAID 5 Disk
hdisk49 Available 07-08-02 EMC CLARiiON FCP RAID 5 Disk
hdisk50 Available 07-08-02 EMC CLARiiON FCP RAID 5 Disk
hdisk51 Available 07-08-02 EMC CLARiiON FCP RAID 5 Disk
hdisk52 Available 07-08-02 EMC CLARiiON FCP RAID 5 Disk
hdisk53 Available 07-08-02 EMC CLARiiON FCP RAID 5 Disk
hdisk54 Available 07-08-02 EMC CLARiiON FCP RAID 5 Disk
hdisk55 Available 07-08-02 EMC CLARiiON FCP RAID 5 Disk
hdisk56 Available 07-08-02 EMC CLARiiON FCP RAID 5 Disk
hdisk57 Available 07-08-02 EMC CLARiiON FCP RAID 5 Disk
hdisk58 Available 07-08-02 EMC CLARiiON FCP RAID 5 Disk
hdisk59 Available 07-08-02 EMC CLARiiON FCP RAID 5 Disk
hdisk60 Available 07-08-02 EMC CLARiiON FCP RAID 5 Disk
hdisk61 Available 07-08-02 EMC CLARiiON FCP RAID 5 Disk
hdisk62 Available 07-08-02 EMC CLARiiON FCP RAID 5 Disk
hdisk63 Available 07-08-02 EMC CLARiiON FCP RAID 5 Disk
hdisk64 Available 07-08-02 EMC CLARiiON FCP RAID 5 Disk
hdisk65 Available 07-08-02 EMC CLARiiON FCP RAID 5 Disk
hdisk66 Available 07-08-02 EMC CLARiiON FCP RAID 5 Disk
hdisk67 Available 07-08-02 EMC CLARiiON FCP RAID 5 Disk
hdisk68 Available 07-08-02 EMC CLARiiON FCP RAID 5 Disk
hdisk69 Available 07-08-02 EMC CLARiiON FCP RAID 5 Disk
hdisk70 Available 07-08-02 EMC CLARiiON FCP RAID 5 Disk
hdisk71 Available 07-08-02 EMC CLARiiON FCP RAID 5 Disk
----------------------------------------------------------------------------------------------------

Regards
aarCee

On Mar 26, 9:39 am, rcee <4mystud...@gmail.com> wrote:
> I was trying the mksysb installation of the new OS ( AIX 5.3 ) . The
> rootvg always gets mounted on different hdisk??? numbers where as it
> should be on hdisk0 and hdisk1 which are the internal disks for the
> LPAR. Is there anyway i can get it mounted back on hdisk0 and hdisk1.
>
> Why weird numbers are showing as the disks for the rootvg. We do have
> SAN connectivity and rest of the hdisk... devices are showing as SAN
> devices. Is there any way we can have the rootvg mounted on hdisk0 and
> hdisk1 and rest of the hdisk.. as SAN disks.
>

1 )Might help during installation but not tested
Customize the bosinst.data and add the location code for the SCSI
disk.
See /usr/lpp/bosinst/bosinst.template.README for details

2) Disconnect any fibre connection during installation

3) Search this group for: Change rootvg hdisk numbers?

4) Stay with it

cheers
Hajo

rcee, thats great and really illutrates a good point with AIX .. as
cfgmgr walks the bus configuring devices .. the first disk it comes
across will be hdisk0, the next hdisk1 etc .. . have you seen the scsi
location numbers ?? 05-08-02 first, then 06-08-00 and then 07-08-02 ..
so, like Hajo said, disconnect the fibres and install
again ..or ..disconnect the fibres, blow away the FC disks, drop the
2nd rootvg our of rootvg and blow away, then cfgmgr, mirror, drop the
second etc... you can change the device names in the odm also is a
quicker and **not so safe way**

Rgds
Mark Taylor

On Wed, 26 Mar 2008 02:48:59 -0700, Mark Taylor wrote:

> rcee, thats great and really illutrates a good point with AIX .. as
> cfgmgr walks the bus configuring devices .. the first disk it comes
> across will be hdisk0, the next hdisk1 etc .. . have you seen the scsi
> location numbers ?? 05-08-02 first, then 06-08-00 and then 07-08-02 ..
> so, like Hajo said, disconnect the fibres and install again ..or
> ..disconnect the fibres, blow away the FC disks, drop the 2nd rootvg our
> of rootvg and blow away, then cfgmgr, mirror, drop the second etc... you
> can change the device names in the odm also is a quicker and **not so
> safe way**
>
> Rgds
> Mark Taylor

Why do you care what hdisk numbers get assigned to rootvg? It is mildly
annoying that they change, but it doesn't affect the system in any
meaningful way, assuming that the bootlist command still shows these new
disks as the boot disks. The above seems to me to be a lot of work and
potential for harm for a change that has no real benefits. A cost-risk
analysis says this is not worth it, IMO.

On Mar 26, 7:22 am, "F. Michael Orr" <michael_or...@yahoo.com> wrote:
> On Wed, 26 Mar 2008 02:48:59 -0700, Mark Taylor wrote:
> > rcee, thats great and really illutrates a good point with AIX .. as
> > cfgmgr walks the bus configuring devices .. the first disk it comes
> > across will be hdisk0, the next hdisk1 etc .. . have you seen the scsi
> > location numbers ?? 05-08-02 first, then 06-08-00 and then 07-08-02 ..
> > so, like Hajo said, disconnect the fibres and install again ..or
> > ..disconnect the fibres, blow away the FC disks, drop the 2nd rootvg our
> > of rootvg and blow away, then cfgmgr, mirror, drop the second etc... you
> > can change the device names in the odm also is a quicker and **not so
> > safe way**
>
> > Rgds
> > Mark Taylor
>
> Why do you care what hdisk numbers get assigned to rootvg? It is mildly
> annoying that they change, but it doesn't affect the system in any
> meaningful way, assuming that the bootlist command still shows these new
> disks as the boot disks. The above seems to me to be a lot of work and
> potential for harm for a change that has no real benefits. A cost-risk
> analysis says this is not worth it, IMO.


check out lsdev -p and cfgmgr -l

seems like your fibre and you internals would be on different scsi
devices:
here's an example:

lsdev -p scsi0
hdisk0 Available 1S-08-00-8,0 16 Bit LVD SCSI Disk Drive
hdisk1 Available 1S-08-00-9,0 16 Bit LVD SCSI Disk Drive
hdisk2 Available 1S-08-00-10,0 16 Bit LVD SCSI Disk Drive
hdisk3 Available 1S-08-00-11,0 16 Bit LVD SCSI Disk Drive
ses0 Available 1S-08-00-15,0 SCSI Enclosure Services Device

assuming you current fibre hdisk0, hdisk1 are on something OTHER than
scsi0 you can :

unmirror rootvg , reduce out hdisk35

rmdev hdisk0 and hdisk35

cfgmgr -l scsi0

that will run ONLY against devices on scsi0-- will prolly leave fibre
alone.

re-mirror rootvg , drop the other hdisk wash rinse repeat, etc

no guarantees expressed or implied. It looks like hdisk0 is just a
LUNZ so it doesn't matter , hdisk1 looks to be a real disk so you'll
need some kind of outage to do this anyway.

On Mar 27, 1:25*am, jthomp1...@yahoo.com wrote:
> On Mar 26, 7:22 am, "F. Michael Orr" <michael_or...@yahoo.com> wrote:
>
>
>
>
>
> > On Wed, 26 Mar 2008 02:48:59 -0700, Mark Taylor wrote:
> > > rcee, thats great and really illutrates a good point with AIX .. as
> > > cfgmgr walks the bus configuring devices .. the first disk it comes
> > > across will be hdisk0, the next hdisk1 etc .. . have you seen the scsi
> > > location numbers ?? 05-08-02 first, then 06-08-00 and then 07-08-02 ..
> > > so, like Hajo said, disconnect the fibres and install again ..or
> > > ..disconnect the fibres, blow away the FC disks, drop the 2nd rootvg our
> > > of rootvg and blow away, then cfgmgr, mirror, drop the second etc... you
> > > can change the device names in the odm also is a quicker and **not so
> > > safe way**
>
> > > Rgds
> > > Mark Taylor
>
> > Why do you care what hdisk numbers get assigned to rootvg? *It is mildly
> > annoying that they change, but it doesn't affect the system in any
> > meaningful way, assuming that the bootlist command still shows these new
> > disks as the boot disks. *The above seems to me to be a lot of work and
> > potential for harm for a change that has no real benefits. *A cost-risk
> > analysis says this is not worth it, IMO.
>
> check out lsdev -p and cfgmgr -l
>
> seems like your fibre and you internals would be on different scsi
> devices:
> here's an example:
>
> lsdev -p scsi0
> hdisk0 Available 1S-08-00-8,0 *16 Bit LVD SCSI Disk Drive
> hdisk1 Available 1S-08-00-9,0 *16 Bit LVD SCSI Disk Drive
> hdisk2 Available 1S-08-00-10,0 16 Bit LVD SCSI Disk Drive
> hdisk3 Available 1S-08-00-11,0 16 Bit LVD SCSI Disk Drive
> ses0 * Available 1S-08-00-15,0 SCSI Enclosure Services Device
>
> assuming you current fibre hdisk0, hdisk1 are on *something OTHER than
> scsi0 you can :
>
> unmirror rootvg , reduce out *hdisk35
>
> rmdev hdisk0 and hdisk35
>
> cfgmgr -l scsi0
>
> that will run ONLY against devices on scsi0-- will prolly leave fibre
> alone.
>
> re-mirror rootvg , drop the other hdisk *wash rinse repeat, etc
>
> no guarantees expressed or implied. * It looks like hdisk0 is just a
> LUNZ so it doesn't matter , *hdisk1 looks to be a real *disk so you'll
> need some kind of outage to do this anyway.- Hide quoted text -
>
> - Show quoted text -

Hi All ,

Thanks a lot for all the inputs. Infact i do agree the numbering
doesn;t matter but we would like to keep it clean and same on all our
servers. About the comments from others, yes we did try the option of
removing the fibre cables and removing all of the fibre definitions
from the host before the OS upgrade. But still it did reflected which
was puzzling for us. Is there any way that the NVRAM level ( SMS
menu ) remembers these hdisk numbers which it had before ?

I will defintely try the last step from Michael .

thanks once again for all the inputs

Rajesh

rcee wrote:
> [...] About the comments from others, yes we did try the option of
> removing the fibre cables and removing all of the fibre definitions
> from the host before the OS upgrade. But still it did reflected which
> was puzzling for us.

Did you remove it with "rmdev -dl" ? (if you use only -l you're not
removing it, only changing it from Available to Defined).

> Is there any way that the NVRAM level ( SMS
> menu ) remembers these hdisk numbers which it had before ?
No. The NVRAM level only knows physical location codes.
(i.e. Slot X, Port Y, LUN Z)


hdisks exist only at the AIX/ODM level.