sonic6

Members
  • Posts

    594
  • Joined

  • Last visited

  • Days Won

    2

Report Comments posted by sonic6

  1. 7 minutes ago, Squid said:

    Why would you want to have a container path that isn't mapped to a host path?

    I didn't "want" it empty. It was like I load that template from the CA and I don't have any reasons using that path at the moment. I didn't recognize that before, because the container was builded with that empty path on later unraid version.

     

    9 minutes ago, Squid said:

    Docker silently failed on .6 as it wouldn't create any container path.  Now they're calling it an error instead of silently failing.

    Okay thank you for explaining me that case. 

     

    9 minutes ago, JonathanM said:

    What happens if you properly fill out the export path?

    The same, like I did (deleting that path): it will work. 

     

    9 minutes ago, JonathanM said:

    I don't think 6.12.6 would have accepted it either.

    I has... Like squid said before.

     

     

    I reported it, because I think I will not the last one who runs into that "problem"

    Just wanna try to help. 

  2. 6 minutes ago, itimpi said:

    If you have the Dynamix File Manager plugin installed then you can navigate to the plugins folder on the flash drive  /boot/config/plugins/parity.check.tuning/ to get a file listing.

    okay, there any files:

    root@Unraid-1:~# ls -la /boot/config/plugins/parity.check.tuning/
    /bin/ls: cannot access '/boot/config/plugins/parity.check.tuning/': No such file or directory

    image.png.5609ddaa3e96f3b399652875801a77b3.png

  3. 5 hours ago, itimpi said:

    The Parity Check Tuning plugin would not have initiated the check.

    I said the same. 

     

    4 hours ago, itimpi said:

    While I think of it we normally recommended that scheduled parity checks are set to be non-correcting.

    Fine, but when I choose a correction for m schedule, than it should do that.

     

    On my last test from 11:00 the parity check tuning plugin wasn't installed. 

  4. @bonienl @JorgeB

     

    50 minutes ago, ChatNoir said:

    Have you tried without the plugin to ensure that it is indeed an Unraid issue ?

    i tried this again at 11:00 without the plugin:

     

    image.thumb.png.ee5256406e176fffec3ef9a5086c1581.png

     

    Jan  2 11:00:02 Unraid-1 kernel: mdcmd (69): check NOCORRECT
    Jan  2 11:00:02 Unraid-1 kernel: 
    Jan  2 11:00:02 Unraid-1 kernel: md: recovery thread: check P ...

     

    Diagnostic is attached.

     

    unraid-1-diagnostics-20240102-1104.zip

  5. 6 minutes ago, ChatNoir said:

    Parity check tuning is a third party plugin, not part of base Unraid.

    i know, but the parity check was triggert by the default unraid parity check schedule and this :

    Jan  2 00:00:07 Unraid-1 kernel: mdcmd (62): check NOCORRECT
    Jan  2 00:00:07 Unraid-1 kernel: 
    Jan  2 00:00:07 Unraid-1 kernel: md: recovery thread: check P ...

    isn't a part of parity-check tuning

     

    6 minutes ago, ChatNoir said:

    Have you tried without the plugin to ensure that it is indeed an Unraid issue ?

    no, not yet.

  6. 1 hour ago, Mainfrezzer said:

    So far its been looking very good. 👍

    The Webterminal does work again on mobile (android 13, chrome) but clicking the syslog shortcut still breaks everything.
    And while im at the syslog, this is certainly new in .12.4 

    syslog.thumb.PNG.80e6e267a421ef37783a81e347993218.PNG

    this keeps on going for a while. seems to have started after the 24h dc.

     

    i think this is because of the changing ipv6 prefix. fe80 prefixes changes in germany after DC's
    so this isn't usable for a static route?

    @bonienl can you take a look into that?

    • Like 1
  7. 1 hour ago, snowy00 said:

    I Checked my router after the update an currently I have to devices with the same IP address that assigned to the Unraid Server,

     

    Are the containers still working in bridge mode?

     

    image.png.bbcba19337270ae0a1dd6f66baa16a28.png

     

    image.thumb.png.c21f5aae11074301ec2b225e2d7fd443.png

     

    It seems Unraid eth0 interface has to MAC addresses --> I use a static IP for may Unraid Server. 

     

    Ist that the Problem?

    image.thumb.png.aee98aede8f9c529b3e1e36740fd8ded.png

     

    this is normal and was the same with the old method.

    go into your unraid web terminal and type "ip address".
    then look for search for MAC-Adresses which are same like your router list with your unraid-server ip addresses

    should be look like this:

    image.thumb.png.9dbb0b95f8d0b2098be6f45a40989e11.png

    • Like 1
  8. i am not sure, but i think the routing tablet isn't correct for vhost?

    image.thumb.png.109a0313e3f70594c3256a35325bba42.png

    image.thumb.png.6f5862cdbc98c5d4ffe2dbebcf43331f.png

     

    fd00:: is my ULA which is needed for peristant hostname resolving.

    2003:c0:xxxx:xxxx:: is the prefix from my provider, which is changing from time to time. so i can't use that addresses in my local DNS for local hostname resolving.

  9. 13 minutes ago, ljm42 said:

    Having said that, I think the recommendations here are valid until we have something better:

    https://docs.unraid.net/unraid-os/release-notes/6.12.0/#known-issues

    okay, i have to say sorry, because just meant this "solution": 

     

    and you are also right, there aren't diagnostic from 6.12.3 ... there aren't any diagnostics. But also hard to post, when the server crashed ;)

     

     

     

    12 minutes ago, ljm42 said:

    Side note - one thing I keep meaning to ask folks is does your ISP *require* you to use the Fritzbox or are you allowed to replace it? In the US, ISPs give you a pretty bare bones router but you are usually allowed to replace it if you want more functionality. Not sure if it works that way everywhere or not.

     

    In germany we normaly can free use our routers, but the Fritzbox is on of the best choise for normal consumers like 99% of the people. (there are a small amount of ISP that gives you a router for their fiberline connections, that you have to use. in most cases this is a Fritzbox.)

  10. @JorgeB I did a short test, but it doen't look good:

     

    Jun  7 08:08:58 Unraid-1 kernel: docker0: port 16(vethcb01385) entered forwarding state
    Jun  7 08:09:59 Unraid-1 webGUI: Successful login user root from 192.168.0.6
    Jun  7 08:16:00 Unraid-1 root: Fix Common Problems Version 2023.04.26
    Jun  7 08:16:01 Unraid-1 root: Fix Common Problems: Warning: Docker Update Check not enabled ** Ignored
    Jun  7 08:16:22 Unraid-1 root: Fix Common Problems: Warning: The plugin un-get.plg is not known to Community Applications and is possibly incompatible with your server ** Ignored
    Jun  7 08:16:23 Unraid-1 root: Fix Common Problems: Warning: The plugin unraid-versionchange.plg is not known to Community Applications and is possibly incompatible with your server ** Ignored
    Jun  7 08:19:11 Unraid-1 kernel: ------------[ cut here ]------------
    Jun  7 08:19:11 Unraid-1 kernel: WARNING: CPU: 7 PID: 29046 at net/netfilter/nf_conntrack_core.c:1210 __nf_conntrack_confirm+0xa4/0x2b0 [nf_conntrack]
    Jun  7 08:19:11 Unraid-1 kernel: Modules linked in: cmac cifs asn1_decoder cifs_arc4 cifs_md4 dns_resolver tls nft_chain_nat xt_owner nft_compat nf_tables xt_nat xt_CHECKSUM ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle iptable_mangle vhost_net tun vhost vhost_iotlb tap macvlan xt_conntrack nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat xt_addrtype br_netfilter veth xfs xt_MASQUERADE ip6table_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nfsd auth_rpcgss oid_registry lockd grace sunrpc md_mod zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) tcp_diag inet_diag af_packet nct6775 nct6775_core hwmon_vid wireguard curve25519_x86_64 libcurve25519_generic libchacha20poly1305 chacha_x86_64 poly1305_x86_64 ip6_udp_tunnel udp_tunnel libchacha ip6table_filter ip6_tables iptable_filter ip_tables x_tables efivarfs 8021q garp mrp bridge stp llc i915 x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm iosf_mbi drm_buddy i2c_algo_bit ttm
    Jun  7 08:19:11 Unraid-1 kernel: crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel sha512_ssse3 drm_display_helper aesni_intel crypto_simd drm_kms_helper cryptd mei_hdcp mei_pxp rapl intel_cstate drm wmi_bmof mei_me nvme mpt3sas intel_uncore e1000e intel_gtt i2c_i801 agpgart nvme_core i2c_smbus cp210x mei syscopyarea i2c_core sysfillrect usbserial sysimgblt joydev raid_class fb_sys_fops scsi_transport_sas intel_pch_thermal tpm_crb video tpm_tis tpm_tis_core wmi tpm backlight acpi_tad intel_pmc_core acpi_pad button unix
    Jun  7 08:19:11 Unraid-1 kernel: CPU: 7 PID: 29046 Comm: kworker/u24:18 Tainted: P           O       6.1.32-Unraid #1
    Jun  7 08:19:11 Unraid-1 kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./H470M-ITX/ac, BIOS L1.22 12/07/2020
    Jun  7 08:19:11 Unraid-1 kernel: Workqueue: events_unbound macvlan_process_broadcast [macvlan]
    Jun  7 08:19:11 Unraid-1 kernel: RIP: 0010:__nf_conntrack_confirm+0xa4/0x2b0 [nf_conntrack]
    Jun  7 08:19:11 Unraid-1 kernel: Code: 44 24 10 e8 e2 e1 ff ff 8b 7c 24 04 89 ea 89 c6 89 04 24 e8 7e e6 ff ff 84 c0 75 a2 48 89 df e8 9b e2 ff ff 85 c0 89 c5 74 18 <0f> 0b 8b 34 24 8b 7c 24 04 e8 18 dd ff ff e8 93 e3 ff ff e9 72 01
    Jun  7 08:19:11 Unraid-1 kernel: RSP: 0018:ffffc900002a0d98 EFLAGS: 00010202
    Jun  7 08:19:11 Unraid-1 kernel: RAX: 0000000000000001 RBX: ffff8881deab9600 RCX: f50c3c8cd53db18b
    Jun  7 08:19:11 Unraid-1 kernel: RDX: 0000000000000000 RSI: 0000000000000001 RDI: ffff8881deab9600
    Jun  7 08:19:11 Unraid-1 kernel: RBP: 0000000000000001 R08: 4ec3617a21e80860 R09: 7cbf210d91d63b67
    Jun  7 08:19:11 Unraid-1 kernel: R10: ac3d1ea7a12092c9 R11: ffffc900002a0d60 R12: ffffffff82a11440
    Jun  7 08:19:11 Unraid-1 kernel: R13: 0000000000037df1 R14: ffff888102c19e00 R15: 0000000000000000
    Jun  7 08:19:11 Unraid-1 kernel: FS:  0000000000000000(0000) GS:ffff88883f7c0000(0000) knlGS:0000000000000000
    Jun  7 08:19:11 Unraid-1 kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    Jun  7 08:19:11 Unraid-1 kernel: CR2: 00007fffe876e038 CR3: 000000000420a002 CR4: 00000000007706e0
    Jun  7 08:19:11 Unraid-1 kernel: PKRU: 55555554
    Jun  7 08:19:11 Unraid-1 kernel: Call Trace:
    Jun  7 08:19:11 Unraid-1 kernel: <IRQ>
    Jun  7 08:19:11 Unraid-1 kernel: ? __warn+0xab/0x122
    Jun  7 08:19:11 Unraid-1 kernel: ? report_bug+0x109/0x17e
    Jun  7 08:19:11 Unraid-1 kernel: ? __nf_conntrack_confirm+0xa4/0x2b0 [nf_conntrack]
    Jun  7 08:19:11 Unraid-1 kernel: ? handle_bug+0x41/0x6f
    Jun  7 08:19:11 Unraid-1 kernel: ? exc_invalid_op+0x13/0x60
    Jun  7 08:19:11 Unraid-1 kernel: ? asm_exc_invalid_op+0x16/0x20
    Jun  7 08:19:11 Unraid-1 kernel: ? __nf_conntrack_confirm+0xa4/0x2b0 [nf_conntrack]
    Jun  7 08:19:11 Unraid-1 kernel: ? __nf_conntrack_confirm+0x9e/0x2b0 [nf_conntrack]
    Jun  7 08:19:11 Unraid-1 kernel: ? nf_nat_inet_fn+0x123/0x1a8 [nf_nat]
    Jun  7 08:19:11 Unraid-1 kernel: nf_conntrack_confirm+0x25/0x54 [nf_conntrack]
    Jun  7 08:19:11 Unraid-1 kernel: nf_hook_slow+0x3a/0x96
    Jun  7 08:19:11 Unraid-1 kernel: ? ip_protocol_deliver_rcu+0x164/0x164
    Jun  7 08:19:11 Unraid-1 kernel: NF_HOOK.constprop.0+0x79/0xd9
    Jun  7 08:19:11 Unraid-1 kernel: ? ip_protocol_deliver_rcu+0x164/0x164
    Jun  7 08:19:11 Unraid-1 kernel: __netif_receive_skb_one_core+0x77/0x9c
    Jun  7 08:19:11 Unraid-1 kernel: process_backlog+0x8c/0x116
    Jun  7 08:19:11 Unraid-1 kernel: __napi_poll.constprop.0+0x28/0x124
    Jun  7 08:19:11 Unraid-1 kernel: net_rx_action+0x159/0x24f
    Jun  7 08:19:11 Unraid-1 kernel: __do_softirq+0x126/0x288
    Jun  7 08:19:11 Unraid-1 kernel: do_softirq+0x7f/0xab
    Jun  7 08:19:11 Unraid-1 kernel: </IRQ>
    Jun  7 08:19:11 Unraid-1 kernel: <TASK>
    Jun  7 08:19:11 Unraid-1 kernel: __local_bh_enable_ip+0x4c/0x6b
    Jun  7 08:19:11 Unraid-1 kernel: netif_rx+0x52/0x5a
    Jun  7 08:19:11 Unraid-1 kernel: macvlan_broadcast+0x10a/0x150 [macvlan]
    Jun  7 08:19:11 Unraid-1 kernel: ? _raw_spin_unlock+0x14/0x29
    Jun  7 08:19:11 Unraid-1 kernel: macvlan_process_broadcast+0xbc/0x12f [macvlan]
    Jun  7 08:19:11 Unraid-1 kernel: process_one_work+0x1a8/0x295
    Jun  7 08:19:11 Unraid-1 kernel: worker_thread+0x18b/0x244
    Jun  7 08:19:11 Unraid-1 kernel: ? rescuer_thread+0x281/0x281
    Jun  7 08:19:11 Unraid-1 kernel: kthread+0xe4/0xef
    Jun  7 08:19:11 Unraid-1 kernel: ? kthread_complete_and_exit+0x1b/0x1b
    Jun  7 08:19:11 Unraid-1 kernel: ret_from_fork+0x1f/0x30
    Jun  7 08:19:11 Unraid-1 kernel: </TASK>
    Jun  7 08:19:11 Unraid-1 kernel: ---[ end trace 0000000000000000 ]---

     

    unraid-1-diagnostics-20230607-0825.zip

    • Like 1