`<div dir="ltr"><div><div>You can get the Seagate firmwares from this link:<br><br><a href="https://apps1.seagate.com/downloads/request.html">https://apps1.seagate.com/downloads/request.html</a><br><br></div>Seems they don't link to this on their site any more I found it in an old email from their site.<br>
<br></div>-Chip<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Apr 15, 2014 at 5:30 PM, Saso Kiselkov <span dir="ltr"><<a href="mailto:skiselkov.ml@gmail.com" target="_blank">skiselkov.ml@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
I've hit this exact same issue on my recent SEAGATE ST2000NM0023 drives.<br>
Can you please direct me to where I can get the firmware package?<br>
Perhaps we could also post the link publicly, so that people can find it<br>
through google or some such method.<br>
<br>
Thanks!<br>
<br>
Best wishes,<br>
<span class="HOEnZb"><font color="#888888">--<br>
Saso<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
On 2/13/14, 11:18 AM, Thibault VINCENT wrote:<br>
> On 02/12/2014 09:59 PM, Steamer wrote:<br>
>> Did you ever find a solution to the overheating faults with the<br>
>> ST4000NM0023?<br>
>><br>
>> I'm currently having the exact same issue with ST1000NM0023 drives,<br>
>> seems like seagate has the user temp probe set at 40'C. The manual<br>
>> states that the temperature settings are programmable via smart, but I<br>
>> haven't found a way to do that.<br>
><br>
> Hello Emile,<br>
><br>
> I've found a workaround but the definitive fix should be handled by<br>
> Illumos I guess. There is no open ticket, first I was waiting for<br>
> something to happen with #4051 before going back to using that distro<br>
> and kernel.<br>
><br>
> Here's the story:<br>
> The SCSI specification defines two registers to store the temperature<br>
> thresholds in SMART data. One contains the recommended maximum operation<br>
> temperature for best MTBF, and the other register is for the absolute<br>
> maximum rating. Usually the industry has always put the same value in<br>
> both, and that is the absolute maximum. That's why we always see<br>
> something like 60/65°C from SMART. But recently Seagate has changed that<br>
> because it was asked by a large OS company to comply with the<br>
> specification for better hardware monitoring integration. The change did<br>
> not only occur in newer products but in a firmware update for existing<br>
> disks and that was applied to the production line which explains some<br>
> disks mays or may not expose this problem although they are the same<br>
> model. Our disks are of the Megalodon serie and all share the same<br>
> firmware basecode.<br>
><br>
> So any Seagate disk will now trigger faults in FMA if they have a<br>
> firmware with the newer policy. Also I think other brands will follow<br>
> the same path.<br>
><br>
> Like other members suggested in that thread, maybe nothing should change<br>
> in FMA but let's face it, you can't maintain a temperature steadily<br>
> under 40°C in a JBOD of hundreds of busy disks. Especially in<br>
> eco-friendly datacenters. IMHO we should not trigger a fault on the<br>
> lower threshold, and certainly not a drive retirement. It breaks storage<br>
> servers on reboot or before a pool import, also spare disks could<br>
> disappear with the retirement triggered.<br>
><br>
> The workaround is to downgrade firmware to the last version before the<br>
> change, and to reset the register with an SCSI command. It is not<br>
> possible to set the register to a user specified value like the<br>
> documentation suggests, they confirmed it.<br>
><br>
> I'm sending a working firmware to you in a private mail. I'm not aware<br>
> of any issue working with that older version and hopefully it should<br>
> upload to 1TB drives as well.<br>
> I'm applying it like this but from Linux not OmniOS:<br>
> # ./dl_sea_fw-0.2.3_32 -f Megalodon_StdOEM_SAS_0002+C84C.lod -m ST4000NM0023<br>
> # ./dl_sea_fw-0.2.3_32 -i<br>
><br>
> Then you should reset the drives so they reload the firmware.<br>
> Here's our example for 4TB drives:<br>
> -------------<br>
> for i in $(lsscsi | grep 'ST4000NM0023' | awk '{print $6}') ; do<br>
> sg_reset -d $i<br>
> done<br>
> -------------<br>
><br>
> And reset the register that contains value from the previous firmware.<br>
> It doesn't work well so we've got this script to run a few times until<br>
> all disks got it. Again it matches 4TB Megalodon.<br>
> -------------<br>
> for i in $(lsscsi | grep 'ST4000NM0023' | awk '{print $6}') ; do<br>
> echo -n "$i "<br>
> if sg_logs $i --page=0x0d | grep 'Reference temperature = 68 C'<br>
>> /dev/null ; then<br>
> echo 'ok'<br>
> else<br>
> sg_logs $i --page=0x0d --reset<br>
> echo 'reset'<br>
> fi<br>
> done<br>
> -------------<br>
><br>
><br>
> Cheers<br>
><br>
<br>
</div></div><div class="HOEnZb"><div class="h5">_______________________________________________<br>
OmniOS-discuss mailing list<br>
<a href="mailto:OmniOS-discuss@lists.omniti.com">OmniOS-discuss@lists.omniti.com</a><br>
<a href="http://lists.omniti.com/mailman/listinfo/omnios-discuss" target="_blank">http://lists.omniti.com/mailman/listinfo/omnios-discuss</a><br>
</div></div></blockquote></div><br></div>
`