Controller naumber chaged when root disk connected in another system

May I suggest that you start reading up on how Solaris (and Sun hardware) works with hard drives and various other storage devices.

As has been recently explained in another thread, c0t0d0s0 means:

Controller 0

Target 0

Disk 0

Slice 0

When moving the disk to another system, there's no guarantee that you're going to connect it to the local "controller 0", unless you first make sure that you know which one it is.

Is there a reason why you -need- to have it at C0?

Cailin_Coilleach at 2007-7-7 0:25:53 >

If you are going to build a disk drive in one system then use it in another,

it would help to use the same architecture.

The device paths in a V480/V480 are different that in a V890.

Glance through Spectrum Infodoc 21216

for a quick summary of device paths in various Sun computer systems:

http://sunsolve.sun.com/handbook_pub/Systems/Example/documents/21216.html

Your V480/V490 disk #1 is a hard-coded device path of

/pci@9,600000/SUNW,qlc@2/fp@0,0

... whereas that same path is for something in slot #7 of the V890.

There is no slot #7 in a V480.

The "onboard" FCAL loop to the V890 disk bay is a hard-coded path to

/pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@<WWN>,0

Of course the larger system will assign a different controller to it.

The path is different.Your path-to-inst will be for the wrong architecture.

That's just one file that will be incorrect.

rukbat at 2007-7-7 0:25:53 >