itimpi

In that case is it not only the ends that are plugged into the drives that are SATA - the other end being the PSU specific connector? If that is the case then that is not what I would normally call a power splitter as the cables that come with the PSU will be rated for the required current.

Sorry, I missed it being beneath the screenshot

You can edit the volume mapping settings in the docker template to specify the type of access allowed. That does, however, assume that the application can soft with the type of access you specify.

You are likely to get better informed feedback if you attach your system’s diagnostics zip file to your next post in this thread so we can see more about your system.

SATA->4x SATA often causes problems due to the initial SATA connector having trouble carrying enough current for 4 drives. Does your PSU have any Molex connectors? Molex->4x SATA tends to be better as the Molex connector can successfully carry more current.

The built in mover behaviour is set under Settings->Scheduler. You only need the plugin if you are trying to do more than the built-in capability.

This is not always that easy any more as USB2 drives are getting harder to find. If a USB3.x drive needs to be used then it is definitely worth seeing if an USB2 port on the server can be used. Even if they do not have an external USB2 port I think most motherboards still tend to have a USB2 header on the motherboard that can be used with the appropriate adapter/cable.

The 015 would explain it as the leading 0 means it is treated as octal number and 015 in octal is 13 in decimal

Have you also checked the power side of things for the problem drive.

You might be better off asking in the Ubuntu forums as this is not really an Unraid issue 😀. Do you even know which web server you want to use? I personally run an Apache web server on my Unraid system as a docker container as I did not want the overhead of a VM. I used standard Apache documentation to help with the detailed configuration.

No. The rebuild overwrites every sector on the drive so whether it is formatted or not is irrelevant.. You need the drive you are going to use to stop throwing ata errors to get a clean rebuild. Have you also checked that the power cabling to the drive is OK? Power related issues can slso cause the symptoms shown in the syslog.

The UD Plus option is an additional plugin that provides extra functionality over the basic UD plugin, but needs the basic plugin to be already installed before the Plus one can be added.

You not want SSDs in the main array as having a HDD parity drive will severely limit their write performance, and in addition drives in the min array cannot be trimmed which might mean SSD speeds diminish over time. Note that you can have multiple pools which might be a better use of the SSDs with each pool dedicate to a particular usage.

Unraid is designed to work with standard HBA cards - not with hardware RAID ones. If you need to use a hardware RAID card (not flashed to IT mode) then the disk need to be configured in JBOD mode to allow Unraid to work with them.

The diagnostics you posted will not include the syslog file from the syslog server - that needs posting separately

It will only revert to copying to the array if the free space is below the Minimum Free Space value BEFORE the next file is copied. Having a value of 0 will effectively stop it ever reverting to the array. That is why the it is recommended that the value is larger than the biggest single file you expect to copy. I believe that in the current implementation the larger of the Minimum Free Space value set on a pool (cache) and the User Share is currently used. I am hoping that these will be decoupled at some point as I have never understood why they are not applied independently depending on whether the next file is going to the pool (primary storage) or the array (secondary storage).

Yes. You would have to start rebuilding parity from the beginning. No harm, but will probably not help if the cabling is the problem as the test is completely internal to the drive and does not talk to the server while carrying it out. If you actually want to test the drive then the Extended SMART test is the one you want (which takes MUCH longer), and if it fails that I would think it was enough for a RMA. If using SATA->SATA power splitters do not spilt more than 2 ways as the master SATA connector is limited in the max current it can draw without voltage saga occurring. If using Molex->SATA you can normally spilt 4 ways as the pins are much more robust.

I do not think user0 is available for an exclusive share as it only shows files/folders that are on the main array - not ones on a pool.

Historically the appdata backup plugin could go both jobs. More recently the Unraid Connect feature had given a web based option for the flash backup.

That is expected until the sync completes successfully.

Restart the array in normal mode and the drives should now mount OK.

I don’t think there is answer to ultra-reliable. The generic guidance is go with USB2 drives if possible (or at least a USB2 port) as they tend to run cooler. If going for USB3 drives then it tends to be a good idea to avoid nano form factor and go for ones with metallic cases (as USB3 drives tend to run hot) to aid with heat dissipation as heat is not good for electronics. I have been using Sandisk and Kingston USB2 drives for many years without issues although they are now getting harder to source. in terms of the transfer you can get one automated transfer annually which can be done very quickly, and if for any reason you need another you need to contact support which can add a day or two delay to the process.

The online documentation is accessible via the ‘Manual’ link at the bottom of the GUI or the DOCS link at the top of each forum page. The Unraid OS->Manual section in particular covers most features of the current Unraid release. Forum links are unreliable. Adding kernel modules is non-trivial as Unraid is only validated against a specific set of options, and adding extras is done at your own risk. In that sense the core system is more like an ‘appliance’. If there is a good Use Case then Limetech can often be persuaded to add them for the next release. Note that all of the GUI and documentation is freely available on GitHub although Limetech maintain control as changes have to be submitted via Pull requests so they can be validated.

No. Unraid will be emulating the drive and it will appear to be present throughout the rebuild and you will be able to read/write it as though the drive had not failed. Performance will be degraded during the rebuild and you are not protected until the rebuild completes. Correct (unless you have 2 parity drives). Yes. This normally ‘just works’. Unraid does not care how drives are connected as it recognises them by serial number. I think this is one area where people are pleasantly surprised with how psinless it can be. Things that can go wrong (but are normally easily worked around) is if one motherboard had a RAID disk controller and the other an HBA so the disks were presented with different serial numbers of different sizes. VMs with passed through hardware might need to be handled carefully as the IDs of the passed through hardware will almost certainly change

Parity does not ‘back up’ anything. It merely provides a way to reconstruct sectors on a failed drive as described 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. The Unraid OS->Manual section in particular covers most features of the current Unraid release. Parity is real-time on Unraid so by default it is kept in sync. There is the option under Settings->Scheduler to do a periodic housekeeping task to check that nothing has happened (e.g. crashes, power cuts) that might mean it is not perfectly synced and (optionally) correct discrepancies found.