NewDisplayName

Members
  • Posts

    2280
  • Joined

  • Last visited

  • Days Won

    1

Report Comments posted by NewDisplayName

  1. 14 hours ago, ljm42 said:

    Please take another look at the 6.12.4-rc18 announce post, the whole goal of the changes in this release is to allow users to enable macvlan.

     

    If you are fine using ipvlan, then you can use the default settings that Unraid ships with:
    * Settings -> Network Settings -> eth0 -> Enable Bridging = Yes
    * Settings -> Docker -> Docker custom network type = ipvlan

     

    If ipvlan doesn't work for you (some example reasons are in the announce post) then you can enable macvlan by using the new settings from the announce post.


    It is difficult to guess why the system crashed, I'd recommend enabling this: Settings -> Syslog Server -> Mirror syslog to flash. If there is a crash you will find the syslog in the logs folder on your flash drive. Note that you should not run in this mode long term as it does increase writes to the flash drive.

    Please upload both the diagnostics and that syslog if there are issues.

    Thank you for your fast response.

     

    Like i said i already enabled log again.

     

    Its advised to use ipvlan, thats what ive set docker to. Question is why is that:

    Quote

     


    root@Unraid-Server:~# docker network ls
    NETWORK ID     NAME                  DRIVER    SCOPE
    263e8f1295d3   bridge                bridge    local
    d05eb8ca1c65   eth0                  macvlan   local
    ba7d287b5243   name                bridge    local
    c426a08021c6   host                  host      local
    d2b93c4c6a03   none                  null      local
    04fb1877a554   webserver_webserver   bridge    local

     

     

    When i set it to ipvlan?

     

    In which config file i can look which config is really set? You know i had the problem that unraid didnt removed debrie out of the network.cfg once i removed my 2. network card, so i wanna make sure its correctly in that .cfg.

     

    Since i didnt had problem with ipvlan (its was enabled even before upgrading to RC) i would rather go with the recommended setup. / if that changes, i might go back to macvlan.

  2. 1 minute ago, a632079 said:

    🤥Frankly speaking, I also don't know what the official team is doing. If they are working on a new test version, perhaps releasing it in the "next" channel for us to test whether the issues have been resolved might be a better idea? However, in reality, they haven't done that.

     

    Another issue related to Docker IPv6 in version 6.12 was also ignored by the official team until I audited the script myself and found the root cause of the problem. At that point, they finally responded to that issue.

     

    However, I'm not an expert in operating systems and don't have access to unraid's source code. Moreover, I'm just an ordinary consumer who has paid for the license, and I'm not obligated to help unraid solve these issues 😌.

     

    Yeah, communication was always their problem. We dont know if they know what the issue is, or if they have no time, or what ever. 

     

    But that doesnt mean they need to have that as stable up, letting more and more ppl update to "STABLE" (!!!!) while there are clearly HEAVY bugs like freezing and crashing. I mean, wtf?

  3. 2 minutes ago, SimonF said:

    This reponse was for the syslog I have just reviewed. Each one may not have the same faults. Please feel free to sjpport and review code in the github repo.

    Oh sorry, im the wrong person.

     

    I posted my crashs months ago, googled errors, posted links to known issues related to linux and those errors - without a response (and before their team is again flaming me, lets just say not the response i was hoping for) - cant say how helpful it was tho.

  4. I don't even have the nerve anymore to talk about this whole ...

     

    Youre right lim answered, but literally NOTHING about my problem, we just chatted about the "why unraid has wrong ip" thing. This answer, came how many days after i posted this and direct sent it to you via feedback?

     

    As long as unraid is working as expected all is good, but if not, your on your own, even if you provide all details and do what asked. And that is a fact.

     

    If you would use as much time on threads or reviewing/answering emails you use to defend yourself (or attack me), then we wouldnt have this problem.

     

    AND STILL no one answered if this problem is now fixed or not, its like im talking to a wall.

     

    I dont understand it.

     

    Maybe you should use a ticket system or something.

     

    I see everyday the same problems with unraid since 6.12 popping up in facebook or here in the forums and it doesnt seem like you guys want to fix it (or see the problem)... and if these problems are still there, your still saying 6.12 is a major release, update.

     

    -Freezing (even with ipvlan)

    -"no internet" (some DNS issue)

  5. I can confirm it doesnt crash anymore, instead if just looses connectifity atleast partly (you always know when 

    "Unraid-Server

    Unraid API Error

    CLOUD: Socket closed" shows up on top right)


    Also logs show

    Jul 12 19:31:32 Unraid-Server root: SabNZBd: Could not download icon https://raw.githubusercontent.com/linuxserver/docker-templates/master/linuxserver.io/img/sabnzbd-logo.png
    Jul 12 19:31:49 Unraid-Server root: SabNZBd: Could not download icon https://raw.githubusercontent.com/linuxserver/docker-templates/master/linuxserver.io/img/sabnzbd-logo.png
    Jul 12 19:33:49 Unraid-Server root: SabNZBd: Could not download icon https://raw.githubusercontent.com/linuxserver/docker-templates/master/linuxserver.io/img/sabnzbd-logo.png
    Jul 12 19:34:05 Unraid-Server root: SabNZBd: Could not download icon https://raw.githubusercontent.com/linuxserver/docker-templates/master/linuxserver.io/img/sabnzbd-logo.png
    Jul 12 19:35:54 Unraid-Server root: SabNZBd: Could not download icon https://raw.githubusercontent.com/linuxserver/docker-templates/master/linuxserver.io/img/sabnzbd-logo.png
    Jul 12 19:36:10 Unraid-Server root: SabNZBd: Could not download icon https://raw.githubusercontent.com/linuxserver/docker-templates/master/linuxserver.io/img/sabnzbd-logo.png

     

    The best thing is while it cant reach a URL IT WILL LITERALLY FREEZE unraid till it times out... network restart didnt help, i have to restart every time (sometimes once a day, sometimes it works for some days)

     

    Still not a answer from devs, sad, they could atleast tell us, they know theres somethign wrong and they work on it, i dont get it.

     

    Sometimes some dockers partly still work, like i can reach plex (via internet), but cant play anything. 

    • Upvote 1
  6. 3 minutes ago, ljm42 said:

    Thanks. The router is giving Unraid a different IP though, 192.168.0.21, right? Please look in your router's interface for that IP address and post a screenshot

    After i removed the file and restartet it didnt took the dhcp (or the fritz didnt gave the correct one - your theory), which i doubt since all other stuff worked 110% - im using these routers since 20 years.

     

    Im looking thru the syslog for dhcp now...

     

    Jun 26 20:14:24 Unraid-Server dnsmasq[11178]: started, version 2.89 cachesize 150
    Jun 26 20:14:24 Unraid-Server dnsmasq[11178]: compile time options: IPv6 GNU-getopt DBus no-UBus i18n IDN2 DHCP DHCPv6 no-Lua TFTP conntrack ipset no-nftset auth cryptohash DNSSEC loop-detect inotify dumpfile
    Jun 26 20:14:24 Unraid-Server dnsmasq-dhcp[11178]: DHCP, IP range 192.168.122.2 -- 192.168.122.254, lease time 1h

     

    Jun 28 03:10:44 Unraid-Server dnsmasq[17708]: started, version 2.89 cachesize 150
    Jun 28 03:10:44 Unraid-Server dnsmasq[17708]: compile time options: IPv6 GNU-getopt DBus no-UBus i18n IDN2 DHCP DHCPv6 no-Lua TFTP conntrack ipset no-nftset auth cryptohash DNSSEC loop-detect inotify dumpfile
    Jun 28 03:10:44 Unraid-Server dnsmasq-dhcp[17708]: DHCP, IP range 192.168.122.2 -- 192.168.122.254, lease time 1h
    Jun 28 03:10:44 Unraid-Server dnsmasq-dhcp[17708]: DHCP, sockets bound exclusively to interface virbr0

     

     

    Jun 29 23:56:06 Unraid-Server dhcpcd[1341]: dhcpcd-9.4.1 starting
    Jun 29 23:56:06 Unraid-Server dhcpcd[1344]: DUID 00:04:ba:d0:e4:00:72:ba:11:e3:b1:7d:9c:5c:8e:87:c4:08
    Jun 29 23:56:06 Unraid-Server kernel: 8021q: 802.1Q VLAN Support v1.8
    Jun 29 23:56:06 Unraid-Server kernel: 8021q: adding VLAN 0 to HW filter on device bond0
    Jun 29 23:56:06 Unraid-Server dhcpcd[1344]: br0: soliciting a DHCP lease
    Jun 29 23:56:06 Unraid-Server kernel: NET: Registered PF_PACKET protocol family
    Jun 29 23:56:06 Unraid-Server dhcpcd[1344]: br0: offered 192.168.0.21 from 192.168.0.1
    Jun 29 23:56:06 Unraid-Server dhcpcd[1344]: br0: probing address 192.168.0.21/24
    Jun 29 23:56:12 Unraid-Server dhcpcd[1344]: br0: leased 192.168.0.21 for 864000 seconds
    Jun 29 23:56:12 Unraid-Server dhcpcd[1344]: br0: adding route to 192.168.0.0/24
    Jun 29 23:56:12 Unraid-Server dhcpcd[1344]: br0: adding default route via 192.168.0.1

    Jun 29 23:56:12 Unraid-Server rc.inet1: ip link set br0 up

     

    maybe its really about vlan shit

     

     

  7. 3 minutes ago, ljm42 said:

     

    Unraid works fine with DHCP

     

    You simply have to make sure the router is setup to use the correct MAC address for the DHCP lease


    Its a consumer router,  i posted already what we can see. There is nothing to do wrong.. xD

     

    2 minutes ago, Zeze21 said:

    Are you using docker? then I am quite certain you are using either ipvlan or macvlan

     

    I also posted a picture that im u sing ipvlan (since thats what all suggest)

     

    image.thumb.png.cc05d39b1ea78f054cfff9b2a5af87ba.png

     

    image.thumb.png.4c72946da8e55046da536ac7683cc42d.png

  8. I dont really understand how that can be a portainer problem when it was working for,  i dont know 5 years? Oo Only after switching to 6.12 problems startet. It is also a bug that unraid doesnt remove the extra nic configs when a nic is removed. anway.

     

    Anyway, the router is one of the most used routers in germany, i dont think thats the problem, also  i dont care, it has now a fixed ip again. I just wanted to report it incase unraid want to fix it.

     

    Im currently not facing any problems after removing the nic config and updating to 6.12.2. I guess well see in some days.

     

    When do you want the diag, before crash, or after?

     

     

  9. Im not technical enought to understand the problem:

     

    1.) i mean why do unraid still have 192.168.3 in his tables, if the network card is removed?


    there is only one phys. connection 192.168.0

     

    2.) if macvlan is disabled, why does it make problems?

     

    3.) can i maybe fix this thru MB and CPU swap? (i have spare parts for upgrade anyway)

  10. Here is finally a log, which shows literally nothing.  On screen was again the same message as always.

     

    Quote

    Jun 28 03:41:34 Unraid-Server kernel: BTRFS info (device dm-8): scrub: finished on devid 1 with status: 0
    Jun 28 03:41:34 Unraid-Server kernel: BTRFS info (device dm-8): scrub: finished on devid 2 with status: 0
    Jun 28 19:11:50 Unraid-Server kernel: microcode: microcode updated early to revision 0xf0, date = 2021-11-12
    Jun 28 19:11:50 Unraid-Server kernel: Linux version 6.1.34-Unraid (root@Develop) (gcc (GCC) 12.2.0, GNU ld version 2.40-slack151) #1 SMP PREEMPT_DYNAMIC Fri Jun 16 11:48:38 PDT 2023

     


     

    syslog (1).txt