• Content count

  • Joined

  • Last visited

Community Reputation

13 Good

About itimpi

  • Rank
    Advanced Member
  • Birthday 06/10/50


  • Gender
  • Location
    United Kingdom
  1. It is simply a case of stopping the array, putting a 10TB in place of the 8TB and then restarting the array to allow parity to built onto the replacement disk. If you want to remain protected then do each parity drive individually. If you replace both of them at the same time then you are unprotected whilst both parity drives are rebuilt, but the elapsed time is shorter. Once the parity is rebuilt on the 10TB drives you can simply assign the 8TB drives as new data disks, and unRAID will Clear them and once the Clear has finished offer to format them with your desired file system (default being XFS).
  2. The two different ways of specifying access to appdata are functionally identical. The advantage (if any) of using 'Cache Prefer' method is that you can initially start without the cache drive and later when/if you add one the system will automatically and transparently migrate the share contents from the array drives to the cache drive you have just installed. All your settings remain unaltered for your dockers.
  3. Some of the new 'mesh' WiFi adapters for pervasive WiFi in home networks look like they can provide better throughput than the Powerline adapters. Since the adapters include Ethernet ports the unRAID server could be plugged into one of those ports. i would be interested to see if anyone has practical experience of the throughput of one of these 'mesh' style WiFi networks vs Powerline. I currently use Powerline but have been think of switching to get higher performance.
  4. Have you told the Windows setup program to load the virtio drivers before trying to find the drives? It is not clear from your description whether you did this step?
  5. 'System Buttons' is a plugin and as such not part of the official unRAID release enemy though it shares the Dynamix branding. The unRAID 'main' tab already includes buttons that allow for the stopping/starting the array and powering the system off or rebooting so 'System Buttons' is not really necessary, but just a nice-to-have.
  6. I do not see your problem when using unRAID in normal mode. if the disk is added to a new slot in a parity protected array then unRAID wipes its current contents (by clearing the drive by writing zeroes to it). if the disk is replacing an existing disk then it is overwritten by the rebuild process. The only time a disks existing contents are retained is if: - it has previously been partitioned and formatted by unRAID. - you have added the drive by doing a 'New Config' (which is not the normal way of adding an additional disk) More worrying is the fact that you have pre-clears that do not finish. That suggests there is some sort of issue at the hardware level on your system.
  7. I assume your parity drive is at least 4TB? you can just swap the disk in and let unRAID build its contents from the combination of the other disks plus parity. If you are not sure of the state of your parity then you should run a check first, but if you think parity is OK this is not required. I would suggest you keep the old disk around untouched 3until you are happy the 4TB has been rebuilt with the data intact. you do not NEED to run pre-clear first when it is replacing an existing disk. The reason you might want to run it is as a confidence check on the new drive before you trust data to it.
  8. Since unRAID runs purely from ram with no swap file then the memory would automatically be locked when you start the VM without you needing to do anything special. Just make sure that you set the minimum and maximum RAM settings to the same value.
  9. Please provide the full diagnostics (obtained either by Tools->Diagnostics from the GUI or by 'diagnostics' command and the command line. As well as logs this will include other relevant information such as your configuration details and the SMART reports for all your drives. This helps immensely when trying to diagnose problems and give advice.
  10. Parity sync does not fix anything related to corrupt file systems/metadata. For that you have to use the file-system specific tools.
  11. No - port numbers are not important to unRAID. Ever since v5 unRAID has recognised drives by their serial numbers not by where they are plugged in.
  12. Under the covers what the parity swap process does is first copy the parity from the old (5gb) parity drive to the new (8gb) parity drive and then uses all the other data drives plus the new parity drive to rebuild data onto the 5gb drive. During this process keep the problem 3Gb drive safe just in case anything goes wrong with the parity swap process (so that is available for emergency data recovery procedures).
  13. You should post the full diagnostics. You get this either from the GUI via Tools->Diagnostics or by using the 'diagnostics' command from the command line. You will find that normally anyone giving advice wants to see what lead up to the log messages you posted, or to look at other files included in the diagnostics.
  14. Worth pointing out that with the mix of drives reported and the default of BTRFS RAID-1 the usable space will be the sum of the two SSD drives so much less that the 624G being reported.
  15. I would have thought that files in the TB range are far outside the typical usage of unRAID. Even an uncompressed BluRay is normally only about 40GB. if you are wanting to manipulate files in this size range then you definitely need to be aware of the fact that unRAID has to be able to store the whole file on a single drive (I.e. It will not be split across drives). At least with 10TB drives becoming mainstream this can actually be managed. However the write performance limitations on unRAID definitely makes files of this size unwieldy.
Copyright © 2005-2017 Lime Technology, Inc. unRAIDĀ® is a registered trademark of Lime Technology, Inc.