Cloudspeed Gen. II SSD firmware update?

Hi, my solutions was to install linux on a pc and use the sandisk software for linux. Then i could update the firmware.

http://forums.sandisk.com/t5/SanDisk-Enterprise-Forums/ct-p/enterprise 

try this link

@khaidir77 wrote:

the enterprise ssd forum not available

Try copy and pasting the link into a browser. If I click the link I get a message that the node is not found but if i copy paste it into chrome it works. 

Since it seems that noone has ever answered this question here or in the Enterprise forums, the half baked Sandisk Guard Tool utility doesn’t work with its default firmware update settings under Windows.

The method to get it to process without errors is to use the non-default firmware update mode (second option in the list I think) which allows you to specify the offset / block size.  Via trial and error with common block sizes, I found that a block size of 256 was accepted and updated my Ultra Gen II drive from ZR07 to ZR08.

Even with the latest update on my drive, performance is still very marginal on consumer-type controller platforms (Intel SATA3 in AHCI mode during my tests) and light-load / QD1 performance is conspicuously low.  This leads to very bad scores on consumer-type benchmarks such as PCMark tests, so I wouldn’t recommend people snap these up to use for non-server environments.  Their firmware is likely specifically optimized around LSI-based hardware RAID controllers vs consumer controllers, so I wouldn’t expect improvement this far into the firmware’s development either.

There seem to be plenty of bricked versions of these drives floating around eBay with customized non-generic firmware, so updated firmware appears to be crucial for long term reliability–and that generally isn’t possible if the drive is not a generic one that can be updated with this unfriendly / DIY-class-support enterprise utility.

1 Like

Thanks, I ended up selecting option one in the drop down menu, and just make sure I selected 256 bit size. Worked for all our drives. We will be testing them out in at our datacenter tomorrow. Only issue with them so far is that the Dell PERC controller doesn’t seem to like them, and iDRAC is seeing them as having faults.

Which PERC controller is it, and what type of faults are you seeing? I can test mine on an H700 in a T310 if you’d like, which has an iDRAC 6 Express in it.

I tested and confirmed the latest firmware on these does trigger bay and chassis drive faults on my combo described above; a Micron P300 SSD running firmware 0003 has exactly the same effect. I attempted to use mine as a Cachecade drive in both cases. The do function, they just cause permanent fault triggering on the drive tray and chassis LCD etc.

They do function, that was.

As a side note, the Micron 5100 series drives work perfectly without causing Dell faults in my tests so hopefully this will light a fire under someone’s butt in the Cloudspeed firmware engineering dept. They are a better performing product in my tests as well, despite being eTLC based (Cloudspeed Eco/Ultra are MLC/eMLC) so Sandisk needs to fix this for a “server class” line to remain competitive and effectively usable in our usage cases.

1 Like

Sorry I missed your last message. So they are faulty for you, yuck. I put some in a r620 that has a PERC H710P. They are reading without a fault in this model, however the write speeds are horrendus. On a vmware server, in a brand new VM, I am getting 50-60 mpbs write speeds, while my reads are at about 800 mbps. How are your read speeds, what program is running on top of these for you?

Sorry, how are your *write* speeds.

Its write speeds are normal but I can’t really live with the false status flagging issues.  Re: your performance issues, maybe you should check out this bug fix for VMware when using SATA vs SAS disks:

https://communities.vmware.com/thread/538732

The link says it only happens with cheap spinning disks, not ssds.

The user comment at the end of the article noted that it affected SATA SSDs as well, since this is a SATA device issue (vs SAS).

Have you hears that the Cloudspeed Gen. II SSD firmware update?

@lsi écrit:

Comme il me semble que personne n’a jamais répondu à cette question ici, ni sur les forums d’entreprise, ni sur les serveurs de Sandisk Guard Tool ne fonctionne pas avec la mise à jour du micrologiciel par défaut sous Windows.

 

La méthode pour le traitement sans erreur est à utiliser le mode de la mise en œuvre du microprogramme autre que celui par défaut (option), ce qui vous permet de choisir la taille de la / du bloc. Tentative of United States, United States, United States, United States, United States, United States, United States, United States, United States (USA), United States (USA), United States (USA), United States (United Kingdom) ont été acceptés et ont déjà été acceptés. Lecteur Ultra Gen II de ZR07 à ZR08.

 

Même avec la dernière mise à jour sur mon disque, les performances restent très marginales sur les plaques-formes de contrôleur grand public (Intel SATA3 en mode AHCI lors de mes tests) et les performances en charge / QD1 sont remarquablement faibles. Cela conduit à de très mauvais résultats sur les tests de performances tels qu’ils sont testés PCMark. Je ne recommanderais donc pas les gens de utiliser pour les environnements non serveur. Leur microprogramme est probablement spécialement optimisé pour les contrôleurs. Je ne m’attendrais donc pas à une amélioration aussi du développement du microprogramme.

 

Il semble y avoir de nombreuses versions briquetées de disques flottants autour de Bay avec un micrologiciel non générique personnalisé. Le micrologiciel est donc crucial pour la fiabilité à long terme - ce qui n’est généralement pas possible si le lecteur n’est pas générique. peut être mis à jour avec cet utilitaire d’entreprise hostile / DIY-class-support.

 J’ai utilisé des outils de protection SanDisk pour Windows. J’ai essayé sur Pike 2108 et Adaptec 8405 mais ce n’est pas possible de trouver le disque quand c’est dans le raid. J’ai essayé avec USB 3 sata hdd dock et usb 2.0 sata hdd dock. J’ai essayé de l’utiliser sur des contrôleurs SATA sur de nombreux ordinateurs et serveurs différents, mais ce n’est pas possible de mettre à jour. Il dit mis à jour, mais c’est toujours l’ancien firmware, si je l’utilise sur les contrôleurs SATA, il dit:

La mise à jour a échoué

@celia wrote:


@lsi écrit:

Comme il me semble que personne n’a jamais répondu à cette question ici, ni sur les forums d’entreprise, ni sur les serveurs de Sandisk Guard Tool ne fonctionne pas avec la mise à jour du micrologiciel par défaut sous Windows.

 

La méthode pour le traitement sans erreur est à utiliser le mode de la mise en œuvre du microprogramme autre que celui par défaut (option), ce qui vous permet de choisir la taille de la / du bloc. Tentative of United States, United States, United States, United States, United States, United States, United States, United States, United States (USA), United States (USA), United States (USA), United States (United Kingdom) ont été acceptés et ont déjà été acceptés. Lecteur Ultra Gen II de ZR07 à ZR08.

 

Même avec la dernière mise à jour sur mon disque, les performances restent très marginales sur les plaques-formes de contrôleur grand public (Intel SATA3 en mode AHCI lors de mes tests) et les performances en charge / QD1 sont remarquablement faibles. Cela conduit à de très mauvais résultats sur les tests de performances tels qu’ils sont testés PCMark. Je ne recommanderais donc pas les gens de utiliser pour les environnements non serveur. Leur microprogramme est probablement spécialement optimisé pour les contrôleurs. Je ne m’attendrais donc pas à une amélioration aussi du développement du microprogramme.

 Torrent TurboTaxGogoanime

Il semble y avoir de nombreuses versions briquetées de disques flottants autour de Bay avec un micrologiciel non générique personnalisé. Le micrologiciel est donc crucial pour la fiabilité à long terme - ce qui n’est généralement pas possible si le lecteur n’est pas générique. peut être mis à jour avec cet utilitaire d’entreprise hostile / DIY-class-support.


 J’ai utilisé des outils de protection SanDisk pour Windows. J’ai essayé sur Pike 2108 et Adaptec 8405 mais ce n’est pas possible de trouver le disque quand c’est dans le raid. J’ai essayé avec USB 3 sata hdd dock et usb 2.0 sata hdd dock. J’ai essayé de l’utiliser sur des contrôleurs SATA sur de nombreux ordinateurs et serveurs différents, mais ce n’est pas possible de mettre à jour. Il dit mis à jour, mais c’est toujours l’ancien firmware, si je l’utilise sur les contrôleurs SATA, il dit:

La mise à jour a échoué

@lsi wrote:

Since it seems that noone has ever answered this question here or in the Enterprise forums, the half baked Sandisk Guard Tool utility doesn’t work with its default firmware update settings under Windows.

 

The method to get it to process without errors is to use the non-default firmware update mode (second option in the list I think) which allows you to specify the offset / block size.  Via trial and error with common block sizes, I found that a block size of 256 was accepted and updated my Ultra Gen II drive from ZR07 to ZR08.

 

Even with the latest update on my drive, performance is still very marginal on consumer-type controller platforms (Intel SATA3 in AHCI mode during my tests) and light-load / QD1 performance is conspicuously low.  This leads to very bad scores on consumer-type benchmarks such as PCMark tests, so I wouldn’t recommend people snap these up to use for non-server environments.  Their firmware is likely specifically optimized around LSI-based hardware RAID controllers vs consumer controllers, so I wouldn’t expect improvement this far into the firmware’s development either.

 

There seem to be plenty of bricked versions of these drives floating around eBay with customized non-generic firmware, so updated firmware appears to be crucial for long term reliability–and that generally isn’t possible if the drive is not a generic one that can be updated with this unfriendly / DIY-class-support enterprise utility.

ve used SanDisk guard tools for windows. I have tried on Pike 2108 and adaptec 8405 but its not possible to find the disk when its in raid. I have tried with USB 3 sata hdd dock and usb 2.0 sata hdd dock. i have tried to use it on sata controllers on many different pc’c and server’s, but its not possible to update. It says updated but its still the old firmware, if i use it on sata controllers it say:

Updating failed

Not being able to detect & apply firmware to drives inside a RAID array is normal and expected behaviour, unless you are dealing with customized firmware updaters produced by manufacturers for their own certified (modified) firmware versions such as Dell, HP etc.

Not being able to do firmware updates on drives via USB adapters is also normal and expected behaviour across all drive manufacturers, older updates used to require IDE mode and most modern updaters needs SATA drives direct connected to a controller in AHCI mode (and often only with msahci drivers vs Intel RST or AMD SATA drivers etc).

Sandisk’s utility, despite newer updates, is still one of the worst and least unintuitive utilities I have ever used–which requires a non-default flash mode and custom block size (256) to be used to successfully update firmware once all those other conditions are met.

I have repeatedly updated multiple Cloudspeed Eco and Ultra drives successfully using this process, with firmwares ZR08 through ZR11–but don’t expect any dramatic improvements.  Sandisk doesn’t seem to have the motivation (or skills, since these bug threads have been in their forums and across the net for years now) to enable their “enterprise class” SSD products to work on Dell enterprise PERC controllers without being flagged yellow / failed in hot swap bays.

It seems that despite the apparent value and competitive performance of these drives, Sandisk doesn’t really take their implementation into real world environments very seriously–even when we document specific bugs and have to document the processes to use their own management utilities effectively in their own forums.

Until Sandisk gets serious about fixing their firmware management tools and glaring firmware bugs (re: Dell PERC compatibility), people should be looking to more competent enterprise drive manufacturers like Intel and Micron.  Samsung doesn’t focus much on the “generic” enterprise SSD market either, and has historically cut some ridiculous corners in firmware design (like not properly monitoring & testing their power protection circuits) so I wouldn’t waste your time there either.  These drives really only deserve to be used in very basic & generic “light enterprise” / SMB implementations where the drives are used on simple SATA controllers.

The Cloudspeed drives also have quite high write latency under stress, which can easily be reproduced in a matter of minutes by running an AS-SSD 10GB test vs its 1GB default.  Write latency skyrockets beyond the mentioned Intel / Micron products (comparing to pretty much anything ~5 yrs or newer gen in my tests), even on ZR11, and there is no significant difference between the Ultra G2 & Eco G2 despite the Ultra G2 having 3x the write endurance rating.  So the Ultra G2 seems to be simply designed to withstand write activity vs being legitimately optimized for it.  If that is truly the case, simply overprovisioning a large Eco G2 drive would probably be more effective than paying for an “Ultra” class drive.

Надо переименовать расширение файла прошивки в .bin

для примера так:

ZR11xxxx_w_boot_BLR-0080_QR.bin

Затем данный фаил позволяет прошить данные SSD из под программы

SanDisk SSD Dashboard штатные образом.

Прошивки лежат в папке  архива cloudspeed2-eco-ultra-fw-zr11

для дисков

SDLF1DAR-480G-1Hxx
SDLF1DAR-960G-1Hxx
SDLF1CRR-019T-1Hxx
SDLF1DAM-400G-1Hxx
SDLF1DAM-800G-1Hxx
SDLF1CRM-016T-1Hxx

а так же подходит для SDLF1xxx-xxxx-1J2