Jump to content

GoChris

Members
  • Content Count

    191
  • Joined

  • Last visited

Community Reputation

3 Neutral

About GoChris

  • Rank
    Advanced Member

Converted

  • Gender
    Male
  • Location
    Calgary, AB, Canada

Recent Profile Visitors

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

  1. Correct. I will update my original post to be more clear, I guess I wasn't as clear as I thought.
  2. Yes but the share min free space takes precedence when that share is set to use the cache, which is ultimately the problem.
  3. The alternative would be to have a separate setting for how much free space you want to maintain on the cache, just like you can for a share. Cache drives are not going to be as big as data drives (let's assume we're talking about 99% of setups), so chances are you might fill it up more than a share setting, but there can remain more than enough space for file transfers. If you need/want an example, I might have my share set to 150GB min, but various files could have been written to multiple shares and reduced the cache drive to (just) under 150GB. If I then want to write another file (size is irrelevant as long as it's under the free space size), it would skip the cache and go to the share directly, obviously that's slower, but really no reason it couldn't go to the cache (before the mover catches up).
  4. If a share is not set to cache only, and a min free space is set, I think it should only apply to free space on HDDs, not how much free space is on the cache. I only want to fill up my drives to certain amount, but I always want to utilize the faster write speed of using the cache drive, however if the cache fills up and has less free space than the share setting, it will write straight to an HDD and be much slower. Making it an option would work too. Perhaps a better explanation:
  5. You have to edit the config file in appdata for the settings you want to stay between sessions.
  6. I love dockers, and I've love to see unraid -> unraid backup/sync.
  7. You have to edit the values in the rtorrent.rc file in your appdata/rutorrent/rtorrent folder
  8. Happy Birthday! I can't even remember how long I've used it, close to 10 years maybe? I just love that it's so easy to expand storage and fix failures, I'm never really that worried about catastrophic failures. Dockers are so easy, it's really quite great. The plugins and community are icing on the cake.
  9. The CPU usage problem has not been fixed. Just had to restart my two instances. Does anyone recall which is the latest before the CPU usage problem?
  10. Wow, seems this one has been ignored but many people would like this. I bet a lot of us have VMs that don't use any share data at all. pfSense, pihole, LibreNMS for example for some.
  11. Yes, I'm still not 100% convinced since I had not done the rebuilds in maintenance mode before so will be good to see a check in normal mode indeed. I might do that soon. Well, it will happen in 4 days anyway on schedule.
  12. Good news finally. I swapped out the PSU with the one I noted above. I then rebuilt the 3TB drive in error, and it completed with no error, so then I rebuilt the 8TB drive in error and it just completed without error. I did it in maintenance mode, but it was probably the different PSU. I know I could have rebuilt two at the same time, but chose to do one at a time. So hopefully the many weeks long ordeal is over. Thanks to everyone for the support.
  13. Okay, I have one of these as well I found in the basement, https://www.corsair.com/us/en/Power/txm-series-2017-config/p/CP-9020130-NA so I will swap that in, as I think it's a single rail and then try a rebuild, in maintenance mode.
  14. Confirmed that the backplanes are powered by two cables, not just split off one. So they're on two rails, which is probably okay. Rebooted, and have a new drive in "error", despite it showing zero errors, don't think there was even any reads. I'm quite frustrated with this, not sure what to do. Swap the i5 cpu back in? Nothing else has really changed. Well when I checked the power, I removed a reverse sata->sas breakout cable and replaced it with a sas straight to the HBA card, so the only drives off the mobo sata are the 2 ssd cache drives. Starting to pull my hair out.