vmxnet4

A Lime Tech Rep reached out to me today and took care of this very quickly. Immediate responses as I sent them the required info so that they could send me a 2nd replacement key. My system and array has been stable since I replaced the PSU (an EVGA SR-2 1200W for anyone curious) with a new Corsair HX850i. FWIW, what a horrible, time consuming experience. HDDs just dissapearing randomly, swapping out SATA cables, swapping out HBAs, swapping out drives, all while doing a parity sync in between each swap, which would fail after about 15-20 minutes, with errors on the parity drive at first (which made me initially think that the brand new WD Gold drive was defective.) Then, had read errors on one of the other drives (the only drive in the array with data on it at the time.) Moved each component to a spare system to rule it out as a problem, and after they all worked fine in the other system, I had the PSU left as the next common thing that had not been tested yet. Put new PSU in, and everything worked like it should, and has been since then (about 1 week so far, and counting.) RIP EVGA SR-2 PSU and 2 USB flash drives. Probably lucky that’s all I lost, now that I think about it.

Lost 2 USB flash drives during troubleshooting a disk issue that turned out to be a failing PSU. Need that "2nd" replacement key as a result.

Just curious, as I have an issue that needs the attention of the person or group responsible for responding to emails sent to the [email protected] address. Has an official response time been mentioned anywhere? I’m having difficulty locating it if so.

Just an FYI ... I followed the steps documented earlier in this thread (editing the XML file for the VM with the values returned by 'lsscsi' for the necessary drive) on 6.4.0 and it works fine on that release, in a Windows 10 Pro VM (10.0.16299, Build 16299). Unfortunately, I did not have a need to use my ASUS BC-12B1ST Blu-Ray drive until about half an hour before posting this, which was after I had upgraded to 6.4.0. So, I cannot answer for certain if this would have worked on a 6.3.x release. However, VM performance was very choppy/laggy through VNC/TeamViewer until I managed to get the Red Hat VirtIO SCSI Controller driver installed ... and I'm talking really laggy/slow. Was almost painfully slow. Had to use keyboard to navigate through Windows because the mouse was just unusable for me, until after that driver was installed. This was on a host with an EVGA SR-2 motherboard (BIOS A58). Drive is attached to one of the on-board SATA2 ports.