Notification

Icon
Error

HPE SAS Solid State Drives failure report

Posted: Tuesday, November 26, 2019 5:57:58 PM(UTC)
Esben.D

Esben.D

Member Administration Original PosterPosts: 1,982
1
Like
After reading a reddit topic regarding this and linking me to the official HPE bulletin. It seems that some SSDs are getting a drive failure at 32,768 hours of operation.

I was curious to try and report on it. Unfortunately, I do not have any of the HPE SAS SSDs to check if my report actually works or not.

I'm hoping (then again maybe not for your sakes) that someone has an SSD that might be affected. It would be great to know if this report actually works:

Code:
Select Top 1000000 tblAssets.AssetID,
  tblAssets.AssetName,
  tsysAssetTypes.AssetTypename,
  tsysAssetTypes.AssetTypeIcon10 As icon,
  tblAssets.IPAddress,
  tblAssets.Lastseen,
  tblAssets.Lasttried,
  tblDiskdrives.Volumename,
  Ceiling(tblDiskdrives.Size / 1024 / 1024 / 1024) As [Max size in GB],
  Ceiling(tblDiskdrives.Freespace / 1024 / 1024 / 1024) As [Free Space in GB],
  tblDiskdrives.FileSystem,
  tblDiskdrives.Description,
  tblDiskdrives.Caption,
  tblDiskdrives.Compressed,
  tblFloppy.Model,
  tblFloppy.Name,
  tblFloppy.FirmwareRevision,
  tblDiskdrives.DriveType,
  tblFloppy.InterfaceType
From tblAssets
  Inner Join tblAssetCustom On tblAssets.AssetID = tblAssetCustom.AssetID
  Inner Join tsysAssetTypes On tsysAssetTypes.AssetType = tblAssets.Assettype
  Inner Join tblDiskdrives On tblAssets.AssetID = tblDiskdrives.AssetID
  Inner Join tblFloppy On tblAssets.AssetID = tblFloppy.AssetID
Where tblFloppy.Name Like '%PHYSICALDRIVE0' And
  tblAssetCustom.State = 1 And tblDiskdrives.Freespace > 0 And
  tblDiskdrives.Size > 0 And (tblFloppy.Model Like '%VO0480JFDGT%' or tblFloppy.Model Like '%VO0960JFDGU%' or tblFloppy.Model Like '%VO1920JFDGV%' or tblFloppy.Model Like '%VO3840JFDHA%' or tblFloppy.Model Like '%MO0400JFFCF%' or tblFloppy.Model Like '%MO0800JFFCH%' or tblFloppy.Model Like '%MO1600JFFCK%' or tblFloppy.Model Like '%MO3200JFFCL%' or tblFloppy.Model Like '%VO000480JWDAR%' or tblFloppy.Model Like '%VO000960JWDAT%' or tblFloppy.Model Like '%VO001920JWDAU%' or tblFloppy.Model Like '%VO003840JWDAV%' or tblFloppy.Model Like '%VO007680JWCNK%' or tblFloppy.Model Like '%VO015300JWCNL%' or tblFloppy.Model Like '%VK000960JWSSQ%' or tblFloppy.Model Like '%VK001920JWSSR%' or tblFloppy.Model Like '%VK003840JWSST%' or tblFloppy.Model Like '%VK003840JWSST%' or tblFloppy.Model Like '%VK007680JWSSU%' or tblFloppy.Model Like '%VO015300JWSSV%')
Order By tblAssets.AssetName,
  tblDiskdrives.Caption


Tommy75
#1Tommy75 Member Posts: 3  
posted: 12/10/2019 7:28:21 AM(UTC)
It appears you report does not produce the desired result on Linux systems.
Tommy75
#2Tommy75 Member Posts: 3  
posted: 12/10/2019 8:04:05 AM(UTC)
Maybe it would be better to create a report based on manufacturer and models and investigate further.


Hardware Platforms Affected: HPE Synergy 480 Gen9 Compute Module, HPE Synergy 660 Gen9 Compute Module, HPE Synergy D3940 Storage Module, HPE 400GB 12G SAS Mixed Use-3 SFF 2.5-in SC 3yr Wty MO0400JFFCF Solid State Drive, HPE 800GB 12G SAS Mixed Use-3 SFF 2.5-in SC 3yr Wty MO0800JFFCH Solid State Drive, HPE 1.6TB 12G SAS Mixed Use-3 SFF 2.5-in SC 3yr Wty MO1600JFFCK Solid State Drive, HPE 3.2TB 12G SAS Mixed Use-3 SFF 2.5-in SC 3yr Wty MO3200JFFCL Solid State Drive, HPE 480GB 12G SAS Read Intensive-3 SFF 2.5-in SC 3yr Wty VO0480JFDGT Solid State Drive, HPE 960GB 12G SAS Read Intensive-3 SFF 2.5-in SC 3yr Wty VO0960JFDGU Solid State Drive, HPE 3.84TB 12G SAS Read Intensive-3 SFF 2.5-in SC 3yr Wty VO3840JFDHA Solid State Drive, HPE Synergy 620 Gen9 Compute Module, HPE Synergy 680 Gen9 Compute Module, HPE ProLiant XL270d Gen9 Server, HPE D6020 Disk Enclosure, HPE StoreVirtual 3000 Storage, HPE ProLiant DL360 Gen10 Server, HPE ProLiant BL460c Gen10 Server Blade, HPE ProLiant DL380 Gen10 Server, HPE ProLiant DL388 Gen10 Server, HPE ProLiant DL160 Gen10 Server, HPE ProLiant DL180 Gen10 Server, HPE ProLiant DL580 Gen10 Server, HPE ProLiant ML110 Gen10 Server, HPE ProLiant ML350 Gen10 Server, HPE ProLiant DL385 Gen10 Server, HPE ProLiant DL325 Gen10 Server, HPE ProLiant DL20 Gen10 Server, HPE ProLiant SL230s Gen8 Server, HPE ProLiant BL460c Gen8 Server Blade, HPE ProLiant BL465c Gen8 Server Blade, HPE ProLiant DL160 Gen8 Server, HPE ProLiant BL420c Gen8 Server Blade, HPE ProLiant DL320e Gen8 Server, HPE ProLiant WS460c Gen8 Graphics Server Blade, HPE ProLiant BL660c Gen8 Server Blade, HPE ProLiant DL560 Gen8 Server, HPE D6000 Disk Enclosure, HPE StoreEasy 1000 Storage, HPE D2220sb Storage Blade, HPE ProLiant SL210t Gen8 Server, HPE StoreVirtual 4335 Hybrid Storage, HPE ProLiant DL580 Gen8 Server, HPE D3000 Disk Enclosures, HPE ProLiant DL180 Gen9 Server, HPE ProLiant DL360 Gen9 Server, HPE ProLiant BL460c Gen9 Server Blade, HPE ProLiant DL380 Gen9 Server, HPE ProLiant ML350 Gen9 Server, HPE ProLiant XL230a Gen9 Server, HPE ProLiant DL388 Gen9 Server, HPE ProLiant DL120 Gen9 Server, HPE ProLiant WS460c Gen9 Graphics Server Blade, HPE ProLiant DL580 Gen9 Server, HPE ProLiant BL660c Gen9 Server Blade, HPE ProLiant DL560 Gen9 Server, HPE Apollo 4200 Gen9 Server, HPE Apollo 4500 System, HPE ProLiant XL450 Gen9 Server

Active Discussions

Lansweeper snmp trap HP 1910 switch
by  info  
Go to last post Go to first unread
Last post: Today at 11:52:17 AM(UTC)
Lansweeper Lsagent cloud relay changes the scanserver value
by  ghelpdesk   Go to last post Go to first unread
Last post: Today at 2:45:11 AM(UTC)
Lansweeper Is there a chance to get the firewall off via Lansweeper?
by  RedWood  
Go to last post Go to first unread
Last post: Yesterday at 11:23:31 PM(UTC)
Lansweeper Not working Wake on Lan
by  RedWood   Go to last post Go to first unread
Last post: Yesterday at 11:17:33 PM(UTC)
Lansweeper Wake on Lan Issues
by  RedWood  
Go to last post Go to first unread
Last post: Yesterday at 11:06:12 PM(UTC)
Lansweeper New Web Interface
by  anpatterson03   Go to last post Go to first unread
Last post: Yesterday at 10:05:19 PM(UTC)
Lansweeper LsAgent failing - Lansweeper SSL Expired
by  nlertn-PRE  
Go to last post Go to first unread
Last post: Yesterday at 9:34:12 PM(UTC)