dtbingle

Tried running a Win10 VM on my unraid box with the intent to be able to VPN in during down time at work and mess around in visual studio on some personal projects. However, it seems incredibly slow loading anything, user inputs delayed, and high CPU usage. Comparatively, running a Win10 VM on my gaming PC feels quite snappy (hosted and accessed on same pc). Differences between unRaid machine vs. my gaming PC: Hardware Unraid machine - Core i3-4360 w/ 8gb DDR3 ECC memory *VM stored on SSD cache drive and never moved to array Gaming PC - i7-11700k w/ 32gb DDR4 memory Network Unraid VM is accessed over wired LAN via VM Console (VMC) Hyper V VM on gaming PC is accessed from the same gaming PC (connection not over ethernet) Configuration Is there something wrong with my Unraid VM configuration causing excessive slowness? Currently pinned to CPU 0 only, but same result with CPU 0 / 2 and leaving it on CPU 0 / 2 and CPU 1 / 3 Given 3gb memory out of 8gb available on the machine Demo video (Unraid at beginning, Gaming PC VM at end) Is my unRaid Win10 VM this slow due to old hardware, accessing over ethernet vs. from same PC, or an Unraid VM configuration or other incorrect setting?

Got it, Thanks! So just pop it in, assign disk, and start rebuild. Then it will just rebuild the pre-existing 3TB of data and write zeros for remaining 7TB?

Current config is (2) 10TB and (4) 3TB drives with a single parity setup. Bought a 14TB drive to replace the existing 10TB parity drive and let Unraid rebuild parity with the new 14TB parity drive in place. Now I want to take the old 10TB parity drive and replace a 3TB data drive in the disk array. Do I need to preclear, or at a minimum format, the old 10TB parity drive before adding to the disk array and letting it rebuild?

As an update, preclear finished successfully this time around. Installed into array as parity drive, rebuilt successfully and seems to be working fine. SMART test also showed no errors. As mentioned above, the errors were like due to some USB issue and not disk fault.

Got it, thanks! What in the log makes you suspect USB problem and not a disk problem? For example, can those returned hex values be looked up and point towards a USB problem? Or are you going off of experience where these types of errors show up, but disk preclears fine -> usually USB problem? Last question, what would cause a 3TB drive to run with no errors, but 14TB is consistently throwing I/O errors around same % of the preread process?

Thanks. I'll let the preclear run its course, assuming it doesn't hang up, and then plug in drive to another PC via SATA and check SMART status. Looks like a few more sectors popped up with I/O errors (16 sectors total now) and at 56% preread. If SMART test passes, how would you interpret the I/O read errors at various sectors during this preread? Additional, what else should I be looking for in the logs for additional issues (ie. power issue, connection issue, etc)? Full diag logs attached, preread cycle at 57%. tower-diagnostics-20221231-2338.zip

Just bought a WD Red Plus 14TB (WD140EFGX) that I intend to replace & upsize the parity drive with. My normal process is to put the new drive in a USB3.0 external drive enclosure, plug into Unraid box, and preclear it before adding to the array. However, the 14TB drive keeps hanging within the first 2-4% of the pre-read cycle and has I/O errors showing up in the syslog. After a half dozen attempts, the preread process made it passed this 2-4% mark (13% and going strong), but had the same I/O errors listed in syslog. So I/O errors still there, just this time the preclear process didn't get stuck and hang for eternity. Are the consistent I/O errors during the first few % of pre-read indicative of a bad drive? Something funky happening as a result of doing this process via USB external vs. SATA? Related to software versions and preclear (Unraid 6.11.5, UD 2022.12.28, UD Preclear 2022.12.23)? syslog.txt

Confirmed working for me now as well. It's good to see gfjardim already php'ized the fan control script in the other thread too. ASRock fan speed control is very close it seems! We all appreciate this dmacias and everyone else. To restate what dmacias said above, the ipmitool raw values below ARE FOR ASROCK BOARDS ONLY. I'm not entirely sure if the raw data value applies to all ASRock boards, but it is confirmed for my E3C226D2I. Ipmitool raw 0x3a 0x01 0xAA 0xBB 0xCC 0xDD 0xEE 0xFF 0xGG 0xHH Hex sets 0xAA to 0xHH correspond to different headers. For example, 0xAA is to CPU_FAN1 on our ASRock boards. As for values, 0x00 is smart fan mode, 0x01 - 0x64 corresponds to 1%-100% fan speed.

Can't wait for the ASRock fan control! Nice work! However, after installation and reboot, the sensors page remains blank. Missing dependency maybe? EDIT: ipmitool -c sdr from the command line correctly lists all of the sensors, but it doesn't seem to populate the page