Jump to content

rampage

Members
  • Content Count

    3
  • Joined

  • Last visited

Community Reputation

0 Neutral

About rampage

  • Rank
    Newbie
  1. Thanks for the reply. Yes I guess generally it is better to not use the cache if a write job is going to be more than the cache size.
  2. Hi, I'd like to copy the files on the usb drives to the array directly via attaching them and mount. They are same brand model 8TB HDD. However some can be mounted, some can not, which seems to report with this message 'Anyway to mount GPT drive which has 'Partition 1 does not start on physical sector boundary' or mount ntfs-3g just say it can't access the HDD. Any idea if there's a way to mount those? Best Regards,
  3. Hi, Just testing out unraid. It seems to be very promising. I have one problem that, writing to the share and the mover job can happen at the same time, if I put a large cache drive say 500GB or 1TB into the box, and have a writing job say 2TB in the progress keeps hammering the cache drive for long time, then the mover kicks in to read, this situation could bring the cache drive's temperature to close 60 celsius which is really bad ( already have the best cooling I could give for it). So I wonder if there's a setting to limit how much cache space can be used for share writing? The the limit has reached then switch to write to the array directly so the cache drive could rest and cool down. When the mover kicks in hourly and the files have been moved to the array, maybe the current share writing could switch back to use the cache or the next writing job will. For example a 500GB cache drive, I'll allocate 100GB for share writing cache, 300GB for vm and docker stuff, and keep 100GB spare space to ensure performance. Thank you.