trurl

No doubt I am somewhat repeating what has already been said, but sometimes different ways of saying the same thing can clarify. The process in the wiki does maintain parity. The only thing that might make it seem that it doesn't is that message you get after New Config. That is simply because New Config tells unRAID to forget about the disk assignments and whether parity is valid or not. It would be better if the message went away after you check the box, though. It would be possible to remove parity before beginning as I think RobJ mentioned, and that would speed up some of the disk writing, but then parity would need to be rebuilt at the end, which would take time, and you would be unprotected until it was rebuilt. Yes, plugins were introduced in V5. Before that we just had packages with no "official" way to manage them in the webUI. unMenu did have PKG Manager which helped with this but not many developers did any development with it. The problem with plugins and packages was that they were not isolated from the core system, or indeed from each other, and so there could be conflicts which produced serious issues. The recommended approach in V6, and a great improvement in many ways, is to use dockers unless your addin needs to modify the webUI or work directly with the core system in some way. Not only are dockers isolated from the core and each other, but they are easier to develop, as is shown by the incredible number of applications you can now run on your server. You can think of dockers as sort of minimalist VMs with only a single application installed in them.

What time zone? Better yet, how long ago was 7am for you?

Not sure what you are referring to here. Not a lot has changed about User Shares from 4.7 except some of the Use Cache settings. Were you not using User Shares before?

As I said earlier in this thread: When I did this there wasn't a wiki for it. I didn't even bother with rsync and verification. I just used mc to move disk to disk. Never needed New Config, parity rebuild, or preclear. But everyone won't have the spare capacity, or other details specific to my system. And it still took a few days since that is what is needed to move TBs of data. It perhaps doesn't need to be nearly as complex as the wiki procedure for most people, but the specifics of the process will depend on the specifics of their system. The wiki is trying to give a process that will work for all possible systems. And it may even be that some people will have something about their system that nobody thought of and is not covered by the wiki. All of which maybe makes it understandable that Limetech's limited resources haven't gotten involved in this. It is only done once for a given system, and not done at all for new users. So there is nothing built-in and foolproof to do it.

I question whether this is the solution for whatever your (secret) problem is. Hosts just gives names to IPs, sort of an override of DNS. Usually any time you need to specify a network location you can just use the IP instead of the name, Have you tried that?

There is /etc/hosts but I've never heard of anyone needing to edit it.

I think it's more like an artifact of the remote desktop in the container.

Thought I would add a few thoughts to this part. The most important being that if you do wind up using one of these disks in a new data slot, then it will need to be cleared so parity will remain valid. unRAID will clear a disk you add to a new slot if it isn't already marked as clear, but I would recommend using preclear for this since that gets it done before adding and so takes place independently of anything else you have going on like other conversions. Also, when you formatted disk3 to XFS and then rebuild made it RFS again, this was not really a "conversion". unRAID didn't reformat it to RFS or anything like that, it just rebuilt the previous content and the previous content was the RFS filesystem. Rebuilds and other parity operations don't even recognize filesystems, it is all just a bunch of bits.

If you ever want to do a cache pool BTRFS is your only choice. If you will only have a single cache disk you can change it to XFS if you want. Perhaps a confusing thing to call it since Maintenance Mode is already a thing. The only time unRAID requires a clear disk is when you are adding it to a new data slot in an array that already has valid parity. A clear disk is all zeros so has no effect on that valid parity. People often use preclear to test a new disk even when they don't require a clear disk. Unless you really think these previously used disks need further testing, I would say preclearing them is adding needless complication and a whole lot more time to the process. Unassigned Devices plugin. And, first things last Have you read this sticky?

Possibly bad docker volume mapping.

True. The wiki addresses that in the notes before the steps are enumerated: You have one Parity drive, not two! If you have dual parity, this procedure will invalidate the second parity drive. You can still use this procedure, but you might as well unassign the second parity drive until you have finished converting all of the drives you wish to convert. Then you can reassign it and let it rebuild. Why? The first parity drive does not care about drive positioning within the array, so we can freely swap the drives around. The second parity drive *does* care, so no drives can move or be swapped, at all!

yes

Don't know about dolphin, but have you tried in mc (Midnight Commander), where you would be root? There were permission changes after 4.7, you may have to fix that from the command line with an Unassigned Device, or if you could get them copied to your array there is a way to fix those files from webUI.

I think the reason for going to global share settings and taking the drive out of the exclude list is so you won't forget and later accidentally exclude another disk that eventually comes to occupy that disk slot (#). The reason for formatting is because the script that clears the drive checks to make sure it doesn't have any files still on it. Formatting is quicker than deleting to get rid of all the files on it, but formatting doesn't actually clear anything. Formatting actually writes an empty filesystem to the disk. It is the Clear Me script that clears the drive by writing zeros to every bit of the disk, and since the disk is still in the array while it does this, parity is updated to reflect those zeros. Once the disk is all zeros, it can be removed without affecting parity.

Settings - Unassigned Devices Settings - Enable NFS Export

As you have done, you should post in the support thread already started for the specific plugin you want to get support for. Creating new threads here should only be done by plugin developers for new plugins they will support.

Also, there are some other things in your syslog: Mar 21 19:43:59 Tower root: Fix Common Problems: Warning: Share Movies is set for both included (disk1,disk2,disk3,disk4,disk5,disk6,disk7,disk16) and excluded (disk17) disks ** Ignored Mar 21 19:43:59 Tower root: Fix Common Problems: Warning: Share Music is set for both included (disk8) and excluded (disk17) disks ** Ignored Mar 21 19:43:59 Tower root: Fix Common Problems: Warning: Share TV is set for both included (disk9,disk10,disk11,disk12,disk13,disk14,disk15) and excluded (disk17) disks ** Ignored Why do you have it set to ignore these? They are there for a reason. Include means "include ONLY the listed disks", but Exclude means "ALL EXCEPT the listed disks". You should never set both include and exclude. And then there's this: Mar 21 19:44:23 Tower root: container "MineOS" hostpath "/mnt/appdata/minecraftos" does not exist It should be /mnt/user/appdata/minecraftos or possibly /mnt/cache/appdata/minecraftos

Sorry, I meant go to Tools - Diagnostics and post complete zip. It includes syslog(s), SMART for all drives, lots more. Thought you might have already known about it. The standard for V6.

Post diagnostics of course

I just control things by setting each of my user shares to only include specific disks. I have several shares that are not very large and are all together on one disk. Only my Movies share spans (only 2 so far) disks. If it ever needs more I will just include another when needed (or more likely, upsize its disks). This is why I think user share settings gives you all the control you need. And my other user never has an opportunity to do the "User Share Copy Bug", since I don't share disks.

Looks like a download problem. Can your server ping raw.githubusercontent.com?

Maybe the instructions were meant to cover everything that might be important to anyone. Not likely to bring the whole thing down, but it is possible to make things work differently than they did before depending on how you have things configured. And people can make mistakes if they aren't careful that would cause them to actually lose data. My system is more complex than yours, but I did the conversion pretty early when this thread wasn't very long. If you know how parity works and how formatting works and how user shares work you can pretty much adlib it. The main idea is that changing the filesystem on a disk will format it, so its contents must be moved or it will be lost. Swapping disks, for example, is only important if you have something configured to use specific disks.

Linuxserver.io has their own forum and if you aren't using unRAID you should use that instead. Here is their docker support section. https://forum.linuxserver.io/forum-20.html