Skip to main content

HP SSD on ProLiant DL360p Gen8 p420i controller - no TRIM?



We have a HP Proliant Dl360 Gen8 server with the 420i 2Gg disk controller. (646905-421)



we have a couple of the HP Gen8 200GB 6G SAS SLC SSDs (653078-B21), (they run in RAID1)



We run Debian6 on this server, and HP says that the "trim" command is not supported on this controller.




-How will this affect the speed and lifetime of the SSD?
-Does anyone know any controller that might do a better job?
-has anyone run similar configuration, can you say anything on the lifetime of disks?


Answer



You're using (expensive) enterprise SAS SSDs. This drive is OEM by Sandisk, an LB206S, whose specifications show that it's a write-optimized drive. There is no need for TRIM. TRIM is for cheap consumer SATA disks. In addition, your drives are heavily overprovisioned and have their own wearout indicators available.



This is visible from the controller using the Array Configuration Utility, the HP Smart Storage Administrator or the hpacucli and hpssacli command-line utilities. If you have any of the HP Management Agents installed or even ILO-based monitoring, the server will email/SNMP trap on SSD failure or dwindling drive wearout indicator.



An example from a similar same-OEM drive in my system (LB406M, read-optimized). Pay attention to the Usage remaining field or the field that says "Estimated Life Remaining based on workload to date":




  physicaldrive 1I:1:4
Port: 1I
Box: 1
Bay: 4
Status: OK
Drive Type: Data Drive
Interface Type: Solid State SAS
Size: 400 GB
Firmware Revision: HPD9
Serial Number: 00211644

Model: HP MO0400FBRWC
Current Temperature (C): 28
Maximum Temperature (C): 56
Usage remaining: 99.68%
Power On Hours: 5845
Estimated Life Remaining based on workload to date: 75863 days
SSD Smart Trip Wearout: False
PHY Count: 2
PHY Transfer Rate: 6.0Gbps, Unknown


Comments

Popular posts from this blog

linux - iDRAC6 Virtual Media native library cannot be loaded

When attempting to mount Virtual Media on a iDRAC6 IP KVM session I get the following error: I'm using Ubuntu 9.04 and: $ javaws -version Java(TM) Web Start 1.6.0_16 $ uname -a Linux aud22419-linux 2.6.28-15-generic #51-Ubuntu SMP Mon Aug 31 13:39:06 UTC 2009 x86_64 GNU/Linux $ firefox -version Mozilla Firefox 3.0.14, Copyright (c) 1998 - 2009 mozilla.org On Windows + IE it (unsurprisingly) works. I've just gotten off the phone with the Dell tech support and I was told it is known to work on Linux + Firefox, albeit Ubuntu is not supported (by Dell, that is). Has anyone out there managed to mount virtual media in the same scenario?

hp proliant - Smart Array P822 with HBA Mode?

We get an HP DL360 G8 with an Smart Array P822 controller. On that controller will come a HP StorageWorks D2700 . Does anybody know, that it is possible to run the Smart Array P822 in HBA mode? I found only information about the P410i, who can run HBA. If this is not supported, what you think about the LSI 9207-8e controller? Will this fit good in that setup? The Hardware we get is used but all original from HP. The StorageWorks has 25 x 900 GB SAS 10K disks. Because the disks are not new I would like to use only 22 for raid6, and the rest for spare (I need to see if the disk count is optimal or not for zfs). It would be nice if I'm not stick to SAS in future. As OS I would like to install debian stretch with zfs 0.71 as file system and software raid. I have see that hp has an page for debian to. I would like to use hba mode because it is recommend, that zfs know at most as possible about the disk, and I'm independent from the raid controller. For us zfs have many benefits,

apache 2.2 - Server Potentially Compromised -- c99madshell

So, low and behold, a legacy site we've been hosting for a client had a version of FCKEditor that allowed someone to upload the dreaded c99madshell exploit onto our web host. I'm not a big security buff -- frankly I'm just a dev currently responsible for S/A duties due to a loss of personnel. Accordingly, I'd love any help you server-faulters could provide in assessing the damage from the exploit. To give you a bit of information: The file was uploaded into a directory within the webroot, "/_img/fck_uploads/File/". The Apache user and group are restricted such that they can't log in and don't have permissions outside of the directory from which we serve sites. All the files had 770 permissions (user rwx, group rwx, other none) -- something I wanted to fix but was told to hold off on as it wasn't "high priority" (hopefully this changes that). So it seems the hackers could've easily executed the script. Now I wasn't able