flyize

And now it looks like it just got pulled

Well that's interesting!

I had a friend try a couple of months ago, but was not able to do so. IIRC, the UI would never load.

Gotcha. Is it safe to assume that 6.11 RCx is probably months away?

Anyone know if we were able to package up the intel non-free driver, if that would help the situation? This guy here talks about using it with the 5.15 kernel. @ich777 Would you have any ideas if that is possible, or would help?

According to this, its 5.18 I kinda almost regret picking up an Alder Lake at this point. 😅 https://forums.plex.tv/t/plex-media-server-on-ubuntu-21-10-with-intel-12th-gen-alder-lake/768123/30

Mine still crashed.

Then I'd like to update the wiki to something like: For best performance, make sure there are no reads/writes happening to the array. The easiest way to do this is to bring the array up in maintenance mode. Does that make sense? Had *I* known that, I'd have already had the old drive removed and the new drive replaced days ago.

The array was online and mounted (except the drive I was zeroing out). There isn't any mention that the array shouldn't be mounted in the wiki. Should there be?

Yeah, I started to attempt your suggestion which is why the array was stopped. The drive I'm removing isn't SMR. However, with the array in maintenance mode, I'm getting 182MB/s. That will do. Thanks!

I had that specific drive unmounted (that's what the advanced section of the wiki says to do). Just in case, here are diagnostics. truffle-diagnostics-20220419-1020.zip

I have reconstruct write enabled, and am doing it manually. However, the array isn't in maintenance mode. Could that be the actual issue?

Following the writeup here: https://wiki.unraid.net/Shrink_array Using dd to zero out the drive and its writing at about 1.1MB/s. At that rate, it seems the process will complete sometime around the fall of humanity. Am I doing something wrong?

It for sure doesn't work with tone mapping enabled (thats apparently an ICR issue). But either way, you can expect more lockups.

Nice find. I'm glad they found the issue, but that does NOT sound like a fix will happen soon. #FML

I wish you the best of luck @Cajones, but I don't think it will be stable.

Except from what I'm reading, there seems to be a good chance that 5.16 alone will not fix the issue.

I suppose so. Honestly, when I bought it I had no idea how much trouble I'd have with it. I've probably built 20+ computers at this point and never had an OS support issue with a processor. New territory for me...

Mine is measured in hours. Not sure if it makes a difference, but my Plex server is pretty heavily used.

Generally unstable, even with tone mapping off.

It works. Until it crashes (in my case, no more than 24 hours). I've been monitoring this intently and don't think I've seen it work long term for anyone. I'd love to be wrong though!

I see you quoted a post from someone with an Alder Lake CPU. If you have one of those, QS just isn't going to work with Plex yet, no matter what you do.,

Yeah. Coming from an old Xeon, I was hoping to future proof myself, but I somewhat regret the Alder Lake purchase.

I keep seeing these repeated a couple times a day. Feb 7 02:53:43 Truffle nginx: 2022/02/07 02:53:43 [error] 11093#11093: *1932704 open() "/usr/local/emhttp/stub_status" failed (2: No such file or directory), client: 127.0.0.1, server: localhost, request: "GET /stub_status HTTP/1.1", host: "localhost" Feb 7 02:53:44 Truffle nginx: 2022/02/07 02:53:44 [error] 11093#11093: *1932706 open() "/usr/local/emhttp/server-status" failed (2: No such file or directory), client: 127.0.0.1, server: localhost, request: "GET /server-status?auto HTTP/1.1", host: "localhost" Feb 7 02:54:04 Truffle nginx: 2022/02/07 02:54:04 [error] 11093#11093: *1932884 open() "/usr/local/emhttp/server-status" failed (2: No such file or directory), client: 127.0.0.1, server: localhost, request: "GET /server-status?auto HTTP/1.1", host: "localhost" Feb 7 02:54:05 Truffle nginx: 2022/02/07 02:54:05 [error] 11093#11093: *1932891 open() "/usr/local/emhttp/us" failed (2: No such file or directory), client: 127.0.0.1, server: localhost, request: "GET /us HTTP/1.1", host: "localhost" Feb 7 02:54:05 Truffle nginx: 2022/02/07 02:54:05 [error] 11093#11093: *1932897 open() "/usr/local/emhttp/server-status" failed (2: No such file or directory), client: 127.0.0.1, server: localhost, request: "GET /server-status?format=plain HTTP/1.1", host: "localhost" Feb 7 02:54:05 Truffle nginx: 2022/02/07 02:54:05 [error] 11093#11093: *1932905 open() "/usr/local/emhttp/status" failed (2: No such file or directory), client: 127.0.0.1, server: localhost, request: "GET /status?full&json HTTP/1.1", host: "localhost" Feb 7 02:54:05 Truffle nginx: 2022/02/07 02:54:05 [error] 11093#11093: *1932915 open() "/usr/local/emhttp/server-status" failed (2: No such file or directory), client: 127.0.0.1, server: localhost, request: "GET /server-status?auto HTTP/1.1", host: "localhost" Feb 7 02:54:05 Truffle nginx: 2022/02/07 02:54:05 [error] 11093#11093: *1932928 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 127.0.0.1, server: localhost, request: "GET /admin/api.php?version HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "localhost" Feb 7 02:54:14 Truffle nginx: 2022/02/07 02:54:14 [error] 11093#11093: *1933000 open() "/usr/local/emhttp/stub_status" failed (2: No such file or directory), client: 127.0.0.1, server: localhost, request: "GET /stub_status HTTP/1.1", host: "localhost" Feb 7 02:54:14 Truffle nginx: 2022/02/07 02:54:14 [error] 11093#11093: *1933007 open() "/usr/local/emhttp/status" failed (2: No such file or directory), client: 127.0.0.1, server: localhost, request: "GET /status HTTP/1.1", host: "localhost" Feb 7 02:54:14 Truffle nginx: 2022/02/07 02:54:14 [error] 11093#11093: *1933014 open() "/usr/local/emhttp/status" failed (2: No such file or directory), client: 127.0.0.1, server: localhost, request: "GET /status?full&json HTTP/1.1", host: "localhost"