dboonthego

Members
 View Profile  See their activity

  • Posts

    266

  • Joined

  • Last visited

  • Days Won

    1

Community Answers

  1. dboonthego
    dboonthego's post in Data on cache only was marked as the answer   
    My Nextcloud share uses primary cache and secondary array storage with mover going from cache-->array, but I only use it for auto-upload of photos and not much else.
     
    There's nothing wrong with using a cache only if you have the space.  You'll be protected by mirror and remote backups.
  2. dboonthego
    dboonthego's post in SMART Error on 2 week old disk was marked as the answer   
    I wouldn't.  Just replace and rebuild the disk.
     
    If you choose to also copy, toss it in a subfolder on disk2 that way when you rebuild disk1, you won't have duplicate files in the same path across multiple disks.
     
    This will do it.
     
    rsync -avhPX /mnt/disk1/ /mnt/disk2/disk1copy/  
  3. dboonthego
    dboonthego's post in Problem with adding new disk: preclear plugin no longer supported, array currently in unprotected state was marked as the answer   
    If I understand correctly, you installed disk5 and formatted it.  Then unassigned it and pre-cleared again using UD?  
     
    Yes, it will rebuild the disk using emulated contents; which is nothing at this point.
     
    Why not get your OS current?
  4. dboonthego
    dboonthego's post in [SOLVED] Stopping array, will it stop SSH as well? was marked as the answer   
    SSH is still available with array stopped.
  5. dboonthego
    dboonthego's post in Separating SSD and HDD to different pools was marked as the answer   
    Well, what are you waiting for???
     
    Yes, you can have multiple separate pools.  In your case, you have two disks so you could have one pool of two disks or two pools with one disk.  Just setup how you want.  For example:

     
    Give this a read:
    https://docs.unraid.net/unraid-os/manual/storage-management/#why-use-a-pool
  6. dboonthego
    dboonthego's post in How to search for files on Unraid GUI? was marked as the answer   
    You can choose to export disk shares which allows you to browse individual disks in file explorer.  There's no native search capability in the GUI.  I'm sure there's a docker out there that can catalog your files.
  7. dboonthego
    dboonthego's post in App Updates Best Practice was marked as the answer   
    Yes.  Some apps such as Nextcloud may also require additional steps to upgrade the app version.
  8. dboonthego
    dboonthego's post in New setup, adding disks? was marked as the answer   
    No.  You'd need an 8TB to support 2nd parity.  You can still add the 4TB disks without having 2nd parity.  You can't add 2nd parity with anything less than 8TB because you have a data disk that is 8TB.
     
    You can turn one of your 8TB data disks into the 2nd parity and add the 2 4TB to the array.  You will still end up with 16TB capacity.
  9. dboonthego
    dboonthego's post in [Solved] How to mount vdisk.img files was marked as the answer   
    I figured it out.  I needed to specify the byte offset of where the partition begins.  For anyone who might have the same question in the future, here is what I did.
     
    From the unRAID command console, display partition information of the vdisk:

    fdisk -l /mnt/disks/Windows/vdisk1.img
     
    I was after the values in red.  The output will looks something like this:
    [pre]Disk vdisk1.img: 20 GiB, 21474836480 bytes, 41943040 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disklabel type: dos
    Disk identifier: 0xda00352d
     
    Device      Boot  Start      End  Sectors  Size Id Type
    vdisk1.img1 *      2048  206847  204800  100M  7 HPFS/NTFS/exFAT
    vdisk1.img2      206848 41940991 41734144 19.9G  7 HPFS/NTFS/exFAT[/pre]
     
    To find the offset in bytes, multiply the sector start value by the sector size to get the offset in bytes.  In this case, I wanted to mount vdisk1.img2. 
    206848 * 512 = 105906176
     
    Final command to mount the vdisk NTFS partition as read-only:

    mount -r -t ntfs -o loop,offset=105906176 /mnt/disks/Windows/vdisk1.img /mnt/test