itimpi

I could see that catering explicitly in the standard extension for Unraid could be an issue. However, sounds like at the very least there should be a whitelist capability (assuming there is not already one) so you can explicitly allow sites you determine are OK.

Deginitely worth checking out the power connections. Do you use splitters to provide the power? They can sometimes be problematical.

You could already do that manually I think as far as basic booting is concerned. However the USB stick would still be used for storing all settings so not sure you would gain much as currently they are always stored on the device holding the licence.

You cannot change the file system type in this way as the rebuild process works at the raw sector level and is file system agnostic so it can only rebuild the previous file system. Stopping the array and setting the file system back to XFS and then restarting the array should with any luck bring back your data. Changing file systems on a drive always involves copying the data elsewhere; reformatting the drive to the new file system (wiping it contents); and then copying the data back.

You will find that the section on the New Config tool in the online documentation accessible via the Manual link at the bottom of the Unraid GUI will answer your question. In addition every forum page has a DOCS link at the top and a Documentation link at the bottom.

Sometimes after an upgrade it seems that system files end up not being readable for some reason. It might be worth doing a manual upgrade as documented here in the online documentation accessible via the ‘Manual’ link at the bottom of the GUI or the DOCS link at the top of each forum page. While at it do a chkdsk on the flash drive while you have it plugged into a PC/Mac to do this to make sure it is not having problems. Make sure before attempting this upgrade you first make a backup of the current contents of your flash drive in case you need to revert.

The syslog in the diagnostics is the RAM version that starts afresh every time the system is booted. You should enable the syslog server (probably with the option to Mirror to Flash set) to get a syslog that survives a reboot so we can see what leads up to a crash. The mirror to flash option is the easiest to set up (and if used the file is then automatically included in any diagnostics), but if you are worried about excessive wear on the flash drive you can put your server's address into the remote server field.

No idea why you thought that.

not sure I understand this question. The ‘appdata’ share is just the default location for stroring the working set data for docker containers and can easily be many GB in size (and in the case of containers like Plex it can be hundreds of GB) and as such it is stored on either an array drive or a pool depending how you have it configured.

Some plugins are now part of core Unraid so not sure if that is safe. What you could do is replace the plugins folder contents with the content from a ZIP download of the Unraid release to get the default setup.

Assuming you want encryption? It is worth pointing out that encryption can compromise the ability to recover without data loss if you have harware issues with your system. Why? Do you have some other use for that drive? Not quite sure what you mean by 'apodaca'? If you mean the 'appdata' share then it is a User Share that is located on whatever drives it is configured to use. It is quite typical for this to be configured to reside on a pool if you have one (and this is the default) for best performance of docker containers, but if you do this you need to use something like the 'appdata backup' plugin to make periodic backups to the array in case of the pool failing for some reason.

I cannot remember - does Safe Mode also avoid loading anything from the 'extras' folder on the flash drive.

Drives are only encrypted when you set them to be encrypted before formatting them. Unraid uses standard Linux encryption so even when encrypted they can be read on any Linux system if you can provide the key. Formatting is not automatic and only happens when you decided to use the Format option after starting the array and it would list the drives about to be formatted. I assume you did not notice that the cache pool was amongst those listed. Note that Unraid does not require you to have a pool - this is optional although frequently done for performance reasons. Plugins are stored on the flash drive along with all your settings, and loaded into RAM along with the main Unraid OS as part of the boot process.

It should be FAT32 - is that one of the options offered?

Click the >_ icon at the top right of the GUI.

No - I mean did you make sure the cables were well seated in case they worked slightly loose, or alternatively try different cables. Cabling seems to be the commonest cause of errors.

CRC errors typically indicate a connection issue. Did you do anything to confirm that the SATA and power cabling to the drive are fine. The syslog in the posted diagnostics is full off resets on the drive that look like this sort of issue which is also consistent with getting lots of CRC errors.

Ideally you should post your system's diagnostics zip file in your next post in this thread to get more informed feedback. It is always a good idea to post this if your question might involve us seeing how you have things set up or to look at recent logs. Having said that, the syslog in the diagnostics is the RAM version that starts afresh every time the system is booted. You should enable the syslog server (probably with the option to Mirror to Flash set) to get a syslog that survives a reboot so we can see what leads up to a crash. The mirror to flash option is the easiest to set up (and if used the file is then automatically included in any diagnostics), but if you are worried about excessive wear on the flash drive you can put your server's address into the remote server field.

Do you even have an appdata folder (even if empty) on the listed drives? If so (check first it is empty) then deleting them using something like Dynamix File Manager will stop them being listed.

This will be because you have not enabled disk shares under Settings->Global Share Settings.

Are they by any chance shucked drives? If so they may have the 3.3v SATA issue.

I am afraid if you assigned a data drive as a parity drive you have almost certainly wiped much of its contents. You may find that file recovery software such as UFS Explorer on Windows can recover some (maybe most) of the drive contents.

Each container can have its own settings for security on the its appdata folder and its contents. You should be able to access it OK if you use the Dynamix File Manager as that runs with root privileges.

Your problem is due to the fact the pool is formatted as xfs and that format only supports single-drive pools. If it had been formatted as btrfs then you could have easily added the drive. to do what you want you need to back up the current contents of the pool to the array; delete the existing pool; set up a new 2 drive pool using btrfs. Format the pool to btrfs and then copy the contents back. By default the pool will be set up as raid1 with the usable space that of the smallest drive, but you can click on the drive on the Main tab and change it to use the Single btrfs profile which will give you the full 1.5TB of usable space.

You click on the boot device on the Main tab and go to the syslinux section.