MathieuBC

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

Issue was cache floor being too low, when file are above cache floor, somehow unraid fills up Docker RAM.... Anybody have explanation for such behavior ? At the moment RAM usage is up high and stays there even after reboot...

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.

Also note that I can transfer files from windows to /mnt/user/download folder without issue.... looks like Transmission is sending file to wrong place !!

I just reinstalled Transmission docker after docker.img corruption. Now everytime I start a download in Transmission I get error "No space left on device" and can't figure out why Thank you so much for your help yoda-diagnostics-20200413-0916.zip

Sorry to hijack your thread, where do you find the cache floor setting ?!?

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

Thank you for the reply tee-tee jorge, the thing is, unraid is unable to write a new docker.img into the /system/docker location. yoda-diagnostics-20200412-0619.zip

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

Here is complete diagnostic. Thank you yoda-diagnostics-20200106-2207.zip

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