acastellab

Hi all! I've got nvidia plugin installed to passthrough an GPU to Boinc, for crunching work units. GPU in NVIDIA RTX 2060 After sometime the GPU statistics plugin stops giving information. The fans are full throttle. nvidia-smi gives the following: Unable to determine the device handle for GPU0000:01:00.0: Unknown Error Logs have this: I'm unable to stop the BOINC docker. I have to restart the system, that starts an inmidiate parity check on the next start up. Thank you for any indication

I get the message of the title. Unraid 6.11.3 Looked up in the forum and I found this thread: https://forums.unraid.net/bug-reports/prereleases/there-are-differences-between-boot-sector-and-its-backup-r1745/?tab=comments#comment-21587 Did what was recommended: dosfsck -v /dev/sda1 Sorted out most discrepancies, except one. I runned it again and I get this: I used the proper way to reboot the machine, through the option to reboot in the main page. Why would it be unmounting the FS in a unproper way? Also, It could be that each time I shutdown or reboot the machine, one discrepancy is added to the list.

Hi! I had the same problem. I'll try you solution. I did. The amount of differences reduced, but one still appeared: Unraid ver 6.11.3 I'll post in another thread that has not got to do with pre-releases.

I should have been more patient and waited...

I also had the same issue, but with replacing a smaller disk with a bigger one. I ended downgrading but the issue did not go away and started the array and replaced the data in the new disk using the parity. The only option the system gave me was formating the new disk. Afterwards the system worked ok but I lost what I had in the disk that was replaced. I have it and I looked what was in it mounting it and it's just Linux ISOs and stuff that is easyly replaceble. Do I have to do anything special, like run a parity check or something so the system is not inconsistent? Update: I tried to update to 6.11.3 and the machine would not boot, the usb was not recognized and I had to download a backup from Unraid and look for a new usb drive. After this I was able to upgrade to 6.11.3 Running a parity check and finding out many errors.

I noticed my log was around 71% full so I had a look at my log and it is full of the following: I'm attaching my diagnostics file. I understand it has something to do with SAMBA. I have stopped the array and started it and it's no longer happening. What can I do about it? Thanks tower-diagnostics-20221010-2009.zip

How can I copy from de VNC display and paste in my local browser? For example to copy an address from the wallet to paste in the destination of a transfer in my local web page? Thanks

After 45 minutes it stopped working. I read everything in the Nvidia Plugin support and tried different solutions to no avail. In the end I extracted the GPU from the Unraid machine and inserted it to a bare metal ubuntu machine with BOINC and it worked fine. Perhaps the plugin is not yet up to the workload BOINC puts on it, and I don't want it to break up my unraid machine with all my stuff on it.

I uninstalled the complete docker, deleted the image and reinstalled it from scratch. Anyone trying to do the same, not only you have to remove /der/dri: parameter but also: add the following parameter: --runtime=nvidia and add an environment variable -e NVIDIA_VISIBLE_DEVICES=[GPU ID you find in the NVIDIA plugin] And it works

Hi! Since I've added a GPU I've occasionally have had problems accessing BOINC through the incorporated Guacamole in the Docker. Since last update, on the 24th of September, It never works. I can access BOINC through the console and I can see it is working. The errors that appear on the log are the following: Any idea on what could I do about it. I would use the Official Unraid docker, but including the GPU looks cumbersome, and this one has been working fine for me for a long time. Thank you

Hi, I've got the "Call traces found on your server". I'm attaching the diagnostics zip for you to see if you can give me a hand. I'm not sure, but it looks like it is something to do with the network. I'm I right?. Thanks, Alex tower-diagnostics-20180527-1250.zip

OK, same thing for me, after an update of the openvpn as docker I'm unable to connect from outside. When I get home from work I'll try to do that and I'll post back. <After some hours of gruesome work down in the mine> I got home, it was correctly configured. I stopped the docker and started it again, I connected through my mobile phone and... it worked ok.

Hi! I got the call traces error again: Apr 23 23:28:08 Tower kernel: ------------[ cut here ]------------ Apr 23 23:28:08 Tower kernel: WARNING: CPU: 0 PID: 0 at net/netfilter/nf_conntrack_core.c:769 __nf_conntrack_confirm+0x97/0x4d6 Apr 23 23:28:08 Tower kernel: Modules linked in: xt_CHECKSUM iptable_mangle ipt_REJECT nf_reject_ipv4 ebtable_filter ebtables ip6table_filter ip6_tables vhost_net tun vhost tap macvlan xt_nat veth ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 iptable_filter ip_tables nf_nat xfs nfsd lockd grace sunrpc md_mod bonding x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd glue_helper cryptd intel_cstate intel_uncore intel_rapl_perf e1000e i2c_i801 i2c_core ahci libahci ptp wmi pps_core video backlight fan thermal acpi_pad button [last unloaded: i2c_dev] Apr 23 23:28:08 Tower kernel: CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.14.34-unRAID #1 Apr 23 23:28:08 Tower kernel: Hardware name: Gigabyte Technology Co., Ltd. X150M-PRO ECC/X150M-PRO ECC-CF, BIOS F21 12/26/2016 Apr 23 23:28:08 Tower kernel: task: ffffffff81c12480 task.stack: ffffffff81c00000 Apr 23 23:28:08 Tower kernel: RIP: 0010:__nf_conntrack_confirm+0x97/0x4d6 Apr 23 23:28:08 Tower kernel: RSP: 0018:ffff88083ec038d0 EFLAGS: 00010202 Apr 23 23:28:08 Tower kernel: RAX: 0000000000000188 RBX: 0000000000007c91 RCX: 0000000000000001 Apr 23 23:28:08 Tower kernel: RDX: 0000000000000001 RSI: 0000000000000000 RDI: ffffffff81c08844 Apr 23 23:28:08 Tower kernel: RBP: ffff8806c6978200 R08: 0000000000000101 R09: ffff880783d1bb00 Apr 23 23:28:08 Tower kernel: R10: 00000000000002b8 R11: 0000000000000006 R12: ffffffff81c8b080 Apr 23 23:28:08 Tower kernel: R13: 000000000000581f R14: ffff8806d6298280 R15: ffff8806d62982d8 Apr 23 23:28:08 Tower kernel: FS: 0000000000000000(0000) GS:ffff88083ec00000(0000) knlGS:0000000000000000 Apr 23 23:28:08 Tower kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Apr 23 23:28:08 Tower kernel: CR2: 000000c420080780 CR3: 0000000001c0a004 CR4: 00000000003606f0 Apr 23 23:28:08 Tower kernel: Call Trace: Apr 23 23:28:08 Tower kernel: <IRQ> Apr 23 23:28:08 Tower kernel: ipv4_confirm+0xac/0xb4 [nf_conntrack_ipv4] Apr 23 23:28:08 Tower kernel: nf_hook_slow+0x37/0x96 Apr 23 23:28:08 Tower kernel: ip_local_deliver+0xab/0xd3 Apr 23 23:28:08 Tower kernel: ? inet_del_offload+0x3e/0x3e Apr 23 23:28:08 Tower kernel: ip_sabotage_in+0x2b/0x31 Apr 23 23:28:08 Tower kernel: nf_hook_slow+0x37/0x96 Apr 23 23:28:08 Tower kernel: ip_rcv+0x2f2/0x346 Apr 23 23:28:08 Tower kernel: ? ip_local_deliver_finish+0x1b8/0x1b8 Apr 23 23:28:08 Tower kernel: __netif_receive_skb_core+0x6ba/0x733 Apr 23 23:28:08 Tower kernel: netif_receive_skb_internal+0xbb/0xd0 Apr 23 23:28:08 Tower kernel: br_pass_frame_up+0x12d/0x13a Apr 23 23:28:08 Tower kernel: ? br_port_flags_change+0xf/0xf Apr 23 23:28:08 Tower kernel: br_handle_frame_finish+0x41a/0x44a Apr 23 23:28:08 Tower kernel: ? br_pass_frame_up+0x13a/0x13a Apr 23 23:28:08 Tower kernel: br_nf_hook_thresh+0x93/0x9e Apr 23 23:28:08 Tower kernel: ? br_pass_frame_up+0x13a/0x13a Apr 23 23:28:08 Tower kernel: br_nf_pre_routing_finish+0x268/0x27a Apr 23 23:28:08 Tower kernel: ? br_pass_frame_up+0x13a/0x13a Apr 23 23:28:08 Tower kernel: ? nf_nat_ipv4_fn+0x116/0x166 [nf_nat_ipv4] Apr 23 23:28:08 Tower kernel: ? nf_nat_ipv4_in+0x21/0x68 [nf_nat_ipv4] Apr 23 23:28:08 Tower kernel: br_nf_pre_routing+0x2d8/0x2e8 Apr 23 23:28:08 Tower kernel: ? br_nf_forward_ip+0x32c/0x32c Apr 23 23:28:08 Tower kernel: nf_hook_slow+0x37/0x96 Apr 23 23:28:08 Tower kernel: br_handle_frame+0x2a0/0x2d3 Apr 23 23:28:08 Tower kernel: ? br_pass_frame_up+0x13a/0x13a Apr 23 23:28:08 Tower kernel: ? br_handle_local_finish+0x31/0x31 Apr 23 23:28:08 Tower kernel: __netif_receive_skb_core+0x463/0x733 Apr 23 23:28:08 Tower kernel: ? inet_gro_receive+0x25a/0x26f Apr 23 23:28:08 Tower kernel: ? recalibrate_cpu_khz+0x6/0x6 Apr 23 23:28:08 Tower kernel: netif_receive_skb_internal+0xbb/0xd0 Apr 23 23:28:08 Tower kernel: napi_gro_receive+0x42/0x76 Apr 23 23:28:08 Tower kernel: e1000_clean_rx_irq+0x295/0x303 [e1000e] Apr 23 23:28:08 Tower kernel: e1000e_poll+0x66/0x215 [e1000e] Apr 23 23:28:08 Tower kernel: net_rx_action+0xfb/0x24f Apr 23 23:28:08 Tower kernel: __do_softirq+0xcd/0x1c2 Apr 23 23:28:08 Tower kernel: irq_exit+0x4f/0x8e Apr 23 23:28:08 Tower kernel: do_IRQ+0xa5/0xbb Apr 23 23:28:08 Tower kernel: common_interrupt+0x7d/0x7d Apr 23 23:28:08 Tower kernel: </IRQ> Apr 23 23:28:08 Tower kernel: RIP: 0010:cpuidle_enter_state+0xe3/0x135 Apr 23 23:28:08 Tower kernel: RSP: 0018:ffffffff81c03ec8 EFLAGS: 00000246 ORIG_RAX: ffffffffffffff2d Apr 23 23:28:08 Tower kernel: RAX: ffff88083ec20980 RBX: 0000000000000000 RCX: 000000000000001f Apr 23 23:28:08 Tower kernel: RDX: 000156be00b1565e RSI: 0000000000020180 RDI: 0000000000000000 Apr 23 23:28:08 Tower kernel: RBP: ffff88083ec28800 R08: 0004b447bf04376e R09: 0000000000000090 Apr 23 23:28:08 Tower kernel: R10: ffffffff81c03ea8 R11: 00000004000755fc R12: 0000000000000006 Apr 23 23:28:08 Tower kernel: R13: 000156be00b1565e R14: ffffffff81c59398 R15: 000156be00631545 Apr 23 23:28:08 Tower kernel: ? cpuidle_enter_state+0xbb/0x135 Apr 23 23:28:08 Tower kernel: do_idle+0x11a/0x179 Apr 23 23:28:08 Tower kernel: cpu_startup_entry+0x18/0x1a Apr 23 23:28:08 Tower kernel: start_kernel+0x3e4/0x3ec Apr 23 23:28:08 Tower kernel: secondary_startup_64+0xa5/0xb0 Apr 23 23:28:08 Tower kernel: Code: 48 c1 eb 20 89 1c 24 e8 24 f9 ff ff 8b 54 24 04 89 df 89 c6 41 89 c5 e8 a9 fa ff ff 84 c0 75 b9 49 8b 86 80 00 00 00 a8 08 74 02 <0f> 0b 4c 89 f7 e8 03 ff ff ff 49 8b 86 80 00 00 00 0f ba e0 09 Apr 23 23:28:08 Tower kernel: ---[ end trace c647bfacc3bea2a3 ]--- This es the zip file: tower-diagnostics-20180424-0556.zip

Please excuse my presbyopia I just managed to find the link at the bottom of the page.

Do you have a RSS or atom link of any new posts to subscribe with my newsreader?. I think it would be more convenient than having to visit the forum. Also, you could have different links by sub-forum or even by topic. Thank you.

Thank you very much.

¿Could I please bother you with one more question? ¿Could you please give me a link on how to scrub the disk of the cache pool?

I’ll have a look at the cables. Thanks

Thank you very much for your answer. “Related to docker with custom IP addresses, try updating to latest rc.” I will update to the latest release candidate. By the way, I’ve noticed quite a few errors in the logs relating to some sort of error with a ssd disk I use in the cache pool. I will follow the instructions to change the disk in this cache pool. Alex

Hi! I've received this notice through the Fix Common Problems plugin. This is the diagnostics. ¿Do you see anything odd? Thank you. Alex tower-diagnostics-20180419-0656.zip