atsmusz

Looks like it was HDD hardware issue. Many errors (over 900) once I got the drive on SATA instead of USB. Going to RMA it and replace. Thanks @trurl and anybody else that assisted. Appreciate your patience and support!

Yeah ...... that makes sense ...... My case only has one more slot for a drive internally and it already runs too hot ......( case not designed for "server" use ) I'm going to see if I can figure out another way to put the drive inside the case but just in the main compartment and get it back on SATA cable.

Parity drive is in external enclosure on USB3 w USBA connector.

This is my partiy check progress so far. In past checks, it seems to "hang" at around 46 or 47% and then says it will take over 31 days instead of the 2 days and change showing now.

When you say rebuild, is this something that will happen or you mean I need to do something specific to initialize the rebuild process? Apologize for these probably noob questions but while I have many years in IT related stuff, I have not had too much experience dealing with HDD hardware issues. It's likely I can get this drive replaced from WD and even have the replacement drive cross-shipped, in the past I have always just replaced drives that had any issues.

SMART test still running ...... now at 90% Do see this yellow as shown in screen-shot but no idea what it means.

Yeah, I figured that was the case. Running the long test now but it seems to be stuck at 10% for a long time. That drive is less then 6mos old. Gonna be irritated w WD if it's already failing. 😞 SMART self-test "full" now at 20% so still moving.

Parity Drive "short" SMART test finished w no errors. Parity check now running and at 4.8%. Got some warnings about Parity drive but can't find the text now. The parity-check usually seems to hang around 40%.

Yeah thnx. will re-check connections. Good idea. When I woke up diags had still not finished. Will attempt re-start and try again, but seems I have to do ugly power-off as command line re-start/shutdown not working either. Diags now uploaded. System fine after re-boot ....... probably until parity check kicks in.

I had a cache drive that was going bad so I removed it and swapped it out for a much larger one following an article I found on how to do this. I brought the server back up and due to some other issues decided to reload all my dockers. I put the Docker appdata on cache-only since my cache drive was now 2TB (used to be 256GB) and then when my weekly parity check started it got to 47% and just hung there for days and a number of my CPU cores are constantly running at 100%. It now seems that there are SMART errors with my parity drive which is quite new 4TB. New Diags. tower-diagnostics-20210923-0827.zip tower-diagnostics-20210923-1019.zip

Was just having this issue on an old centos 6 image that I needed to spin up for some dev work. The answer was to select the oldest "machine" I had available:

Ok ...I've tinkered with this for a while and can't figure it out. Tried looking in the VM guides section but didn't find anythng specific. Need to create a WIN10 VM for some work stuff as well as running PRTG. Every time I create one there's no VNC connection ... and I get some interesting bits in the log (Domain id=x is tainted). I think the issue might be with HyperV? Added the start-log and a screen-shot of the VM edit page. Any help is appreciated! V 6.9.2 MSI MEG Motherboard 64GB Ram AMD Ryzen 3700x CPU startwin10log.txt