Posts by mxr

    unless your /etc/apt/sources.list has "stable" or "buster" in the repo lines, you will never upgrade to buster. If you are worried about the upgrade, I suggest backing up the system.

    Thanks! Always learning! My sources.list has only "stretch" in it (stretch, stretch-updates, stretch/updates).

    Probably a silly question, but is it safe to install all updates offered under "Update Management"? In particular packages that have "next" in their names like "linux-u-boot-helios4-next 5.91". I'm running Arrakis 4.1.35-1 on Armbian Stretch on a Helios 4 (ARMv7) and do not want to accidentally start an upgrading process to Armbian Next (i.e. Debian 10 Buster).

    I finally resolved the problem by building the lsioarmhf/plex container myself. The underlying plexmediaserver-installer package is built either using the Netgear or Synology build. The fact that the log shows "Illegal instruction" probably indicates that the lsioarmhf/plex container available on the Docker Hub is built using the build which is not supported by my board. For me it is the Synology build that worked (which also seems to be the build for the OMV Plex plugin).

    I tried to disable IPv6 in the container, but without much success. Would it even make a difference if host networking mode is used?

    I went back and tried to disable IPv6 completely in the host, but without much success either. Using "armbian-config" I tried disabling IPv6, but after reboot NM created a new Wired Connection 2 and shows again an inet6 line when running "ip addr show".

    Why? Since NM is evil?
    When I did a quick google search for the issue described above the solution seems to be to disable IPv6 in the Docker container.

    Yes, it seems to be related to IPv6. I will try disabling IPv6 in the container as you say. So far I only tried disabling IPv6 in the host.

    I'm not saying that NM is evil. It just takes some time to get used to it and figure out how the configuring works.

    I am experiencing exactly the same issue, but have not been able to find a solution yet. At the moment my best guess is that the problem could be caused by NetworkManager which is enabled by default on my Helios4 ARM build.

    How can I downgrade from 2.0.5 to 1.9? Yesterday I encountered the apt sources error and after fixing that I ran one command too many :) After the upgrade media plugins Sickbeard and CouchPotato became unresponsive in the webgui (could not really enable or disable, pressing the save button did not work and webgui menu became unresponsive after that until refreshed).

    Update: Decided to post my question into a separate thread.

    is it not a fight about which device has to become MasterBrowser?
    try to see with the command smbtree what has been broadcasted.
    I can remember that when devices do battle about becoming MasterBrowser that in some situations Windows cannot detect a device automatically.
    Long time ago I had a printserver causing devices not being detected correctly when it was turned on. In the end rebooting various devices in different order gave the solution.

    Will give it a try. I did notice that everything was working again once my local network had been down for some time. I was reconfiguring my router and as a result many devices where offline for longer time and then I added them back one by one and discovery was working properly again.

    Just letting you know guys that Samba started to advertise itself again. Then it disappeared again, then it reappeared again. I am not able to reproduce this behavior.

    Workgroup is the same for all computers and Samba. Maybe let's just wait and see until next releases. Maybe some bug is discovered. As far as I know I am not the only one experiencing this issue. The shares work like a charm it is just that OMV is not being detected anymore by Windows computers in the Network section. As far as I remember it did not happen when I was enabling the WINS server and specifying the OMV address as a WINS server to DHCP clients in my router, but a few weeks after that and some updates to OMV and other updates. Maybe there was even a Samba update in between.

    Yes, still no luck. I even tried to take a spare good old Linksys WRT54GL with fresh NVRAM erase and settings as default as they could be and connected my Windows computers to that, but OMV was still not showing up. But all other Windows 7 computers on the network are being detected and I have like 4 or 5 of them. So we are back to Samba in my opinion.

    All the machines are Windows 7. I have to admit that this issue came up after I was playing for some time with WINS setting. Basically I had Local Master Browser, Time Server and WINS server enabled and in my router I let DHCP include the WINS server (OMV) IP. In the beginning everything was working until it stopped working.

    Now I tried to disable Local Master Browser, Time Server and WINS and also removed the WINS server IP from DHCP configuration, restarted the router and Samba as well, but the OMV machine is still not showing up in Network.

    Also the machine is not visible anymore in Kodi.

    Here is the values part of smartctl

    For a couple of days already Samba is not advertising itself to Windows client's anymore. Today I received 'Panic or Segfault in Samba' e-mail. Don't know if these things are connected though. My system drive is a couple of months old Crucial M550 SSD. Any ideas?