itimpi

No data drive can be larger than the smallest parity drive so you cannot currently use a 16TB drive to replace the failed data drive as parity! Is only 12TB. You can use the parity swap procedure to upgrade the parity1 drive to 16TB and then use the old parity1 drive to replace the failed drive. It is specifically intended for this Use Case. Alternatively you can simply upgrade parity1 to a 16TB drive and when that completes use another 16TB drive to replace the failed drive. the first approach is definitely best if you want to end up with 3 data drives.

It is the same as what used to be Use Cache=“Yes”. To be equivalent to the old “Prefer” setting the mover direction would have to be Array->Cache.

As was mentioned an ‘empty’ disk still has space used due to the overhead of creating the directory structures for the empty file system.

The problem will be that Unraid uses a different start sector for HDD and SSD (for performance reasons) so the SSD will have a few less sectors available for data than the HDD had. The only easy way around this that I can think off is to use the New Config tool to get the SSD into the array, rebuild parity, format the SSD, and then mount the old HDD drive via Unassigned Devices to copy its data back to the array. This would not be ideal as if the HDD failed during this process (and you do not have a backup of its contents) you could end up with data loss.

You are likely to get better informed feedback if you attach your system’s diagnostics zip file to your next post in this thread. It is always a good idea when asking questions to supply your diagnostics so we can see details of your system, how you have things configured, and the current syslog.

Looks like you have macvlan enabled for docker networking and bridging enabled for eth0. This combination is known to cause system instability. You either need to switch to using ipvlan for docker networking or disable bridging on eth0. This was mentioned in the 6.12.4 release notes.

Easiest way would be to use the manual upgrade method described here in the online documentation accessible via the Manual link at the bottom of the Unraid GUI. In addition every forum page has a DOCS link at the top and a Documentation link at the bottom. Before doing that make a backup of your current flash drive contents just in case you want to revert for some reason. Before updating you should first make sure any plugins you are using are up-to-date. If after updating you have trouble booting then try booting in Safe Mode (which avoids loading plugins) to see if there is a plugin you were using that is nor compatible with the latest release. If that happens posting diagnostics would be the best way to get quick guidance on what plugins might be the issue.

The licence is tied to the flash drive used to boot Unraid so in that sense you cannot move it between the flash drives. What you CAN do is copy the config folder (except for the licence file) between the two flash drives to transfer the settings. The config folder contains all the settings you have made so doing that would swap the settings over. After doing that you can then move the flash drives between the servers to get the setting appropriate to a particular server. Make a backup of the flash drives first just to avoid accidentally making a mistake when copying the 'config ' folders.

That suggest that either you have tried to use this USB device before or it does not have a unique GUID. If the latter then you need to use a different USB device. Failing that you need to wait until your contact support request gets answered.

You might find this section of 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 to be of use.

Since according to the screenshot you got errors on multiple drives then it seems that something common to those drives is probably the problem (e.g. PSU, HBA). How many drives do you have - there seem to be more in the screenshot than I could see in the diagnostics. the diagnostics you posted seem to have been taken immediately after a reboot and therefore show no sign of the problem since logs are reset after a reboot.

I tend to use NoMachine to connect remotely to systems and find it superior to RDP. It has the advantage that it can be used on Windows, Linux and MacOS. It is free for non-commercial use.

I have used ones like that (although mine are only splitting 4 ways rather than 5) successfully so I would say they should be fine.

See some syslog error entries I have not seen before relating to /dev/sdc (disk3) which is I assume the one you are trying to format. It appears there is a failed attempt to update the partition table.. I also notice that you are on a very old Unraid release (6.11.2) and cannot remember if there were errors in that release that might be relevant. it might be worth making a backup of your Unraid flash drive and then updating to the current Unraid release (6.12.10) and seeing if the problem still occurs. You can use the manual update method as described here to do the upgrade. Make sure all plugins are up-to-date, and if you encounter any problems immediately after updating you can boot in Safe Mode to see if they are plugin related. At the very least that will mean you are on the current Unraid release which is likely to make further troubleshooting easier.

I do not see any attempt to format in the diagnostics 😒 Have you tried rebooting to see if it then works?

They quote something like a maximum of 2 working days, but in practice something like 2-3 hours seems not atypical.

You could try disabling the VM service to give you a chance to investigate further.

Probably not. The SATA connection at the host end can typically not carry enough current to handle a 4-way SATA split without voltage SAG. If you want a 4-way splitter then you are better off using a Molex->SATA one.

You can transfer all settings except disk assignments (assuming you are transferring to another trial licence). You can redo the disk assignments and Unraid will pick them up with their data intact.

What file system is on the cache? To switch to a multi-drive pool it needs to be btrfs (or ZFS). Btrfs pools can have new drives added dynamically. It cannot be xfs which is limited to a being a single drive.

It is always possible that something has changed on the web site and support requests are no longer getting through. Not getting an automated acknowledgement often meant something has gone amiss. Limetech have in the past been very good at responding rapidly once the request definitely got through. I guess we need an official reply from a Limetech employee on whether requests are getting through. It would also be nice to know whether an automated acknowledgement is still to be expected when making the initial request.

How are you booting (legacy or UEFI). you may need to redo the flash drive if it is not showing as bootable.

No. It sounds as if you are going to need to redo the flash drive. Make sure you have made a backup first.

If you click on the link in my previous reply then it takes you directly to the form I mentioned.

Did you create it by the Contact Support form? That seems to be the most reliable way, and if done that way you should get an automated acknowledgement.