Wingold

Members
  • Posts

    15
  • Joined

  • Last visited

Posts posted by Wingold

  1. How to recognize on the picture I have the problem that my Docker image from time to time is always fully running but is also emptied again automatically. I suppose it is due to my Plex container, but I could not prove the notcht because the error here occurs irregularly sometimes 2 times a day sometimes 2 weeks.
    Does anyone have any idea how I can locate and fix the bug?

    BR Wingold

     

    848870935_Unraidfehler.PNG.c189386e5dd386e7b16b399f7fb1e8fb.PNG

    1465027536_Unraidfehler2.thumb.PNG.44bf0eb425724497f9997766163eacf0.PNG
    The Presentage is driving up rapidly and then comeing down again after sone time

    homeserver-diagnostics-20210712-2132.zip

  2. I checked the Bios configuration, the c-state was already disabled and the Power Supply Idle Control was already set to the typical Idle power as in the post. I also checked the memory, it is running at 2133Mhz. Then I had the system search for an updated bios and installed it, but it didn’t help. The system’s crashing all the time.

  3. After Changign the Cachefile to XFS the System was fine for 2days but yesterday at 19:13 the system crashed again this time the last lines where this instead of the BTRFS Error.

    Dec  8 19:13:16 Homeserver kernel: Call Trace:
    Dec  8 19:13:16 Homeserver kernel: _raw_spin_lock_irqsave+0x29/0x31
    Dec  8 19:13:16 Homeserver kernel: __test_set_page_writeback+0x7a/0x37c
    Dec  8 19:13:16 Homeserver kernel: ? clear_page_dirty_for_io+0x7e/0x25a
    Dec  8 19:13:16 Homeserver kernel: xfs_do_writepage+0x20a/0x2f4 [xfs]
    Dec  8 19:13:16 Homeserver kernel: write_cache_pages+0x21e/0x2e2
    Dec  8 19:13:16 Homeserver kernel: ? xfs_vm_writepages+0x92/0x92 [xfs]
    Dec  8 19:13:16 Homeserver kernel: xfs_vm_writepages+0x5e/0x92 [xfs]
    Dec  8 19:13:16 Homeserver kernel: do_writepages+0x28/0x51
    Dec  8 19:13:16 Homeserver kernel: __writeback_single_inode+0x36/0x15a
    Dec  8 19:13:16 Homeserver kernel: writeback_sb_inodes+0x1e7/0x373
    Dec  8 19:13:16 Homeserver kernel: __writeback_inodes_wb+0x63/0x9a
    Dec  8 19:13:16 Homeserver kernel: wb_writeback+0x11f/0x1c3
    Dec  8 19:13:16 Homeserver kernel: wb_workfn+0x1d1/0x253
    Dec  8 19:13:16 Homeserver kernel: process_one_work+0x16e/0x24f
    Dec  8 19:13:16 Homeserver kernel: worker_thread+0x1e2/0x2b8
    Dec  8 19:13:16 Homeserver kernel: ? rescuer_thread+0x2a7/0x2a7
    Dec  8 19:13:16 Homeserver kernel: kthread+0x10c/0x114
    Dec  8 19:13:16 Homeserver kernel: ? kthread_park+0x89/0x89
    Dec  8 19:13:16 Homeserver kernel: ret_from_fork+0x22/0x40

    The Last Thing I was doing, was moving Files From an UAD Drive to the Array via MC
     

    syslog-1

  4. Hello togehter,

     

    my Unraid Sever keeps Crashing. From on to the other Moment i can´t reach the guy any docker/VM or the SMB share even trying to log on via SSH isn´t possible the only way to fix it is Hard resseting the System.

     

    In the Systemlogs i found some error of the NVME SSD but i dont´t know if this is the reason for the crashes an what i can do to fix it.

    Dec  2 21:19:01 Homeserver kernel: BTRFS critical (device nvme0n1p1): corrupt leaf: root=5 block=87605248 slot=89, unexpected item end, have 805314679 expect 8311

     

    syslog

    homeserver-diagnostics-20201205-2046.zip

  5. Hello Jungle you can stop the plex container at your site for a while and see if the server still crashes. If this is not the case, I would activate it again if there is another crash. There's a very high probability that that's what it is. In my case it is unfortunately not the Plex Docker which is why I am still looking for the cause.

  6. On 3/19/2020 at 8:47 PM, horrorhound said:

    Turns out to be plex docker crashing the server each night during it's maintenance run.  I've tried both binhex and linuxserver docker versions of plex and they both crash the server... Still trying to figure out why.

    Hi i have the same Problem at the Moment so my Unraid keeps crashing every night. Do you have found a fix for  issue with the maintenance run?

  7. On 7/8/2020 at 11:16 PM, muwahhid said:

    Hello. I want to share, because I myself was looking for Old.
    I have NextCloud production, nextcloud repository: production-apache. Version 17.

    1. I entered the script from the topic in the terminal

    sysctl -w vm.max_map_count=262144

     

    2. I installed 4 plug-ins with a magnifier in the NextCloud, on the NextCloud web.
     

    3. I installed the plugin for NextCloud.
    ingest-attachment
    Entered in the terminal:

     

    docker exec -it elasticsearch bash /usr/share/elasticsearch/bin/elasticsearch-plugin install ingest-attachment

     

    4. Then I made the settings in NextCloud, as in the photo.
     

    5. Then started indexing. In terminal:
     

    docker exec --user www-data nextcloud php occ fulltextsearch:index

    ______________
    I hope this helps someone.

     

    page 3.jpg

    page 2.jpg

    1 Page.jpg

    Page 0.jpg

    Thank you for your help is worked so far for me exept of the last step when i want to start with the indexing it give me de following error


    root@Homeserver:~# docker exec --user www-data nextcloud php occ fulltextsearch:index
    unable to find user www-data: no matching entries in passwd file

    do you haven an Idea what i have to do to solve this error?

  8. No it is disabled on both Systems in the picture below you can see my settings.

    These are the same Settings as on the other System which is working just fine.

     

    I turned it on and tried angain but still no option of custom Networks.

    image.thumb.png.0ac6415018aa1014ffd4ffee9c6e1613.png