trurl

What do you mean by this? We seldom talk about docker commands, since most of what you do with dockers in unRAID doesn't require you to run any docker commands. In this particular case we are trying to find out how you have configured this particular docker to run on unRAID. unRAID will display the docker run command it uses when it starts the docker, based on the way you have configured the docker in the unRAID webUI. Or are you not even running unRAID?

I don't think it is required, but I've never tried it that way. Even without the UD plugin, you still have unassigned devices. UD just allows you to work with them in some ways that you can't without going to the command line.

In Disk Settings

You seem to think you need to remove a disk then add it back. That must be where you are going wrong. You absolutely do not need to do what you are proposing. We have all done this before and this is all you need to do: Stop the array. Click on the disk you want to reformat to get to its settings page. Change the filesystem to XFS. Start the array to reformat. There is never any removing a disk or adding a disk back again. The disk is already part of the array. You want to keep the disk as part of the array. You can format the disk while it is part of the array. Formatting will write a new filesystem to the disk, and since it is still part of the array, that write will also update parity so it remains valid. As for the other thread, it is completely irrelevant whether the replacement disk had a filesytem or not. When you replace a smaller disk with a larger disk, that smaller disks contents are rebuilt to the larger disk. The filesystem of the smaller disk is its contents. If you try to follow my instructions above, and for some reason you think it isn't working, post a screenshot.

It gets pretty confusing after step 2. Maybe I missed something in your previous posts (haven't reread them), but I can't imagine why you want to get Unassigned Devices and parity rebuilds involved. Probably don't even need step 1. After step 2, you have moved all data off disk3, so you can just stop the array, change its format, start the array to reformat. Parity remains valid, disk3 is now XFS and empty, ready for you to move data onto from any other disks you want to convert. Not sure what is getting you confused here and making you come up with this scenario. Basically you just need to move all the files from a disk so you can reformat it to another filesystem. Formatting a disk while it's in the array updates parity at the same time. Format is simply a write operation, it writes an empty filesystem. unRAID treats this write just like any other, by updating parity. OK, I just went back and read this post you made on another thread At the point where you said you replaced a drive, you seemed to think unRAID decided to format the replacement to XFS. It didn't format anything. It rebuilt the smaller drive (which had just been formatted XFS) to the larger one.

Do you have any other working dockers?

1) The disk is part of the parity array, but not part of the user shares. 2) Since the disk is not part of the user shares, the disk is shared. 3) All the disks that are part of the user shares are included, but not any disks that are not part of the user shares. 4) Since the disk is part of the parity array, parity is written when the disk is. 5) Not sure what you mean here. Writing to the disk will obviously decrease its free space.

You might have to actually go in and Force Stop it (android, I don't know how iOS calls this), since sometimes these keep things running in the background even after you close them. Or maybe reboot your phone.

Do you have an app on your phone that may have accessed your server, such as Controlr or Margarita?

Lots of search results for "wrong csrf_token".

You might try deleting and recreating docker.img, then reinstall your dockers from CA Previous Apps. Also, though I have tried both Krusader and Dolphin, I don't use either. Midnight Commander (mc) is builtin to unRAID and is very easy to learn and use.

The syslog in your diagnostics only has a couple of minutes just after reboot. It would be better if we could see some activity that would show the problem.

Sounds like you have larger issues. Tools - Diagnostics. Post complete zip.

What version of unRAID? Do you have any other working dockers?

See this post for some explanation of how cache_dirs works and how Windows Explorer might cause disks to spin up anyway.

Do you have an rutorrent folder within the appdata folder (that is how most people do it)? I would expect an rutorrent plugins folder to be within the rutorrent folder in appdata. Do you really understand volume mapping?

Does your BIOS see both drives?

I don't use this but it sounds like there is supposed to already be a plugins folder in your appdata for rutorrent. Have you looked?

I wouldn't think that would have broken anything, but you can try removing the container and recreate it from the template.

Your limetech plex has a container path of "/Media" but your linuxserver plex has a container path of "/media". These are not the same and if you are using a copy of the same library then it is expecting to find everything in "/Media". You will have to change your linuxserver container path to "/Media".

And if instead of a user share, you are trying to use an Unassigned Device that you have mounted as media, it is in /mnt/disks/media.

Not necessary to use a disk, but /mnt/media isn't anywhere. If you have a user share named media, it is at /mnt/user/media

I would say that not only do most users not know it's not going to work, but they wouldn't really know how to proceed if it did work. The user can only get a disk with data on it added to the array by doing New Config, at which point they should NOT check the parity valid box. But you know how people don't bother to understand things, or even read the first post of the support thread. The more advanced users can still get this done by partitioning and formatting the disk at the command line, and then just having UD mount it.

I managed to split this, I think without losing any of it. Split works quite a bit differently than the old forum (you must select all the posts you want before telling it to split), and merge does something completely different (merges multiple posts into one, instead of merging them into another topic).