dboonthego

You can't rebuild onto existing data disk if that's what you're asking. If the disk isn't already part of the array, you can rebuild to it, but any pre-existing data will be overwritten. Also, if the problem is within the file system, a disk rebuild from parity will result in having same problem.

So parity was rebuilt onto a new disk and you added an additional data disk, then decided to pre-clear them afterwards? Did you clear one or both? If you cleared both at the same time, you'd have no choice but to new config. If one at a time, then each would go through a sync/rebuild. Is your question about how to rebuild or the GUI? A missing GUI isn't normal.

I would highly recommend using a SSD cache disk especially if you use dockers.

Try updating the unassigned devices plug-in to current version and see if that resolves it.

I'm assuming the account in question is chase? Are you logged into the Windows machine as chase? Have you set chase's Unraid user password to match chase's Windows password?

Any exported disk shares will also be removed. I think the key takeaway is all disk settings are reset to defaults. I had similar experience recently realizing it did more than reset drive assignments.

Those are the same switches I use, except for 'h' which is for human readable output. The command is more of a delta copy though. If the intent is to match destination with source, adding --delete will remove files that exist on the destination, but don't exist on the source.

Check out Nextcloud. The Android app can monitor the Camera folder among others and do exactly what you want. Auto-upload works great. It may be a feature now, but keeping in sync wasnt available. Ex. Once uploaded, file stays on server even after deleted from phone. You're an Unraid user, you can figure it out.

Can you elaborate on what you really mean by start over? Do you really want to start over from ground zero and keep nothing? You mention not caring about tv/movies, but are there any precious cat pics dear to your heart? The easy answer is format everything and rebuild your flash. I doubt you want to do that though.

From the documentation:

Can you SSH to the server? If so, type diagnostics at terminal prompt and it will save to flash.

It was changed to make it easier to underatand for new users.

It works for you because you have only two disks; lazily taylored for you. As is, the output doesn't tell you which disk the dupe is on (with 2 it doesn't need to) and doesn't properly handle disks 10+ Bummer nothing was found. I'm interested to find out the cause.

You want to compare the files of disk1 against disk2. No reason to compare the user share. Try this. Duplicates will save to /mnt/disk1/output2.txt. find /mnt/disk* -type f > /mnt/disk1/output1.txt sed -i 's/disk[0-9]/diskX/g' /mnt/disk1/output1.txt sort /mnt/disk1/output1.txt | uniq -d --all-repeated=separate > /mnt/disk1/output2.txt

Unraid's default cache pool name is "cache", but yours is named "plexer." You don't have another pool named "cache," but looks like you DO have a share called "cache" which exists on the array. Maybe that's what you're expecting to see and why you don't see it? You can add multiple pools and elect to designate a specific pool in your share settings. If you just added the m.2 in cache slot, you should see it as available "Primary storage" option in the share settings. I would edit your system, domains, and appdata shares and set them to use a primary storage pool and no secondary storage. Then move every instance of these folders off the array disks and onto the primary storage pool.

If I understand correctly, you installed disk5 and formatted it. Then unassigned it and pre-cleared again using UD? Yes, it will rebuild the disk using emulated contents; which is nothing at this point. Why not get your OS current?

If your replacements aren't bigger than 6TB then it really doesn't matter. I would probably do the data disk first.

On one hand you're saying you want to copy to the cache temp video folder and then have mover move those to array, but on the other hand you're saying you want to have the mover move those files back to cache? The mover is one direction. Also, there is no mover on a cache-only share, but I think I know what you meant. This is the old terminology of "prefer." Use this if you primarily want the files to reside on the cache. New files are written to the cache, and you want them to stay on the cache. If the cache gets full, then new files go on the array. The mover will move them back to cache when space is available. This is the old terminology of "Yes." Use this if you primarily want files to reside on the array but want to take advantage of the cache disk for faster write speeds. The mover will move files from the cache to the array. This is what you said you wanted.

SSH is still available with array stopped.

You do it like this: Primary Storage = Cache Secondary Storage = Array Mover Action=Cache --> Array

You probably would have received a link if you just asked. Remember, people are volunteering their time to try to help you; a positive attitude goes a long way. The manual is at docs.unraid.net and is laid out rather well. Follow these clicks: Unraid OS > Manual > Storage Management > Replacing disks > Rebuilding a drive onto itself

Basically, your friend purchased this and gave a license to you. It's frowned upon. I'm not sure if Limetech will transfer the registration.

Files amongst your shares can be spread across multiple disks. It's normal to have the share folder on multiple disks, but the abnormal part is having the same filename in the same directory on two or more disks. There are several reasons why this can happen; moving files from disk to disk is one of them. If the files are copied to destination, but not removed from source, you have a duplicate situation. Unraid fetches your files from the array disks and shows them to you as if they are in one spot. Your SMB share can only contain unique filenames so if duplicates are encountered, Unraid picks one to return; probably lowest disk#. It's the same reason why you cannot have duplicate file names in the same directory on your Windows system. Reading or writing to a duplicate file may also spin up those other disks and parity. When one spins down another might spin up because the file exists there too. It's weird behavior and the resolution is to make sure there are 0 duplicates across your array.

Normal stuff, not the issue. The dupeGuru docker might be a good option for you. It may or may not be easy to determine yourself if you have duplicates or where they exist. Considering you've used unBalance to shift files around, there's a good chance you have duplicates somewhere. All it takes is one to cause this. You can poke around your disks to compare. Go to shares > disk shares > diskX -> Export=Yes to enable disk level shares. Just be careful not to copy files between disk and user shares and perhaps set Export=No when you're done. No single file should exist in the same location between two disks. You will need to determine which file to keep as these are duplicate file names, but binary content could be different. You can test how it works yourself. Create a text file called dupetest.txt. Edit the contents to something like "This file is located on disk1" and save it to a share on disk1. Copy the file to the same location on disk2 and edit its contents to "This file is located on disk2" and save it. Now browse to \\tower\share\dupetest.txt and open it. Unraid will serve you one of the two versions. Now, delete it and it will seem like the file did not delete. If you open it again, it will be the other version. Delete it again and the file is gone.

They're not USB, but coincidentally, they spun down on their own eventually. The orb works, but I couldn't find a UD setting to control it automatically. I have 3 unassigned disks. None are mounted; two are zeroed. They were consistently green, and I was puzzled why. Thanks.