ChatNoir

The MySevers plugin will keep the flashdrive automatically up to date. But you can still use the Backup plugin to have a local backup if you want. (I do)

Did you try to first contact support ? There is a limit for the automatic flashdrive change, but Limetech can probably help you out if you provide enough information to identify you (email address, etc.)

Did you adjust the name of the EFI folder accordingly to the boot type you were trying ? for UEFI the folder needs to be named 'EFI' for BIOS/CMS the folder needs to be named 'EFI-' the trailing '-' is important

Please attach your diagnostics.

Unraid does not care about brand and model. You can replace by any drive that is the same size or larger than the previous data drive but still smaller or equal to the parity drive.

Well this card uses a port multipler, those are not recommended with Unraid. That's probably why it's cheaper than a HBA.

Please attach your diagnostics to your next post.

Difficult without knowing how you set it up. Maybe a screenshot can help ?

Je n'utilise pas de VMs, mais j'ai l'impression que tu as isolé tes 4 uniques coeurs de CPU pour la VM. Ce serait peut-être la cause s'il ne reste (presque) plus de ressources pour faire tourner Unraid et l'hyperviseur ? Essaye de n'en isoler que 3 ?

Hello, I moved your post in the Spanish subforum. If you want to post on the forum, please use English except on the multi language subforums.

It is possible to use a large number of drives with Unraid, there was a discussion some time ago between Tom and a user about that in the Bug report section. But I did not bookmark it and I cannot find it now. 😕

It would check the bzfiles against their hash on the flash drive and I think it would refuse to load the file (and thus the OS) in case of mismatch.

And if you are not sold on Unraid, the drives of the Array can be read as independent file systems in a Linux distribution.

Indeed, 2GB might be too small. You can do the manual update. Simply replace all the bz* files by the ones from the Download page, it is also recommended to replace the changes.txt file. Obviously, do a flash backup first.

In Main, clic on the drive name, go to the Self-Test tab and run the SMART extended self-test. You might have to disable spin-down on that drive (Settings tab).

You should attach your diagnostics file in the next post. The parity drive only needs to be as large or larger than the larger data drive. You are fine on that point.

Only the automatic change is limited to 1/year. You can always ask Limetech for another change through the support form.

It seems that there is a new automatic link with support . I feel that is it more confusing than helpful. The word is often used on the forum, but rarely relating to the official Unraid support contact form. Maybe use a less generic expression ?

Did not make the link, it seems that it is an new automatic link that is not that useful.

This is a feature of Community Applications, not Unraid itself. From what I understand, it takes some time to start once you open the Apps tab, but then adds the Action centre where you can update different type of Apps from one place (plugins, docker containers, translations). For more details, you should ask on the Community Applications support thread.

I would guess the notification service ?

Is it true for all drives or only some of them ? I have similar symptoms issue only with my 2 Ironwolf disks. Not sure if it's the same problem.

The runtime is dependent on the larger Parity disk size and limited by the slowest active drive. Array with smaller drives can be done much quicker. It is possible to pause and restart the parity check. Manually and also automatically since 6.11 but AFAIK you cannot stop the array (thus not stop the system) during that time. Maybe the Parity check tuning plugin would allow that ?