tuxfania

Members
  • Posts

    34
  • Joined

  • Last visited

Posts posted by tuxfania

  1. I did this a while back and used this method...

     

    Install Unassigned Devices and attach an external USB drive large enough to hold the data in your shares

    Copy all of the data from shares to the external drive

    Put in your new drives and assign as desired...hold off on assigning parity for now

    Set up your disks/shares as desired

    Copy data back to shares from the external drive

    Assign parity and let it rebuild

     

    I liked this method because I had a copy of my data on external USB and the disks I removed prior to the upgrade of the drives.

     

    Also, waiting to assign parity made the copying of the data back to the Unraid server faster...let it rebuild parity after the copy

     

  2. 5 minutes ago, Memes11 said:

    Thanks for all the answers.

     

    The idea is to use the SSDs in a cache pool, run the VM off of it. The data resides on the HDD pool.

     

    But from further reading I have done, seems that I mis-conceptualized Unraid as an hypervisor while it is more a NAS OS with built-in virtualization for easy spin off of container or VM. am I right?

    Correct...IMO...

  3. On 12/14/2018 at 2:12 PM, maxse said:

    Any issues with reliability, and XFS encryption and constantly writing of plex database and transcoding, and Sabznbd stuff?

    I use encryption on all of my drives...data and cache and have had no issues whatsoever...

  4. 18 hours ago, johnnie.black said:

    If parity is valid, and the by way you describe what happened it should be, this should work to rebuild disk2:

     

    -Assign the new disk2
    -Important - After that leave the browser on that page, the "Main" page.

    -Open an SSH session/use the console and type:

    
    mdcmd set invalidslot 2 29

    -Back on the GUI and without refreshing the page, just start the array, do not check the "parity is already valid" box, disk2 will start rebuilding, disk should mount immediately but if it's unmountable don't format, wait for the rebuild to finish and then run a filesystem check

    Johnnie,

     

    Can you break down what the mdcmd command does...specifically the "29"?

     

    Thanks!

     

  5. 10 hours ago, -Daedalus said:

    +1

     

    I've love something like this as well.

    To expand on this: It would be great to be able to setup sync options as well, something like:

    Pick your share (specific, all)

    Pick your sync type (one-way backup, bidirectional sync)

    Pick your schedule (day, month, etc.)

     

    Yep...really like these additions too.

     

    :)

  6. I would like to request the ability to easily (and possibly securely/remotely) backup the data on a primary unRAID system to a secondary unRAID system.

     

    Could a feature be added that allows a setup like this in the GUI?  Something that sets up a secure link between the systems, be they local or remote and backs up on a schedule?  I know RClone and Rsync are already plugin options, but I'm looking for something baked into unRAID.

     

    Perhaps Limetech could even offer a discounted two system bundle on matching licenses for creating this kind of setup?

     

    • Like 1
    • Upvote 1
  7. On 5/30/2018 at 11:16 AM, Alphahelix said:

    To be honest after 5 days I used another solution. But yes I know I had a lot of duplicates both in number of files (200.000+) and in amount of GB (200gb+)

     

    But still I love the docker. :) thank you for making this possible. 

     

    Curious...what other solution did you use?

     

    Thanks!

  8. 3 hours ago, trurl said:

    maybe if you shared it would help others

     

    Sure, glad too...

     

    I wanted to encrypt my volumes so if a drive failed, I could simply pull the disk and send it in for warranty repair.  This is ideal in the event of a mechanical failure of the disk as the data has been stored encrypted...I don't have to worry about anybody at the factory reading it.  I also wanted the array to autostart on boot/reboot...

     

    LimeTech gave me the following advice:

     

    This can be accomplished by saving your encryption keyfile somewhere on your USB flash boot device, maybe in 'config' directory.  Then edit your 'go' file and put this just before emhttp is started:

     

    ln -s /boot/config/keyfile /root

     

    Edit: be sure and make a backup of your USB flash device: Main/Flash click Flash Backup to download a zip of your USB flash contents.  Note that this zip file can be fed into our USB Creator tool if needed to migrate to a new USB flash device.

     

    -----

     

    So, I copied the key file to the area suggested, renamed it to keyfile and editted the go file with WordPad to insert the suggested line.

     

    Once I did that, the array autostarts on reboot!  :)

     

    Not helpful if my hardware gets stolen, but good enough for dealing with disk failure/warranty work.