Hi there !

I just switched a SE3511 with 5 SATA disks from the onboard controller of a
SF E280R to a QLogic in a V20z. The OS found the new disks immediately BUT
Solaris 8 on the 280R saw c9t[0-4]d0, now I have something very confusing:

root@rayserv# format
Searching for disks...done


AVAILABLE DISK SELECTIONS:
0. c1t0d0 <DEFAULT cyl 8921 alt 2 hd 255 sec 63>
/pci@0,0/pci1022,7450@a/pci17c2,10@4/sd@0,0
1. c1t1d0 <DEFAULT cyl 8921 alt 2 hd 255 sec 63>
/pci@0,0/pci1022,7450@a/pci17c2,10@4/sd@1,0
2. c2t22d0 <DEFAULT cyl 30397 alt 2 hd 255 sec 63>

/pci@0,0/pci1022,7450@a/pci1077,132@5/fp@0,0/disk@w22e5000a3300f7b6,0
3. c3t22E4000A3300F7B7d0 <DEFAULT cyl 30397 alt 2 hd 255 sec 63>
/scsi_vhci/disk@g22e4000a3300f7b7
4. c3t22E4000A3300F7B8d0 <DEFAULT cyl 30397 alt 2 hd 255 sec 63>
/scsi_vhci/disk@g22e4000a3300f7b8
5. c3t22E4000A3300F7B9d0 <DEFAULT cyl 30397 alt 2 hd 255 sec 63>
/scsi_vhci/disk@g22e4000a3300f7b9
6. c3t22E4000A3300F7BAd0 <HITACHI-HDS7225SBSUN250G-A81A-232.88GB>
/scsi_vhci/disk@g22e4000a3300f7ba
Specify disk (enter its number):

rayserv#

c2t22d0 sounds familiar, though I wonder why it's t22 - but why the hells
are the other 4 disks at c3 at what are thos funny target IDs?

I'm not very familiar with Solaris x86 (yet) but I'm afraid that it works
as expected when I can't see the former MDs made on the SPARC machine due
to completely different disk geometry stuff? At least, I was able to do a
"newfs" on one of the disks and mount it.

Any comments on those devices?

TIA

fw

I wrote:

>I just switched a SE3511 with 5 SATA disks from the onboard controller

I should add that this is a JBOD so I expect to see old-fashioned disk
devices ...

Regards

fw

I wrote:

>root@rayserv# format
>Searching for disks...done
>
>
>AVAILABLE DISK SELECTIONS:
> 0. c1t0d0 <DEFAULT cyl 8921 alt 2 hd 255 sec 63>
> /pci@0,0/pci1022,7450@a/pci17c2,10@4/sd@0,0
> 1. c1t1d0 <DEFAULT cyl 8921 alt 2 hd 255 sec 63>
> /pci@0,0/pci1022,7450@a/pci17c2,10@4/sd@1,0
> 2. c2t22d0 <DEFAULT cyl 30397 alt 2 hd 255 sec 63>
>
>/pci@0,0/pci1022,7450@a/pci1077,132@5/fp@0,0/disk@w22e5000a3300f7b6,0
> 3. c3t22E4000A3300F7B7d0 <DEFAULT cyl 30397 alt 2 hd 255 sec 63>
> /scsi_vhci/disk@g22e4000a3300f7b7
> 4. c3t22E4000A3300F7B8d0 <DEFAULT cyl 30397 alt 2 hd 255 sec 63>
> /scsi_vhci/disk@g22e4000a3300f7b8
> 5. c3t22E4000A3300F7B9d0 <DEFAULT cyl 30397 alt 2 hd 255 sec 63>
> /scsi_vhci/disk@g22e4000a3300f7b9
> 6. c3t22E4000A3300F7BAd0 <HITACHI-HDS7225SBSUN250G-A81A-232.88GB>
> /scsi_vhci/disk@g22e4000a3300f7ba
>Specify disk (enter its number):
>
>rayserv#

As quite a newbie to FC stuff, I didn't have much understanding of what's
happening here yesterday. But nowthings are partly clear.

The scsi_vhci paths come from MPxIO and I'm still wondering why the first
disk wasn't recognized correctly.

Now I disabled MP in fp.conf and after putting the disks into other slots
and setting back the array ID (must have been switched during the physical
movement), things are like I want to see them: c2t[0-4].

Regards

fw