-
[Unraid 7.2] Replacing cache with new NVME drive makes problems | BTRFS error | Unmountable
I never had bound the GPU on the old system, it never seemed to be necessary. All seems to work, I had to change a few options (SR-IOV Support - enable; Resizable Bar - enable)in the bios and to bind the GPU to make the GPU usable in the VM.
-
[Unraid 7.2] Replacing cache with new NVME drive makes problems | BTRFS error | Unmountable
Which I tried: Creating a new VM: You are meant to passthrough the NVME by making a check mark in front of it in 'system devices' and the thing marked there is the new NVME(4TB), the old one (1TB) is not checked? waterline-sv-diagnostics-20251118-2037.zip Edit: So, I have removed all bindings, restarted, and bound the 4TB NVME again. It seems to work for the VM manager now, but I haven't yet moved the appdata back. Anyway, my passthrough GPU doesn't show video anymore and also the sound card part of the GPU only shows Nvidia device, the graphic card on the other hand shows normally. Should I made a new thread for that problem or continue this one? waterline-sv-diagnostics-20251119-0327.zip
-
[Unraid 7.2] Replacing cache with new NVME drive makes problems | BTRFS error | Unmountable
Okay, after starting VM manager again and trying to edit my VM: waterline-sv-diagnostics-20251118-2009.zip
-
[Unraid 7.2] Replacing cache with new NVME drive makes problems | BTRFS error | Unmountable
After starting up unraid again, the NVME seems to work like normal. I have not yet started VM manager or docker. Now that I have access to the files again, should I copy them to the array again and format the NVME again, but different. If yes, how should I format it?
-
-
[Unraid 7.2] Replacing cache with new NVME drive makes problems | BTRFS error | Unmountable
Hello! I changed my system from [Asrock Rack EPC612D8A & Xeon E5-2690 v4] to [Gigabyte MC62-G40 & Threadripper PRO 3945WX] and wanted to change my cache pool from [2x Samsung 850 EVO 250GB] to [Samsung NVME 970 EVO Plus 1TB]. The first part worked fine, but when I put the new board into the old case I remembered that I forgot to move the files from the cache to the array and had to put the old board in a different case because the new one hadn't enough SATA ports. That worked more or less fine. I then put my NVME drive into the new board and started it without the unraid USB stick and used the OS on it to migrate my data from the NVME to a new [Samsung 990 EVO Plus 4TB]. Then I put in the unraid USB stick again and replaced the two Sata SSDs with the NVME 1TB drive and started the array. I then saw that the previous OS and data was still on it, so I manually removed the files on it in the unraid GUI. Then I moved appdata, system and domains back on the new NVME 1TB which worked seemingly fine. But when I started the VM manager and Docker, and tried to bind my new 4TB NVME to my old VM (and change other things like core counts) it throw me an error that it couldn't write into libvirt. So I restarted and moved the files from the NVME back to the array and tried to format the NVME, moved the files back on it and tried again with the same error, I tried that a few more times and last I formated it with btrfs, moved the files on it again and now it is completely unavaible with the data on it and the following error: Cache shows: To summarize my hardware changes: From Asrock Rack EPC612D8A Xeon E5-2690 v4 8x16GB (128 GB) Ram Samsung NVME 970 EVO Plus 1TB (exclusively bound to VM) Cache: 2x Samsung 850 EVO Plus Several HDDs To Gigabyte MC62-G40 [https://www.gigabyte.com/de/Enterprise/Server-Motherboard/MC62-G40-rev-1x#Support-Manual] Threadripper PRO 3945WX [https://www.amd.com/en/support/downloads/drivers.html/processors/ryzen-threadripper-pro/ryzen-threadripper-pro-3000wx-series/amd-ryzen-threadripper-pro-3945wx.html] same 8x16GB Samsung M393A2G40EB1-CRC [https://semiconductor.samsung.com/dram/module/rdimm/m393a2g40eb1-crc/] Samsung 990 EVO Plus 4TB (to be bound exclusively to VM) Cache: Samsung NVME 970 EVO Plus 1TB Several HDDs Things I tried: changed in the bios "Power supply idle control" to "typical current idle" tried "tried btrfs rescue zero-log /dev/nvme1n1p1 waterline-sv-diagnostics-20251117-1916.zip
-
Temperature problems, Xeon E5-2690 v4 no thermal throttling
So, the problem seems to be, that the case fans stayed idle, like said before the fans were on [Smart Fan] and should have increased with the temperature. The CPU fan did, the rear and front ones didn't. Maybe they took the motherboard temperature as measure? Anyway, bought myself a fan hub (https://www.arctic.de/en/Case-Fan-Hub/ACFAN00175A) and used the CPU fan as indicator and now the case fans seem to rise in speed accordingly.
-
Temperature problems, Xeon E5-2690 v4 no thermal throttling
What is strange is, that unraid will notify me if disks are to hot, but my CPU can melt for all it cares. I only stumbled over it by chance. And shouldn't there be a blue screen if the temperarture reaches a critical level?
-
Temperature problems, Xeon E5-2690 v4 no thermal throttling
At 57°C the heat pipes and the fins feel hot to the touch. The room temperature is at 20-30°C, and there are is enough space in front and back of the case. I checked the bios and all fans were on [Smart Fan] (100% at 78°C), as the CPU fan seems to increase at load, I put all the case fans on [Full On]. It doesn't feel like they are on 100%. If I remember correctly than opening the case didn't effect the temperature much (+- 1-2°C). Using an online stress test (https://cpux.net/cpu-stress-test-online) in a VM: Closing the case increased the temperature from 69°C to 77°C. The case fans didn't seem to increase in speed, holding a small paper at the fan, the paper moves 10° maybe 15° angle. Hm, the VM uses 12 HTs (see picture) and does not increase the temperature in such a rapid way. Stash on the other hand uses 16 HTs (see the grey ones in the picture) and reaches critical temperature fast. It seems the case fans don't work as they should. Tried using pwmconfig: Found the following devices: hwmon0 is coretemp hwmon1 is nct6776 Found the following PWM controls: hwmon1/pwm1 current value: 127 hwmon1/pwm2 current value: 127 Giving the fans some time to reach full speed... Found the following fan sensors: hwmon1/fan1_input current speed: 0 ... skipping! hwmon1/fan2_input current speed: 0 ... skipping! There are no working fan sensors, all readings are 0. Make sure you have a 3-wire fan connected. You may also need to increase the fan divisors. So what can I do? Should I buy one of those fancy old school fan controller?
-
Temperature problems, Xeon E5-2690 v4 no thermal throttling
Hello! Everytime I integrate several scenes inside stash (https://github.com/stashapp/stash) my CPU temperature rises over 100 °C and slowly climbs higher until stash is done. The docker container uses CPU core 0-7 (and HT 14-21) up to 100% utilization. Shouldn't the CPU throttle when it gets to hot? Is it somehow possible to activate thermal throttling? The CPU fan seems to get louder, the case fans however don't seem to change, hard to judge. Is there a way to create a load, to stress test the CPU in unraid, so I can reproduce the temperature increase? Any good CPU cooler upgrade that is tolerable quiet, the NH-U12DX i4 doesn't seem to fit (3mm argh) and 2011-3 narrow ILM makes it hard to find something. Mainboard: Asrock Rack EPC612D8A (https://www.asrockrack.com/general/productdetail.asp?Model=EPC612D8A#Specifications) CPU: Intel® Xeon® CPU E5-2690 v4 @ 2.60GHz (https://www.intel.com/content/www/us/en/products/sku/91770/intel-xeon-processor-e52690-v4-35m-cache-2-60-ghz/specifications.html) CPU Cooler: Noctua NH-D9DX i4 3U (https://noctua.at/en/nh-d9dx-i4-3u) Chassis: Inter-Tech 4416 (https://www.inter-tech.de/en/products/ipc/storage-cases/4u-4416) Unraid: 6.10.0-rc4 Stash: 0.15.0 Fans: Noctua NF-R8 redux-1800 PWM (https://noctua.at/en/nf-r8-redux-1800-pwm) Noctua NF-R8 redux-1800 PWM (1 & 2 together via 4-Pin Y-Cable [https://noctua.at/en/na-syc1] on the same fan header) Noctua NF-S12B redux-1200 PWM (https://noctua.at/en/nf-s12b-redux-1200-pwm) Noctua NF-S12B redux-1200 PWM Noctua NF-S12B redux-1200 PWM (In use the chassis is closed.) waterline-sv-diagnostics-20220602-0342.zip
blkopler
Members
-
Joined
-
Last visited