• Content Count

  • Joined

  • Last visited

Community Reputation

13 Good

About DanielCoffey

  • Rank


  • Gender
  • Location
    South Ayrshire, UK

Recent Profile Visitors

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

  1. Thank you - I will be able to follow that. If I get into difficulty I will come back and ask.
  2. I am currently set up with a pair of 512Gb SSDs in a btrfs cache pool and I would like to know the smoothest way of moving over to a single M.2 SSD, preferably without having to redo my Docker settings if possible. Mt Forum Signature is up to date. I do understand that I should run Mover first. Thank you.
  3. The Basic license will allow you to grow your array in the future and you do still get the full Docker and VM support that the larger two licenses also share.
  4. On the NAS in my signature I came across a bottleneck today and I am interested in knowing what might have caused it. This is a lightweight NAS that serves one PLEX Docker and also acts as an on-site backup for my desktop PC. My wife was watching a movie that was already encoded correctly for the Apple TV and without thinking I decided to back up a large number of small files to the backup share while the movie was playing. Very quickly the movie started to stutter then froze until the file transfer was complete. The movie was streaming from one of the HDDs. I know from
  5. And remember that if you have a cache drive, movies will sit on it and contribute to it filling up until the Mover process runs according to its schedule (or you manually kick it off yourself) at which point they should be sent over to the array shares.
  6. I am at 2560x1440 on Win10 if that matters. If you want me to check it on other platforms I have a Mac Mini (also at 1440p) running Safari browser and an iPad.
  7. VERSION : 6.8.1 ISSUE : UI on Dashboard page - "thumb down" dropdown menu for SMART options cannot see last menu item and cannot scroll down to it. BROWSER : Firefox 72.0.1 (64-bit) I had several CRC errors on my first cache device which displayed the yellow "error" thumb down icon. When I clicked on the error thumb to reveal the Attributes/Capability/Identity and Ignore (or cancel?) menu, the final menu item was not visible even when I scrolled the window down as far as possible. The last Ignore (or Cancel?) option was tucked behind the menu footer. I was able to just cl
  8. I have just tried 6.8.0-rc1 to compare its parity checks to both 6.7.2 and the Tunables script since my array is very straightforward and the result is interesting and shows there is still room for improvement. The first thing I did before upgrading from 6.7.2 was reset all the Disk Settings tunables back to default (including nr-requests which defaults to auto now). My array is 2x WD Red 8Tb dual parity and 6x WD Red 8Tb data with 2x 512Gb SSD for cache. 6.7.2 default - 17h15 to 17h30 6.7.2 tunables - 15h30 6.8.0-rc1 default - 16h45 I
  9. If you have a spare PCI slot you also have the option of adding an HBA card such as the LSI SAS 9201-8i which will have two SAS ports. Each of these can be connected to four SATA drives using a SAS to SATA cable giving a total of eight mroe SATA ports. There are reputable resellers on eBay who will sell tested and flashed cards ready to plug in and go. EDIT : This does assume you have spare slots in your unRAID license of course.
  10. Perfect - I didn't know you could do that. Thanks!
  11. On my 6.7.2 Array with a 2xSSD Cache Pool, one of the cache drives threw a CRC Error during a Mover run and I would like to know how to clear the warning. I had just manually transferred about 13Gb from my main PC to the backup share and clicked the Mover to distribute it all according to the share preferences and I got a popup saying that the first Cache drive had experienced one CRC Error. Looking at the SMART Report for that device does show one CRC Error Count but all other values are healthy. A quick SMART test passes. The device is still flagged in yellow on the
  12. Here's a tip based on personal experience... make sure the array is not due to go to sleep while the Preclear is running. In my case it watched the array for 30 minutes, decided all was quiet, ignored the unassigned devices and shut down. Oh poop! Time to start over I guess. EDIT : well colour me impressed! When I woke the array, the Preclear docker simply resumed from where it had left off and was up and ticking by the time I reopened the WebUI.
  13. That is just what I needed, thank you. So just as with other Dockers, we can close the Docker window and the process inside it will carry on running. We can pop back later and reopen the WebUI and take a fresh peek at how it is getting on. Once it is completely finished we are free to stop the Docker if we want. Cheers.
  14. Please excuse the possibly idiot question but can I close the Docker command prompt window while the preclear is running (like you could with Screen) or must it remain open in order for the script to continue? On an 8Tb drive it will of course need to run for quite a while and this was not mentioned in the FAQ.
  15. Good point, thanks. I will report back with what I receive.