gyrene2083

Hello, @ack0049 I actually checked my scripts, and apparently, I don't have it running. But here is what my setup on this mobo looks like. I made some changes to the BMC fan control a while back, and so far it seems to be working. Here's a screenshot of what I have. Here are my fan speeds right now. FAN1 are my two rear fans, and FAN3 are my Noctua NF-A4x20 fans (2). I have blowing on my nvme. I hope this helps.

I couldn't figure it out. I thought I had it working, but didn't I ended up just using an ipmi script to control the fans.

This would be cool to compare to what I did. I just installed 7 beta 4 on Proxmox late last night. Considering I have no idea what I'm doing, I managed to figure it out. I wish you look and look forward to your write up.

Also, real quick. Going back to the docker.img, then can I delete those .legacy files from the system folder?

Thank you for responding and your patience. I just worked so hard on learning how to use compose, and I learned some so it wasn't a failure and there is no easy way to go back to the compose image other than inputting everything manually correct?

So, I could either update to the beta or move everything off the cache, reformat and copy everything back. I just want to make sure I understand before I do anything. I appreciate the help and suggestions you may have.

I know this thread is a year old, but I done something similar. I moved everything to portainer, formatted my cache to zfs and have several of these legacy files now on my system folder with snapshots I never created. My question is can those files be deleted? if not do I have to go back to docker.img? or can as you suggested can I just copy my folders back to the array and format to xfs with in zfs? If this is a route I can take, how would I format xfs in zfs?

So the question I would ask is how long is the nvme going to last with the constant writing, and should moving the cache to a hdd help.

I to would like to know if this is still the way to go as I just saw my cache being written to non stop.

So I figured it out thanks to a post by @hathi_ndg Fix for Hotio Containers with not available Thanks so much for all the help I hope this helps other people.

Thank you for the response, I ran the command from the log file (e2fsck) and cleared those errors. Or at least they aren't showing up in the disk log, but I am seeing this though: Aug 26 16:25:28 Tsunade unassigned.devices: Mount of 'nvme2n1p3' failed: 'mount: /mnt/disks/S467NX0M705964T-part3: unknown filesystem type 'LVM2_member'. dmesg(1) may have more information after failed mount system call.' Also, would you have an idea of how I could fix the 'not available' in the prowlarr app in Docker? Thank you so much.

Good Afternoon. I updated to 6.12.13 last night and noticed, (This could have been there before and I never noticed) a red star on the button bar. I tried to hover over it but nothing happened, I was on Chrome. I then opened Firefox and tried there and it said incorrect autostart order. I then looked up what that was and tried to move things around as suggested in a post I read. That didn't work. Then I noticed that I had a few docker apps with broken links. I remember on 6.11.* there was an issue and you needed to install Docker Patch, but that was just for 6.11.*. So I started to read more threads and before I started trying what I was reading I wanted to just come and ask for help before I started doing anything. By the way, while creating the diagnostic log, I just saw that there is a nvme error. Is it possible to explain that error to me, as I have no idea what it means. I appreciate any and all help. tsunade-diagnostics-20240826-1411.zip

Thanks for that, this is just to test it out. I thought I was doing something wrong. I'm actually going to use my desktop that is a Threadripper with 128gb Ram, and it has a nvidia 3090 w 24gb VRam. With a spare 2TB NVME.

Thanks for this curious though is there anyway to speed up responses?

@Nightshade So, I kind of got it to run, what I did was take the exhaust fan of the Noctua NH-U9 TR4-SP3, and placed that on CPU0-fan, then I placed the intake fan of the Noctua NH-U9 TR4-SP3, and placed that on FAN2. I made the following policy; So what I gathered was the Reference is the Temp, and the Duty% is the fan speed. So for the example above I have CPU0 Fan to the exhaust and Fan2 Fan the intake of the CPU, I also added Fan1 as the exhaust of the chassis in this Profile. In the Policy Reference Table it's saying if the temp (Reference 0) reaches 25C then set the fan (Duty%) to 50 percent and so on and so on. Before I figured this out, I was getting the CPU with a fan speed of 150rpm, right now it's a 1050rpm. (see below) As you can see, CPU0_FAN, SYS_FAN1, SYS_FAN2, are the Exhaust CPU cooler, Exhaust Chassis Fans, and Intake CPU cooler, respectively. I hope this helps you understand it a little better. Now I haven't been able to figure out how to get Fan 4 & 5 work off the HD temps. I haven't had success in trying to create another Fan profile run together. If there is anyone that knows how to use the BMC management please, I would appreciate all help.