• Content count

  • Joined

  • Last visited

  • Days Won


itimpi last won the day on October 22

itimpi had the most liked content!

Community Reputation

52 Good

About itimpi


  • Gender
  • Location
    United Kingdom
  1. Waiting for /dev/disk/by-label/UNRAID

    That sounds as if you are not passing the unRAID USB stick through to the VM. This is required for key authentication purposes.
  2. Secure SSH

    With unRAID you always log in as the 'root' user when using SSH. There is no other users in the Linux sense.
  3. Need help with Super Micro AOC-SASLP-MV8

    It is. however there may be a setting in the PC Bios that controls whether add-on boards display ROM messages. Ideally you need the SASLP card displaying the drives it finds connected, as it is after that display that you press CTRL-M to get into the SASLP settings.
  4. Use the -L option - it virtually never results in a loss of data. This is quite a standard message. If you really want to avoid using the -L option then it is possible to do a mount/umount from the command line before doing the xfs_repair, but this is normally more effort than it is worth.
  5. According to that log you ran the xfs_repair with the -n flag set which carries out a check but does not fix any errors found. You need to rerun it without the -n flag to get xfs_repair to actually fix the issues found.
  6. XFS is now the recommended format for array drives. It is better supported than ReiserFS that is now end-of-life in the Linux world. There is no problem with using a mix of formats for the drives in the array. You might want to check Settings->Global Share Settings in case you limited the drives there? if that is not the issue then I suggest you post the diagnostics zip file (obtained via Tools->Diagnostics) as this gives more information about your system.
  7. That will only happen if you put it into a folder that has a name corresponding to a share which is set to Cache=Prefer. Remember that all top level folders on array drives are effectively User Shares.
  8. There is no support for this built into unRAID.
  9. Have you run the check on disk7 yet?
  10. I think you are over-thinking this!. You can always specify a specific disk for the vdisk of your VMs. That way you bypass the User Share System System and have absolute control over where the vdisk is placed.
  11. I never see much value over using anything other than Windows Defender which has minimal impact and comes as standard with Windows.
  12. Pre-clearing is never a requirement - it is only worth doing if you want to do a confidence check on a drive before adding it to an already existing parity protected array. the OP message sounds like a new array where the disks have already been tested. If that is true then the easiest thing is to just create the array and then let the unRAID format the drives and build parity. Preclearing the drives in such a scenario adds no value.
  13. Cache Appdata (Plex Docker)

    Yes. Cache=Prefer means that when you first add a cache drive the mover will move any appdata files from the main array to the cache. Once this move has happened then the Cache=Prefer is equivalent to the Cache=Only setting in normal use. The main difference is that with Cache=Prefer files will be written to the Main array if the cache runs out of room, while with Cache-Only writes will start failing when the cache runs out of rooms.
  14. leave drive spun down

    I very much doubt this is possible. I think you will find that the drives need to be spinning to allow them to be cleanly unmounted.
  15. This is covered in which is a sticky post in the 6.4 prerelease area of the forum.
Copyright © 2005-2017 Lime Technology, Inc. unRAIDĀ® is a registered trademark of Lime Technology, Inc.