• Content count

  • Joined

  • Last visited

  • Days Won


trurl last won the day on April 12

trurl had the most liked content!

Community Reputation

278 Very Good


About trurl

  • Rank
  • Birthday 12/26/1954


  • Gender
  • Location
    North Carolina
  • Personal Text
  1. [Plugin] CA Fix Common Problems

    Could you be a little more specific? Do you mean you want to remove a folder from the appdata share? Or what?
  2. From your last screenshot: 1.11Gbps is pretty much the same as 110 MB/s. What do you think it should be?
  3. You need to have all of your system shares set to cache-prefer with no files on the array, and all other shares set to cache-no with no files on cache. This will require a couple of moves by mover. Follow these steps in this order. There is a lot of stuff here so read carefully and ask if you have any questions about what to do or why. If there is a problem at any step, stop and let us know about it. 1) Go to the Docker page and stop the docker service. Also stop all writing to your server. 2) Set the appdata, domain, and system user shares to cache-only. This will keep them from being touched by mover until we get the other stuff off of cache to make room for any of their files that may be on the array. 3) Set all other shares to cache-yes. This will prepare them for being moved off of cache. Also set these user shares to have Minimum Free larger than the largest file you will ever write to the share. 4) Go to Main - Array Operations and click Move now. Wait for it to finish. This should result in all the folders except appdata, domain, and system moved off of cache to the array. 5) Set the appdata, domain, and system user shares to cache-prefer. This will prepare them for getting any of their files on the array moved onto cache. And this is the way these shares will stay set, so if there is ever any overflow to the array they will be moved to cache when space is free. 6) Set all other shares to cache-no. Since they have already been moved to the array, they don't need to be moved. And, they don't ever need to be cached again because you don't have the space on cache for them. 7) Go to Main - Array Operations and click Move now. Wait for it to finish. This should result in any files from appdata, domain, and system moved off the array and onto cache. That completes all the moves, and has your shares the way they need to be set going forward. The system shares belong on cache, and you don't have the cache space to cache any of the other user shares. After all that, go to the User Shares page and click Compute All and when it's done post a screenshot. After we get your shares where they need to be we can work on the other problems.
  4. one or more controller
  5. Unable to update plugins

    Not without diagnostics. I suspect the OP might still have some issues too but since nobody ever asked for diagnostics we will just have to wait until he fills his docker image again. And you really should have started your own thread, but since this one seems abandoned by the OP, let's just keep it here. Go to Tools - Diagnostics and post the complete diagnostics zip.
  6. Put your flash in your PC and let it checkdisk. If necessary, try different USB port. Also, since you are having flash issues I can't say for sure if you have Minimum Free set for any of your user shares. You have many disks that are almost full. You must set Minimum Free larger than the largest file you will write to the user share. There is also a Minimum Free for cache in Global Share Settings.
  7. If anyone still has an issue with this, and you're NOT running unRAID V5, then please don't post in this thread. It is a V5 thread. See if anything here helps: If you have tried all that and still have a problem, and you are running a recent version of unRAID, then start another thread in General Support.
  8. Not clear how to interpret some of what I see in your syslog because: You have something dropping offline and I'm guessing it has something to do with the problem, perhaps making your flash inaccessible which could cause your symptoms. Lots of this in your syslog: Apr 21 11:48:19 Tower emhttpd: device /dev/sdb problem getting id
  9. If the backup is a single file then unRAID will not split it at all. Each disk is an independent filesystem so each file must fit completely on a single disk. Possibly it was incomplete because it ran out of space. This may be what you meant, but I will explain it just in case. What you need to do is set Minimum Free for each of your user shares to be larger than the largest file you expect to write to the share. unRAID cannot know how large a file will become when it starts writing it. If there is less than Minimum Free remaining on a disk, unRAID will choose a different disk to start writing the file. There is also a Minimum Free for cache in Global Share Settings. It comes into play if cache needs to overflow to the array. See here:
  10. System currently has NVME in RAID 0

    Will what run OK? I thought you were planning to boot another OS from your NVME RAID. If so, then I presume it would work just as before, and you shouldn't let the unRAID OS even touch it. Are you saying you can't have any AHCI devices if you have this NVME RAID? That doesn't seem right. Maybe I don't understand what you're asking.
  11. System currently has NVME in RAID 0

    Sounds like you are mostly interested in unRAID as a virtual host. unRAID is actually a NAS with docker and virtual hosting capabilities. While it would be possible to present a RAID as a single volume to unRAID, unRAID must format any disk it will use in the array or cache pool. So, your 3 questions can be reduced to just the 3rd question. If you set your BIOS boot order you might be able to boot from the unRAID USB or from the NVMEs, but it might remove a drive from the boot order if you remove it. You should be able to boot from any device if you manually select the boot device though. It is very important if you do boot another OS, you don't allow it to access any of the unRAID cache or array disks.
  12. [Plug-In] Community Applications

    Cache drive filling up is also not correct. You should never allow a drive to get too full, and there are settings you can make to prevent this.
  13. The best time to get a diagnostic is immediately after the problem exhibits and before reboot. Is there some reason you are still running this old version of unRAID? Some plugin authors will not support their plugins on this old version. And it might be that whatever is causing your trouble was fixed on a later version. Also the diagnostics from this old version are a little more trouble to work with. From your syslog it looks like you originally setup without a cache drive and maybe some of your system shares (appdata) are still at least partially on the array. Stop the docker service, change appdata to cache-prefer, run mover, then restart docker service.
  14. one or more controller

    unRAID only supports up to 2 parity disks. Parity is not a substitute for backups. btrfs raid1 is the default setting for the cache pool.
  15. Looks like this was taken with the array stopped. Start the array and give us another.

Copyright © 2005-2018 Lime Technology, Inc.
unRAID® is a registered trademark of Lime Technology, Inc.