MathieuBC

Members
 View Profile  See their activity

  • Posts

    11

  • Joined

  • Last visited

 Content Type 

Posts posted by MathieuBC

    [Possibly solved] [6.8.3] Transmission docker running out of space while array and cache has plenty of space left

    in General Support

    Posted

    2 hours ago, Dissones4U said:
    • Make a new post for your other issues, this one says [Possibly solved] in the title so people may not even look at it
    • Post diagnostics with your new request for help
    • Describe your scenario in detail, include recent changes to hardware, software, share settings etc

    You can do several things:

    • Set share temporarily to cache = no
    • For a large folder with multiple files (Episodic TV seasons) increase mover frequency

    We'd need to see settings for the share in question, I'm not sure why it would be writing into RAM as that will disappear on reboot

    Yes sorry I did create a seperate post here with logs and details.

     

    [Possibly solved] [6.8.3] Transmission docker running out of space while array and cache has plenty of space left

    in General Support

    Posted

    3 hours ago, Dissones4U said:

    settings ==> global share settings (under system settings) ==> scroll down to cache settings = min free space (Array must be Stopped to change)

    Thank you for your answer that also solved my issue, now what if I want to download a file that is larger than my cache drive ? I have set my download Share to not use cache but now it's filling ram instead !! I am back to square one.

    Docker Service failed to start

    in General Support

    Posted

    1 hour ago, johnnie.black said:

    Yep, that's why I mentioned posting the complete diags, cache filesystem is also corrupt, you need to backup and recreate cache filesystem, note that checksum errors are usually a sign of bad hardware, like bad RAM.

    Hmmm ok great thank you for looking it up for me.

    Docker Service failed to start

    in General Support

    Posted

    This issue started today after power shutdown. When going into Docker tab I have error Docker Service failed to start.

     

    My docker.img file is missing from /mnt/user/system/docker and unraid is unable to create a new one. When I change directory for docker creation it works fine but not inside system directory. In log I see this :

     

    Apr 11 20:49:44 Yoda root: Starting Samba: /usr/sbin/smbd -D
    Apr 11 20:49:44 Yoda root: /usr/sbin/nmbd -D
    Apr 11 20:49:44 Yoda root: /usr/sbin/wsdd
    Apr 11 20:49:44 Yoda root: /usr/sbin/winbindd -D
    Apr 11 20:49:44 Yoda emhttpd: shcmd (1198): /usr/local/sbin/mount_image '/mnt/user/system/docker/docker.img' /var/lib/docker 20
    Apr 11 20:49:44 Yoda root: Creating new image file: /mnt/user/system/docker/docker.img size: 20G
    Apr 11 20:49:44 Yoda kernel: BTRFS warning (device sdg1): sdg1 checksum verify failed on 370032640 wanted 44247587 found 8F4B5078 level 0
    Apr 11 20:49:44 Yoda root: touch: cannot touch '/mnt/user/system/docker/docker.img': Input/output error
    Apr 11 20:49:44 Yoda kernel: BTRFS warning (device sdg1): sdg1 checksum verify failed on 370032640 wanted 44247587 found 8F4B5078 level 0
    Apr 11 20:49:44 Yoda kernel: BTRFS warning (device sdg1): sdg1 checksum verify failed on 370032640 wanted 44247587 found 8F4B5078 level 0
    Apr 11 20:49:44 Yoda kernel: BTRFS warning (device sdg1): sdg1 checksum verify failed on 370032640 wanted 44247587 found 8F4B5078 level 0
    Apr 11 20:49:44 Yoda kernel: BTRFS warning (device sdg1): sdg1 checksum verify failed on 370032640 wanted 44247587 found 8F4B5078 level 0
    Apr 11 20:49:44 Yoda kernel: BTRFS warning (device sdg1): sdg1 checksum verify failed on 370032640 wanted 44247587 found 8F4B5078 level 0
    Apr 11 20:49:44 Yoda root: failed to create image file
    Apr 11 20:49:44 Yoda kernel: BTRFS warning (device sdg1): sdg1 checksum verify failed on 370032640 wanted 44247587 found 8F4B5078 level 0
    Apr 11 20:49:44 Yoda emhttpd: shcmd (1198): exit status: 1
    Apr 11 20:49:44 Yoda kernel: BTRFS warning (device sdg1): sdg1 checksum verify failed on 370032640 wanted 44247587 found 8F4B5078 level 0
    Apr 11 20:49:44 Yoda kernel: BTRFS warning (device sdg1): sdg1 checksum verify failed on 370032640 wanted 44247587 found 8F4B5078 level 0

     

    I thought it was problem with cache so I set system directory to not use cache but still same issue.

     

    Thank you for your help

    Disk on SATA CARD not detected

    in General Support

    Posted

    Currently in the process of making my first unraid server. Motherboard is ASRock AM1H-ITX and using SATA card  https://www.amazon.ca/-/fr/gp/product/B07T66ZXMT/ref=ppx_yo_dt_b_asin_title_o04_s01?ie=UTF8&th=1

     

    My SATA is using ASM1061 chipset which should be supported by unraid. 

     

    The disk connected to the motherboard are all detected fine, the disks connected to the SATA card are not detected by UNRAID. They are detected during boot but can see errors in UNRAID log which I am unable to "translate".

     

    Anybody can take a look at my log ?

     

    Thank you !

     

    https://mega.nz/?fbclid=IwAR1-YrqA3WGihdAvV_ImBVhMd6E8bO76MZoQoqyWpUB-cBzGz9ybWe9AZPU#!1x9hmKhC!T_skrk_326qtfH-nNhnwRs0esJEHHV6eYXRDv8hZzoM

    tower-syslog-20200107-0214.zip