Jump to content

trurl

Moderators
  • Content Count

    19455
  • Joined

  • Last visited

  • Days Won

    41

Everything posted by trurl

  1. Were you not using the onboard controller before this? Is it in RAID mode?
  2. Not entirely sure what you are thinking here, but nothing ever gets moved, except for cache-yes moving from cache to array or cache-prefer moving from array to cache. And in general, user share settings only tell it where to write new files.
  3. After this you go on to describe how it is working terribly. Did it work for a while and this is new behavior?
  4. trurl

    New Build

    Your HTML is obviously not working.
  5. LAN makes more sense to me. Why go to a lot of extra trouble to save a little bit of time for a one time operation?
  6. I don't see anything obvious in those. By "check" do you mean a parity check? Just a word of advice on using the forum. When you edit a post, for example, to attach those diagnostics, the thread doesn't show up as having anything new in it for the rest of us. The only reason I even looked at this thread again is because you had made a new post to it. If you hadn't, I would likely have forgotten all about it since I read a lot of threads and only look for those that have new posts in them. So, it is best to put new information in a new post or it could be overlooked by the people who are trying to help you.
  7. That screenshot of your Krusader configuration may not be showing us the whole picture. Post the docker run command for Krusader. https://forums.unraid.net/topic/57181-real-docker-faq/#comment-564345
  8. Complete Diagnostics zip file please. Have you done memtest?
  9. You seem to have had some issues communicating with disk2. Check connections.
  10. It also occurs to me that there might be some misunderstanding about Unassigned Devices shares, and Unraid User Shares. Unassigned Devices plugin lets you share, on the network, devices that are not part of Unraid cache or array. These will show up in Windows, for example, next to your Unraid User Shares. But they are not part of Unraid User Shares. If you move one of your user shares completely over to an Unassigned Device, it is no longer an Unraid User Share.
  11. And if you did actually move (not simply copy) those user shares off of cache or array drives, and onto an Unassigned Device, then you have effectively removed those user shares. They will probably still show up, but they are not really there, and they would disappear when you restarted the array or rebooted. EXCEPT, probably the system share would be recreated with a new docker image since docker service is probably enabled. So, your description is pretty confusing. I hope your system isn't actually in that much confusion.
  12. Your system, domain, and appdata folders (not uppercase) are Unraid user shares. Since I don't know the details of how you may have changed the Krusader mappings, I don't know what you would see within the Krusader application itself. And here is where I am unclear what specifically you mean by "Shares". Where did they "appear". What exactly are you looking at when you say that. Windows? Krusader? The Unraid webUI? To elaborate on this, any top level folder on cache or array is automatically a user share with the same name as the folder. If Unraid now has user shares named "UNASSIGNED" and "NVMe", you must have accidentally created them as top level folders on cache or array, probably due to the way you moved or copied.
  13. Volume mapping is pretty basic to understanding how to configure dockers, and if you understand it you are most of the way to being able to use dockers without relying on other people. I think people are perhaps confused by the word "map". It is a little like a road map or google maps or the other common uses of the word map many people are familiar with, but it is more general in meaning. It is more like the meaning it has in mathematics, or in this case, information theory. A map is simply a correspondence. Just as a place on a road map corresponds to a place in the real world, the docker volume mappings are a correspondence between paths within the docker container, which the container application sees, and the paths in the docker host (Unraid). The other piece to this puzzle is where the user shares are actually stored in Unraid. If you have a user share named Movies, the path to that storage is /mnt/user/Movies. So, for example, with the plex docker, you could have a container volume (path) at /movies, and map that to the host path that corresponds to your Movies user share, /mnt/user/Movies. The plex application would see those files in that user share in /movies. Here is a link to the Docker FAQ with a lot more information: https://forums.unraid.net/topic/57181-real-docker-faq/
  14. Here is what I have experienced with rsync, and others have experienced similar things with other applications like Krusader. The application creates all the folders in advance, then copies all the files to those folders. A user share can span disks in Unraid, so a user share has a lot more capacity than a single disk does. But, when all the folders are created in advance, they wind up on a single disk, then when the files are copied to those folders, that single disk won't hold them all. One way to work around this is to not rsync so much at once. After one copy is complete then depending on Allocation Method etc. a different disk will be chosen for the next rsync. When it happened to me, I noticed that it was working in alphabetical order, so I began moving some of those precreated folders to other disks before it got around to copying their files.
  15. Your plex library (appdata) expects your media to be at certain paths and these paths are stored in that library (database). Those container paths are mapped to your Unraid storage (host paths). Plex won't work with its existing library unless the plex container finds your media at those same container paths. When you said you had moved your shares, I assumed you meant you had moved all the files and folders for each of the shares, and the share names are the same as you had before. Is this not true? Do you understand container volume mapping? It would be possible to change the mappings so the container paths mapped to different host paths (shares) than you had before, but it would be simpler if your shares names are the same as before, then you wouldn't have to change anything. I don't use mariadb or nextcloud but if you understand container volume mapping these sorts of questions can be figured out pretty easily.
  16. I don't remember if it was mentioned. Are you booting from a USB2 port? USB2 ports are often more reliable for this, regardless of which flash drive you use.
  17. keep working on getting us more information, see the "Need Help?" topic pinned near the top of this same subforum.
  18. If you had asked for advice sooner, this is what I would have recommended. It's really just a case of what the hardware is capable of. There is simply no way to move stuff from the faster cache to the slower parity array as fast as you can write it to the faster cache.
  19. When I had a similar setup, I put my internal router in the DMZ of the router facing the internet. Then everything just went directly through to the internal router and I only had to deal with configuring the internal router and its firewall.
  20. Another thing that your question suggests you may not completely understand. Cache is part of the user shares, just like the array disks are. If you try to write a file to a user share, and that file already exists, whether on cache or array, then it is handled just as expected. If you agree to replace it, it will replace it on the specific disk where the file actually exists.
  21. This is not unusually slow for writes to the parity array. See this for more on how parity writes work and another setting that can make that faster (at the expense of spinning all disks): https://forums.unraid.net/topic/50397-turbo-write/ Just wanted to repeat this. Don't share disks on the network. Only work with user shares, whether over the network or directly on the server. If you get into a situation where you think you need to work directly with a disk, ask for further advice.
  22. Parity is realtime. Every write to the array writes parity at the same time, so that would NOT happen "after a short while". What might happen after a very short while is RAM buffering would fill and the initial burst of speed related to that would settle down to the actual write speed. You should usually include the diagnostics when asking for help. Go to Tools - Diagnostics and attach the complete diagnostics zip file to your next post.
  23. You have configured a fixed IP address (the old one) for your server, so it isn't on the 10.... network. I usually recommend using DHCP and letting the router assign IP addresses, then work in the router to reserve specific IPs for specific devices.