I've a handful or two of Windows Server 2012 R2 systems that can with some consistency, make various flavors of Samsung 850 Pro drives disappear from the OS.
My test systems include a number of different hardware configurations.
These includes combinations of Xeon E5 V2/3 processors with LSI SAS 2308 / 3008 and Intel ICH10 disk controllers.
The OS has all patches applied and the drivers, controllers and disks have all been updated to their latest versions.
The behavior where the disks are "surprise removed" from the OS happens with these drives:
128G Samsung 850 Pro
256G Samsung 850 Pro
512G Samsung 850 Pro
I've not been able to reproduce this with the following models of SSD:
128G Samsung 840 Pro (slightly different failure mode)
250G Samsung 850 Evo
480G Samsung PM863 **
512G Samsung 950 Pro M.2 *
1T Samsung 850 Pro
2T Samsung 850 Evo
I was first notified of this issue by a colleague who was running various types of MS SQL workloads that were causing the drives to slow down and in some cases, disappear from the OS.
My methods for reproducing this include the use of iometer.
Assign a drive to a worker and set 'outstanding IO' to 128.
Use the workload 'all in one' and set hours to 2.
Let the drive fill up then monitor I/O.
Eventually it slows & falls over!
Read and write workload bandwidth should be equal.
So I'm seeing simultaneous ~30MB/s read and write to the 850 Pro drives.
After a while, IO drops to zero before the drives disappear and need to be power cycled.
Apologies if there are somehow gaps in my testing, methodology, or descriptions.
Would anyone else out there be able to try to reproduce this in their environments?
I'm happy to modify workloads or answer questions about my steps / thought processes.
Thanks
Lance
*Edit: forgot to add 950 Pro M.2 to list of unaffected devices.
**Edit#2: added 480G Samsung PM863 to list of unaffected devices.
My test systems include a number of different hardware configurations.
These includes combinations of Xeon E5 V2/3 processors with LSI SAS 2308 / 3008 and Intel ICH10 disk controllers.
The OS has all patches applied and the drivers, controllers and disks have all been updated to their latest versions.
The behavior where the disks are "surprise removed" from the OS happens with these drives:
128G Samsung 850 Pro
256G Samsung 850 Pro
512G Samsung 850 Pro
I've not been able to reproduce this with the following models of SSD:
128G Samsung 840 Pro (slightly different failure mode)
250G Samsung 850 Evo
480G Samsung PM863 **
512G Samsung 950 Pro M.2 *
1T Samsung 850 Pro
2T Samsung 850 Evo
I was first notified of this issue by a colleague who was running various types of MS SQL workloads that were causing the drives to slow down and in some cases, disappear from the OS.
My methods for reproducing this include the use of iometer.
Assign a drive to a worker and set 'outstanding IO' to 128.
Use the workload 'all in one' and set hours to 2.
Let the drive fill up then monitor I/O.
Eventually it slows & falls over!
Read and write workload bandwidth should be equal.
So I'm seeing simultaneous ~30MB/s read and write to the 850 Pro drives.
After a while, IO drops to zero before the drives disappear and need to be power cycled.
Apologies if there are somehow gaps in my testing, methodology, or descriptions.
Would anyone else out there be able to try to reproduce this in their environments?
I'm happy to modify workloads or answer questions about my steps / thought processes.
Thanks
Lance
*Edit: forgot to add 950 Pro M.2 to list of unaffected devices.
**Edit#2: added 480G Samsung PM863 to list of unaffected devices.
Last edited: