This is a discussion on hdisk numbers and NIM within the AIX Operating System forums, part of the Unix Operating Systems category; --> I have an issue I hope someone can assist me with. I have a server that has two internal ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| I have an issue I hope someone can assist me with. I have a server that has two internal 73 gigabyte SCSI drives and also has a Fiber Adapter connected to a SAN. Prior to the overwrite install of the Operating System using NIM the two internal disks were labeled hdisk0 and hdisk1. After performing a NIM installation the two internal disks are now labeled hdisk2 and hdisk3. The Operating System was installed on the disk I specified but the hdisk number has changed. This is not causing any issues with the functioning of the server but I am trying to stay consistent with all of our other servers, which is to have the Operating System installed on hdisk0. Does anyone know of a way to ensure that the internal disks are found/labeled prior to external drives attached to the fiber adapter during a NIM installation? |
| |||
| I was able to resolve my issue by manipulating the ODM after the installation. It appears there is not a way to instruct the installation of the Operating System to label/number the disks in a particular order. Thanks to everyone who took the time to read the post. |
| ||||
| Adman wrote: > I was able to resolve my issue by manipulating the ODM after the > installation. It appears there is not a way to instruct the > installation of the Operating System to label/number the disks in a > particular order. > > Thanks to everyone who took the time to read the post. > Shudder :-P (the LAST thing I want to do is mess with the ODM even WITH IBM support on the line directing me to do so!). I have 2 racks of 6C4s (I think they're aka "p650") with this same issue; I'm told it's a known problem on some of these systems. W/O going into the long technical explanation (which I'd probably get wrong anyway <G>), I've found the easiest thing to do is (BEFORE starting the NIM installatition and since you said "overwrite" install) DISCONNECT the FC cables from the adapter(s) until after the system is installed! Once installed, connect the cables and run cfgmgr...done. Paul p.s. The problem has something to do with the way the FC adapters are read first during the BIST/POST phase...if you watch closely enough, you'll see the HBA adapter microcode appears WAY before the scsi buses are seen...PS |
| Thread Tools | |
| Display Modes | |
|
|