[OpenIndiana-discuss] Only one SSD detected on expander
Scott Marcy
oi at mscott.org
Wed Oct 17 17:07:31 UTC 2012
Sure.
Here's the only one that can be seen in the expander:
$ smartctl -d sat,12 -i /dev/rdsk/c7t5002538043584D30d0s0
smartctl 5.42 2011-10-20 r3458 [i386-pc-solaris2.11] (local build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net
=== START OF INFORMATION SECTION ===
Device Model: SAMSUNG SSD 830 Series
Serial Number: S0Z3NEAC876961
LU WWN Device Id: 5 002538 043584d30
Firmware Version: CXM03B1Q
User Capacity: 128,035,676,160 bytes [128 GB]
Sector Size: 512 bytes logical/physical
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: 8
ATA Standard is: ACS-2 revision 2
Local Time is: Wed Oct 17 10:58:36 2012 MDT
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
And these are the two that are connected to the mobo's built-in SATA ports:
$ smartctl -d sat,12 -i /dev/rdsk/c4t0d0s0
smartctl 5.42 2011-10-20 r3458 [i386-pc-solaris2.11] (local build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net
=== START OF INFORMATION SECTION ===
Device Model: SAMSUNG SSD 830 Series
Serial Number: S0Z3NEAC876658
LU WWN Device Id: 5 002538 043584d30
Firmware Version: CXM03B1Q
User Capacity: 128,035,676,160 bytes [128 GB]
Sector Size: 512 bytes logical/physical
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: 8
ATA Standard is: ACS-2 revision 2
Local Time is: Wed Oct 17 11:01:56 2012 MDT
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
$ smartctl -d sat,12 -i /dev/rdsk/c4t1d0s0
smartctl 5.42 2011-10-20 r3458 [i386-pc-solaris2.11] (local build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net
=== START OF INFORMATION SECTION ===
Device Model: SAMSUNG SSD 830 Series
Serial Number: S0Z3NEAC876031
LU WWN Device Id: 5 002538 043584d30
Firmware Version: CXM03B1Q
User Capacity: 128,035,676,160 bytes [128 GB]
Sector Size: 512 bytes logical/physical
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: 8
ATA Standard is: ACS-2 revision 2
Local Time is: Wed Oct 17 11:02:25 2012 MDT
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
I called Samsung and they basically told me there was nothing they could do. The guy I spoke with said the 830s weren't intended to be used in servers. (He did seem to understand what I was talking about, which was actually more than I expected from simply picking up the phone and getting transferred twice to get to the right department. So at least kudos to Samsung there.)
He did suggest that maybe the new 840 Pros might work, and he was going to check to see if they report unique WWNs or not. Since those don't appear to be shipping yet, I don't have any way of finding out myself, but if anybody is interested, I can pass along what Samsung says when (if) they get back to me on the 840 Pro.
Thanks again!
-Scott
On Oct 17, 2012, at 10:57 AM, Roy Sigurd Karlsbakk <roy at karlsbakk.net> wrote:
> make that smartctl -i …
>
> you may have to add -d sat to that
>
> roy
>
> ----- Opprinnelig melding -----
>> it'd be interesting to see what WWN smartctl -l would report from
>> these. I've worked with SATA SSDs in similar setups, but never seen
>> them reported with the same WWN
>>
>> roy
>>
>> ----- Opprinnelig melding -----
>>> Ah, I see now. Yes, all the drives report the same LU WWN Device Id
>>> in
>>> smartctl, and I see the same constant WWN reported online (for
>>> example,
>>> http://blog.gmane.org/gmane.linux.utilities.smartmontools.database/page=7).
>>> I'll see what Samsung has to say.
>>>
>>> Thanks! This at least gives me more to work from.
>>>
>>> -Scott
>>>
>>>
>>> On Oct 17, 2012, at 10:13 AM, Rich <rercola at acm.jhu.edu> wrote:
>>>
>>>> SATA devices are not required to provide a WWN - I would guess
>>>> that
>>>> they're providing the same WWN, and as a result, your SAS devices
>>>> are
>>>> becoming sad.
>>>>
>>>> If you could tell the expander(s) to ignore that and assign one,
>>>> that'd be neat. If there's a firmware update to fix it, even
>>>> better.
>>>> If you want to shell out for SAS -> SATA interposers, that would
>>>> probably also solve it, though I can't swear to anything, but
>>>> that'd
>>>> probably be more expensive than returning + replacing the SSDs.
>>>>
>>>> Don't know. If it were me, I'd complain to Samsung support and see
>>>> what you got back.
>>>>
>>>> - Rich
>>>>
>>>> On Wed, Oct 17, 2012 at 11:13 AM, Scott Marcy <oi at mscott.org>
>>>> wrote:
>>>>> Well, I enabled multipath support with 'stmsboot -e -D mpt' and
>>>>> rebooted and now it seems I have two paths to what is no doubt
>>>>> two
>>>>> physical devices:
>>>>>
>>>>> $ mpathadm list LU
>>>>> /dev/rdsk/c7t5002538043584D30d0s2
>>>>> Total Path Count: 2 <-- Unlikely that this is
>>>>> correct
>>>>> Operational Path Count: 2
>>>>> /dev/rdsk/c7t5000C5005168B2F0d0s2
>>>>> Total Path Count: 1
>>>>> Operational Path Count: 1
>>>>> /dev/rdsk/c7t5000C5005169A612d0s2
>>>>> Total Path Count: 1
>>>>> Operational Path Count: 1
>>>>> /dev/rdsk/c7t5000C500517042D9d0s2
>>>>> Total Path Count: 1
>>>>> Operational Path Count: 1
>>>>> /dev/rdsk/c7t5000C5005169CC6Ad0s2
>>>>> Total Path Count: 1
>>>>> Operational Path Count: 1
>>>>> /dev/rdsk/c7t5000C500515199BDd0s2
>>>>> Total Path Count: 1
>>>>> Operational Path Count: 1
>>>>> /dev/rdsk/c7t5000C500513A0EFEd0s2
>>>>> Total Path Count: 1
>>>>> Operational Path Count: 1
>>>>>
>>>>> $ mpathadm show LU /dev/rdsk/c7t5002538043584D30d0s2
>>>>> Logical Unit: /dev/rdsk/c7t5002538043584D30d0s2
>>>>> mpath-support: libmpscsi_vhci.so
>>>>> Vendor: ATA
>>>>> Product: SAMSUNG SSD 830
>>>>> Revision: 3B1Q
>>>>> Name Type: unknown type
>>>>> Name: 5002538043584d30
>>>>> Asymmetric: no
>>>>> Current Load Balance: none
>>>>> Logical Unit Group ID: NA
>>>>> Auto Failback: on
>>>>> Auto Probing: NA
>>>>>
>>>>> Paths:
>>>>> Initiator Port Name: w500605b0054819b0
>>>>> Target Port Name: w5002538043584d30
>>>>> Override Path: NA
>>>>> Path State: OK
>>>>> Disabled: no
>>>>>
>>>>> Initiator Port Name: w500605b0054819b0
>>>>> Target Port Name: w5002538043584d30
>>>>> Override Path: NA
>>>>> Path State: OK
>>>>> Disabled: no
>>>>>
>>>>> Target Ports:
>>>>> Name: w5002538043584d30
>>>>> Relative ID: 0
>>>>>
>>>>> And cfgadm still only shows one SSD on each expander, when I
>>>>> actually have two on each expander.
>>>>>
>>>>> $ cfgadm -al
>>>>> Ap_Id Type Receptacle Occupant Condition
>>>>> c6 scsi-sas connected configured unknown
>>>>> c6::es/ses0 ESI connected configured unknown
>>>>> c6::smp/expd0 smp connected configured unknown
>>>>> c6::w5002538043584d30,0 disk-path connected configured unknown
>>>>> c6::w5000c500513a0efe,0 disk-path connected configured unknown
>>>>> c6::w5000c5005168b2f0,0 disk-path connected configured unknown
>>>>> c6::w5000c5005169a612,0 disk-path connected configured unknown
>>>>> c6::w5000c5005169cc6a,0 disk-path connected configured unknown
>>>>> c6::w5000c500515199bd,0 disk-path connected configured unknown
>>>>> c6::w5000c500517042d9,0 disk-path connected configured unknown
>>>>> c8 scsi-sas connected configured unknown
>>>>> c8::es/ses1 ESI connected configured unknown
>>>>> c8::smp/expd1 smp connected configured unknown
>>>>> c8::w5002538043584d30,0 disk-path connected configured unknown
>>>>> c9 scsi-sas connected unconfigured unknown
>>>>>
>>>>> I also wonder if there might be an issue with duplicate
>>>>> initiator-port names:
>>>>>
>>>>> $ mpathadm list initiator-port
>>>>> Initiator Port: w500605b0054819b0
>>>>> Initiator Port:
>>>>> iqn.1986-03.com.sun:01:bb4db0fbffff.507ec650,4000002a00ff
>>>>> Initiator Port: w500605b0054819b0
>>>>>
>>>>> Although I'm definitely venturing outside my knowledge base
>>>>> here--maybe this is expected and correct. (I assume each
>>>>> initiator-port represents an expander, but both expanders are
>>>>> connected to the one HBA, one to each SFF-8087 port. Also, I do
>>>>> have comstar running, which I expect explains the iSCSI initiator
>>>>> in this list.)
>>>>>
>>>>> -Scott
>>>>>
>>>>> On Oct 17, 2012, at 8:37 AM, Scott Marcy <mscott at mscott.org>
>>>>> wrote:
>>>>>
>>>>>> No, multipath support is disabled. I will try enabling it with
>>>>>> stmsboot.
>>>>>>
>>>>>> Thanks.
>>>>>>
>>>>>> -Scott
>>>>>>
>>>>>> On Oct 17, 2012, at 8:15 AM, Bob Friesenhahn
>>>>>> <bfriesen at simple.dallas.tx.us> wrote:
>>>>>>
>>>>>>> On Wed, 17 Oct 2012, Scott Marcy wrote:
>>>>>>>>
>>>>>>>> Note that both c6 and c8 have the exact same name for these
>>>>>>>> drives. I *CAN* access the two drives separately, but why on
>>>>>>>> earth am I getting these duplicates? This means I can only
>>>>>>>> reliably access one Samsung SSD per expander.
>>>>>>>
>>>>>>> Do you have multipath support enabled on this system? I assume
>>>>>>> that the default for OpenIndiana x86 is still that multipath
>>>>>>> support is disabled by default.
>>>>>>>
>>>>>>> Bob
>>>>>>> --
>>>>>>> Bob Friesenhahn
>>>>>>> bfriesen at simple.dallas.tx.us,
>>>>>>> http://www.simplesystems.org/users/bfriesen/
>>>>>>> GraphicsMagick Maintainer, http://www.GraphicsMagick.org/
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> OpenIndiana-discuss mailing list
>>>>>>> OpenIndiana-discuss at openindiana.org
>>>>>>> http://openindiana.org/mailman/listinfo/openindiana-discuss
>>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> OpenIndiana-discuss mailing list
>>>>> OpenIndiana-discuss at openindiana.org
>>>>> http://openindiana.org/mailman/listinfo/openindiana-discuss
>>>>
>>>> _______________________________________________
>>>> OpenIndiana-discuss mailing list
>>>> OpenIndiana-discuss at openindiana.org
>>>> http://openindiana.org/mailman/listinfo/openindiana-discuss
>>>
>>> --
>>> “It is in the admission of ignorance and the admission of
>>> uncertainty
>>> that there is a hope for the continuous motion of human beings in
>>> some
>>> direction that doesn't get confined, permanently blocked, as it has
>>> so
>>> many times before in various periods in the history of man.”
>>> - Richard P. Feynman
>>>
>>>
>>> _______________________________________________
>>> OpenIndiana-discuss mailing list
>>> OpenIndiana-discuss at openindiana.org
>>> http://openindiana.org/mailman/listinfo/openindiana-discuss
>>
>> --
>> Vennlige hilsener / Best regards
>>
>> roy
>> --
>> Roy Sigurd Karlsbakk
>> (+47) 98013356
>> roy at karlsbakk.net
>> http://blogg.karlsbakk.net/
>> GPG Public key: http://karlsbakk.net/roysigurdkarlsbakk.pubkey.txt
>> --
>> I all pedagogikk er det essensielt at pensum presenteres
>> intelligibelt. Det er et elementært imperativ for alle pedagoger å
>> unngå eksessiv anvendelse av idiomer med xenotyp etymologi. I de
>> fleste tilfeller eksisterer adekvate og relevante synonymer på norsk.
>>
>> _______________________________________________
>> OpenIndiana-discuss mailing list
>> OpenIndiana-discuss at openindiana.org
>> http://openindiana.org/mailman/listinfo/openindiana-discuss
>
> --
> Vennlige hilsener / Best regards
>
> roy
> --
> Roy Sigurd Karlsbakk
> (+47) 98013356
> roy at karlsbakk.net
> http://blogg.karlsbakk.net/
> GPG Public key: http://karlsbakk.net/roysigurdkarlsbakk.pubkey.txt
> --
> I all pedagogikk er det essensielt at pensum presenteres intelligibelt. Det er et elementært imperativ for alle pedagoger å unngå eksessiv anvendelse av idiomer med xenotyp etymologi. I de fleste tilfeller eksisterer adekvate og relevante synonymer på norsk.
>
> _______________________________________________
> OpenIndiana-discuss mailing list
> OpenIndiana-discuss at openindiana.org
> http://openindiana.org/mailman/listinfo/openindiana-discuss
More information about the OpenIndiana-discuss
mailing list