IMuijtjens

After a lot of reasearch and sweating I finnaly figured out the issue. This issue was driving me nuts.
 
Looks like it was the firmwire version on the LSI SAS 9211-8i controller. The controller was flashed with version P20. This firmwire version can cause a lot of troubles like drives falling out of the raid, CRC Errors etc. I flashed the controller back to firmwire version P19, reconnected my drives, and tried some file copies on the drive pool. None of the drives increased the error count. It's a shame the errors will always stay visible in the S.M.A.R.T. details, but I'm glad this fixed the issue.

Hello,
 
Today I migrated my Drive Pool from Windows Server 2012 to Windows Server 2016 (ESXI).
 
I have some problems with re-adding my disks. I have linked all my hard drives to a .vmdk file using this article from VMware: https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1017530.
On my Server 2012 configration I had 5 drives (8TB) added to the drive pool. When I add those drives as a SCSI drive (Virtual Device Node) the drives will show up as RAW and I cannot open them.
 
I tried to change the Virtual Device Node to IDE controller, they will show up normally and are automtically added to the pool. I can only setup 2 drives with an IDE controller (master and slave).
Does anyone have experience with this? I'm afraid of losing the data stored on the disks.
 
Disks that where not part of the drive pool before can all be added on de SCSI controller.
 
Thanks!