figurefive

I'm still learning about dockers and so this question might be really silly but hopefully someone can help me out. I'm trying to apply nice and ionice to the unrarcmd in nzbget. The problem is that if I try to do it like this ${AppDir}/nice -n 10 ionice -c2 -n4 unrar The unpack just fails saying it can't find ${AppDir}/nice I solved this by just making symlinks in the appdir folder pointing to /bin/nice and /bin/ionice but these symlinks will get destroyed every time the docker updates, won't they? Is there a better way to do this? I don't know if the path can be modified somehow to make it able to access nice and ionice without the symlink or maybe i'm just doing it completely wrong.

That is a very strange move. Why would you even want to replace MLC with TLC? Because the MLC wasn't working. Not that it matters because neither works properly.

Don't know about your speed enigma, but you do have a choice. If apps is a cache-only share, then /mnt/cache/apps and /mnt/user/apps are the same. If you're exporting both the cache drive and that cache-only apps share, then \\unraid\apps and \\unraid\cache\apps are the same. Good point, but it looks like whatever I was seeing was just a fluke as now it's slow again no matter where I copy files to.

I replaced my Crucial M500 with a Samsung Evo SSD as my cache drive just to see if there was an issue with the SSD. Still having the same issues with slow and inconsistent write speed. One thing I noticed is that if I'm copying a file from windows to \\unraid\cache\movies then the speed is slow but if i instead copy to \\unraid\movies which uses the cache then my write speed seems normal. Why would that be? What is happening differently? They both end up on the cache drive at the end of the copy. I wouldn't really be concerned about it and would just copy everything to the share instead of the cache drive folder but I have cache-only shares that suffer from the same write speed problems. In that case I have no choice but to copy to \\unraid\cache\folder which gives me the slow speeds.

This appeared to be one of the more helpful pages about it. I don't see evidence of overclocking or overheating, but that still leaves possible problems with the system bus, the CPU caches, the memory (especially if ECC memory), or other even rarer issue. The easiest one to test for is memory, so try a long memtest. And no, I can't say if there is any connection with your SSD I/O speed, although it is possible. I've been reading this forum extensively the past few days, and MCEs seem to have one thing in common, the H87I-Plus. I'm trying my unRAID setup on an older B75/G1620 rig later, and will report back, but I think there's something not right with the H87I-Plus and unRAID (or perhaps it's Haswell?). Well that's disappointing if it's a motherboard compatibility issue. Were you having any problems with your setup, though? Or were you just getting MCE's in your log?

This appeared to be one of the more helpful pages about it. I don't see evidence of overclocking or overheating, but that still leaves possible problems with the system bus, the CPU caches, the memory (especially if ECC memory), or other even rarer issue. The easiest one to test for is memory, so try a long memtest. And no, I can't say if there is any connection with your SSD I/O speed, although it is possible. This article doesn't seem relevant to unraid because mcelog does not seem to be a function in unraid unless it must be run in some different fashion. So I guess that leaves it up to a guessing game as to what the machine check error is in reference to. As far as memtest, I left it running for 5 passes yesterday and did not have any errors. I'm going to order a new SSD and when it gets here I'm going to take all the drives out and start over with that much of it at least. Guess that'll narrow down whether it is a problem with the SSD itself.

I did find threads about SSD alignment but after looking through all that information it appears that my SSD is properly aligned. ... Still no parity drive so no parity calculations going on. I attached my syslog which is probably a bit of a mess since I've been screwing with it so much. Its very late for me, so I haven't finished looking at your syslog. but a couple of thoughts: 1. Add-ins/Plug-ins aren't well synchronized with each other...so they may start feuding over which library version to load in order to run properly. These conflicts are hard to find. Best practice is to install the ones you actually USE, and not everything you see that your might want to try. Get a basic working flash key set up. Copy it to your PC. Then, as you add plugins, if things don't work, you can always revert back to the saved version of the key. 2. Certain plugins are known to be incompatible with version 5. Headphones is one. Check the forums for the latest status on that one. 3. I'm not sure about Transmission. I don't use it, but I saw someone suggesting that it,too, didn't work with version 5. Check the forums for status on that one, too. 4. I don't think the plug in conflicts explain the speeds you're seeing. Are you sure you didn't flip the labels on the speed graphs by mistake? I installed most of the plugins just to screw around but am planning to remove a few of them (including transmission). Also, are you sure about headphones? I see many people on the forum running version 5 with influencer's headphones installed and it functions perfectly fine for me. As you say though I don't think it's a plugin issue, especially since I saw this issue before I had any plugins installed. I wish I had flipped the labels on those pictures but unfortunately it's true edit: I noticed some more strange behavior. When I'm copying to the cache drive, the unraid web interface becomes completely unresponsive. However, if I'm copying to directly to disk1 or the other hdd in the array, the web interface behaves normally. I don't understand that at all.

I believe you, but your graphs don't seem right! Most of us would *LOVE* to have 111 meg write speed to a regular hard drive. And if we were only getting 28 meg from an SSD, we'd throw it out! So you aren't calculating parity at all, correct? There is a thread in the forums about SSD drives and how to make sure their internal format is properly aligned. It was a problem with older SSD...but I think the newer ones don't have that problem. You might search the forums for it. (something like: "SSD internal block align" or SSD format) If you're still concerned, add some details about your configuration (number of drives, motherboard, RAM, etc.) so we know what you're working with. Also, details about the SSD (make, model, size, etc.) And a Syslog from unRAID would be very helpful. I did find threads about SSD alignment but after looking through all that information it appears that my SSD is properly aligned. As far as system specs go: i5 4570 asus h87i plus 8gb ram 2x wd red 3tb 1x crucial m500 240gb unraid 5.0.5 Still no parity drive so no parity calculations going on. I attached my syslog which is probably a bit of a mess since I've been screwing with it so much. syslog.zip

Does anyone know why write speeds to my SSD cache drive would be so bad or what I could look at to try to figure it out? I'm very new to unraid and linux so I'm not really sure how to troubleshoot this. When I'm writing to the cache drive, my speed starts out fine but after about 5 seconds they start becoming really slow and erratic. On the other hand when I write directly to one of the hard disks in the array, I get a pretty constant 100mb/s. I'm not currently using a parity drive because I'm waiting for it to arrive, but it seems to me that should make my speeds faster if anything. Writing to the cache drive: Writing directly to hdd in array: