itimpi

Once you start the array any slots which do not have assigned devices will be hidden. You will need to stop the array; set the slots to at least 4 to be able to assign disk2 (when array stopped first two slots are always parity1 and parity2 even if they have no device assigned).

That almost certainly means Windows has credentials stored against the network name. IIRC Windows 10 treats the network name and the IP address separately for authentication purposes.

1). The /mnt/user0 location is in principle reserved for Unraid use and could disappear in some future release so you should get used to using /mnt/user. 2) For Windows you should check the username/password set up under the Windows Credentials Manager for your Unraid server. The details there should correspond to a user you have set up on the Unraid server. Not sure about why the Linux machine is not prompting you - what are you using on the Linux machine to access the Unraid server.

There is an option under Settings->Scheduler->Mover options to enable mover logging (entries get written to the syslog). It can be very verbose so only leave it enabled if you are actively investigating a mover problem. It might be worth posting your system's diagnostics zip file so we can check your settings to see if we can spot anything that might cause this.

You are likely to get more informed feedback if you attach your system's diagnostics zip file to your next post in this thread. It is always a good idea to do this to allow us to see the current state of your system and so we can see logs and configuration information.

The content of the ‘config’ folder in the diagnostics looks incomplete. It as if something went wrong during the boot sequence and the contents of the ‘config’ folder were not correctly read from the flash drive. It could be worth backing up the flash drive; recreate it using the USB Creator tool; and then copy the ‘config’ folder from the backup to the flash drive overwriting the config folder already there.

If you have the parity check tuning plugin installed then you get the new command 'parity.check' installed that allow you to query the parity check status amongst other things. It does not provide exactly the same information as your script (although it would be easy to enhance it to do so if there is a demand). Do you want me to enhance the "parity.check status" command in the parity check tuning plugin to provide the additional detail so you do not need to maintain your script?

The current release of Unraid more strict about the partitioning of the boot flash. Backup the current contents of the flash drive; recreate the flash drive using the USB Creator tool; and then copy the ‘config folder from the backup overwriting the ‘config’ folder on the flash drive.

You are likely to get more informed feedback if you start by attaching your system's diagnostics zip file to your next post in this thread. It is always a good idea to do this to allow us to see the current state of your system and so we can see logs and configuration information.

The replacement drive must be at least as large as the disk to be replaced. It can also be larger, but it should not be larger than your smallest parity drive (although there are ways to work around that limitation). The replacement procedure is covered in the online documentation.

It depends on what your licence allows. The 7.2.8 is intended for those already on a 7.2.x release and who have not paid for support beyond the 7.2.x series. The 7.3.8 is the latest release available but as you are on 7.2.5 you will only be able to upgrade to that if your licence if valid for upgrades to next release.

CRC values never reset. All you can do is stop them from increasing.

You need to look into the config/shares folder on the flash drive and make sure the .cfg file for each share is in the same case as the actual folders for the share on your disks. If not delete the .cfg file and then go into the settings for the share and make any change to cause a new .cfg file to be generated with the correct case.

The overall assessment is typically worthless. If you go further down to the section that covers SMART tests run SMART Extended Self-test Log Version: 1 (1 sectors) Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Completed: read failure 40% 43159 45416952 # 2 Short offline Completed without error 00% 43153 - # 3 Extended offline Completed: read failure 10% 43153 620726664 # 4 Short offline Completed without error 00% 43116 - # 5 Short offline Completed without error 00% 23599 - The short tests only tend to test the drive electronics, not the actual sectors. The extended tests are the meaningful ones and they have not been completing. you will see your test failed at 40% in, so it is highly likely the disk needs replacing.

Have you tried clearing your browser's cache?

Not sure I agree. You are in effect saying that Unraid should NOT make a 7.2.x release they have finished testing on that includes security fixes if they are still testing a 7.3.x release that includes those same fixes but also has other fixes so testing is still on-going.

Not necessarily. It is likely that 7.3.3 will include the same fixes that are in 7.2.8, but also any fixes specific to 7.3.x series so may take longer to get ready.

That shows eth0 is now the 2.5Gbps NIC. However you may want to disable the bonding as it is unlikely to be serving any practical pupose.

Just because your RAM is rated for 3600 does not mean you can safely run it at that speed. The CPU and/or Motherboard can impose a lower safe speed that should not be exceeded.

I suspect that Unraid does it for containers set up via DockerMan. You were using Compose so Unraid does not know about that type of container.

If it works in Safe Mode it is almost certainly a plugin issue. Unfortunately your diagnostics do not show what plugins you have installed so unable to suggest a likely culprit. It could also be worth clearing your browser cache in case it has something there causing an issue. It will be a case of elimination to identify the culprit plugin(s). You can temporarily disable a plugin by renaming its .plg file on the flash drive in the config/plugins folder to have a different file extension and then rebooting. Reverse the process to enable it again.

Try turning off logging associated with the Mover Tuning plugin. After doing that reboot to clear the logs. Not sure if that is the only thing causing your issue but it will not be helping.

The mover direction is correct. For performance reasons you normally want appdata files to end up on a pool rather than the main array. The 'system' share should also be like that as you want its contents on a pool for performance reasons. Note that you need to have the docker and VM services disabled if you want mover to move files for the 'system share' as those services keep files open while they are enabled which stops them being moved. If you run VMs then you may also want the 'domains' share set up like - again for performance reasons although in this case size considerations of the disk image files used by VMs may make it more awkward. When you have any those shares purely on a pool you may want to remove the Secondary Storage of 'array' option (which then removes the mover option) and then check that Exclusive shares are enabled under Settings->Global Share settings as this enhances performance for accessing files that are only on a pool and set to stay that way. There is the appdata backup plugin available for periodically moving the contents of those shares to a backup location on the main array.

Start by disabling mover logging as your syslog is full of messages from mover and I suspect that is the cause of your problem. You should only leave mover logging enabled when investigating problems with mover.

That location is only in RAM so will not survive a reboot. The image needs to be stored on the boot drive, so I expect that 'config/plugins/dockerMan/images' location on the boot drive is where you need to store them to survive a reboot. I do not use Compose so cannot test it. It is possible you might need to run a script to move them into position during the boot sequence, but the User Scripts plugin would make this easy.