Edival76

I realize it's a display issue. Deleting the pool sounds insanely dangerous. My concern is that it should fix it itself by comparing the display information with the pool data on the linux system.

Here are my diagnostics. As far as I can tell, Unraid can't tell that the zfs pool is working correctly and the drive is part of it, but parts of the system can tell that. tower-diagnostics-20250901-1649.zip

I had to replace a ZFS pool cache drive. Copying files from the cache to the array would have taken a full day (not an option), so instead I used zpool replace to swap the drive in place. Everything worked perfectly, and the system is running fine. However, in the UI my new drive is showing as “Cache 3” with the correct details, but it has a blue square icon indicating it’s a “new drive” (not initialized). In reality, it is initialized and working as expected. @SpaceInvaderOne — this might be a great topic for one of your videos, since I couldn’t find much on replacing cache drives with ZFS directly. Has anyone run into this before? How can I get the UI to catch up to reality?

Great question. Over SMB. I even confirmed the share is using SMB only — to ensure I'm using Samba.

Hi, I'm trying to get a simple macOS VM setup to do testing for websites on Safari. Nothing strenuous. I have Unraid 7, I've installed the latest MacInABox, followed SpaceInvaderOne's video tutorial, but it stops at the white mac logo after selecting the Host icon and pressing enter. It never gets past the logo. I have a dual Xeon CPU, 128 GB of system memory and a GPU, but at the moment I don't need to pass the GPU through (due to what I need for now). When it launches, I get a bunch of this error message: qemu-system-x86_64: warning: host doesn't support requested feature: And when I try to shut off the VM, it won't shut off unless I go to Settings→VMS and turn it off and back on again. Can anyone provide any pointers or suggestions to help me figure this out? Thanks so much.

Here you go. root@Tower:~# ls -la /tmp/disklocation/* -rw-r--r-- 1 root root 2368 Feb 14 10:17 /tmp/disklocation/benchmark.2025-02-14.log -rw-r--r-- 1 root root 1455 Feb 14 16:55 /tmp/disklocation/cron_smart.log -rw-rw-rw- 1 root root 345042 Feb 14 16:55 /tmp/disklocation/disklocation.log -rw-r--r-- 1 root root 2455 Feb 14 10:07 /tmp/disklocation/hddcheck.log -rw-r--r-- 1 root root 7018 Feb 14 16:55 /tmp/disklocation/lsblk.json -rw-r--r-- 1 root root 332 Feb 14 10:00 /tmp/disklocation/powermode.ini -rw-r--r-- 1 root root 409 Feb 14 16:55 /tmp/disklocation/powermode.json -rw-r--r-- 1 root root 308 Feb 14 16:55 /tmp/disklocation/zpool_status.dat /tmp/disklocation/smart: total 636 drwxr-xr-x 2 root root 340 Feb 14 10:05 ./ drwxr-xr-x 3 root root 220 Feb 14 16:56 ../ -rw-r--r-- 1 root root 41442 Feb 14 16:55 CT500MX500SSD1_2402E88CAE79.json -rw-r--r-- 1 root root 46667 Feb 14 16:55 ST10000VN0004-1ZD101_ZA2BM9VD.json -rw-r--r-- 1 root root 47715 Feb 14 16:55 ST10000VN0008-2JJ101_ZHZ16KL5.json -rw-r--r-- 1 root root 27720 Feb 14 16:55 ST1000NC000-1CX162_Z1D5Z19H.json -rw-r--r-- 1 root root 47669 Feb 14 16:55 ST12000VN0008-2PH103_ZL2J50WH.json -rw-r--r-- 1 root root 48052 Feb 14 16:55 ST16000NE000-2RW103_ZL2N3TRC.json -rw-r--r-- 1 root root 47916 Feb 14 16:55 ST16000NE000-2WX103_ZR50LC5G.json -rw-r--r-- 1 root root 48245 Feb 14 16:55 ST20000NE000-3G5101_ZVTCS7CY.json -rw-r--r-- 1 root root 49348 Feb 14 16:55 ST20000NE000-3G5101_ZVTDLEZW.json -rw-r--r-- 1 root root 48572 Feb 14 16:55 ST20000NM007D-3DJ103_ZVT62YBA.json -rw-r--r-- 1 root root 31864 Feb 14 16:55 ST2000DL003-9VT166_5YD1J22W.json -rw-r--r-- 1 root root 45535 Feb 14 16:55 ST8000VN0022-2EL112_ZA1FVHHA.json -rw-r--r-- 1 root root 40623 Feb 14 16:55 WDC_WD80EMAZ-00M9AA0_VAGG91SL.json -rw-r--r-- 1 root root 27301 Feb 14 16:55 WDC_WDS500G2B0A_190806A00018.json -rw-r--r-- 1 root root 27635 Feb 14 16:55 WDC__WDS500G1R0A-68A4W0_23520P801790.json disklocation-2025-02-14.log

I did that a couple of times. No change.

This is amazing and makes so much sense!! Thank you!

Ahh, now that is super helpful! Thank you for that. I've made those adjustments.

I'm making it complex because it's still very loud despite the reasonable CPU temp of 58 °C. As you can see, the top temp is 80 °C, which should give it plenty of movement to ramp speeds at that point. It's running at 9600 rpm, which is a bit too loud at that temp, IMO. So, I'm just hoping to be able to make tweaks to it. If not, no worries, it's still WAY better than without.

Question: how do I adjust the curve? My temps are reasonable, but the fans are still much noisier than they should be for the temps I'm seeing. I'm guessing in the Config Editor, but I can't figure out what I need to change.

I just set up Nginx Proxy Manager on Unraid. Everything is going amazing — so much easier than Traefik! Anyway, some of my *Arrs are giving the following error: Could not connect to SignalR, UI won't update I found that I need to add the following location block for the app(s): proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection $http_connection; My question is… HOW? I can't find instructions anywhere on how to do this on the Unraid UI for Nginx. Thanks

Okay, so I removed my other IPMI fan scripts and updated (plus, uninstalled and reinstalled) this plugin. I had an issue where the fans continued running at full speed despite correctly reading the IPMI data (fan speeds, temps, etc). I needed to go to Fan Control → Advanced View → change the max fan speed before it would actually modify the fans correctly. Not sure if I'll need to do this after reboot, but I thought it would be important for you to be aware of.

As I said, it works fine as long as I load that script, but not if I keep it from loading. I will need to do some additional testing later when no one is home or using the server, I guess.

Dell R730XD Dell Inc. 0599V5 , Version A03 Dell Inc., Version 2.19.0 BIOS dated: Tue 12 Dec 2023 12:00 AM