tjb_altf4

Retested under RC2, still have 2 cores maxed. Fresh diagnostics attached before array and docker/vm services started, but experiencing the maxed 2 cores fortytwo-diagnostics-20201219-1459.zip

Still seeing two cores maxed, same as RC1.... otherwise no issues.

Bifurcation itself shouldn't cause a performance penalty, but sometimes the risers used to physically split the slots can bring a small penalty, or instability if it is of poor quality. Same sort of issues as seen when simply vertically mounting GPUs though risers etc. It should be noted bifurcation support is via bios and it is invisible to the OS other than the change to vfio grouping

Not in 6.9.0-rc1

Are you running a modern Intel system that natively support thunderbolt, or just using the add in card on something else? Because your board should have a header pin for TB and it should be connected? Without that TB can't reset the hardware.

I've only been able to get it working by deleting all including the database. The postgres database version changed and it's not backwards compatible.

Best to post in the support thread for the application you are using, that said I'd take a punt that your VPN provider is PIA and you now need to update your certs due to infrastructure changes on their end.

Click on the docker to bring up the context menu, then edit (template editor) Change repository to linuxserver/musicbrainz:v-2019-08-08-ls6 And hit apply. Like I said before, make sure you clean out your appdata folder for musicbrainz, the database version between latest and this tag are incompatible.

As the latest image is not working, you will need to use linuxserver/musicbrainz:v-2019-08-08-ls6 You will need to clear your appdata also

Uncovered a couple of issues that may be impacting me.... Looks like this might be a kernel bug that was introduced in kernel 5.6.8, when USB4 support was introduced. Unraid 6.8.3 which had kernel 4.19 did not have this issue. The bug report post description accurately describes the issue "Batch mode top showing high CPU usage by usb_hub_wq and pm" https://bugzilla.redhat.com/show_bug.cgi?id=1858291 Also looking at the output of dsmeg there are zenstates errors (I don't have zenstates added to go file) Is zenstates part of the kernel or the unraid OS now? [Tue Dec 15 08:18:54 2020] msr: Write to unrecognized MSR 0xc0010292 by zenstates Please report to [email protected] [Tue Dec 15 08:18:54 2020] msr: Write to unrecognized MSR 0xc0010292 by zenstates Please report to [email protected] [Tue Dec 15 08:18:54 2020] msr: Write to unrecognized MSR 0xc0010292 by zenstates Please report to [email protected] [Tue Dec 15 08:18:54 2020] msr: Write to unrecognized MSR 0xc0010292 by zenstates Please report to [email protected] [Tue Dec 15 08:18:54 2020] msr: Write to unrecognized MSR 0xc0010292 by zenstates Please report to [email protected] [Tue Dec 15 08:18:54 2020] msr: Write to unrecognized MSR 0xc0010292 by zenstates Please report to [email protected] [Tue Dec 15 08:18:54 2020] msr: Write to unrecognized MSR 0xc0010292 by zenstates Please report to [email protected] [Tue Dec 15 08:18:54 2020] msr: Write to unrecognized MSR 0xc0010292 by zenstates Please report to [email protected] [Tue Dec 15 08:18:54 2020] msr: Write to unrecognized MSR 0xc0010292 by zenstates Please report to [email protected] [Tue Dec 15 08:18:54 2020] msr: Write to unrecognized MSR 0xc0010292 by zenstates Please report to [email protected] Same issue reflected here, stating same issues with kernel 5.9.x https://github.com/r4m0n/ZenStates-Linux/issues/16

That was the JOINED date! 😛

FYI https://github.com/linuxserver/docker-musicbrainz/issues/86

Also 6.9.0-RC1 here. I was able to successfully update cache and cache 2 for those settings, I had previously set them in earlier releases, but this release had reset those settings.

I do have Tips and Tweaks installed, however the Governor is already set to On Demand.

Great plugin! Thanks for your effort! Would just request a future enhancement for a download meter of some kind, thats my only (minor) feedback

OK, with the array stopped, wireguard and shfs are not in use but kworkers are still hitting 2 cores at 100%

Sounds like its connected to a usb2 port, if the drive supports usb3 try and connect it to a usb3 port for better speeds.

@ich777 I've just moved to 6.9.0-rc1 and it looks like iSCSI support has been added to the unraid kernel. Is your iSCSI Target plugin still compatible with rc1, or should I wait for the new iSCSI GUI plugin to be complete?

Wireguard and SHFS seem to be the chewing the most (top)

Output: root@fortytwo:~# grep EN -r /sys/firmware/acpi/interrupts/ /sys/firmware/acpi/interrupts/ff_pwr_btn: 0 EN enabled unmasked /sys/firmware/acpi/interrupts/gpe08: 0 EN enabled unmasked /sys/firmware/acpi/interrupts/ff_gbl_lock: 0 EN enabled unmasked

Have opened a report with a fresh diagnostic

Changed Status to Closed

Diagnostics added for reference fortytwo-diagnostics-20201212-1352.zip

I've since uninstalled some plugins (docker folder, preclear, lsio unraid nvidia) and the issue has been resolved This was an upgrade from 6.8.3 to 6.9.0-rc1.