Replacing SCSI controllers of boot disks for another

[Jdamian]

Hi

I want to replace two COMBO SCSI/ETHER controllers for new COMBO SCSI/Giga ones. But the boot disks are affected.

will the system keep the old disk device files or will it create new ones?

Thanx in advance

[Sunny123_1]

After changing the SCSI do insf -e then it will create new paths for disk.

[Jdamian]

Do you realize that in that case the system will not boot because the boot disk paths will have been changed?

[Sunny123_1]

ya you are right.change the boot disk path when you will get new path

[Ganesan R · Accepted solution]

Hi Oscar,

If boot disk paths are getting changed followed by controller replacement, you need to boot into maintanance mode then export and import the VG00.

It will update the /etc/lvmtab with new device paths. You need to reboot from maintanance mode and do not directly boot from there using init 3.

[Ganesan R]

Hi Oscar,

This has the steps what you need to follow after controller replacement. Look at the appendix J at the end of the document.

http://docs.hp.com/en/5991-1236/When_Good_Disks_Go_Bad_WP.pdf

[Torsten.]

Hi Oscar,

it depends.

Depending on the HBAs you have and the HBAs you will have, they can have a different "internal" hardware path.

Look at this:

this is the slot
ba 1 2/0/1 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (783)

This is the first SCSI port of a combo
ext_bus 0 2/0/1/1/0/4/0 mpt CLAIMED INTERFACE HP AB290-60001 PCI/PCI-X U320 SCSI 2-port U320 SCSI/2-port 1000B-T Combo Adapter
/dev/mpt0

and this the second:
ext_bus 1 2/0/1/1/0/4/1 mpt CLAIMED INTERFACE HP AB290-60001 PCI/PCI-X U320 SCSI 2-port U320 SCSI/2-port 1000B-T Combo Adapter
/dev/mpt1

and these are the LAN devices:
lan 1 2/0/1/1/0/6/0 iether CLAIMED INTERFACE HP AB290-60001 PCI/PCI-X 1000Base-T 2-port U320 SCSI/2-port 1000B-T Combo Adapter
lan 2 2/0/1/1/0/6/1 iether CLAIMED INTERFACE HP AB290-60001 PCI/PCI-X 1000Base-T 2-port U320 SCSI/2-port 1000B-T Combo Adapter



In case this is changing, boot to maintenance mode and vgexport/vgimport your vg00.

[TTr]

There several pieces that make up the HW path of a device coming from the system bus, slot, card, card bus and device(disk) parts. The system bus, slot and disk will not change assuming you will be putting the new cards in the same slots and of cource you will be using the same disks. So you need to verify if the enumeration of the scsi and LAN sub-buses is the same within the old and new controllers.
This is from an rx8640 with a dual SCSI/LAN (Gbit/U320) combo card AB290
0/0/10/1/0/4/0 scsi bus
0/0/10/1/0/4/0.x scsi devices
0/0/10/1/0/4/1 scsi bus
0/0/10/1/0/4/1.x scsi devices
0/0/10/1/0/6/0 LAN
0/0/10/1/0/6/0 LAN
The last two digits 4/0, 4/1, 6/0, 6/1 in each path depend on the combo controllers, everything else should stay the same. So if the old and new combo controllers have the same enumeration in their SCSI/LAN sub-busses nothing will change, otherwise you need to boot in LVM maintenance mode and do the boot device SCSI address change.
You should be able to see the new HW paths after you install the cards from either the EFI menu or the ISL prompt.

[sujit kumar singh]

hi,

if you have the latest patches and release for 11.31 hopefully you need not do anything due to the boot resiliency feature of the Next Gen Mass Storage stack.

again depends that you might be asked by the system to run vgscan -k -f vg00 and do a vgcfgbackup and lvlnboot -R.

but the dev files shall change for the legacy DSF naming system if the H/W path to the disks change as the legacy DSF are bound to HW path.

for the persistent DSF that are featuredly bound to WWID of a LUN the PDSFs are not going to change.

anyway identify the boot disks properly in BCH or EFI whatever applies to the system and boot in LVM maint mode to do vgexport vg00 and re-import vgimport vg00 properly idrntifying the boot disks. do a subsequent vgcfgbackup and lvlnboot -R if the things do not occur automatically.

regards
sujit

[Torsten.]

This is a good point, because all answers so far were focused on releases up to 11.23.