[OpenIndiana-discuss] Only one SSD detected on expander

[Robin Axelsson]

Isn't it possible to somehow make the drive dump the firmware somehow, 
edit it with a HEX editor (and recalculate firmware checksums) and flash 
the modified .bin file back to the drive? I guess that the WWN must be 
found in the firmware somewhere.


On 2012-10-19 02:38, Scott Marcy wrote:
> FWIW, this is what Samsung tech support had to say about the SSD 840 Pro:
>
> "The next generation Samsung SSD 840 Pro series will have WWN. The Samsung 840 Pro is aimed for customers who need to use them on servers which is why only the 840 Pro will have the WWN identifier."
>
> Guess I'll get in line for a few and find out.
>
> -Scott
>
>
> On Oct 17, 2012, at 11:27 AM, Scott Marcy<oi at mscott.org>  wrote:
>
>> I am returning the 4 drives I planned to use in the expanders, but will keep the two I'm using as my mirrored boot pool.
>>
>> My intention was to use these are ZIL and L2ARC drives, so I can do without them for now. I've had very good luck with these Samsung drives in non-SAS usages—quite a bit more reliable in my (admittedly quite limited) experience than the SanForce-based SSDs.
>>
>> Here's hoping they've fixed this on the 840 Pro models.
>>
>> Thank you all for your help. I learned something new and now understand why it doesn't work. :-)
>>
>> -Scott
>>
>> On Oct 17, 2012, at 11:18 AM, Bob Friesenhahn<bfriesen at simple.dallas.tx.us>  wrote:
>>
>>> On Wed, 17 Oct 2012, Scott Marcy wrote:
>>>> 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.)
>>> Maybe you should try to return these and get your money back. The problem does not seem to be specific to use in a "server".
>>>
>>> The physical block size also seems to be reported incorrectly.
>>>
>>> Samsung cut corners by not taking the time to give each device a unique addressable ID as part of their manufacturing process.  It may even be that a step was "accidentally" skipped in the manufacturing process (to make quotas) and that some devices are correctly configured from the factory while others are not.
>>>
>>> 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
>
> .
>