kaiguy

I would volunteer as tribute to test this, but I'm currently running a preclear. Sorry guys.

Not a support need, per se, but curious if anyone has tried bypassing http auth on local network(s). I tried modifying the proxy-confs to accomplish this, but I haven't been able to get this to work. Not sure if I'm doing something wrong, or if it just doesn't work with reverse proxy for some reason. location / { satisfy any; # bypass http auth for local IPs allow 192.168.0.0/24; allow 172.18.0.0/16; deny all; # enable the next two lines for http auth auth_basic "Restricted"; auth_basic_user_file /config/nginx/.htpasswd; ...

Thanks, @Hoopster, for taking the plunge and finding out about the iGPU. I'm going to hold off on updating. Also appreciate your letting us know that all the settings reverted. I have static a DHCP address set on my router for the IPMI MAC, so luckily it would have still worked for me with the same IP. I'm going to hold off for the next revision, however.

William was nice enough to email me as well asking me to update and keep him informed. I'm really impressed with his support! Edit: I wonder what order we should update (BMC vs. BIOS). Did you get any indication that the additional features from the beta BIOS made its way into this one? I'd hate to lose QS.

While I'm sure one of you would have posted about it if you did, I figured I'd check in to see if anyone has heard anything from ASRock... If the two previous times it happened to me is any indication (about 20 days apart), I'm due for another high temp warning here in a couple of days...

Glad to hear it. Does it really matter, though, since the ASRock IPMI shows that high temp as well?

Thanks for making those reports. William didn't indicate any concern when I contacted him. Hopefully we'll get some action now!

Both times I've gotten the temp warning my server was idle, so I'm pretty sure load has nothing to do with it.

Considering just about all of us with this board here have experienced this, I'm surprised ASRock wasn't aware of this already.

Yeah, I figured the BIOS wasn't going to fix it since you've been on it since day one. If you have some time, can you maybe let ASRock know? He wanted me to update him if I get it again, and perhaps having more users reporting this MB temp issue would be helpful to get a solution...

@Hoopster That's a much more informative response than I got from Noctua when I asked about the CPU and cooler. I have seen temps in the 80s, but it never got above 85. That's with a thermal pad and not paste.

I flashed via html5 IPMI interface (firmware update, as Hoopster pointed out). It was pretty simple, though there were some times I thought it hung.

Update on the high MB temp. ASRock suggested I update to the latest BMC firmware. I was actually surprised I didn't already update it--for some reason I thought I was on the latest version. In any case, I'm now on P1.60. We shall see if this addresses this issue. @Hoopster and @Burizado, are you both on P1.60? If so, I doubt this is a fix.

Got another motherboard temperature warning tonight... my second. Server wasn't doing anything. I'm debating disabling the MB temp sensor in IPMI because I can't imagine that's an accurate reading. But I'm going to email ASRock tomorrow and ask about this being a known issue before I do that.

When you install a container, a user template is created under /boot/config/plugins/DockerMan/templates-user ... you can try deleting the "my-plex.xml" file before reinstalling. That could be what you're running in to?

If you read back into this topic, both Hoopster and I have experienced IPMI reporting ridiculously high mobo temps. The one time it happened to me I rebooted and it returned to normal, and I haven't encountered it since. My guess was it was a stuck sensor, but not sure. Looks like this is not uncommon with this mobo...

Thanks for sharing, @Hoopster. One thing I did with the ipmi plugin for my fans pulling air across the hard drives (and into the case)... I do have it linked to HDD temp, but I set the minimum percentage to a higher level (currently 70%, since my Noctua fans are pretty darn quiet). That way I'm always getting adequate airflow into the case, and only bump it up to above 70% when the HDDs need additional cooling. So far I've found this to be the best balance for my case and temps.

@Burizado yeah, it’s 50% of RAM. Re: LAN ports, I have not, and everything I’ve read is it’s not worth the hassle. Too many complications for extra bandwidth that’s not needed 98% of the time. Not saying you shouldn’t try, but I’ve never felt the need to. My drives don’t exceed gigabit anyway—even my SSDs.

@Hoopster Sure thing. I've attached it since it's pretty big. I did not setup the GUI link within the container setup yet, so I just manually go to my IP:port. Edit: Yes, I did passthrough the GPU, but I'm not entirely sure Rosetta is using GPU at this point.

@Hoopster I saw that you were experiencing lockups. I can't speak to the original container, but I manually installed the new linuxserver boinc and ran it all last night on 4 cores/8 threads. Luckily no lockups for me so far (knock on wood). I did do the pinning and the recommended settings, as well as setting some manual processor limitations within the app. Maybe try the new container? This is me right now:

@Burizado Glad you got it sorted! Personally I switched from /tmp to /dev/shm for transcodes only because with 64GB I can't imagine needing more than 32GB of transcode space. Still not sure what best practice is (it used to be /tmp), but its been working well for me. Curious, how are your temps with your bigger Noctua tower cooler? My CPU temps seem to bounce all over the place. Idle in the lower 30s, but under any load it jumps around between 40-80C. Could be my smaller cooler, or the fact I used a thermal pad instead of paste. Or maybe because I have Smart Fan Control for most of the fans. But I'm interested to get some more datapoints on this processor. Thanks!

v4-preview branch working for anyone else? Mine seems to have bombed out in the last few days. Tried starting fresh and still getting an sqlite error 14.

Similar to this user, I did need to change the setting from auto to onboard graphics.

Everything has been smooth sailing here! Digging this setup knowing I have the power when needed, but even with multiple Plex transcodes and QSV, the CPU sits pretty idle the majority of the time. Only two items that have stumped me so far: 1. The mobo temp stays very consistent in the mid 20C-range. However yesterday I got a notification of critical temp, and saw that IPMI was reporting the mobo temp at 87C degrees. The server was completely idle, CPU temp was 31C, and the fans were operating as normal (which I have set to be operating at 75% of full speed at a minimum. Had to reboot the server to correct and haven't seen the same since. Stuck sensor, maybe? 2. Despite having IPMI plugged in via its dedicated port, I am not able to access the HTML5 IPMI GUI from the server itself (when at work I utilize Guacamole to RDP to a Win 10 VM or Firefox container). Not a showstopper since I can connect via openvpn to my router if needed, but it is odd. I thought that would only be an issue with a shared LAN/IPMI port.

@Burizado Thanks! Yep, I contacted ASRock after I bought the combo to request the beta BIOS. They replied fairly quickly with a link to download. Also, while not directed to me, both VT-x and VT-d were enabled by default in the BIOS. The problem I made was configuring the BIOS first then flashing. Some of the settings didn't seem to stick (explicitly enablling the onboard graphics, for example). I'd recommend flashing first thing, then configuring. Flashing is super simple. Throw the binary onto a flash drive, plug it in, and select the option for Instant Flash during POST.