This benefits my Solarflare 10Gbps NICs as well, which can get quite toasty. I’ve now got a 120mm fan on the side-panel cooling the slots directly. My lab is geared toward silence more than cooling so the airflow near the PCIe slots is pretty poor. To get things cooler I decided to move my fans around in my Antec VSK4000 cases. This isn’t a suggestion as I’ve come to learn the hard way. watch -n 4 "esxcli storage core device smart get -d t10.NVMe_SAMSUNG_MZVPW256HEGL2D000H1_6628B171C9382499"Īs you can see, the maximum temperature is listed as 70’C. Running a four second refresh interval using ‘watch’ is a useful way to monitor the drive under stress. First, I needed to get the t10 identifier for my nvme drives: esxcli storage core device list |grep SAMSUNG
Thankfully, drive temperature is one of them. Since I had no idea it was running so hot, I’d say I’m thankful for this feature – but none the less, I’d have to figure out some way to keep these drives cooler.ĮSXi has a limited implementation of SMART monitoring and can pull a few specific metrics. It appears that this is safety measure to stop the controller from cooking itself to the point of permanent damage.
it was no longer listed as a NVMe device or HBA in the system. Looking more closely in ESXi, I could see that the drive completely disappeared. As soon as the heavy writes started, the drive’s temperature steadily increased until it approached 70’C. Sure enough, it wasn’t the older PM953s overheating, but the newer Polaris based SM961 cache drives. One of my nvme drives had overheated! The second time I tried the test, I watched more closely.
#Samsung sm961 driver registration#
T15:43:26.087Z cpu9:2097671)nvme:NvmeExc_RegisterForEvents:370:Async event registration requested while controller is in Health Degraded state. T15:43:26.087Z cpu9:2097671)nvme:NvmeExc_ExceptionHandlerTask:317:Critical warnings detected in smart log, failing controller Looking through the logs, it became clear what had happened: T15:43:26.083Z cpu0:2341677)nvme:AsyncEventReportComplete:3050:Smart health event: Temperature above threshold My guest running the test would completely hang after a few minutes of testing and I’d be forced to reboot the ESXi host to recover. As I started running some performance tests using synthetic tools like Crystal Disk Mark and ATTO, I began to see instability.
#Samsung sm961 driver pro#
The Samsung Polaris based SM961 is similar to the 960 Pro and well suited for vSAN caching.īeing OEM drives, they don’t have any heatsinks and are pretty bare. These drives are plenty quick for vSAN and can be had for great prices on eBay if you know where to look. I’ve got 256GB SM961 MLC based drives for my cache tier, and larger 1TB enterprise-grade PM953s for capacity. I’ll be posting more information on my setup soon, but I decided to use OEM Samsung based SSDs. I recently deployed an all-NVMe based vSAN configuration in my home lab.
0 kommentar(er)
