
Froberg
Members-
Posts
256 -
Joined
-
Last visited
Recent Profile Visitors
The recent visitors block is disabled and is not being shown to other users.
Froberg's Achievements
Contributor (5/14)
34
Reputation
-
Considering you already mentioned using mp3tag, just use that. It works beautifully when using audible for data.
-
[SUPPORT] DiamondPrecisionComputing - ALL IMAGES AND FILES
Froberg replied to biggiesize's topic in Docker Containers
Asking here if anyone's actually using it.. Genea was Updated on Mar 23, 2022 last.. doesn't exactly inspire confidence. The issue tracker doesn't appear to be getting responses. Abandonware, or? -
This sounds like my original issue, where the Noctua fans I had populated my case with were operating at too low RPM's, so the IPMI on the motherboard panicked and made them run full-bore - so the noise floor when up, down, up, down, up down.. irritating to say the least. I raised the minimum fan speed to a fairly high level, but considering it's Noctua fans they're still silent. That made the IPMI shut up. Maybe check if you have events in IPMI concerning fan errors that's how I clued in on mine.
-
Yep, that did it. Cheers!
-
Froberg started following [Plugin] IPMI for unRAID 6.1+ , [PLUGIN] IPMI for 6.11+ and BTFRS once again rearing it's ugly side
-
Read the release notes for 6.12. Uninstalled old plugin. Updated OS. Installed this. All settings and options blank pages. Tried uninstalling and re-installing a few times. Where to begin? Even my config you've asked for above seems much shorter. root@FortyTwo:~# cat /boot/config/plugins/ipmi/fan.cfg FANCONTROL="enable" FANPOLL="24" FANIP="" HDDPOLL="24" HDDIGNORE="" HARDDRIVES="enable" FAN_FAN1234="607" TEMP_FAN1234="4" TEMPHI_FAN1234="65" TEMPLO_FAN1234="50" FANMAX_FAN1234="80" FANMIN_FAN1234="39" FAN_FANA="875" TEMP_FANA="138" TEMPHI_FANA="65" TEMPLO_FANA="50" FANMAX_FANA="80" FANMIN_FANA="39" root@FortyTwo:~# Any advice?
-
So I woke up early this morning, had to go pee, checked my phone and UnRAID had notified me of corruption on my cache pool again. It's been a long while since I last had an issue with BTFRS - the proposed problem back then was my memory but I was never able to find any faults with it. Of course it has to happen the one time I'm away on vacation.. but that's just a law of nature at this point I built an entirely new server and everything seemed to be going OK, until today. I set up the userscript to monitor as recommended by JorgeB.. Output: root@FortyTwo:~# btrfs dev stats /mnt/cache [/dev/sdb1].write_io_errs 0 [/dev/sdb1].read_io_errs 0 [/dev/sdb1].flush_io_errs 0 [/dev/sdb1].corruption_errs 6 [/dev/sdb1].generation_errs 0 [/dev/sdc1].write_io_errs 0 [/dev/sdc1].read_io_errs 0 [/dev/sdc1].flush_io_errs 0 [/dev/sdc1].corruption_errs 8 [/dev/sdc1].generation_errs 0 Scrub didn't see anything: Which just seems.. odd. So as per Jorge's recommendations I used btrfs dev stats -z /mnt/cache and am now rebooting with my fingers crossed and my cheeks clenched. Please advise! fortytwo-diagnostics-20230301-0534-anon.zip
-
Works fine on my 'droid..
-
Can we send you a few $$$ yet? You've saved my daily commute, must contribute beer or coffee or just discretionary funds.
-
nerdtools, isn't that depreciated?
-
-
Yeah that works. Was worried about fan noise but raising the floor to 39 it remains silent under load.. so yay.
-
Hi guys I'm running a SuperMicro board and it doesn't like my Noctua fans, they run too slowly. I've adjusted the curves in the config file to 200,300,400 for lower thresholds - as recommended by SuperMicro themselves (if unsupported) but that just floods the system with fan-speed errors and makes them sound like they're starting and stopping constantly. As it is, I have to set it to "full speed" to not have fluctuations in noise levels. Not sure how to go about fixing this any more. Here's what SuperMicro wrote: IPMI FAN thresholds: Linux: $ sudo ipmitool sensor thresh FAN1 lower 200 300 400 Locating sensor record 'FAN1'... Setting sensor "FAN1" Lower Non-Recoverable threshold to 200.000 Setting sensor "FAN1" Lower Critical threshold to 300.000 Setting sensor "FAN1" Lower Non-Critical threshold to 400.000 $ sudo ipmitool sensor thresh FAN5 lower 200 300 400 Locating sensor record 'FAN5'... Setting sensor "FAN5" Lower Non-Recoverable threshold to 200.000 Setting sensor "FAN5" Lower Critical threshold to 300.000 Setting sensor "FAN5" Lower Non-Critical threshold to 400.000 Now as I said, I modified the FAN values I could find in the config and set the fan-profile in IPMI (SuperMicros own) to "standard" and it just kept start/stopping the fans. Please let me know if anyone has a solution to this, other than not using Noctua fans.
-
Yeah that did it. As a side effect I got dedicated IP working again so a better setup than before. Now it'll probably just run without problems for years again. 🙂 Edit: Spoke too soon. LetsEncrypt worked, but it seems not all is well. Favicon downloads, but yeah.. Guess I have some work left still Edit2: Forgot the docker network restrictions. All good now. Cheers.
-
So my certificate expired and everything stopped working.. I've just been ignoring NPM because it's just been.. working. I'm getting this error in the log: [12/16/2022] [11:23:54 PM] [Express ] › ⚠ warning Command failed: certbot certonly --config "/etc/letsencrypt.ini" --cert-name "npm-7" --agree-tos --authenticator webroot --email "xxxx" --preferred-challenges "dns,http" --domains "xxxx" Another instance of Certbot is already running. When attempting to request a new cert. "Internal error" in the webinterface. I'm unsure if I screwed something up when my server crashed and I had to restore from backup, shortly after which my ubiquiti setup imploded and I had to redo it from memory. Just found I had forwarded port 80 to the internal port 3000 for some reason. It's now this: I feel like I'm missing something glaringly obvious here, probably network related or docker-setting related, but the entire household is down with the plague so I'd greatly appreciate a helping hand so I can get access to my audiobooks back 😃 Thank you and appreciate it.
-
Does the container track any faults or errors in the logs? I find it changes state to "unhealthy" within a day and needs a restart to function again. I'm baffled as to what could be the cause.