threefoursixeight

Members
  • Posts

    14
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

threefoursixeight's Achievements

Noob

Noob (1/14)

0

Reputation

  1. Hello! Currently I have a single SSD as a cache drive for all my shares. All my shares are "Cache - Yes" (except for app data which is Cache - Only) so that data moves to the array nightly. I'm interested in potentially adding another SSD as a cache drive for only my "media" share. Sabnzbd downloads are stored here that are then moved to the relevant folders (still in the media share) for my Plex libraries. What I'd like to do is retain the current mover behavior (data on cache moving to the array nightly) for all shares EXCEPT the media share, and then have different behavior for the media share. The behavior I'd like to have for the media share is this: Data stays on cache until cache is X% full Once X% full, move oldest data onto the array I feel like this could potentially be achieved using the Cache - Prefer option, but how does that work when the share is much larger than the cache drive? It sounds like Cache - Prefer will move data from the Array back to the Cache drive if there is space, but what files are chosen to be moved? Once the old data is moved to the array, I'd like it to stay there instead of being moved back to cache. That way the X% threshold is met, files older than Y days are moved to the array, and space is made for new files to be downloaded... process repeats as time goes on, threshold is met.
  2. I'm thinking of upgrading my system and adding an additional SSD to a new pool to store Sabnzbd downloads and Plex Media and curious if my thoughts below are correct: I'd like my shares like nextcloud, etc. to behave like they do now - files transferred into unraid stay on cache until the nightly move where they will always move to the array. If I leave this share as "Yes: Cache" and in the plugin set "Move all from Cache-Yes shares when disc is above a certain percentage" to "Yes" and set the % to 0, will that achieve this? I'd like my media share that contains downloads and Plex media to stay on cache until X% full. Would I need to set this share to "Prefer: Cache", and then play with "Only move at this threshold of used cache space" and/or the moved based on age setting? Basically, I'd like some shares to move nightly no matter what, and then other shares stay on cache until a certain age/used space is reached. Thanks!
  3. Hey everyone! I’m a couple versions behind on 6.9.1. I’m planning to upgrade to the latest version which seems to be 6.11.5. Just wanted to do a quick check in and see if anyone has had any issues with the upgrade process or if it was pretty smooth. Thanks 🙂
  4. I'm having the same issue (can't access sabnzbd gui via browser). It worked fine until I updated the docker container today. Host ports are 8280 and 8290 and I've tried both and just get the error that the webpage cannot be reached. I've attached the log files. Some googling suggested it could be permissions? But there wasn't much information and I'm not sure what the permissions should be changed to or if that is the issue in the first place. EDIT: Reverting back to version "binhex/arch-sabnzbd:3.6.1-1-03" fixed it, but if anyone has any insight into the error it'd be awesome to fix it and get up to date sabnzbd_log.log
  5. Probably a dumb question, but I am new to docker. I see in the plex GUI that an update is available; do I update using that link, or wait until there is an update for the docker container? Or are docker container updates not necessarily related to updates for the program they contain?
  6. Gotcha, thanks! Just wanted to confirm the parity drive shouldn't be accessed very often so I can spin it down quickly
  7. Hi everyone, I'm just curious how often the parity drive is accessed? Is it just during the daily moving from cache to the array, and then during parity checks? Thanks!
  8. In case anyone finds themselves in this thread with the same issue, this thread mentions disable p states and that worked for me!
  9. Hi everyone! I have Unraid all set up and am loving it so far, but just have one question. I'm monitoring my CPU frequency using the command 'watch "cat /proc/cpuinfo | grep \"^[c]pu MHz\""' in the terminal, and noticed that my CPU never seems to "wind down" into lower CPU frequencies. It always seems to be above or around the base clock of 3.5GHz. The CPU is an i5 4690k for reference. I double-checked the BIOS and C-States are turned on, power saving is turned on, and voltages and frequencies are set to auto. htop also shows that load average is less than .1 when I am looking at the frequencies, and CPU usage is normally never above 5% per core when it's idling like this. I'm just wondering if this is normal? Normally on Windows machines I can see my CPU go down to 1600mhz or 800mhz when idling, but those Windows machines also didn't have 7 docker containers running. If this is normal, that's fine. I'm just looking to make my system as power efficient where possible. Thanks!
  10. To add to this, there is an awesome spaceinvader one video detailing how to use Krusader.
  11. I started setting up my unraid setup last night, but am having a hard time adding my old data drive to the unraid array. My setup consists of two new hard drives, one new SSD, and one old drive with data. What I did was: Install the new SSD and new hard drives, with SSD as a cache drive, one HDD as a data drive, and the other HDD as a parity drive. Install the unassigned devices plugin, turn off PC and install old data drive Started up PC and mounted old drive as an unassigned drive and used Krusader to move data from old data drive to the relevant user shares on my new data drive When all the transferring was done is where my problem began... I stopped my array, unmounted the unassigned drive, and added it to the array as disk 2. However, I cannot save the configuration because I get an error along the lines of "Invalid expression. Cannot add and remove disks at the same time". How can I fix this error? Is it because the disk is moving from unassigned to the array, which appears to unraid as being removed and then added? When I first setup unraid, parity started to be calculated so I paused it because I still had data to transfer, could this be the issue? I tried canceling it to start fresh but that didn't seem to help. Currently, I'm having parity calculate while I'm at work, hoping that once it is calculated that I'll be able to add the old disk to the array. Will this fix the issue? Will parity have to be recalculated when I do add that old drive? Thank you very much in advance!