• Content Count

  • Joined

  • Last visited

Community Reputation

1 Neutral

About JokesOnYou77

  • Rank

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. If this can be done in an OS update, it would be awesome. But I don't have that power, unless there's something I'm missing in the code on github. But what I can do to solve this problem for myself and others in the immediate term is to write about 50 lines of code/JSON with instructions on my github. But by no means am I proposing that we mark this topic as closed/solved. Building this into the OS would be great. But I think that's a much longer discussion around the right scope, user experience, and implementation. To me, that means it's likely to take a while. To
  2. The modified move command makes sense to me and I can change my commands accordingly. But I seem to be getting conflicting information here in that I absolutely am getting duplicate files and I can delete the one on the cache without removing the one on the array disk (checked and double-checked but I'll check again later today to confirm).
  3. Hi all, I have two shares, downloads and Media. Downloads uses a cache pool and Media does not. When a download finishes, I ssh in and mv downloads/some_dir/ /mnt/user/Media/. But this results in two copies of the data, one in /mnt/cache/Media/some_dir/ and the other in /mnt/disk1/Media/some_dir/. It seems like this is some kind of conflict between the default Linux mv behavior, which simply changes the reference for where data is stored when moving data on the same physical disk, and the UNRAID behavior that follows caching rules. Is this expected/desired
  4. @ljm42 My PHP isn't very good, but it doesn't look like there's a place to inject logic for this in the UNRAID webGUI on github. That leaves browser plugins or greasemonkey scripts as the best way to distribute this in an easy to use fashion. If I were to build such a thing, what would be the right forum to announce it in?
  5. I'd also like to see the web terminal don't size made configurable. As it is, I can't increase the terminal font size without also zooming in on the main UI page which blows that up and makes it difficult to have terminal and GUI both open and readable. Has anyone done the work to see how we could actually use xterm-webfonts? Maybe we can make a browser addon to inject it? UPDATE: I spent some time messing with it and reading docs and made a little progress. Entering the following in the browser JavaScript console gets the desired behavior: term.setOption("
  6. I'd like to request the addition of the pixz compression tool. It's a wonderful extension to the standard xz (LZMA) compression tool that allows random access to files in the archive. For large tarballs, the ability to extract any arbitrary file, and show the archive index, without reading the rest of the files in the archive (more or less constant time). I deal with 2-3 GB archives in my day to day work and I am guessing that I'll be dealing with a lot more as I get into UNRAID and it would be really nice to have random access to my compressed/archived files.
  7. Packaging as Docker container is a great idea, I do that at work to make executables. If pixz didn't need pthreads I'd even be tempted to use scratch as the base image. I'll start with a petition to Nerdpack though. For future reference:
  8. I've installed the Nerdpack plugin but it's missing a command I'd like to have: pixz I've seen other posts suggesting that UNRAID isn't a "full" linux distribution and I'm guessing that means I need to download and compile from source, and I'm comfortable with exploring that if that's the route to go. But if there's a better/recommended way I'd like to try that first. To address questions I assume will come. Yes, I know xz is included, and I know xz now supports blocked archives and parallelism. It's just not the same as the ease of use of the random
  9. Ok, I would not say that my tests were definitive, but I am confident enough to say that this was user error (my fault). The ultimate issue sprang from how I made my key. I tried to concatenate a few binary files to make a file key and, for whatever reason, the key that actually registered was only the first of the concatenated files (I made sure to test with a combined keyfile size of less than 8 MB). While I don't have a complete, in-depth understanding of what happened, I think I have enough information for me to keep going with my build.
  10. Hi all, I'm pretty new here, just starting my UNRAID journey, and I just noticed there is a polls section on the website. I took a look at the RAM poll and saw the first page was from 2014 and many people were using 2 GB of RAM. I thought it would be interesting to look at how the poll results have changed over time and maybe share that back to the community. So I thought I should ask a few questions to start with: Has this kind of thing been done before? I.e. looking at forum poll results over time. Are there approved methods for scraping the forums or dow
  11. If I plug in a USB drive and directly copy data from it to local share, or cp a local file from somewhere else to a share, is the data parity protected? E.g.: cp -r /mnt/disks/External/Movies /mnt/user/Media/. I looked at system stats and drive I/O and it looks like the answer is, yes, but I didn't want to assume since I'm new to this and I don't have a good mental model for how the parity operations are integrated into the system (kernel? user-space program? something else?).
  12. I tried a bunch of things that didn't appear to fix the problem (wipefs, write the first 4 MB with zeros). That made me more sure it's something I'm doing wrong. I'll post again when I can confirm. @JorgeB Thank you for your help and prompt replies. I appreciate it.
  13. Not strictly relevant to fixing my issue, but shouldn't UnRAID have prevented me from making an array with a new key if it wasn't going to work? Is there a command I can run to quickly test if a disk will take a new key so that I can "fail fast"?
  14. I erased and formatted when adding to a new array in the GUI. And the new disks were both brand new and pre-cleared. I can try putting them on a different machine and doing a "quick erase" with /dev/zero and dd and then come back to the unRaid box.