How To Monitor SSD Health Status on VMware ESXi Host

Kent Chen — Wed, 21 Aug 2019 23:54:15 +0000

With more SSD drives added into the VMware host, I need to find a way to monitor the health status of these drives before it’s too late. Here is what I gathered so far:

First of all, enable SSH service so you can tune in through SSH to perform the commands.

To get the list of storage devices installed on the host, run

esxcli storage core device list

Find the one that has Is SSD: true and mark down the device ID for the next step.

esxcli storage core device smart get -d=deviceID

The output will look something like this. Mine says all N/A so there could be something still missing.

You can archive the same results for all disks in once by running a script called smartinfo.sh in the following folder:

/usr/lib/vmware/vm-support/bin

If you are satisfied with the information provided by this builtin command, great. Otherwise, you may want to try a modified copy of smartmontools for VMware, thanks to this vExpert.

Here is a step of how to get the tool installed on VMware host.

Download smartctl-6.6-4321.x86_64.vib.
Upload it to the /tmp folder of the ESXi host.
SSH to the host.
Set the ViB acceptance level to CommunitySupported.
Then install the package.

esxcli software acceptance set --level=CommunitySupported
esxcli software vib install -v /tmp/smartctl-6.6-4321.x86_64.vib

The tool is installed at /opt/smartmontools folder and works just like the Linux version.

/opt/smartmontools/smartctl -d sat --all /dev/disks/[DISK]

The post How To Monitor SSD Health Status on VMware ESXi Host first appeared on KC's Blog.

Why RAID 5 is OK on SSD Drives?

Kent Chen — Fri, 28 Jul 2017 23:09:53 +0000

First of all, here is why RAID 5 is so bad and has stopped working since 2009.

To recap, two things to blame here.

UREs (Unrecoverable Read Error)
Disk storage capacity

Here is an example to illustrate why it’s so bad having RAID 5 on large capacity hard drives.

With a 7-2TB drives RAID 5 setup, when one drive failed, you will have 6 2-TB drives remaining. After you put in a new 2-TB drive, the resilver process kicks off to rebuild the array. Because the RAID controller needs to read through all remaining 6 disks, total of 12-TB of data, to reconstruct the data from the failed drive, there is a very high possibility that it will see another URE during the process. When that happens, it’s the second drive failure in the array, simply meaning Game Over.

I actually had that exact nightmare before on one of the backup servers. I ended up having to rebuild everything from scratch.

However, the theory applies to the traditional Winchester hard drives (spindle drives) that have a pretty high URE no matter how reliable it claims. What about the SSDs that slowly take over the whole world?

Surprisingly, it seems to be absolutely fine utilizing SSD drives on RAID 5 array. Here is a nice run down by Scott Alan Miller:

SSDs generally just don’t have UREs so the second disk failure due to URE during the resilver process is non-existed.
Time to reconstruct the data from the failed drive is hugely reduced.
Resilver impact is much reduced as SSDs handles non-sequential data access so much better.

The only concern remaining here is the lifespan on SSD drives. For example, if you utilize 6-1TB SSDs from the same brand on a RAID 5 array, there are chances down the road when two of them died at the same time because they share the same endurance lifespan. Maybe, you could pick SSDs from a different brand with the same size or intentionally perform a disk failure to the array, e.g. sequentially hot-swap one with a spare drive in the array to differentiate their lifespans.

Now, I am marching on my way to build a new SSD RAID5 array.

A few more good readings regarding the disk array:

The post Why RAID 5 is OK on SSD Drives? first appeared on KC's Blog.

SSD | KC's Blog

How To Monitor SSD Health Status on VMware ESXi Host

Why RAID 5 is OK on SSD Drives?