- Community Home
- >
- Storage
- >
- HPE SimpliVity
- >
- Critical customer bulleting regarding SanDisks SSD...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-07-2020 07:18 AM
тАО05-07-2020 07:18 AM
Critical customer bulleting regarding SanDisks SSDs in OmniCubes
Greetings!
HPE sent out a critical customer bulletin regarding SanDisk SSDs failing after 40000 work hours.
https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00099180en_us
I'm wondering if the someone has already attempted upgrading that firmware and wouldn't mind sharing the experience? I suppose all the VMs must be powered off before that and the host requires a restart afterwards?
Hopefully the data will remain intact after the upgrade and there is no need to evacuate VMs before the upgrade.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-07-2020 08:09 AM
тАО05-07-2020 08:09 AM
Re: Critical customer bulleting regarding SanDisks SSDs in OmniCubes
Thanks for your query. Please remember that not all OmniCubes will be affected by this. Only OmniCubes with certain SanDisk drives. There is a Dell EMC knowledge article linked from the bulletin which explains how to check if your sever needs to have the firmware upgraded.
There are also steps outlined of how this needs to be done in the EMC knowledge article linked from the bulletin.
Thanks,
DeclanOR
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-07-2020 09:09 AM
тАО05-07-2020 09:09 AM
Re: Critical customer bulleting regarding SanDisks SSDs in OmniCubes
We are one of the lucky ones who happen to have those SSDs.
My inquiry was not about how to perform the upgrade but to find out if there were any issues when upgrading OmniCubes specifically. Dell EMC articles just provide generalized guidelines without mentioning SimpliVity.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-10-2020 03:32 PM
тАО05-10-2020 03:32 PM
Re: Critical customer bulleting regarding SanDisks SSDs in OmniCubes
Hello!
Just wanted to give feedback in case someone will face the same task. Updating via iDRAC 8 worked fine. Just in case I powered down the host beforehand, because a restart would be needed anyway.
The only thing that I had hoped would revert back to "green" is the health status in SimpliVity plug-in's Hardware tab. While it detects the new disk firmware version, the remaining life of the SSDs is still showing as N/A (and "Low" when the mouse cursor is over the yellow exclamation mark).
Well, at least we can hope the drives won't fail after 40K operation hours, which in our case would have happened in a month or two.