IMuijtjens

Are you using 4TB disks? I saw someone who was using 4TB Dekstar disks with no issues running the P20 firmware, he had issues with a 6TB Dekstar NAS disk. Perhaps it depends on the brand/size of the disk. I'm using 5x WD Gold 8TB and 2x WD Red 8TB which are both failing under firmware P20.

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 noticed the S.M.A.R.T. values of my hard drives in my storage server are reporting a huge count of Interface CRC Errors. All disks are showing these errors. I'm using ESXI on my Home Server. 2 VM's (1 web server and 1 storage server). 7 hard disks (8TB) are connected on my LSI SAS 9211-8i controller, which is flashed in IT Mode (JBOD). I configured pass-through and linked the controller to my storage VM. The error count continues to increase, but the performance of the disks stays ok. I did a copy from my data pool to my backup pool. 100GB of data copied in 13 minutes. After the copy completed, the error count was increased on all the disks. I'm wondering what is causing these errors. All the disks in my Storage VM are showing these errors. The hard drive which is connected to my web server (RDM) is not showing these errors. That disk is connected on a SATA-port on my motherboard. Could it be the pass-through configuration which causing issues? HD Tune Pro: ATA WDC WD80EFZX-68U Health ID Current Worst ThresholdData Status (01) Raw Read Error Rate 100 100 16 0 ok (02) Throughput Performance 132 132 54 112 ok (03) Spin Up Time 145 145 24 38684393924 ok (04) Start/Stop Count 100 100 0 225 ok (05) Reallocated Sector Count 100 100 5 0 ok (07) Seek Error Rate 100 100 67 0 ok (08) Seek Time Performance 128 128 20 18 ok (09) Power On Hours Count 100 100 0 1270 ok (0A) Spin Retry Count 100 100 60 0 ok (0C) Power Cycle Count 100 100 0 220 ok (16) Unknown Attribute 100 100 25 100 ok (C0) Unsafe Shutdown Count 100 100 0 275 ok (C1) Load Cycle Count 100 100 0 275 ok (C2) Temperature 176 176 0 214749478946 ok (C4) Reallocated Event Count 100 100 0 0 ok (C5) Current Pending Sector 100 100 0 0 ok (C6) Offline Uncorrectable 100 100 0 0 ok (C7) Interface CRC Error Count 200 200 0 9163 attention Health Status : ok Setup:

Supermicro X8DAi The onboard controller is the "82801HR/HO/HH (ICH8R/DO/DH) 6 port SATA AHCI Controller". Now I used 2 cheap controllers bought from Aliexpress which will work fine Marvell 88SE9235 PCIe 2.0 x2 4-port SATA 6 Gb/s Controller Marvell PCI 4-port SATA controller card

Found the problem. The onboard SATA ports on the motherboard caused this issue. After reconnecting all hard drives on my SATA PCI-E cards, the drives show up correctly on my guest.

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!