kaiguy

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.

Upgrade went smooth! Great job Limetech team! Now in the process of transitioning unassigned devices to pools. Question -- I know there was a previous issue with SSDs and excessive writes with btrfs, so I switched all my SSDs to xfs a while back. I see that any new pool defaults to btrfs. Has the excessive writes issue been fixed? Is there any benefit to running btrfs on single SSD pools or should I stick with xfs? THANKS!

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?

Thanks, Sycotix, for setting up this template and providing your writeup. This was super helpful to get me up and running behind the LSIO Letsencrypt container. Just FYI, the section where you provide the maridadb command to add a user requires a semi colon at the end. It should be: CREATE USER 'authelia' IDENTIFIED by 'YOURPASSWORD'; After a bunch of issues likely related to my own misconfig, I took the configuration.yml down to its basics then added in the items I knew I'd need from the Authelia docs. That seemed to help get me going. DUO integration is working great, with totp as a backup. Since LSIO doesn't have much instruction on how to configure, it did take a while to figure out I needed to add this under the server block for its out-of-the-box Authelia support to work: server: path: authelia If others are going with the LSIO LE container, there's no need to utilize Authelia as its own subdomain reverse proxy.

I'm not seeing Authelia in CA... either by name or browsing under Security... was it pulled? Edit: I think it may be blacklisted in CA as seen here.

I have this motherboard and cpu combo, but was severely limited by case clearance. So I purchased a lower-profile Noctua that does an adequate job but still gets pretty darn hot at full load. If I could have chosen any cooler, I would have gone with the Noctua NH-D15.

2 weeks in for me on the L2.21A BIOS. No high temp warning yet (though I would bet money given everyone else getting the warning within the last few days I'm due for one). I'll be sure to comment here and let William know if/when it happens. Server has been fairly idle and its been pretty cool here in gneral lately, but that's the norm anyway so I doubt that's a factor.

I tried to make a switch from the non-GUI version to the GUI (pointed the config to the old appdata directory but started with a fresh container). It's running and working, but I can't access the GUI at all. Any suggestions? I manually added the port but nada.

Bummer, @Hoopster. I haven't ran into that yet, though I am a few days behind you since the BIOS update. I'm on the 1.80 BMC... Is there a 2.30 BMC, or are you thinking of the newer BIOS on their website that doesn't incorporate the QSV item?

No clue about the iOS app, but to install the preview, just change the repository in your container setting to "linuxserver/ombi:v4-preview" It's been working great for a while now.

Too soon to tell, but so far so good. I didn't get my first mobo temp warning for about 2 or 3 weeks after deployment.

Updated the BIOS to 2.21A this morning, then the BMC firmware to 1.80. BIOS did indeed revert the dual monitor setting, as well as my manual SmartFan settings. After BMC firmware was flashed, I had to go back into the hardware monitor in the BIOS to for the fans to kick back in. Rebooted back into unRAID, re-enabled the modprobe setting, and QS in Plex worked as expected. No issues as of yet to report.