Jump to content
  • UNRaid server frequently lost response


    latelx
    • Urgent

    My Unraid server frequently becomes unresponsive, with the hardware fans continuing to run loudly even though access to the Unraid WebUI and Docker services is lost. Additionally, active SSH connections are disrupted, preventing any further login attempts. I have redirected the Unraid syslog to the array appdata, yet each time, I fail to identify any significant information within.

     

    On this occasion, the server became unresponsive at 5:57 AM, and I proceeded to reboot it at 8:50 AM:

    Apr 10 04:37:02 Tower apcupsd[4390]: Communications with UPS lost.
    Apr 10 04:38:42 Tower emhttpd: spinning down /dev/sdf
    Apr 10 04:38:46 Tower emhttpd: spinning down /dev/sdi
    Apr 10 04:39:06 Tower emhttpd: spinning down /dev/sdh
    Apr 10 04:47:05 Tower apcupsd[4390]: Communications with UPS lost.
    Apr 10 04:50:14 Tower emhttpd: read SMART /dev/sdh
    Apr 10 04:50:32 Tower emhttpd: read SMART /dev/sdi
    Apr 10 04:50:45 Tower emhttpd: read SMART /dev/sdf
    Apr 10 04:57:09 Tower apcupsd[4390]: Communications with UPS lost.
    Apr 10 05:05:58 Tower emhttpd: spinning down /dev/sdh
    Apr 10 05:06:00 Tower emhttpd: spinning down /dev/sdf
    Apr 10 05:06:03 Tower emhttpd: spinning down /dev/sdi
    Apr 10 05:07:13 Tower apcupsd[4390]: Communications with UPS lost.
    Apr 10 05:17:17 Tower apcupsd[4390]: Communications with UPS lost.
    Apr 10 05:27:21 Tower apcupsd[4390]: Communications with UPS lost.
    Apr 10 05:37:25 Tower apcupsd[4390]: Communications with UPS lost.
    Apr 10 05:47:29 Tower apcupsd[4390]: Communications with UPS lost.
    Apr 10 05:57:33 Tower apcupsd[4390]: Communications with UPS lost.
    Apr 10 08:50:45 Tower file.activity: Starting File Activity
    Apr 10 08:50:45 Tower emhttpd: Starting File Activity...
    Apr 10 08:50:45 Tower file.activity: File Activity inotify starting
    Apr 10 08:50:45 Tower inotifywait[10880]: Setting up watches.  Beware: since -r was given, this may take a while!
    Apr 10 08:50:46 Tower rsyslogd: [origin software="rsyslogd" swVersion="8.2102.0" x-pid="10863" x-info="https://www.rsyslog.com"] start
    Apr 10 08:50:47 Tower network: reload service: nginx
    Apr 10 08:50:47 Tower unassigned.devices: Mounting 'Auto Mount' Devices...
    Apr 10 08:50:47 Tower unassigned.devices: Mounting partition 'sda1' at mountpoint '/mnt/disks/EFI'...
    Apr 10 08:50:47 Tower unassigned.devices: Mount cmd: /sbin/mount -t 'vfat' -o rw,relatime,nodev,nosuid,iocharset=utf8,umask=000 '/dev/sda1' '/mnt/disks/EFI'
    Apr 10 08:50:47 Tower kernel: FAT-fs (sda1): utf8 is not a recommended IO charset for FAT filesystems, files

     

    I'm experiencing an issue once or twice daily, How can I further investigate this issue? Could it be related to the SSD cache overheating, or is there another potential cause?

     

    I have also made the notification files permanent, and I observed that there were no heating warnings around 5 AM.

    image.thumb.png.e34ddd024a6e12269603d5e500c634c8.png

     

    tower-diagnostics-20240410-1007.zip




    User Feedback

    Recommended Comments

    Apr  9 22:29:07 Tower kernel: macvlan_broadcast+0x10a/0x150 [macvlan]
    Apr  9 22:29:07 Tower kernel: ? _raw_spin_unlock+0x14/0x29
    Apr  9 22:29:07 Tower kernel: macvlan_process_broadcast+0xbc/0x12f [macvlan]

    Macvlan call traces will usually end up crashing the server, switching to ipvlan should fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enabled, top right)), then reboot.

    Link to comment
    3 hours ago, JorgeB said:
    Apr  9 22:29:07 Tower kernel: macvlan_broadcast+0x10a/0x150 [macvlan]
    Apr  9 22:29:07 Tower kernel: ? _raw_spin_unlock+0x14/0x29
    Apr  9 22:29:07 Tower kernel: macvlan_process_broadcast+0xbc/0x12f [macvlan]

    Macvlan call traces will usually end up crashing the server, switching to ipvlan should fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enabled, top right)), then reboot.

     

    Since the initial setup of my server, I've configured Macvlan. However, it's only recently that the server has become unstable.

    I deployed a Docker service called Scrypted, which streams my Onvif camera stream to Homekit, necessitating a fixed IP address. To achieve this, I assigned a fixed IP address through DHCP using the MAC address, so Macvlan is an indispensable choice.

    Link to comment


    Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.
    Note: Your post will require moderator approval before it will be visible.

    Guest
    Add a comment...

    ×   Pasted as rich text.   Restore formatting

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.


  • Status Definitions

     

    Open = Under consideration.

     

    Solved = The issue has been resolved.

     

    Solved version = The issue has been resolved in the indicated release version.

     

    Closed = Feedback or opinion better posted on our forum for discussion. Also for reports we cannot reproduce or need more information. In this case just add a comment and we will review it again.

     

    Retest = Please retest in latest release.


    Priority Definitions

     

    Minor = Something not working correctly.

     

    Urgent = Server crash, data loss, or other showstopper.

     

    Annoyance = Doesn't affect functionality but should be fixed.

     

    Other = Announcement or other non-issue.

×
×
  • Create New...