likesboc

Members
  • Posts

    25
  • Joined

likesboc's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. i see, this could be it, it was multiple files. circumventing the cache drive appears the only valid option in this case. thanks for the guidance!
  2. I'm trying to manage a download that is larger than my cache drive. It is being downloaded into a share that uses the "Yes : Cache" Setting. Thus i thought it would use up all available space (900/1000gb see the setting from above) and then overflow into the array. It didn't though. For the transfer i'm targeting my share located at "/mnt/user/downloads/" - if i understand it right this shouldn't bypass the set limit of keeping 100gb free.
  3. sadly it happened again, that setting did not prevent the cache from filling up. am i doing something wrong?
  4. I'm still facng this issue. What can i do to follow up on this? Every monday morning those docker containers are shutdown although they are excluded through the "excluded folder" option. Any help is appreciated.
  5. I'm running 6.9.2, that global pool setting is what i was looking for. I could swear i had this set already. What put me using it off before was the "not enought space error" that is mentioned in the description. I set it to 100GB and i hope this means it will overflow when it only has this amount left. Thank you very much for your help!
  6. I have various shares using the cache drive. How can i achieve that they don't fill it up completely? The "minimum free space" setting doesn't make sense to me as it only applies to single files? I'd like all the shares on my cache drive to use up 80% of my cache so that i never run the risk of having dockers or other system shares halt.
  7. Hi, i need to manage a download larger than my cache drive. I vaguely remember having set a max usage limit to 80% of the cache drive but can't seem to find it anymore. I thought the cache would fill up and overflow to the diskshare after it reached this limit, thus the huge download wouldn't be a problem. In reality the cache drive filled up to 100% all dockers crashed and i had to reboot the whole system How can i resolve this? I want to keep using the cache drive for downloads, offloading per mover at night. Thanks! diagnostics-20210510-1825.zip
  8. Alright, thank you for your tip, i'll check it out. Thanks!
  9. Hi, i'm facing "Parity - ST8000DM004-2CX188_ZCT3**** (sde) - active 33 C (disk has read errors) [NOK]". The array overview shows 169 read errors. I did a full parity check than ran through without any errors, i am using two parity disks. The nightly array report states "fail" though. What do i do? Any help is appreciated! Regards
  10. hi, i'm facing the problem that some dockers do not turn on again after the backup. every monday morning, after my sunday night backup, i see that "binhex-jacket" and "binhexx-radarr" are turned off. how can i find out what is causing this? thanks!
  11. hi, thanks for the tip. turns out the ssd i got was indeed faulty. i noticed that it was running hot, but didn't think any more of it. i changed the ssd for the cache and now the system performs much better. using the mover is still slowish, but it's not killing the whole OS. thanks again! cheers
  12. i have a hard time following those new changes. i'm running sonarr through rtorrentvpn, with the ip tables change i need to adjust the container networks if i understoof correctly. i'm following A24, trying to remove Host Port 1 and 2 from the Docker Container but those fields are not allowed to be empty. what can i do?
  13. hi! i'm a new unraid user and liking the system very much so far. i'm moving from a synology ds, built a cheapish 40tb desktop nas and am in the process of moving all applications and data to my new unraid system. in the past 2 weeks i've researched everything that was needed for the initial setup, tried and configured different dockers and became familiar with most of its options. i've followed besst practices where i could. now, after 14 days i'm stuck with issues i ran into and am asking for support/feedback. it is moving data, using cache, using dockers that give me quite the headache because the system becomes unusuable when those issues appear. -the system becomes unusable slow when running the mover. webui is not reacting, dockers not reacting, sometimes crashing. i am now running the mover at night. it's not a super big issue but it leaves a sour aftertaste. -moving data manually peaks the cpu with 100% on single cores, sometimes many cores. moving data generally is a pain, it appears it's cpu or IO issues. -this also happens while normal operation. sometimes rutorrent bugs out although it is barely doing anything. also using 100% cpu, i kinda suspect this happens also when it moves data (fo the finished folder). -when these issues appear other applications are affected, namely when rutorrent bugs out or the mover is running, plex dies on me, which is quite frustrating to say the least. - 4 out of my 10 drives are spinning all the time. my understanding is that using the cache drive the array disks would only need to spin up at night when the mover is running. in the past 2 weeks the 2 parity drives and the first two data drives (where all my data is) never spun down. with all this happening i thought i split the mdeia folder in two, to circumvent all those ssd cache problems, leaving only appdata and downloads cached, creating a new library share that holds all media on the array without any caching at all. while this is doable i guess, it would also kinda leave a sour aftertaste because i'd have it stuck in the back of my head that there is a cache ssd issue and i can't fully use the cache feature. also it would mean that my array disks would be spun up most of the time which would mean a couple of additional drawbacks (energy, noise, lifetime). my question with those issues now are: -is there a general ssd cache writing data bug that i'm running into? can i somehow resolve this? what can i do to figure it out? -is my setup correct or did i maybe make something wrong causing those issues i described? did i miss any best practices? thank you very much for any feedback and support, looking forward on becoming a happy unraid user unraid-diagnostics-20210221-1325.zip
  14. does it make sense to disable the cache for media shares entirely and only use it for appdata? how do you circumvent this until it is adressed in a new unraid version? i'm still on trial so any additional information is very much appreciated!