Jump to content

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 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!

  4. 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.

     

  5. On 9/4/2018 at 12:11 PM, limetech said:

     

    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.

    I tried this method and cannot get it to automatically start the array?

     

    I copied the file I am using as the keyfile (Pic.jpg) to the config directory on the USB flash drive and editted the go file as suggested adding the line:

     

    ln -s /boot/config/Pic.jpg /root

     

    right in front of the emhttp line...after reboot, the system starts, but the array remains stopped.

     

    Any idea what I might be doing wrong?  Should I not use an image file as the keyfile?

     

    Thank you!

     

  6. 6 hours ago, limetech said:

     

    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.

    Thanks...this was very helpful!  :)

     

  7. Answered my own question...I went back and reviewed the video I saw it in...it's basic encryption using a GELI key stored on the boot drive, not passphrase encryption which would require that be entered at boot.

     

    They suggested basic encryption since it's helpful to use in the event a drive fails and you have to send it in for warranty...you don't have to worry about the data on it being read.  The basic encryption wouldn't help if your rig gets stolen.

     

×
×
  • Create New...