Daxxio

I have replaced the ram with 16GB Crucial CT2K8G4DFS824A DDR4-2400 DIMM CL17 Dual Kit now. From the info before it was 3200mhz. Will check if it is better now

Hey there, a few days ago I started noticing that after transfering some files and installing some programs that CRC unarc.dll mismatch errors are showing up. Also hashchecks fail. I am installing directly from the unraid server over SMB. It also happened on another pc in the same network with the same file. What could be the cause? - I replaced the RAM, but going to assume that old broken files won't be fixed automatically, since the file that was corrupt with the old ram, still didn't work. - Network cable has been replaced and I also used a different NIC on the same mobo. - Dusted off the entire pc and checked all sata cables. I attached a few log files that might be interesting.. Hopefully someone could give me some pointers where to look for errors... Thank you! unraid-smart-20220323-1219 (3).zip unraid-smart-20220323-1219 (2).zip unraid-smart-20220323-1219 (1).zip unraid-smart-20220323-1219.zip unraid-diagnostics-20220323-1218.zip unraid-syslog-20220323-1355.zip

I actually do not and it worked perfectly fine without changing anything... I saw this was a problem with the container before in the thread. Could that be it?

Regarding Valheim... I have been trying to fix an issue for 3 hours now. Remade the docker 4 times but it just does not work. Whatever I try, I get lots of errors. When starting it like normally I get this error: ---Prepare Server--- ---ValheimPlus enabled!--- ---Can't get latest version of Valheim Plus!--- ---Please try to run the Container without ValheimPlus, putting Container into sleep mode!--- When disabling valheim plus it runs just fine... I already did a force update.

Thanks a lot Johnnie! I will look into it. The NVMe drive also goes offline if I copy back and forth huge files (40g). I'll report back when I'm done. EDIT: Performed a BIOS update, appended the line you mentioned and cleared the btrfs stats. Will monitor if the problem still exists. EDIT2: Still had some errors after doing that but it was better. In the end I formatted my cache drives and made a new btrfs cahe pool. After that I still had a lot of PCIe Bus Error: severity=Corrected, type=Physical Layer errors. That seems to be resolved with booting Unraid like this: Unraid OS kernel /bzimage append initrd=/bzroot nvme_core.default_ps_max_latency_us=0 pcie_aspm=off

Hello Fellow Unraiders, Today the error log of Unraid showed a lot of BTRFS errors, so I searched what you can do and what causes it. Unfortunately I did not find the cause of the issues. Anyone who knows what is the best thing todo at this point. Diagnostics are attached. The harddrives are 2 SAMSUNG_MZVLB256HAHQ. Unraid version 6.8.1 Found this command root@Unraid:~# btrfs device stats /mnt/cache [/dev/nvme1n1p1].write_io_errs 31955 [/dev/nvme1n1p1].read_io_errs 4654 [/dev/nvme1n1p1].flush_io_errs 2150 [/dev/nvme1n1p1].corruption_errs 0 [/dev/nvme1n1p1].generation_errs 0 [/dev/nvme0n1p1].write_io_errs 4107117 [/dev/nvme0n1p1].read_io_errs 1036814 [/dev/nvme0n1p1].flush_io_errs 128904 [/dev/nvme0n1p1].corruption_errs 0 [/dev/nvme0n1p1].generation_errs 0 and here is a part of the log files: Feb 24 16:07:53 Unraid kernel: BTRFS info (device nvme1n1p1): read error corrected: ino 0 off 615257444352 (dev /dev/nvme0n1p1 sector 228489672) Feb 24 16:07:53 Unraid kernel: BTRFS info (device nvme1n1p1): read error corrected: ino 0 off 615257448448 (dev /dev/nvme0n1p1 sector 228489680) Feb 24 16:07:53 Unraid kernel: BTRFS info (device nvme1n1p1): read error corrected: ino 0 off 615257452544 (dev /dev/nvme0n1p1 sector 228489688) Feb 24 16:09:17 Unraid kernel: BTRFS warning (device loop2): csum failed root 5 ino 7348103 off 5263360 csum 0x4a11041d expected csum 0xf96124e9 mirror 1 Feb 24 16:10:21 Unraid kernel: BTRFS error (device nvme1n1p1): parent transid verify failed on 614962642944 wanted 19507514 found 19505513 Feb 24 16:10:21 Unraid kernel: BTRFS info (device nvme1n1p1): read error corrected: ino 0 off 614962642944 (dev /dev/nvme0n1p1 sector 227913888) Feb 24 16:10:21 Unraid kernel: BTRFS info (device nvme1n1p1): read error corrected: ino 0 off 614962647040 (dev /dev/nvme0n1p1 sector 227913896) Feb 24 16:10:21 Unraid kernel: BTRFS info (device nvme1n1p1): read error corrected: ino 0 off 614962651136 (dev /dev/nvme0n1p1 sector 227913904) Feb 24 16:10:21 Unraid kernel: BTRFS info (device nvme1n1p1): read error corrected: ino 0 off 614962655232 (dev /dev/nvme0n1p1 sector 227913912) Feb 24 16:11:20 Unraid kernel: BTRFS error (device nvme1n1p1): parent transid verify failed on 614829047808 wanted 19507387 found 19505396 Feb 24 16:11:20 Unraid kernel: BTRFS info (device nvme1n1p1): read error corrected: ino 0 off 614829047808 (dev /dev/nvme0n1p1 sector 227652960) Feb 24 16:11:20 Unraid kernel: BTRFS info (device nvme1n1p1): read error corrected: ino 0 off 614829051904 (dev /dev/nvme0n1p1 sector 227652968) Feb 24 16:11:20 Unraid kernel: BTRFS info (device nvme1n1p1): read error corrected: ino 0 off 614829056000 (dev /dev/nvme0n1p1 sector 227652976) Feb 24 16:11:20 Unraid kernel: BTRFS info (device nvme1n1p1): read error corrected: ino 0 off 614829060096 (dev /dev/nvme0n1p1 sector 227652984) Feb 24 16:13:21 Unraid kernel: BTRFS error (device nvme1n1p1): parent transid verify failed on 614831276032 wanted 19507389 found 19505396 Feb 24 16:13:21 Unraid kernel: BTRFS info (device nvme1n1p1): read error corrected: ino 0 off 614831276032 (dev /dev/nvme0n1p1 sector 227657312) Feb 24 16:13:21 Unraid kernel: BTRFS info (device nvme1n1p1): read error corrected: ino 0 off 614831280128 (dev /dev/nvme0n1p1 sector 227657320) Feb 24 16:13:21 Unraid kernel: BTRFS info (device nvme1n1p1): read error corrected: ino 0 off 614831284224 (dev /dev/nvme0n1p1 sector 227657328) Feb 24 16:13:21 Unraid kernel: BTRFS info (device nvme1n1p1): read error corrected: ino 0 off 614831288320 (dev /dev/nvme0n1p1 sector 227657336) unraid-diagnostics-20200224-1616.zip

unfortunately that does not work. been trying lots of thing: both apache guacamole and ff are now in bridge, I tried it in custom with a fixed IP. I can access firefox from the docker itself, just not from apache guacamole. also killed all sessions, limit increased to 20. nothing seems to work except for VNC and RDP to VM's, those work without any problems.

Helllo, somehow whatever parameters i set, can't get either the Firefox or VNC Web Browser docker container working under this Guacamole container. It always gives me error: The Guacamole server is denying access to this connection because you have exhausted the limit for simultaneous connection use by an individual user. Please close one or more connections and try again.