kaiguy
Members
-
Joined
-
Last visited
Everything posted by kaiguy
-
This board has a reputation of erroneous motherboard temp readings. I pretty much am always rocking an 80+ mobo temp via IPMI.
-
Not directed to me, but I can share my experience with this CPU. It runs hot. Airflow and HSF will play a big role in keeping temps down, but this processor just has a high TDP. Even an idle Windows 10 VM seems to raise my overall CPU utilization by 5-15%, which subsequently increases temps. Using the best HSF that your case can support would be my recommendation. I was limited by case clearance so the HSF I use is a little small for my liking, but still does an admiral job. Personally I wouldn’t be concerned with the temp you mentioned just based on my own averages. I think an item that would be more meaningful is what are your temps at full load?
-
Truth be told I'm not 100% sure if this is due to 6.9.x, but the issues did start when I upgraded so I figured I'd give it a shot in here. Prior to 6.9.x, I had zero locks since deploying my current hardware from a year ago. The only material config change since the upgrade was that I began using my nvme drive as my primary cache drive, whereas before it was sitting idle in my server via unassigned devices. Also I no longer use unassigned devices but single- and multi-disk pools. At least one of the prior locks showed a CPU_CATERR event via my IPMI, but the last one did not (the forum thread on my motherboard had others running into this with prior BIOS versions and Intel Turbo Boost enabled, but I never experienced it). I just lost all connectivity and was unable to access the system via IPMI remote control. After one of the prior locks, I began running a local syslog server on the unraid server. This is what was captured prior to the lock: https://pastebin.com/raw/afA6Wd5a The only thing that stands out to me is CPU tainted errors. It does look like something similar happened earlier in the day, but the system continued to function. When this lock occurred, I believe there was writes occurring to the cache drive. I have since disabled turbo boost in the Tips and Tweaks plugin, and removed some plugins that are not commonly used. Diagnostics attached. titan-diagnostics-20210311-1331.zip
-
Welp, after a couple days of success, it looks like I got another hard lock. I setup a syslog server (back to unraid) so I think I was able to capture some stuff, but I don't really know how to read this aside from noticing that I have a bunch of kernel warnings about the CPU being tainted. Anyone here have more experience reading this type of logging? Looks like something similar happened earlier in the day (but the server was still up), then it happened again and took everything down. I think. https://pastebin.com/raw/afA6Wd5a I have since disabled turbo boost. I should probably run a memtest (even though its ECC), but I think that means I need to disable EFI boot as when I try at bootup it just does a reboot. Ugh. Everything was running so smoothly for me before updating to 6.9.0/6.9.1... Edit: Well, disabling turbo boost seems to have helped--no system locks since. Crazy how this was something others experienced with older BIOS versions and I never did. Then with the upgrade to 6.9.x, I'm suddenly getting it. It probably has nothing to do with it, but I decided to remove the graphite thermal pad I was using and replaced it with Arctic MX-5 compound. Going to run the system a few more days with turbo boost disabled then try re-enabling it. My thought process is one of the cores may have not been getting enough contact with the pad and that may have been causing my lockups. Complete guess, but I'm going with it.
-
@Hoopster I have a few VMs but by default they aren't running. I have had my system on Power Save and Turbo Boost since I started using this mobo. I also think the lock happened during the mover process, and the only change is I started using an nvme for my cache instead of one of my SSDs when I switched to 6.9.0, so in retrospect perhaps that's the culprit. In Performance, the CPU is at max freq the whole time, right? Think that's a material increase in power consumption? Heat?
-
Are you still running with Turbo Boost disabled, @Hoopster? I never had to disable it before, but I wonder if I'm not being plagued with that system lock. Running a grep MHz /proc/cpuinfo while the system is running a parity check from the system lock results in cpu MHz : 3500.338 cpu MHz : 3500.505 cpu MHz : 3500.004 cpu MHz : 3500.169 cpu MHz : 3500.220 cpu MHz : 3500.430 cpu MHz : 3500.135 cpu MHz : 3499.397 cpu MHz : 3499.443 cpu MHz : 3500.380 cpu MHz : 3500.302 cpu MHz : 3502.510 cpu MHz : 3500.185 cpu MHz : 3500.332 cpu MHz : 3500.376 cpu MHz : 3500.164 but as I recall it was showing similar frequencies when idle... not sure if its normal for it to be at such a high freq all the time. Hoping for no more locks, but I'm not confident.
-
Well, at 4:11am this morning my server had its first hard lockup. I am not home but VPN'd in via my router and saw that IPMI logged a Run-time Critical Stop. Nothing has changed with my hardware setup, so I have to assume something has changed with 6.9.0 that has exposed some instabilities with my system. So strange. Hopefully no one else starts experiencing issues.
-
After not encountering it since pretty much the first few weeks of building this new server, I got the IPMI motherboard temp warning tonight. I didn't realize this was still a thing. Running the latest L2.34 BIOS. Are others still getting this from time to time?
-
Upgraded to 6.9.0 recently. Changed around some of my SSDs/nvme uses, and started using single-disk pools instead of unassigned devices. Decided to just run a test on my nvme, which is now my cache drive (formatted XFS with the new 1MB offset). The result was really disappointing compared to when I first ran a test. A follow-up test showed a similar curve. My other SSD drives are fairly consistent with prior tests, albeit slightly slower (about 40MB/s). There is data on the nvme now compared to when I first ran the test, and a trim did run this morning, but this is not an expected result, right? Any suggestions on what I can do to troubleshoot? Could this be a result of 6.9.0? Thanks for any insight!
-
Yeah, the onboard GPU for Intel QuickSync.
-
I went ahead and removed the items from my "go" file after performing the "touch" command to enable the driver. All working fine. Anecdotally, hardware transcoding seems to be using more CPU than I remember, but I think I could easily just not be remembering correctly 😂
-
Just upgraded to 6.9.0 and I'm noticing this as well. All disks are set to use the default delay, and the default delay is set for 30 minutes. Disks do not spin down.
-
You're absolutely right. I don't remember seeing that, but it was enabled. Maybe I need to stop multitasking when I'm doing server maintenance. Also took your lead and disabled inventory. Everything running smoothly.
-
Hey Hoop, was that the exact wording for you? Truth be told I think mine still said onboard.
-
What a coincidence. I too upgraded today. I wasn't running into any problems--just my standard need to run the latest and greatest. Only 5ish hours of uptime but all seems to be going well so far. Aside from having to re-enable the onboard graphics item, I don't think I had to make any other config changes. One BIOS setting I never noticed before but did exist in the 2.21 BIOS is a setting for HDD or SDD for onboard SATA disks. Anyone know what the purpose of that is?
-
Thanks for sharing. I'm still on L2.21A as its been running great for me, but I've been itching to update for no particular reason. Curious to hear if anyone notices any improvements. Edit: I should ask, did they tell you if it supports iGPU, unlike their public BIOS?
-
Hey @Hoopster. I've been running into a lot of random issues with my wifi lately, and I wonder if it may be due to me being on the 6.x version. To you knowledge, am I able to roll-back to 5.14.23, regardless of what AP firmware I'm running (likely latest as well)? I have a backup in the Unifi controller from late August, and an overall appdata backup from September, but truth be told I have no clue what version I was on at that time... looking at the linuxserver github, I think they didn't start rolling 6.x until mid-September, so perhaps I could find a good backup...
-
For what it’s worth, I have never disabled turbo boost and have not had a hang. Granted though I rarely ever hit anywhere close to my CPU Max. But I have put it through some stress tests though without issue (Folding, for example).
-
Thanks for sharing the link to this bios, int2e! I take it you received this directly from William? Any idea what has been fixed/changed?
-
@realdiel Yep, that links looks good still for QSV setup. I also have the chmod in my "go" file but I also recall reading its redundant. In any case, I kept it in mine.
-
Weird, right? I can't seem to figure out why that started happening. Everything log-wise is fine on my end and nothing seems to be out of the norm. Oh well--guess it doesn't matter. Knock on wood, I haven't ran into the CPU_CATERR issue yet, though my server is pretty darn idle overall with QSV enabled. But seeing how everyone is running into this, I'm sure I'll get it on my next parity check.
-
I'd be super interested in getting more information about failover. Aside from a brief explanation in the first video I haven't found any other references to it. I'm specifically curious about: Are the configurations identical (e.g., did you take a backup from the primary pfsense instance and restore it on the failover device (obviously updating the interface assignments to WAN and LAN)? Have all the extra packages installed? Does it require any different configurations of the network setup? For example, do devices on the network complain when the switchover occurs since DHCP assignments may get wonky? Does it require a different gateway? Does the changeover require physically changing the modem network cable to the physical box, or do you have something going on with the switch to assign it its own VLAN? If anyone can shed some light, that would be outstanding! Thanks!
-
Their wording of the free trial is odd since they have DUO Free (see their pricing comparison). I have been on DUO Free for Bitwarden for over a year now. Works great.
-
Thanks for your reply, @Hoopster. Yeah, it does seem strange. BMC/IPMI seems fine--just accessed the HTML5 client--no problems. Server is up and running and working as expected. This is actually the 2nd time I've heard the 5 beeps at boot, so I don't think it was a fluke. Considering everything else seems fine, I'm tempted to just let this one go for now. I don't reboot often, and I can't seem to find any negative side effects. Curious if others have had this 5-beep deal. Edit: Ok, I rebooted to pop into the BIOS. No 5 beeps. Super odd. I looked at the BIOS error log as well, and the only thing it complained about was no keyboard over the past 6 or so boots (maybe it didn't beep this time since I was actively in an IPMI remote KVM and thus there was a virtual keyboard?). When I exited saving changes, again, no beeps. Shrug! Edit2: Happened again on a reboot. I wonder if its only during reboot and not a full power down.
-
Hi all. I noticed today upon reboot that I got a 5-beep warning during POST. I believe that is just letting me know that it's running headless, but I don't recall ever hearing that before. Am I going crazy and it's always been there, or is this something I need to start investigating?
