trurl

Was this an update for the docker or an update for plex itself? I think LSIO issues weekly updates for their dockers, so if that was what you were doing then that sounds right. If trying to update the plex application itself you would just restart the container. I use this docker and I have updated it weekly just as you described. Does it do this when you update your other dockers?

How did you try to apply the update? Normally all you need to do is restart the existing docker and it will update itself. It sounds like you tried to install an additional instance.

Maybe it would be appropriate to unsticky this thread now.

It seems my Formatting FAQ tells about reformatting, but doesn't say a lot about actually formatting in the webUI. And it should probably also include something about not formatting when you have an unmountable disk. I will be away for a few hours so can't get to it right now, just looking for some more feedback. *edit* I have moved it from the FAQ to this thread until I can gather enough information to finish it properly.

Yes, you need to isolate this issue before it corrupts your data.

See the Nerdpack sticky starting here

Formatting Disks in unRAID The word "format" means "write an empty filesystem". That is what it has always meant in every operating system you have ever used. You must let unRAID format any data disk it will use in the array or cache pool. Note that format is a write operation. When you format a disk that is part of the array, unRAID treats this write just as it does any other, by updating parity. So, after the format is done, parity agrees that the disk has an empty filesystem. Format is NEVER part of the process of rebuilding a data disk. Sometimes, unRAID does not need a formatted disk. The parity disk does not need to be formatted since it has no filesystem. A disk that will be used to rebuild another disk does not need to be formatted, since it will be completely overwritten with the original disk's data. A formatted disk is not a clear disk, since it has a filesystem written to it. When you add a disk to a new slot in the parity array, it must be clear so parity will remain valid. If you don't preclear it, unRAID will clear it. Changing the format of a disk in the array If there are any files on the disk you wish to keep, copy them somewhere else. Then, in the webUI: Main - Array Operation - Stop. Main - Array Devices - click on the disk you wish to reformat to get to the settings page for the disk. Select the File system type. Main - Array Operation - Start will start the array and format the disk.

That one is still stickied in Legacy Support, but it has a link to it in the V6 FAQ. That is certainly one that I often refer to though. Unfortunately, the people that need it the most aren't the people who read FAQs.

It depends on if you have any settings that refer to specific drives. User shares can be set to include only certain disks or exclude specific disks, for example. It is also possible that you would have docker settings specifying certain drives. Etc. If you have settings that refer to user shares, such as docker volume mappings, for example, then changing the disk number that those user share reside on won't make any difference. You will have to consider your specific setup and deal with these if you move the files.

No. It is not even possible to do what you suggest without setting a new config. Assuming you have already moved all the files off the disk. Just stop the array, click on the disk to get to its settings page, choose the filesystem, and start the array to reformat it.

Is your Windows VM on unRAID, or another computer?

That one is still stickied in Legacy Support, but it has a link to it in the V6 FAQ.

You will only have a template to select if you have added a repository (don't bother) or if you already had a template for a specific docker. A template is just the stored settings for the Add container page. But you don't need to select a template. When you selected the "App" from Community Applications, it took you to the Add container with the page already filled out. The only thing you would typically need to do is set one or more volume mappings for the particular application to let it find your files. In this specific case, I don't think it needs access to anything except the appdata (config), which should already be set.

I think I need to make another one about the equivalence of user shares and top folders, since that is another one I have written and rewritten over and over.

This really sounds like a question for plex instead of for this specific docker implementation of plex. Are you sure you have your plex settings the same in both places? I know you can tell plex where to look to try to match movies and tv shows.

2) would work, but the concern I would have would be deciding what was the original drive number. Especially if you had disks of different sizes and needed to copy the contents of one disk to multiple disks, etc. 1) makes me ask another question though. Where else do you have drive references except in the user share settings? If you only had user share references elsewhere you wouldn't have that problem.

Makes complete sense. I formatted disk2 to XFS, but my data is still showing up in windows explorer for \\tower\disk2. Why is that? If I look from the console /mnt/disk2 is empty as expected. Is it being emulated from parity? At what point can I trust what windows explorer says? What you are seeing is the user share named "disk2" that you accidentally created when you botched the rsync command. Any top level folder on cache or array disks is automatically a user share.

That's what this thread is about. Start reading it from the end and you will find the latest recommendation a few pages back.

Thanks, good to know since I only use NTFS disks with Unassigned Devices.

Any disk you change the filesystem on will be formatted, so you must copy the files somewhere before changing. Simple as that.

I don't think there is anything for repairing an NTFS filesystem on unRAID. You will have to plug it into a Windows computer and let it checkdisk.

A tad misleading since you don't outright say to copy the data off of the disk prior to formatting. Although you do say in the main body that formatting erases everything, I'm worried that people will ignore the body (who reads nowadays?) and go straight to the step by step. Updated post to help keep people who don't bother to read from reading the wrong parts and making a mistake. Yes, I know it has happened many times with other instructions around here.

Since I have written about formatting many times in the forum, I thought I would make a FAQ for it so I can just post a link to it in the future. I am posting my thoughts here for feedback, especially wrt the reformatting steps, since I am not going to test them. I would also be willing to put this in the Wiki (where?). Formatting Disks in unRAID The word "format" means "write an empty filesystem". That is what it has always meant in every operating system you have ever used. You must let unRAID format any data disk it will use in the array or cache pool. Note that format is a write operation. When you format a disk that is part of the array, unRAID treats this write just as it does any other, by updating parity. So, after the format is done, parity agrees that the disk has an empty filesystem. Format is NEVER part of the process of rebuilding a data disk. Sometimes, unRAID does not need a formatted disk. The parity disk does not need to be formatted since it has no filesystem. A disk that will be used to rebuild another disk does not need to be formatted, since it will be completely overwritten with the original disk's data. A formatted disk is not a clear disk, since it has a filesystem written to it. When you add a disk to a new slot in the parity array, it must be clear so parity will remain valid. If you don't preclear it, unRAID will clear it. Changing the format of a disk in the array If there are any files on the disk you wish to keep, copy them somewhere else. Then, in the webUI: Main - Array Operation - Stop. Main - Array Devices - click on the disk you wish to reformat to get to the settings page for the disk. Select the File system type. Main - Array Operation - Start will start the array and format the disk.

Some users including me that had this discovered they had bad RAM. Please do a memtest immediately!

You could simply bookmark http://tower/Dashboard This is the only bookmark I have to my server. It's really a better overview than Main and I can easily get to my Dockers webUIs from there. If you have already have a bookmark to your server, just replace it with a bookmark to your server's Dashboard.