New 3510s not presenting LUNs correctly.

Question

Whoops! I originally posted this on the Other Sun Hardware forum, but this is definitely the more appropriate place.
I just attached four new 3510s to a server that already has a 3510 attached. They each have their own connection to the server, so there is no daisy-chaining going on. The server sees the old 3510 as a 3510 with each LUN properly presented as 3510s of the correct sizes.
The new 3510s, however, are not identifying themselves as 3510s, nor are they presenting the logical disks in their correct sizes. Instead each LUN (consisting of no less than 2-disk, RAID 0s) is showing up like single, 146GB drives! They're not even displaying StorEdge3510 in the disk type when I run format! It's as though the new 3510s are presenting themselves as JBODs (of incorrect sizes, no less) instead of 3510s with controllers!
The new 3510s were upgraded to the latest firmware (4.15G) before any RAIDs were created and given four logical disks, each in a RAID 0 configuration, made of 2 disks (~290 GB), 3 disks (~435 GB), 3 disks (~435 GB), and 4 disks (~580 GB). This is different from our original 3510 which has all of the disks in a RAID 5 with two partitions. (The original 3510 is running firmware 4.13C.)
When I run format, the server sees each of the 16 LUNs. (I verified this by taking some LUNs offline, which then showed up in format as "disk format undetermined" or something like that.) So, the server definitely sees the LUNs, but the 3510 is not showing them in their correct size nor is the disk name reflecting that it's a 3510. That tells me that the 3510 is not presenting itself properly, but it responds without a problem to sccli and appears to be configured properly.
I tried creating a logical partition inside one of the 2-disk, logical disks and presented that as a LUN. No dice. It still showed up as a non-3510, 146GB disk. I tired making a logical volume and presented that. Same thing -- a non-3510, 146GB disk was presented.
With the exception of the different firmware versions and using RAID 0 instead of RAID 5, I can't see any difference between the configuration between the two 3510s. Any ideas what I could be missing with the new ones? Could firmware 4.15G be bad? I really would like to get this resolved by this weekend.

Answer 1

It's what would normally be in a JBOD - what would be the equivalent of FC2 and FC3. In fact, I took it out as a test at which point the 3510 complained about losing temperature and redundancy modules! So, it's not ignoring the JBOD controller.
But It gets better! I rebuit one of those 3-disk, RAID 0 logical drives as RAID 5. Not only is the 3510 building that RAID 5 now, but look at how format is presenting the LUNs now!
     464. c12t40d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848>
          /ssm@0,0/pci@19,600000/SUNW,qlc@1/fp@0,0/ssd@w216000c0ff87d116,0
     465. c12t40d1 <SUN146G cyl 14087 alt 2 hd 24 sec 848>
          /ssm@0,0/pci@19,600000/SUNW,qlc@1/fp@0,0/ssd@w216000c0ff87d116,1
     466. c12t40d2 <SUN146G cyl 14087 alt 2 hd 24 sec 848>
          /ssm@0,0/pci@19,600000/SUNW,qlc@1/fp@0,0/ssd@w216000c0ff87d116,2
     467. c12t40d3 <SUN-StorEdge3510-415G cyl 35073 alt 2 hd 64 sec 255>
          /ssm@0,0/pci@19,600000/SUNW,qlc@1/fp@0,0/ssd@w216000c0ff87d116,3
partition> print
Current partition table (default):
Total disk cylinders available: 35073 + 2 (reserved cylinders)
Part      Tag    Flag     Cylinders         Size            Blocks
  0       root    wm       0 -    16      135.47MB    (17/0/0)       277440
  1       swap    wu      17 -    33      135.47MB    (17/0/0)       277440
  2     backup    wu       0 - 35072      272.94GB    (35073/0/0) 572391360
  3 unassigned    wm       0                0         (0/0/0)             0
  4 unassigned    wm       0                0         (0/0/0)             0
  5 unassigned    wm       0                0         (0/0/0)             0
  6        usr    wm      34 - 35072      272.67GB    (35039/0/0) 571836480
  7 unassigned    wm       0                0         (0/0/0)             0The RAID 5 is now identifying itself as a 3510 disk of 272 GB, which is correct for a 3-disk RAID 5!!
And according to the 3510 Best Practices manual on page 23, having the JBOD panel in the other slot appears to be acceptable even if there is nothing attached to it.
But considering how differently the 3510 is treating the RAID 5 compared to the RAID 0, something is defintely not right here.