JonathanM

That's perfectly normal. You must either run the command in the docker to force a nextcloud database update so the new files are indexed every time you manually add files, or you can utilize the external storages plugin and map locations that you want to use that way. Either option has been discussed before in this thread.

Tools, diagnostics, download, attach zip file here.

If you are asking how to restore files in place, you can't, for good reason. You must copy the files to a different location first, and then after you have recovered everything you can copy them back. If you write to the drive you are doing the recovery from you will likely corrupt the recovery. Your question is unclear to me, so if you want better advice I'd suggest being a little more detailed and specific. Firstly, I am not aware of a 48TB drive, the largest I've seen generally available is 15TB.

@Squid was maintaining a solution for that here, https://forums.unraid.net/topic/51997-plugin-ca-docker-autostart-manager/?do=findComment&comment=538750 but when the delay and start order got built into the stock gui, I don't know if it's possible to use this plugin currently.

Parity doesn't have any concept of data or files, just mass blocks of ones and zeroes on each drive. Unmountable means the file system may be damaged or otherwise not readable, but the individual ones and zeroes on that unmountable drive are still used along with the parity drive and all the rest of your other drives to calculate what ones and zeroes should be on the missing disk. If the emulated copy of the missing disk mounted and was readable, the rebuilt disk should be as well.

Yes, with the caveat that if it wears thin and allows contact either by insertion friction or vibration you may end up with a non-spinning drive at a very awkward time. Also, if the coating is too thick, you may end up damaging the SATA power cable or port. Kapton is the clear winner, as it's practically designed for this type of application. Other insulating solutions would work, but you need to be mindful of the downsides. Another alternative is to disconnect the pad from the trace, but that's risky if you aren't super careful with your abrasive method. Clipping the pin out of the SATA power cable is another risky method. Any solution that keeps power off of that pin will technically work, your choice.

Sure. Both servers will be required to rebuild parity after doing a new config with the drives how you want them. Only the drives in the parity slots will be altered.

Linked in the very first post of this thread. https://forums.unraid.net/topic/48383-support-linuxserverio-nextcloud/?page=8#comment-493083

After reading this little anecdote in the lounge I would like to see this information more prominently displayed somewhere. I don't think it needs to be realtime on the main page, but maybe some place more prominent than digging through the tools, registration and doing the research of what your current license limit is vs. attached devices would be nice. What I would like to see is a line in the Info popup, stating something like this. Unraid Basic, using 5 of 6 attached devices. or, Unraid Basic, using 7 of 6 attached devices. Please remove extra devices before rebooting. Show the extra warning line when a hotplug storage device that would exceed the license limit has been attached after the array started. Help text mouseover on the warning could show the option of upgrading to the next license tier as an alternative to removing of the device. Another feature that may be occasionally useful would be to track an over license condition when the array is commanded to stop or restart, and pop up a warning about unplugging extra drives so the array will successfully auto start on next boot.

Edit the very first post in this thread, and change the subject.

https://forums.unraid.net/bug-reports/prereleases/unraid-os-version-660-rc2-available-r145/?do=findComment&comment=1052

Tools, Diagnostics, Download, attach the zip file to your next post.

Sure, pretty much any linux distribution should read them with no problems.

What? No ?

Did you look at the first post of this thread? The link is right there. https://forums.unraid.net/topic/48383-support-linuxserverio-nextcloud/?do=findComment&comment=493083

If you don't have a cache drive, and you are saving your plex config to /mnt/cache which is actually RAM, then if you reboot, all your plex configuration will be lost. Do you care if plex needs to be set up again? If so, you need to move that folder to a physical disk before you reboot.

If the proper options are in place, it will work, however, it's not recommended by calibre's author. Changes made by one client may not get seen by the other client until the database is reloaded, so strange things are possible. The way I handle it is to manually ensure only one client at a time is actually running, it only takes a second or two to shut down the docker when I want to load the desktop client. See here for one discussion. https://www.mobileread.com/forums/showthread.php?t=295590 It's been discussed many times on the calibre forums.

How is it physically connected to the drive? Just because the cable has the correct connectors doesn't mean it's the proper cable. Describe in detail (model numbers or physical descriptions) the cables and / or enclosures, hot swap bays, whatever.

Yes. No, as long as you assign the drives back to their correct slots. Yes, but as long as you can set the mappings the same, you shouldn't lose anything. Use that to assign your drives to the correct slots. Any users and share specific security is going to be reset to defaults, so you'll have to recreate those.

Post a screenshot of the bottom of the main tab.

Yes, but if there is corruption detected you still need to have backups to recover from. 99.9% of the time if corruption occurred, it wasn't the disks fault. Bad RAM would be the biggest issue, and that would potentially corrupt reads or writes or both. Disks are very good at detecting when they can't get an accurate read, and notify the OS that something is wrong.

The good thing to come out of all this is that you know how to set up scripts, and what they can and can't do on startup. It's pretty simple really, a script can be just a list of commands you could type at the command line, but don't particularly want to type over and over again manually. You can start dockers, VM's, do pretty much anything with a script.

Cool, hopefully it stays working. That's some weird juju though, maybe do a checkdisk on the USB stick.

Weird. So if you type just the portion inside the double quotes, what happens? /boot/config/plugins/user.scripts/scripts/StartVMs/script