BRiT

I don't know if this is the situation, but it was (is?) not uncommon in the Linux realm to only be able to read NTFS filesystems. One used to have to use different drivers to be able to write to it. Hopefully someone that does use UD and NTFS can give more specifics.

No. The docker engine requires the host to have IPv6 support, which unRAID does not support for some odd reason despite requests for IPv6 support for a long time now.

Normal preclear or fast-preclear? I dont have experience with the slow 5900 RPM HGST, but the 7200RPM HGST completed 3 cycles of fast-preclear in 75 hours.

Are you saying the existing warnings were too big and you want them to be smaller?

Amazing!

Master plugin has no settings. It's a display only tweak.

No. The Recycle Bin plugin is correct. I see this all the time with multiple programs. What they seem to do is initially create a 0 byte file with the original filename. They then write to a new temp file, then delete the place-holder file, then rename the new temp file to the original filename. This happens exactly like this when downloading .NZB or .Torrent files from WinOS clients via web browser and writing to it from SAMBA. It also happens when Emby does media scans from WinOS clients. It seems to be how WinOS Clients operate when writing to network shares.

There's 69218 users, slightly over 9000 users have made 1 post [ http://lime-technology.com/forum/index.php?action=mlist;sort=posts;desc;start=9000 ]. That's roughly 87% of users are spam-bots that never made a post. I thought it was more. Of those accounts which made 1 or 2 posts, a majority are likely to be spam-bots who's posts has been moved to the bilge. Anyways, humans suck.

According to the forum stats, 87.4% of the users here will never read a manual (or ask for directions). http://lime-technology.com/forum/index.php?action=stats That's because this forum is archaic and doesn't have proper spam-bot prevention. That went over your head. [emoji14] Sent from my LG-D852 using Tapatalk Oh. I thought you were pointing out that the majority of all "registered users" in these forums are really spam-bots. Though I think that number is far larger than 87%.

According to the forum stats, 87.4% of the users here will never read a manual (or ask for directions). http://lime-technology.com/forum/index.php?action=stats That's because this forum is archaic and doesn't have proper spam-bot prevention.

First all, I applaud everyone who keeps working to provide functionality that spans the gaps in unRAID. As it is, this plugin should not exist at all. The moment unraid started limiting the number of all devices attached is the moment unraid needs to provide real management of all those devices. Let's hope LT realizes this and builds in the required support. In the mean time, keep up the great work and try not to take things too personally when users remain human and refuse to help themselves by looking at the provided help and manuals.

I cant see any pic, but you might be navigating up to the parent directory which is /mnt/user, which is the entire contents of your array. The simple fix is don't.

Those are built in shares for WinOS, such as C$ or D$, so one can not rename those. They can however create their own shares with the proper share names.

I have 4 docker containers that handle irc bots, usenet downloads, torrent downloads, and pushing items to the Tivo. My Docker image file is a consistent 1.7GB. After months of usage it may hit 1.8GB. I really don't know what dockers you're using or why they're so large.

You really should be running the latest beta21 first. Earlier betas of 6.2 are no longer supported by LimeTech and thus shouldnt be supported by the community either.

I don't want it because I already have my network permissions setup properly with appropriate users on other systems and I have my local docker docker containers properly configured. Your proprosed forced change would completely undo all of that.

I request this setting is not made globally. I dont want it. Others won't want it. Let it be an option, but do not put it as default.

Any idea what is causing this? If i had to guess I'd say its special characters in the directory filenames, the apostrophe and the semicolon causing script issues.

what is the point in leaving a dead drive in the array. Once you get any write errors to a drive unRAID will stop writing to it so no point in keeping it in the array. You also increase the chance of encountering a multiple drive failure scenario which will lead to data loss. I meant keeping it in till it dies. As in reallocated sectors could go into the 100's and you'd still keep running with it. Heck, don't even bother with parity. It's your data, take whatever risks you want with your data.

Well I checked while cache dirs is running and I have 3,5GB free acording to free -m command information If you're using windows explorer to check, be aware that it will inspect the files which is not part of what is cached, just the directory entries. You need to use a file client that wont inspect the files themselves. The best way to check if a disk directory is part of the cache is using a linux command shell and typing "ls /mnt/user/share/dir/subdir" or "ls /mnt/disk#/share/dir/subdir". If the disk is spundown and cached by cachedirs it should not spin up using that command.

wow rly? So my problem is that i did't calculate it with the kibibyte system? Well ok, i must tell my server that it's the problem, sure it will fix it right away! Ya,RLY! Your problem has nothing to do with the fact that 64GB = 65536 MB. Your problem is entirely something other than the basic scientific computing facts.

Units. Conversions. Learn them.

Any chance of triggering an updated container build? Thanks as always hurricane!! Capt.Insano, please read the immediate post above yours.

It works with parity since the operation is against the parity-protected device(s) that you specify, /dev/md#. It really is no different than other various writes to the array devices.

You will get your command prompt back, when it's complete. There really is no other means of telling when it's finished.