oh-tomo

Found the box. The controller is a Orico PVU3-4P USB 3.0 PCI-E Express Card which has been part of the VM since April 2019. I paid $20 for it. Is 30 months just the lifespan of a USB Card and I should get another? I shut down and checked that the molex power into the card was seated and the rest of the power cable was secure at the other end. I've started a file move operation within Windows from the unRAID storage to an external USB dock connected to the Orico. I've done this many times over the past 30 months but only today has the move been interrupted by this Windows code 43 error. At first I thought it was due to a Windows update that occured yesterday so I tried rolling back to the system restore point on October 31. Or maybe something got jostled in the PC case when I swapped out one of the data drives yesterday. Maybe pulling and reseating the molex power back into the Orico will help.

My USB controller stops working after about 40 minutes after booting Win10 VM. Is this an unRAID VM thing or a hardware failure on the USB controller? How do I diagnose the issue?

What does that mean? I can stub a toe. Or a cigarette. But stub a card?

So I upgraded the CPU to a Intel Core i7-9700K and it has helped the Win10 VM significantly. It took quite a few reboots and unplugging of USB and HDMI to get the VM to get past the Tianocore screen but it finally got into Windows. But since upgrading the CPU there have been five "Cache disk is hot" notifications (53, 51, 53, 54, 50 C -- one yesterday and four so far today. So I raised the warning temperature for that drive to 70 C. How should I set the Logical CPUs for a MacOS VM? I've allocated all 8 cores to Windows 10. When I try to start MacOS Catalina VM while Win10 VM is running, audio playback becomes garbled in Win10. Is there a specific balance of Logical CPUs between MacOS VM and Wind10 VM that won't result in warbly Windows audio?

Ran a PC test. Result: "PC Performing below expectations (23rd percentile)": https://www.userbenchmark.com/UserRun/44921725 Would upgrading the unRAID's i3-8100 CPU help the VM significantly? Chrome tabs are no longer crashing but apps do become temporarily non-responsive.

DNS change to 8.8.8.8, 8.8.4.4 and 1.1.1.1 didn't do it for me. Trying an update to 6.9.2 from 6.8.3.... update: after updating unRAID to 6.9.2, checked Docker and still found "not available", so then checked "/usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php" and saw it already had the "@i" edit mentioned in the other thread, then checked Docker again and "not available" was gone and replaced with a mixture of "apply update" and "up-to-date" Hope everything else still works in 6.9.2...

Rebooted unRAID and VM was able to boot again. Weird. Looks like VIA USB controller is back too.

I noticed that the assigned device VIA Technologies VL805 USB 3.0 Host Controller in my Win10 VM wasn't showing up in Win10 (in device manager it had a stroke through it), so I rebooted the VM. Rebooting got stuck on the TianoCore screen. I tried powering off everything connected to the USB controller and rebooting again with a force stop first. I'll next try pulling all the USB cables. Don't recall having this issue before in the two years I've been running this VM.

How do I edit my.cnf file?

Well this goes back to my original question about my old disk1 passing the SeaTools tests. From Seagate's "Warranty Claim Validation Process": Will Seagate hold me to SeaTool's inability to see the issues that my unRAID is experiencing?

Test done! RMA label printed.

What action should I have taken at 3 digits? SMART extended self-test of disk1 has reached 40% I'm doing a Windows long format of old disk 1 before submitting it for Seagate RMA.

I got these SMART health emails on Nov 15: And on Dec 15 this email: Should I have acted on them? There weren't any read error alert emails until March 23. I'll start an extended test on new disk1 tomorrow. Does it take as long as a rebuild?

Dashboard shows SMART errors on: disk1 - Reallocated_Sector_Ct - 8 disk3 - UDMA_CRC_Error_Count - 64 disk5 - UDMA_CRC_Error_Count - 25 I am set up with email notifications. Past SMART health warnings have been about the *GDM (removed as disk1, formerly parity1 -- on 11/15 and 12/15) and *LX1 (new disk1, former parity2 -- all on 03/23) 12TB drives.

Rebuild of new disk1 finished. server2018-diagnostics-20210329-0818.zip

Rebuild of new disk1 (old parity2) started. Should I wait until rebuild is complete before wiping and RMA-ing old disk1? server2018-diagnostics-20210328-0925.zip

parity2 is rebuilding because that HDD was upgraded to a larger HDD. Rebuild is done. What do I do with old disk1 after I replace it? Wipe and send to Seagate? "WARRANTY Valid till 09/Aug/2021" server2018-diagnostics-20210328-0832.zip

Smart health warning for Disk 1. Unraid Disk 1 SMART health [198]: 27-03-2021 23:31 Warning [SERVER2018] - offline uncorrectable is 24 ST12000VN0007-2GS116_*0TGDM (sdi) server2018-diagnostics-20210328-0016.zip

Rebuild is done! server2018-diagnostics-20210326-2333.zip

I haven’t noticed any VM issues with Nvidia. Rebuild of disk1 has started.

Here are the new diagnostics. server2018-diagnostics-20210325-2125.zip

It's plugged into a USB HDD dock and the USB is connected to a Win10 VM.

Attached! server2018-diagnostics-20210325-1309.zip

Yes the server is running without the disk.

unRAID disabled the disk (red x) I removed the disk. Contents are currently emulated. I placed the disk in a HDD USB dock connected to a Windows 10 VM and ran some SeaTools tests: 24 hours running a Long Generic SeaTools test and the HDD passed. This is troubling. The HDD is under warranty until August. But unRAID thinks the HDD is error prone while SeaTools tests aren't finding errors. I can't put the disk back in the array because unRAID has disabled it and I can't send the disk in for RMA to Seagate because their software doesn't show any problems. How should I proceed?