JorgeB

Sorry, cannot really help, never used Plex, maybe try posting in the appropriate docker support thread in the forum, or even the Plex forum, there might be some known issues with specific hardware.

Nothing obvious, enable the syslog server, it might catch more.

There's nothing relevant logged, since it's a Ryzen CPU did you already see this? https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=819173

No, there's no need to start in maintenance mode, after doing a new config there will be a checkbox with "parity is already valid" next to the array start button, just check that before first array start.

That's the regular syslog, it starts over after every reboot, we need the permanent syslog, it will be in the share it's set to save to, or just enable the mirror to flash option, then it will be saved in the flash drive, /logs folder.

I forgot that safe mode disables autostart, you can temporarily prevent all plugins from loading by going to /boot/config/plugins and renaming all *.pgg files to *bak for example, then reboot.

Cannot help with that since I've never used it but I believe it's a compressed file, you should be able to manually unpack to where you want, if not best to ask in the existing plugin support thread.

It is enabled: Nov 7 09:29:42 Biohazard-UR emhttpd: Autostart enabled Try rebooting in safe mode to rule out any plugin issues.

NVMe device dropped offline, you should add the line above.

Run a scrub on disks 22 and 23, others look OK for now.

It means the files are corrupt and btrfs prevents them from copying/moving so that you don't copy corrupt files without knowing.

Difficult to say just by that, you can enable the syslog server and post that if it happens again.

Not seeing any flash drive issues, do you see that warning right after boot?

https://forums.unraid.net/bug-reports/stable-releases/

You can, you can also replace one device at a time: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=480419

Please post the diagnostics.

Nov 6 12:46:58 unDOOT kernel: BTRFS info (device sdc1): bdev /dev/sdc1 errs: wr 0, rd 0, flush 0, corrupt 10, gen 0 Nov 6 12:46:58 unDOOT kernel: BTRFS info (device sdc1): bdev /dev/sdh1 errs: wr 0, rd 0, flush 0, corrupt 50, gen 0 Nov 6 12:46:58 unDOOT kernel: BTRFS info (device sdc1): bdev /dev/sdi1 errs: wr 0, rd 0, flush 0, corrupt 55, gen 0 Nov 6 12:46:58 unDOOT kernel: BTRFS info (device sdc1): bdev /dev/sdd1 errs: wr 0, rd 0, flush 0, corrupt 46, gen 0 Nov 6 12:46:58 unDOOT kernel: BTRFS info (device sdc1): bdev /dev/sde1 errs: wr 0, rd 0, flush 0, corrupt 14, gen 0 Nov 6 12:46:58 unDOOT kernel: BTRFS info (device sdc1): bdev /dev/sdg1 errs: wr 0, rd 0, flush 0, corrupt 20, gen 0 Data corruption detected on all members, Ryzen with overclocked RAM like you have is known to is some cases corrupt data, after correcting that run a scrub and delete/restore from backups any corrupt files, they will be listed in the syslog.

Nothing obvious in the log, but no check running now, run a test with the diskspeed docker to see if all disks are performing normally.

You can restore the data to the array, and then if needed change the mappings from /mnt/cache to /mnt/user

It's not the same issue, this thread is about users having the same call trace as described in the 1st post, and for this issue rolling back solves it.

See the tips and tweaks plugin, it has settings for that.

Correct, if you have all 3 replaced disks you can do a new config with them, since parity should be mostly valid you can check "parity is already valid" before array start but should then run a correcting check.

Yep, that's why I mentioned

It's working for me, please post the diagnostics.

After rebooting?