Addy

Interesting to make something mandatory on my server.. but here we are. is anything relating to share access, dockers or VM's likely to break once I do this? How can I change the root password in SSH? Since I no longer can access the gui? I can't seem to find info on it figured it out (its passwd in terminal for anyone that may stumble)

Hey, wondering if I can get some help with below I updated from 6.9.1 to the latest version, 6.12 - update seemed to have gone smoothly, but I get a login prompt when I go to the GUI via browser.. can someone help me understand how I login to it.. root & blank doesn't work, I know this is my root password because I never updated it and I can still access SSH with it.. but the form on the login seems to require a password? I fail to also understand why I'm being asked to login to a local server, which I never enabled a login to also... I guess it came with the update. I also checked passwd and root:x:0:0:Console and webGui login account:/root:/bin/bash so root is the login, but it doesn't have a password - I'd also rather not create one, I can see this breaking things?

having a interesting issue, ------------------------------------- _ () | | ___ _ __ | | / __| | | / \ | | \__ \ | | | () | |_| |___/ |_| \__/ Brought to you by linuxserver.io ------------------------------------- To support the app dev(s) visit: Sonarr: https://sonarr.tv/donate To support LSIO projects visit: https://www.linuxserver.io/donate/ ------------------------------------- GID/UID ------------------------------------- User uid: 99 User gid: 99 ------------------------------------- [custom-init] No custom files found, skipping... * Assertion at gc.c:1005, condition `is_ok (error)' not met, function:mono_gc_init_finalizer_thread, Couldn't create thread. Error 0x0 assembly:<unknown assembly> type:<unknown type> member:(null) ================================================================= Native Crash Reporting ================================================================= Got a SIGABRT while executing native code. This usually indicates a fatal error in the mono runtime or one of the native libraries used by your application. ================================================================= ================================================================= Native stacktrace: ================================================================= 0x562d25484ffb - mono : 0x562d2548538d - mono : 0x562d25432087 - mono : 0x562d2548457c - mono : 0x1504fcc72520 - /lib/x86_64-linux-gnu/libc.so.6 : 0x1504fccc6a7c - /lib/x86_64-linux-gnu/libc.so.6 : pthread_kill 0x1504fcc72476 - /lib/x86_64-linux-gnu/libc.so.6 : raise 0x1504fcc587f3 - /lib/x86_64-linux-gnu/libc.so.6 : abort 0x562d253f43c4 - mono : 0x562d256d9135 - mono : 0x562d256f65be - mono : 0x562d256f6c73 - mono : monoeg_assertion_message 0x562d25673f08 - mono : 0x562d255619f6 - mono : 0x562d253f7047 - mono : 0x562d254057b6 - mono : mono_main 0x562d253f44df - mono : 0x1504fcc59d90 - /lib/x86_64-linux-gnu/libc.so.6 : 0x1504fcc59e40 - /lib/x86_64-linux-gnu/libc.so.6 : __libc_start_main 0x562d253f4b1e - mono : _start ================================================================= Telemetry Dumper: ================================================================= Entering thread summarizer pause from 0x23111170584704x Finished thread summarizer pause from 0x23111170584704x. Failed to create breadcrumb file (null)/crash_hash_0x0 Waiting for dumping threads to resume ================================================================= External Debugger Dump: ================================================================= mono_gdb_render_native_backtraces not supported on this platform, unable to find gdb or lldb ================================================================= Basic Fault Address Reporting ================================================================= Memory around native instruction pointer (0x1504fccc6a7c):0x1504fccc6a6c 05 00 44 89 e2 89 ee 89 c7 b8 ea 00 00 00 0f 05 ..D............. 0x1504fccc6a7c 41 89 c5 41 f7 dd 3d 00 f0 ff ff b8 00 00 00 00 A..A..=......... 0x1504fccc6a8c 44 0f 46 e8 e9 6d ff ff ff 0f 1f 00 48 89 ef e8 D.F..m......H... 0x1504fccc6a9c 10 a8 ff ff e9 29 ff ff ff 0f 1f 00 48 89 ef e8 .....)......H... ================================================================= Managed Stacktrace: ================================================================= ================================================================= * Assertion at gc.c:1005, condition `is_ok (error)' not met, function:mono_gc_init_finalizer_thread, Couldn't create thread. Error 0x0 assembly:<unknown assembly> type:<unknown type> member:(null) found a fix here, but I don't know how to use docker compose.. Rolled back to binhex/arch-sonarr:3.0.9.1549-1-01 and working fine, I am guess its an issue with the release as linuxserver's also has this problem?

yes adding it manually works, until the container updates and nukes itself. Can the template be fixed to include this?

also required

Hey guys, I have been using this forever, but it stopped working in the last week. This is the log ___. .__ .__ \_ |__ |__| ____ | |__ ____ ___ ___ | __ \| |/ \| | \_/ __ \\ \/ / | \_\ \ | | \ Y \ ___/ > < |___ /__|___| /___| /\___ >__/\_ \ \/ \/ \/ \/ \/ https://hub.docker.com/u/binhex/ 2022-09-20 11:38:27.952087 [info] Host is running unRAID 2022-09-20 11:38:28.646084 [info] System information Linux b145c01db624 5.10.21-Unraid #1 SMP Sun Mar 7 13:39:02 PST 2021 x86_64 GNU/Linux 2022-09-20 11:38:29.539366 [info] OS_ARCH defined as 'x86-64' 2022-09-20 11:38:30.777404 [info] PUID defined as '99' 2022-09-20 11:38:32.657967 [info] PGID defined as '100' 2022-09-20 11:38:51.489580 [info] UMASK defined as '000' 2022-09-20 11:38:51.528883 [info] Permissions already set for '/config' 2022-09-20 11:38:53.063372 [info] Deleting files in /tmp (non recursive)... 2022-09-20 11:38:53.847467 [info] SCAN_ON_BOOT defined as 'Yes' 2022-09-20 11:38:53.877272 [info] SCHEDULE_SCAN_DAYS defined as '06' 2022-09-20 11:38:53.907330 [info] SCHEDULE_SCAN_HOURS defined as '02' 2022-09-20 11:38:54.050392 [info] Starting Supervisor... 2022-09-20 11:40:16,300 INFO Included extra file "/etc/supervisor/conf.d/minidlna.conf" during parsing 2022-09-20 11:40:16,301 INFO Set uid to user 0 succeeded 2022-09-20 11:40:17,122 INFO supervisord started with pid 6 2022-09-20 11:40:18,124 INFO spawned: 'crond' with pid 72 2022-09-20 11:40:18,126 INFO spawned: 'start' with pid 73 2022-09-20 11:40:18,127 INFO reaped unknown pid 7 (exit status 0) 2022-09-20 11:40:18,134 DEBG 'start' stdout output: [info] PID file from previous run found, deleting file /home/nobody/.config/minidlna/minidlna.pid... 2022-09-20 11:40:18,134 INFO success: start entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2022-09-20 11:40:19,135 INFO success: crond entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2022-09-20 11:40:51,153 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 22775648492304 for <Subprocess at 22775648487024 with name start in state RUNNING> (stdout)> 2022-09-20 11:40:51,153 DEBG fd 15 closed, stopped monitoring <POutputDispatcher at 22775648492352 for <Subprocess at 22775648487024 with name start in state RUNNING> (stderr)> 2022-09-20 11:40:51,153 INFO exited: start (exit status 0; expected) 2022-09-20 11:40:51,154 DEBG received SIGCHLD indicating a child quit Seems to just quit, I have tried deleting the .pid, reinstalled, entire directory delete + reinstall, plus I rebooted my server.. I'm out of idea's.. anyone able to point me in the correct direction?

The NVIDIA visible devices has gone from the template? or am I missing something? My container failed during updating.. maybe because this option doesn't exist, but I'm not sure. Manually adding the variable worked for me, but figured I should report it..

Hey, is there a link to the GPU enabled container somewhere? or a guide? I can't seem to find it

Thanks dude, you might wanna have an attitude check

Hey guys, anyone have any idea why it would say my GPU is not supported? says not enough free memory? 20210830 00:09:25 Starting on: asia1.ethermine.org:4444 20210830 00:09:25 Using protocol: stratum1. 20210830 00:09:25 Authorizing... 20210830 00:09:25 ApiServer: HTTP server started on 0.0.0.0:4067 20210830 00:09:25 ----------------------------------------------------- 20210830 00:09:25 For control navigate to: http://172.17.0.13:4067/trex 20210830 00:09:25 ----------------------------------------------------- 20210830 00:09:25 ApiServer: Telnet server started on 127.0.0.1:4068 20210830 00:09:25 Authorized successfully. 20210830 00:09:25 GPU #0(000100): ASUS NVIDIA GeForce GTX 1050 Ti, intensity 22 20210830 00:09:25 ethash epoch: 437, block: 13123548, diff: 4.29 G 20210830 00:09:26 WARN: NVML: can't get power for GPU #0, not supported 20210830 00:09:29 TREX: Can't find nonce with device [ID=0, GPU #0], GPU #0: not enough free memory to mine ethash at epoch 437 20210830 00:09:29 WARN: Miner is going to shutdown... 20210830 00:09:29 Main loop finished. Cleaning up resources... 20210830 00:09:29 ApiServer: stopped listening on 0.0.0.0:4067 20210830 00:09:29 ApiServer: stopped listening on 127.0.0.1:4068 20210830 00:09:30 T-Rex finished. 20210830 00:09:31 WARN: WATCHDOG: T-Rex does not exist anymore, restarting... smi +-----------------------------------------------------------------------------+ | NVIDIA-SMI 465.19.01 Driver Version: 465.19.01 CUDA Version: 11.3 | |-------------------------------+----------------------+----------------------+ | GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. ECC | | Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. | | | | MIG M. | |===============================+======================+======================| | 0 NVIDIA GeForce ... Off | 00000000:01:00.0 Off | N/A | | 31% 32C P8 N/A / 75W | 2MiB / 4039MiB | 0% Default | | | | N/A | +-------------------------------+----------------------+----------------------+ +-----------------------------------------------------------------------------+ | Processes: | | GPU GI CI PID Type Process name GPU Memory | | ID ID Usage | |=============================================================================| | No running processes found | +-----------------------------------------------------------------------------+ Do I need more than 4GB to mine ethash?

okay have fix that, think there is something corrupt inside the docker.img? Is that loop3? as you stated. I will try re-create it.. hope my plex files are gucci I get a tone of errors of this nature when starting plex Mar 31 20:46:09 unRAID kernel: BTRFS warning (device loop3): csum failed root 9874 ino 10569 off 8192 csum 0xb8ef9c9e expected csum 0xba489cc3 mirror 1 Mar 31 20:46:09 unRAID kernel: BTRFS error (device loop3): bdev /dev/loop3 errs: wr 0, rd 0, flush 0, corrupt 654, gen 0 Mar 31 20:46:09 unRAID kernel: BTRFS warning (device loop3): csum failed root 9874 ino 10569 off 8192 csum 0xb8ef9c9e expected csum 0xba489cc3 mirror 1 Mar 31 20:46:09 unRAID kernel: BTRFS error (device loop3): bdev /dev/loop3 errs: wr 0, rd 0, flush 0, corrupt 655, gen 0 Mar 31 20:46:09 unRAID kernel: BTRFS warning (device loop3): csum failed root 9874 ino 10569 off 8192 csum 0xb8ef9c9e expected csum 0xba489cc3 mirror 1 Mar 31 20:46:09 unRAID kernel: BTRFS error (device loop3): bdev /dev/loop3 errs: wr 0, rd 0, flush 0, corrupt 656, gen 0 Mar 31 20:46:09 unRAID kernel: BTRFS warning (device loop3): csum failed root 9874 ino 10569 off 8192 csum 0xb8ef9c9e expected csum 0xba489cc3 mirror 1 Mar 31 20:46:09 unRAID kernel: BTRFS error (device loop3): bdev /dev/loop3 errs: wr 0, rd 0, flush 0, corrupt 657, gen 0 Mar 31 20:46:09 unRAID kernel: BTRFS warning (device loop3): csum failed root 9874 ino 10569 off 8192 csum 0xb8ef9c9e expected csum 0xba489cc3 mirror 1 Mar 31 20:46:09 unRAID kernel: BTRFS error (device loop3): bdev /dev/loop3 errs: wr 0, rd 0, flush 0, corrupt 658, gen 0 After docker.img rebuild, plex is gucci again... thanks so much for you help @JorgeB

Seem to still be spamming this into syslog when starting plex however Mar 31 20:45:58 unRAID kernel: BTRFS warning (device loop3): csum failed root 9874 ino 10569 off 8192 csum 0xb8ef9c9e expected csum 0xba489cc3 mirror 1 Mar 31 20:45:58 unRAID kernel: BTRFS error (device loop3): bdev /dev/loop3 errs: wr 0, rd 0, flush 0, corrupt 268, gen 0 Mar 31 20:45:59 unRAID kernel: BTRFS warning (device loop3): csum failed root 9874 ino 10569 off 8192 csum 0xb8ef9c9e expected csum 0xba489cc3 mirror 1 Mar 31 20:45:59 unRAID kernel: BTRFS error (device loop3): bdev /dev/loop3 errs: wr 0, rd 0, flush 0, corrupt 269, gen 0 Mar 31 20:45:59 unRAID kernel: BTRFS warning (device loop3): csum failed root 9874 ino 10569 off 8192 csum 0xb8ef9c9e expected csum 0xba489cc3 mirror 1 Mar 31 20:45:59 unRAID kernel: BTRFS error (device loop3): bdev /dev/loop3 errs: wr 0, rd 0, flush 0, corrupt 270, gen 0 Mar 31 20:45:59 unRAID kernel: BTRFS warning (device loop3): csum failed root 9874 ino 10569 off 8192 csum 0xb8ef9c9e expected csum 0xba489cc3 mirror 1 Mar 31 20:45:59 unRAID kernel: BTRFS error (device loop3): bdev /dev/loop3 errs: wr 0, rd 0, flush 0, corrupt 271, gen 0 Mar 31 20:45:59 unRAID kernel: BTRFS warning (device loop3): csum failed root 9874 ino 10569 off 8192 csum 0xb8ef9c9e expected csum 0xba489cc3 mirror 1 Mar 31 20:45:59 unRAID kernel: BTRFS error (device loop3): bdev /dev/loop3 errs: wr 0, rd 0, flush 0, corrupt 272, gen 0 Mar 31 20:45:59 unRAID kernel: BTRFS warning (device loop3): csum failed root 9874 ino 10569 off 8192 csum 0xb8ef9c9e expected csum 0xba489cc3 mirror 1 Mar 31 20:45:59 unRAID kernel: BTRFS error (device loop3): bdev /dev/loop3 errs: wr 0, rd 0, flush 0, corrupt 273, gen 0 Mar 31 20:45:59 unRAID kernel: BTRFS warning (device loop3): csum failed root 9874 ino 10569 off 8192 csum 0xb8ef9c9e expected csum 0xba489cc3 mirror 1 Mar 31 20:45:59 unRAID kernel: BTRFS error (device loop3): bdev /dev/loop3 errs: wr 0, rd 0, flush 0, corrupt 274, gen 0 Mar 31 20:45:59 unRAID kernel: BTRFS warning (device loop3): csum failed root 9874 ino 10569 off 8192 csum 0xb8ef9c9e expected csum 0xba489cc3 mirror 1 Mar 31 20:45:59 unRAID kernel: BTRFS error (device loop3): bdev /dev/loop3 errs: wr 0, rd 0, flush 0, corrupt 275, gen 0 Mar 31 20:45:59 unRAID kernel: BTRFS warning (device loop3): csum failed root 9874 ino 10569 off 8192 csum 0xb8ef9c9e expected csum 0xba489cc3 mirror 1 Mar 31 20:45:59 unRAID kernel: BTRFS error (device loop3): bdev /dev/loop3 errs: wr 0, rd 0, flush 0, corrupt 276, gen 0 Mar 31 20:45:59 unRAID kernel: BTRFS warning (device loop3): csum failed root 9874 ino 10569 off 8192 csum 0xb8ef9c9e expected csum 0xba489cc3 mirror 1 Mar 31 20:45:59 unRAID kernel: BTRFS error (device loop3): bdev /dev/loop3 errs: wr 0, rd 0, flush 0, corrupt 277, gen 0 Mar 31 20:46:04 unRAID kernel: btrfs_print_data_csum_error: 147 callbacks suppressed Mar 31 20:46:04 unRAID kernel: BTRFS warning (device loop3): csum failed root 9874 ino 10569 off 8192 csum 0xb8ef9c9e expected csum 0xba489cc3 mirror 1 Mar 31 20:46:04 unRAID kernel: btrfs_dev_stat_print_on_error: 147 callbacks suppressed Mar 31 20:46:04 unRAID kernel: BTRFS error (device loop3): bdev /dev/loop3 errs: wr 0, rd 0, flush 0, corrupt 425, gen 0 Mar 31 20:46:04 unRAID kernel: BTRFS warning (device loop3): csum failed root 9874 ino 10569 off 8192 csum 0xb8ef9c9e expected csum 0xba489cc3 mirror 1 Mar 31 20:46:04 unRAID kernel: BTRFS error (device loop3): bdev /dev/loop3 errs: wr 0, rd 0, flush 0, corrupt 426, gen 0 Mar 31 20:46:04 unRAID kernel: BTRFS warning (device loop3): csum failed root 9874 ino 10569 off 8192 csum 0xb8ef9c9e expected csum 0xba489cc3 mirror 1 Mar 31 20:46:04 unRAID kernel: BTRFS error (device loop3): bdev /dev/loop3 errs: wr 0, rd 0, flush 0, corrupt 427, gen 0 Mar 31 20:46:04 unRAID kernel: BTRFS warning (device loop3): csum failed root 9874 ino 10569 off 8192 csum 0xb8ef9c9e expected csum 0xba489cc3 mirror 1 Mar 31 20:46:04 unRAID kernel: BTRFS error (device loop3): bdev /dev/loop3 errs: wr 0, rd 0, flush 0, corrupt 428, gen 0 Mar 31 20:46:04 unRAID kernel: BTRFS warning (device loop3): csum failed root 9874 ino 10569 off 8192 csum 0xb8ef9c9e expected csum 0xba489cc3 mirror 1 Mar 31 20:46:04 unRAID kernel: BTRFS error (device loop3): bdev /dev/loop3 errs: wr 0, rd 0, flush 0, corrupt 429, gen 0 Mar 31 20:46:04 unRAID kernel: BTRFS warning (device loop3): csum failed root 9874 ino 10569 off 8192 csum 0xb8ef9c9e expected csum 0xba489cc3 mirror 1 Mar 31 20:46:04 unRAID kernel: BTRFS error (device loop3): bdev /dev/loop3 errs: wr 0, rd 0, flush 0, corrupt 430, gen 0 Mar 31 20:46:04 unRAID kernel: BTRFS warning (device loop3): csum failed root 9874 ino 10569 off 8192 csum 0xb8ef9c9e expected csum 0xba489cc3 mirror 1 Mar 31 20:46:04 unRAID kernel: BTRFS error (device loop3): bdev /dev/loop3 errs: wr 0, rd 0, flush 0, corrupt 431, gen 0 Mar 31 20:46:04 unRAID kernel: BTRFS warning (device loop3): csum failed root 9874 ino 10569 off 8192 csum 0xb8ef9c9e expected csum 0xba489cc3 mirror 1 Mar 31 20:46:04 unRAID kernel: BTRFS error (device loop3): bdev /dev/loop3 errs: wr 0, rd 0, flush 0, corrupt 432, gen 0 Mar 31 20:46:04 unRAID kernel: BTRFS warning (device loop3): csum failed root 9874 ino 10569 off 8192 csum 0xb8ef9c9e expected csum 0xba489cc3 mirror 1 Mar 31 20:46:04 unRAID kernel: BTRFS error (device loop3): bdev /dev/loop3 errs: wr 0, rd 0, flush 0, corrupt 433, gen 0 Mar 31 20:46:04 unRAID kernel: BTRFS warning (device loop3): csum failed root 9874 ino 10569 off 8192 csum 0xb8ef9c9e expected csum 0xba489cc3 mirror 1 Mar 31 20:46:04 unRAID kernel: BTRFS error (device loop3): bdev /dev/loop3 errs: wr 0, rd 0, flush 0, corrupt 434, gen 0 Mar 31 20:46:09 unRAID kernel: btrfs_print_data_csum_error: 214 callbacks suppressed Mar 31 20:46:09 unRAID kernel: BTRFS warning (device loop3): csum failed root 9874 ino 10569 off 8192 csum 0xb8ef9c9e expected csum 0xba489cc3 mirror 1 Mar 31 20:46:09 unRAID kernel: btrfs_dev_stat_print_on_error: 214 callbacks suppressed Mar 31 20:46:09 unRAID kernel: BTRFS error (device loop3): bdev /dev/loop3 errs: wr 0, rd 0, flush 0, corrupt 649, gen 0 Mar 31 20:46:09 unRAID kernel: BTRFS warning (device loop3): csum failed root 9874 ino 10569 off 8192 csum 0xb8ef9c9e expected csum 0xba489cc3 mirror 1 Mar 31 20:46:09 unRAID kernel: BTRFS error (device loop3): bdev /dev/loop3 errs: wr 0, rd 0, flush 0, corrupt 650, gen 0 Mar 31 20:46:09 unRAID kernel: BTRFS warning (device loop3): csum failed root 9874 ino 10569 off 8192 csum 0xb8ef9c9e expected csum 0xba489cc3 mirror 1 Mar 31 20:46:09 unRAID kernel: BTRFS error (device loop3): bdev /dev/loop3 errs: wr 0, rd 0, flush 0, corrupt 651, gen 0 Mar 31 20:46:09 unRAID kernel: BTRFS warning (device loop3): csum failed root 9874 ino 10569 off 8192 csum 0xb8ef9c9e expected csum 0xba489cc3 mirror 1 Mar 31 20:46:09 unRAID kernel: BTRFS error (device loop3): bdev /dev/loop3 errs: wr 0, rd 0, flush 0, corrupt 652, gen 0 Mar 31 20:46:09 unRAID kernel: BTRFS warning (device loop3): csum failed root 9874 ino 10569 off 8192 csum 0xb8ef9c9e expected csum 0xba489cc3 mirror 1 Mar 31 20:46:09 unRAID kernel: BTRFS error (device loop3): bdev /dev/loop3 errs: wr 0, rd 0, flush 0, corrupt 653, gen 0 Mar 31 20:46:09 unRAID kernel: BTRFS warning (device loop3): csum failed root 9874 ino 10569 off 8192 csum 0xb8ef9c9e expected csum 0xba489cc3 mirror 1 Mar 31 20:46:09 unRAID kernel: BTRFS error (device loop3): bdev /dev/loop3 errs: wr 0, rd 0, flush 0, corrupt 654, gen 0 Mar 31 20:46:09 unRAID kernel: BTRFS warning (device loop3): csum failed root 9874 ino 10569 off 8192 csum 0xb8ef9c9e expected csum 0xba489cc3 mirror 1 Mar 31 20:46:09 unRAID kernel: BTRFS error (device loop3): bdev /dev/loop3 errs: wr 0, rd 0, flush 0, corrupt 655, gen 0 Mar 31 20:46:09 unRAID kernel: BTRFS warning (device loop3): csum failed root 9874 ino 10569 off 8192 csum 0xb8ef9c9e expected csum 0xba489cc3 mirror 1 Mar 31 20:46:09 unRAID kernel: BTRFS error (device loop3): bdev /dev/loop3 errs: wr 0, rd 0, flush 0, corrupt 656, gen 0 Mar 31 20:46:09 unRAID kernel: BTRFS warning (device loop3): csum failed root 9874 ino 10569 off 8192 csum 0xb8ef9c9e expected csum 0xba489cc3 mirror 1 Mar 31 20:46:09 unRAID kernel: BTRFS error (device loop3): bdev /dev/loop3 errs: wr 0, rd 0, flush 0, corrupt 657, gen 0 Mar 31 20:46:09 unRAID kernel: BTRFS warning (device loop3): csum failed root 9874 ino 10569 off 8192 csum 0xb8ef9c9e expected csum 0xba489cc3 mirror 1

Hey Berserk, I have a interesting error coming up since I updated to 6.9 First I was getting spammed with this Mar 31 20:40:34 unRAID kernel: NVRM: GPU 0000:01:00.0: Failed to enable MSI; falling back to PCIe virtual-wire interrupts. Mar 31 20:40:34 unRAID kernel: resource sanity check: requesting [mem 0x000c0000-0x000fffff], which spans more than PCI Bus 0000:00 [mem 0x000d0000-0x000d3fff window] Once I figured out it was the plugin, I removed it but now I'm getting Mar 31 20:41:23 unRAID nginx: 2021/03/31 20:41:23 [error] 9939#9939: *10099 FastCGI sent in stderr: "Unable to open primary script: /usr/local/emhttp/plugins/gpustat/gpustatus.php (No such file or directory)" while reading response header from upstream, client: 192.168.2.110, server: , request: "GET /plugins/gpustat/gpustatus.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "192.168.2.155", referrer: "http://192.168.2.155/Dashboard" Mar 31 20:42:23 unRAID nginx: 2021/03/31 20:42:23 [error] 9939#9939: *10605 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 192.168.2.110, server: , request: "GET /plugins/gpustat/gpustatus.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "192.168.2.155", referrer: "http://192.168.2.155/Dashboard" Any idea what's going on?

yay Okay, syslog attached incase, I see this Mar 31 20:26:37 unRAID kernel: BTRFS warning (device sdh1): checksum error at logical 382557040640 on dev /dev/sdi1, physical 59465216000, root 5, inode 8972582, offset 216076288, length 4096, links 1 (path: appdata/binhex-minidlna/files.db) Mar 31 20:26:37 unRAID kernel: BTRFS error (device sdh1): bdev /dev/sdi1 errs: wr 0, rd 0, flush 0, corrupt 2, gen 0 Mar 31 20:26:38 unRAID kernel: BTRFS error (device sdh1): unable to fixup (regular) error at logical 382557040640 on dev /dev/sdi1 Can I assume the appdata/binhex-minidlna/files.db is corrupt? It says Corrupt 2, but says that file twice One being on device sdh1 and sdi1 syslog

Thanks for the info! I am running a scrub on one of the SSD's now. It has come back with a couple un-correctable errors What is my best coarse of action from here? Replace that SSD and rebuild?

Mar 31 18:43:38 unRAID kernel: BTRFS warning (device loop3): csum failed root 9866 ino 10569 off 8192 csum 0x9e9cefb8 expected csum 0xc39c48ba mirror 1 Hey guys, I'm trying to figure out what is going on above, seems to spam my logs with it when I start my Plex Docker (which is currently crashing on start). The only BTRFS drives I have is my cache pool.. could one of those be f'd? Smart seems all good on them That said however, if I run the following root@unRAID:~# btrfs dev stats /mnt/cache/ [/dev/sdh1].write_io_errs 0 [/dev/sdh1].read_io_errs 0 [/dev/sdh1].flush_io_errs 0 [/dev/sdh1].corruption_errs 0 [/dev/sdh1].generation_errs 0 [/dev/sdi1].write_io_errs 3376200 [/dev/sdi1].read_io_errs 1425037 [/dev/sdi1].flush_io_errs 150448 [/dev/sdi1].corruption_errs 0 [/dev/sdi1].generation_errs 0 It shows a tone of write, read and flush io errors I do have two cache drives, but I'm not sure how to run dev stats on sdi(2?) Is one of my cache drives dying? I have the unraid diag attached to this post, notable I am getting GPU errors on my GTX 1050 aswell.. but I don't think its related and I assume will fix when I re-install the upgrade unraid and re-install the drivers. I am going to re-install Plex, maybe this will fix it, but unsure why this has happened, maybe my docker.img is boned? unraid-diagnostics-20210331-1847.zip

yeah spain working but shitty... this is why I moved everything to usenet T.T

sad bump

Hey guys I'm working on setting up my own pfsense router since I finally got gigabit internet in Australia, but my current router isn't cutting it. The NIC's show in system devices, but I seem to be failing to stop unraid for using them Above are the devices Here is my syslinux config With append vfio-pci.ids=8086:1079 I can still see the network adapters listed in NetworkSettings, so it seemed to have 0 change I then also tried append pci-stub.ids=8086:1079 With this the network adapters no longer show in NetworkSettings but I also can't see it as an option to passthrough to a VM I am running unraid 6.8.3 unraid-diagnostics-20200710-1317.zip Above is attached diagnostic download of my tower. in case at all relevant. Should be noted I also have PCIe ACS Override setting enabled. Any help would be appreciated as always!

Hey guys, I could really use some help.. I'm not sure what is going on. I'm trying to get my gbe nic passed through to my VM, but I don't think my syslinux config is working properly This was my original Config kernel /bzimage append pcie_acs_override=downstream initrd=/bzroot pci=nomsi,noaer This is my edited config First I tried kernel /bzimage append vfio-pci.ids=8086:1079 pcie_acs_override=downstream initrd=/bzroot pci=nomsi,noaer This seemed to have 0 effect, the devices were still in the network settings. Then I tried below, as I saw it in a post kernel /bzimage append pci-stub.ids=8086:1079 pcie_acs_override=downstream initrd=/bzroot pci=nomsi,noaer I can no longer see the controllers in my network settings, but I also cannot see them available to passthrough to the VM Any idea's? Edit: I have just been editing the Unraid OS syslinux config, I assume this is fine as this is how I boot it

Yo, my understanding is Host has direct access to the hosts networking, so to eth0 Bridge is done by mapping ports with br0, which is your bridge (if its enabled) and is what allows us to use dockers and VM's on eth0 and also give them their own IP addresses. I could be wrong doe

Okay, I'm reading here that it is safe to upgrade to 6.8.2? Thank you guys for the work - seriously, sorry I had to stop contributing to the thread but it was very frustrating!

Thanks mate

Looks like a reboot killed it, its been back up for about 5 minutes now. I'll keep an eye on it.. Thanks for your help. I think I should have put a password on root. I honestly didn't expect to love unraid so much and didn't plan this very well

I have some ports open for Plex. I did DMZ it (i know) for like 5 minutes the other day to fix something real quick though - could this have been how it got in. When I delete the file, it comes back any idea how I can stop that from happening?