RobJ

I've now added the gist of the above as 'A preliminary step' to File System Conversion. I think this is a good thing, as it generalizes the routine for those who cannot add another drive to the array, but still want to convert it. I've also added the term 'swap drive' to refer to the empty drive used for each conversion. I *think* (not sure) it makes it slightly more intuitive.

Different tools show files sizes differently. It would be helpful to show what you are comparing with, as we can't tell what is wrong that you want us to see. I have NEVER seen so many parentheses in a file name! And more in the path. I can't help wondering if that is tripping up something, particularly if it goes through some regex or shell processing. It's clearly not displaying correctly in the line message for each file (evidence of a buffer overrun), so it may not be loading the right file name into the hasher.

Not sure. They kind of do different things and it might be confusing to combine them. You're right, I didn't realize how different they are. One is more of a search result, and the other a monitor(?).

Hmmm ... I wonder if this could be enhanced to do both?! Perhaps a toggle to show only open, or only written, or both.

Added (with thanks!) to Guides and Videos And added to the Docker FAQ in -> How do I get started using Docker containers?

+1 I'm ready to convert my fs too and after reading this thread, I have a headache. I'm looking for the safest process with easy step by step instructions. I did read the instructions on wiki, and they are good, but conflict with other advice in this thread. That is th e only reason I have not started. I would be happy to see the experts agree on best process to follow (how they would convert their fs) and put on post #1 You mentioned a wiki page, are you referring to this one -> File System Conversion If so, I wrote most of it but others have had a hand in improving it, and I'm perfectly willing to revise it further ... I welcome any suggestions. Can I ask what were the conflicts you saw? Yes, that is it. Conflicts may not be the right word, as I see slightly different steps, suggestions in this thread that very a little from the wiki page. So I wonder if the instructions are slightly out of date in terms of best practice. Given I'm ready to get started, I wanted the safest and fastest (easiest) steps get my fs converted. If you needed to convert your fs today, would you follow the wiki exactly, or is there a few suggestions in this thread that you may use? Means, after reading through this, would you update your wiki page, or follow it as is - again if you needed to do this today? If it is good enough for you Rob, it's good enough for me Because I couldn't remember any differences, I decided to look back a few pages. But unless I missed something (and please tell me!), the only difference I saw was the special situation where several users wanted to convert drives but did not have a free drive, did not have a free port to add a drive. So they had to have special instructions to work around that. But in thinking about it, their situation is just a special case of the regular situation. No matter what, to convert a drive you MUST move all the data off of it, before you can format it with a new file system, then copy data to it. So their case is just an extra preliminary step, basically picking one of the largest drives with the least amount of data, then either using unBalance or manually moving all of its data to the rest of the drives. At that point, they have freed up a drive, and therefore fall into the normal situation, and can use the same procedure as everyone else. There's no way around it, you HAVE to free a drive up! To convert your array, you must start with a free and empty data drive, whether you add it or juggle data around to create it. (I'll try to add this preliminary step to the wiki, for those who need it.) So yes, if I were running v6.1, I would use the procedure in this post, and if I'm running v6.2 or later, I would use the procedure in File System Conversion. At the moment, chip is doing part of the wiki procedure, but what is different is that he's not restoring the converted drive back to the same logical slot, so he is running into the problem of the data being on different logical drives than the previous share settings, and possibly other drive references being wrong now. So chip is either going to have to correct all data and share references, or do a New Config to set all the data back on the original logical drives. Plus, if he is doing copies, he may see file duplication on the shares during the conversions. But chip should probably not listen to me! Because he's got a plan now, and it's working, and he might as well stick to it!

+1 I'm ready to convert my fs too and after reading this thread, I have a headache. I'm looking for the safest process with easy step by step instructions. I did read the instructions on wiki, and they are good, but conflict with other advice in this thread. That is th e only reason I have not started. I would be happy to see the experts agree on best process to follow (how they would convert their fs) and put on post #1 You mentioned a wiki page, are you referring to this one -> File System Conversion If so, I wrote most of it but others have had a hand in improving it, and I'm perfectly willing to revise it further ... I welcome any suggestions. Can I ask what were the conflicts you saw?

Turbo write should be a little faster than normal writes but because the source disk has to alternate between reading the data to copy and data do update parity it's considerably slower then normal turbo writes, IIRC it maxes out at ~60MB/s. Within the past week, I just tested and can confirm this to be true, the constant re-seeks slow down Turbo Write. And another factor that can slow it down further is having a much slower drive in the array, because like parity checks, Turbo Write cannot go faster than the speed of your slowest drive. If your array of drives has a mix of slow and fast drives, and your transfer will be between 2 fast drives, then you probably want read/modify/write, not turbo write. My Turbo Write speeds and parity checks were getting slower and slower, dropping below 30MB/s, and I assumed I had a failing drive, but I couldn't identify it, all SMART reports looked fine. (When I have time, I'll write it up - very interesting/distressing drive failure, some surprising SMART behavior, and some improvements needed in our SMART issue detection.)

Nope. I keep checking the version number, as I said: I'm still on 2.3.1. Have you restarted the app?

For login failures, from Windows or networked devices, especially if you are running unRAID 6.3.0: The Samba developers disabled the older form of authentication between devices. This results in login failures when one of the devices only supports either the new form or the old form, but not both. Here are 2 methods to resolve this, one re-enables the older form on unRAID, the other is an example of how to enable the newer form on the other networked device. You should only need to do one of the methods, choose the one that seems more appropriate. Enable older authentication method on unRAID (from SnickySnacks, here and here) Go to Settings->SMB and enter the following line in the Samba extra configuration: box: ntlm auth = yes Then either reboot or restart Samba (at a command line, execute smbcontrol smbd reload-config). Enable newer authentication method on networked device (from here) You will need to find how to enable NTLMv2 on the device. On some devices, you must find and edit the smb.conf file, and add the following line to it: client NTLMv2 auth = yes Then you will usually need to restart the device. If you wish to view Samba debug messages for further troubleshooting analysis, then see the instructions in this post. We understand that when 6.3.1 is released, this situation may change. We'll update this as needed.

The VirtualBox plugin was updated to current, this morning.

I fear something may have happened to him. He hasn't been on the forums since January 27, his last post was September 7 of 2016, and it said "Probably next week" - after being asked about a time frame for releasing an update. I suspect he wouldn't mind if someone had time to do a little revision of the current testing version, for unofficial release. Use his last discussion for guidelines. Does anyone know him, could check on him?

Dan, respectfully, please don't terminate the previous version, there will be users who stay with older versions, that's just the way it is, probably always will be. Just a note about the term 'deprecate', when you say something is deprecated, you aren't saying it's terminated, you are saying it's still available and completely usable, but that there's another option that is now preferred over it. For example, Microsoft would say that Windows 7 is deprecated in favor of Windows 10. Many users would disagree, and continue using it. I would prefer that auto update be turned off for the previous version, so that the Recycle Bin still works for all users, no matter what version they decide to use.

Are you sure your Preclear plugin is up to date?

More outstanding work! I've added it to Guides and Videos. Also added a plug, for the credit deserved!

I'm sorry, I was avoiding this thread until I had time to answer ALL of the related posts. My apologies to you. I suppose I would have considered killing it after 5 to 6 hours, definitely if it was still running after 10 hours. I don't have any ideas yet as to what could have gone wrong. Can you tell if there is any I/O to the drive? Syslog may help, post your diagnostics (Need help? Read me first!) We should take this to a separate thread.

This is an attempt to collect in one place recommended hardware for VM applications. There are numerous discussions scattered here and there about the pros and cons of various components. Collecting it in one place seems like a good idea, *if* users buy into it and contribute. I'd like to see posts on whole setups that work, as well as posts on a single component that the user has determined works well. For consistency, easier comparison and readability, I'm going to make some simple style and content recommendations, but they are just to get the ball rolling, can change easily, may evolve with time. I don't want anyone to ignore this just because they don't like the way the info is laid out. Info I would like to see is: - the item name or list of item names - preferably one per line (bolding each is suggested) - the best usage for the item or items - a 720 and a 1070 can be equally excellent, for very different usages - the user's rating of the item or items (suggested: Excellent, Good, Fair, Don't bother) - rating could be for a system as a whole or for each item; could also add note about how well it works for the user's own purposes - what settings, modules, and tweaks are needed for setup and best performance - obviously this could be the longest by far; but what a user really wants to know is what will it take to make this component work for them as stable and bulletproof as possible, with reliably great performance - any special notes and comments, and links to actual products (on Newegg, Amazon, eBay, etc) An Example: (this info isn't real!) RX480 Usage: Light to moderate gaming, any general purpose use Rating: Excellent; perfect for my Plex and Far Cry Instructions: use Seabios, i440fx-2.5, do this, do that, see <link> for more info, etc Note: search eBay, often find used for under $100 I'm hoping users with great working systems will contribute here, so any user can search this for the best GPU's for what they need, or the best CPU and motherboard combos for what they want to do, or the best USB cards for passthrough, or whatever other common needs VM users have. I do not feel the need for a list of what *does not* work, or doesn't work without headaches, just what works well, and can be recommended to others. In other words, we don't need anything rated 'Fair' or 'Don't bother'. Please, no support requests or questions here (like 'would this work?'), I'll probably delete or move them. Edit: we're off to a great start! nice contribution from 1812! Index to Recommendations Graphics Geforce GT 710 Geforce GT 730 MSI GTX 750 GTX 760 SC Zotac 1060 3gb mini MSI 1070 Seahawk MSI 1070 Quicksilver Zotac 1070 Founders USB Fresco Logic FL1100 USB 3.0 Host Controller (sold as Inatek KT4006) Network 666172-001 MNPA19-XTR HP 10GB Ethernet Network Card (Mellanox ConnectX-2 EN) Motherboard Asrock Fatal1ty X99M Killer Gigabyte X99 Designare EX

I can't check it now, but there should be an option for retaining everything.

Using unRAID v6.1, and with no gaps in the assignments (8 data drives should be disks 1 through 8, not 1-3 and 5-9), then you can simply unassign and reassign the disks at will. You may have to indicate that Parity is valid on array start. Using v6.2 and later, you will need to use New Config with the Retain Configuration option, then make the assignment changes you want. When you start the array, you will have to indicate that parity is valid (assuming it's the identical set of drives). If you have setup dual parity, then the second parity drive will no longer be valid and will have to be rebuilt. In other words, you cannot preserve the second parity drive if you reorder the data drives.

I'm not qualified to verify the info, but it sure looks good! Very nice work! Hope to see more! I've added it to the Docker section of Guides and Videos.

Agree on both points, safer mode and no autostart

It works well enough as it is, and it's obviously not a big issue, but I suspect some of us would be happier if we had a way to suppress the ignored messages going to the syslog. Perhaps when you have time for a minor enhancement, you could add an option to suppress them even from the syslog, then add a view option to see the last set of ignored messages. So when you run a scan, send the messages either to the syslog or to an internal buffer, which can be viewed on button push ("Display ignored messages").

That custom kernel wiki page is very old, and for 32 bit systems (you need 64 bit only). I really don't recommend trying to use it! Especially if you are new to Linux! Far better to find something precompiled, or ask someone that has done it, such as the 'unRAID DVB Edition'.

This is an avenue I hadn't thought of, worth consideration. As you know, the current method and the new method I've discussed are strictly for protecting shares from attack from *externally* infected machines. They assume the unRAID server itself is safe, uninfected. So when an attack is detected, the lockdown is simply closing the gates to the outside world, blocking write access. We were not worried about software packages (whether plugins, Dockers, or VM's) running on the server, so they have essentially unrestricted access to whatever folders they are configured for. You are suggesting a variant of this new method, that could be used to detect a local infection (something that has infected the unRAID software), and initiate some sort of array lockdown. Certainly it could be used with little change to detect an attack, detect any deletions in /mnt. Mechanisms for arming and disarming would have to be different, not sure how that would work, perhaps a detection of a specific process, or some file that is changed when a software package starts and exits. And the lockdown process really needs some thought. It's simple to initiate stopping the array, but it takes time, and that allows increased encryptions. Array stop has to wait for all VM's and containers to shut down, not necessarily a quick process. Worse yet, the array stop can be easily blocked by opening files on each data drive, blocking the unmounts. We need some kind of hard termination, forced quick unmounts, but with minimal corruption of the VM and container installations. This may be tough to do. Might be better to delay this, give it more time and thought. For now, it's best to keep our systems patched and updated, as uninfectable as possible. For many users who are running their Plex's and other software non-stop, there's no disarming, they are always 'disarmed', and deleting files at any time. If detection was limited to only those data folders they don't access (archive folders, personal collections, bait folders), then it would become more of a smoke detector that has the power to shut the system down.

Hmm, is Help on by default for a new install? Nope!