oh-tomo

I don't know. The Win10 was the only one I was using (why would the size suddenly change?) so I deleted the others and eventually was able to boot back in. I also had to disable the GPU passthrough and boot in using VNC. Once the Windows repairs were done and I got back in, I shut down the Win10 VM, re-added the GPU and booted in again. It seemed faster once I was back in but now after a few days Win10 seems less responsive. Wonder if it's the downloading of Win10 updates that is slowing things down. Space used is still only around 437 GB of out of 899 GB.

Booted into Windows and there's 437 GB of free space out of 899 GB. Why was VM boot up pausing if there's all this space?

I used command line instead ‘rm -rf Mac*’ and was able to make 48GB of space. Still don’t know why Krusader wouldn’t do the same.

My Win10 VM froze 26 hours ago and after several attempts to reboot have been unsuccessful i thought the issue might be due to the lack of space on the drive it is located on. I tried removing other MacOS VMs from the drive using Krusader (after deleting them using the unraid VM control panel) but the folders and files remain in place. How do I get Krusader to actually make room? And why didn’t Windows warn me it was running out of space? If I could get past pause I could see what’s taking up all the space in windows and delete stuff but I’m locked out.

Experienced a fourth "Remaining battery runtime below limit on UPS" shutdown yesterday.... just as UPS (the courier) was supposed to deliver the APC 1500VA... only they didn't deliver it. Hope they come back. When I powered the unRAID back up I checked the APC power cords connection to the wall. It wasn't completely pushed into the socket, but that wouldn't cause a shutdown, would it? I pushed it in before powering unRAID back on.

Saw this thread and ordered the APC 1500VA. Hope it solves things.

Between today and 15 days ago I've had the unRAID message "Remaining battery runtime below limit on UPS" followed by a shutdown on three occasions. On those occasions I've been either away or asleep so have no other evidence that a power failure occurred other than a powered off unRAID (and this notification). In the four year life of this server prior to 15 days ago, this message never appeared. Should I get a new battery? https://www.amazon.ca/dp/B0002QLDLC?tag=pricespiderco553-20&ascsubtag=wtbs_63379b9485be32685487867b Should I get a UPS with a larger capacity battery? Key Value APC 001,034,0847 HOSTNAME Server2018 UPSNAME Server2018 DRIVER USB UPS Driver STARTTIME 2022-09-30 20:17:14 -0400 STATUS Online LOADPCT 59.0 Percent TIMELEFT 8.6 Minutes MINTIMEL 10 Minutes SENSE High HITRANS 139.0 Volts BATTV 13.7 Volts NUMXFERS 0 CUMONBATT 0 Seconds STATFLAG 0x05000008 BATTDATE 2018-03-23 NOMBATTV 12.0 Volts END APC 2022-09-30 21:20:16 -0400 DATE 2022-09-30 21:19:27 -0400 VERSION 3.14.14 (31 May 2016) slackware CABLE USB Cable UPSMODE Stand Alone MODEL Back-UPS ES 650G1 LINEV 122.0 Volts BCHARGE 100.0 Percent MBATTCHG 10 Percent MAXTIME 0 Seconds LOTRANS 92.0 Volts ALARMDEL 30 Seconds LASTXFER Unacceptable line voltage changes TONBATT 0 Seconds XOFFBATT N/A SERIALNO X NOMINV 120 Volts FIRMWARE 906.W1 .D USB FW:W1

So I forced stop and shut down the unRAID and waited 10 seconds and powered the unRAID back on and then started the VM and saw TianoCore spinning dots accompanied by (timestamps in mm:ss included): 00:01 "Preparing Automatic Repair" 00:06 "Diagnosing your PC" 00:28 "Attempting repairs" 00:39 black screen 00:51 TianoCore spinning dots 01:15 "Getting Windows ready. Don't turn off your computer" (white text blue screen) 01:25 Windows login screen So that was faster than 12 hours. Is powering down the unRAID then always the answer? I don't know. It seems kind of extreme. Repair suggests that some kind of damage happened. Was the damage caused because I forced stop during some important process that the spinning dots were hiding from my view?

So I forced stop and restarted the VM at 9:50pm and the dots are still spinning at 10:19pm. Do I continue waiting or reboot the unRAID. These spinning dots are so uncommunicative as to what is going on and the progress of the boot up. They just spin and spin and keep their secrets to themselves. Windows login screen could pop up any minute or I could be looking at 12 hours of spinning still. I just don’t know. I. Just. Don’t. Know.

Chrome Remote Desktop reports at 9:15pm today that my Win10 VM was last online yesterday at 11:22pm. This morning I saw the spinning dots TianoCore screen at 11:09am. So letting the dots do their thing for 10 hours didn't seem to work. Even when disconnecting the usb hub from the usb card assigned to the VM. I wish there was a way to understand the magic of the spinning dots.

It’s is 11:20am and I see the TianoCore spinning dots. Around 11 hours ago I restarted Windows 10 to apply updates. And went to bed. So I don’t know what’s been going on in the past 11 hours. I just see the spinning dots now. Damn. Presumably at some point during the past 11 hour the Windows update finished? But I don’t know when. Unless the spinning dots is masking part of the Windows update process? I’ve unplugged my USB hub from the USB card assigned to this VM if that’s what is keeping the spinning dots occupied. But the dots still spin six minutes later. i just want to add that Windows has been nagging me about restarting to apply updates for some weeks. And these spinning dots remind me why I was so reluctant to restart.

Is there a plugin or app or something that looks up the temperature thresholds for each disk's model and auto-populates the temperature threshold settings in unRAID? For those of us too lazy to look up each model's thresholds and manually type them in.

Saw JDK's November post above suggesting to manually start indexing so ran this command: docker exec -u abc -d diskover python3 /app/diskover/diskover.py /data Then checked http://192.168.0.36:9200/_cat/indices?v but no activity present. ???? I've also uncommented the crontab entry as suggested in an earlier post. Maybe it would be easier to just upload everything to Google Drive and search there. Google used to have a desktop search product from 2004-2011, but alas it went to the graveyard of useful products. https://en.wikipedia.org/wiki/Google_Desktop

New error: "No completed indices found in Elasticsearch. Run a crawl and after it finishes reload select indices page."

Thanks for the quick reply. I've set elasticsearch variable to the IP. I didn't have elasticsearch installed. Now it is installed and running. Also set up the vm.max_map_count user script. Stopped and started diskover and still see the same "Oops something went wrong, Unable to connect... localhost:9200" error. Then stopped and restarted elasticsearch and stopped and restarted diskover. Same error.

Oops something went wrong Unable to connect to Elasticsearch host localhost:9200. Error: Failed to connect to localhost port 9200 after 0 ms: Connection refused Reload index page Logout Getting this after logging into webui.

"1) Just wait it out" worked. Also audio seems to play better now with MSI enabled.

I restarted Windows and am looking at the spinning dots again. Spinning is better than not spinning I think we’ve established, right? It’s been going for over 30 minutes. Not that I watched the spinning for 30 minutes but it was spinning when I first rebooted 30 minutes ago and now that I’m rechecking it 30 minutes later it is still spinning. Before I selected restart in Windows I had just run MSI utility v2 and enabled MSI on both HD audio and NVidia graphics and set both to High. Then when selecting restart I encountered the option to either update and restart or update and power down. I selected update and restart. So are the thirty plus minutes of TianoCore spinning dots because : 1) Windows is applying an update and needs (30+ minutes of) time to finish? 2) my changes using MSI Utility v2 are trapping my VM in a perpetual spinning dot state? 3) something else? should I : 1) just wait it out? 2) force stop the VM and disable NVidia ? 3) something else?

I couldn't see any problem with the cables. Maybe they were arcing too high towards the upper case fan. I tucked them a bit to the side away from the fan. I guess I just wait and see if the problem returns.

I guess I could resume the parity check.

"Completed without error" Now what? ST16000NE000-2RW103_ZL2P6V5T-20220619-2307 redacted.txt

Extended SMART test (second attempt) has been stuck at "self-test in progress, 10% complete" all this time.

Extended SMART test didn't finish -- "Interrupted (host reset)" I'll try again.

I paused the rebuild and ten minutes later got an alert that Disk 1 (the new disk) is in error state. So maybe JorgeB is onto something. Running an extended SMART test now. How long do they take? Will the test reveal an actionable solution to the cause of the errors?

Disk 4 has error (UDMA CRC error count 1), the rest are healthy on dashboard.