ChatNoir

No, Format is NEVER part of data recovery. Please attach your diagnostics to your next post.

This is part of the Unassigned Devices plugin. It would show drives that were connected to UD and are not anymore. You can remove this panel (or any UD panel) with the toggle on the top right of the plugin section.

Bonjour @chis34 Pas vraiment d'API officielle à ma connaissance. Mais il y a un docker Netdata qui propose pas mal d'informations. Un utilisateur s'est monté un Dashboard à base de plusieurs containers différents, tout ça customisable, mais pas évident à déployer :

That's explained in the link. Simply type diagnostics on the commande line, the file will be created in the log directory of the flashdrive.

Please attach your diagnostics to your next post.

That may or may not be the cause of your issue. You would have more chance of a relevant answer if you provide your diagnostics. Maybe on your own thread.

done

In your situation, I would remove as many variables as possible from the equation and test them one at a time. In settings, stop Docker and VM managers. Spin down your disks. Do they stay down ? If they do, probably that one or several Docker and/or VM is causing that. Start the services one at a time (not the actual docker/vms) see if it stays down. If so, try one service at a time (or group of services for dockers that work together), etc. If it is still not staying down with every thing shut down, it might be a plugin or network activity scanning shares ( 'helpful' AV or firewall ). Try to isolate all variables.

I moved that post in the german section. If you want to post in the general sections of the forum, please use English.

There was a change in Pools management in 6.9 that was not present in 6.8 and require the disks to be assigned in case of roll back to a version prior to 6.9.

Il faut généralement quelques heures à ich777 pour faire les versions de plugin compatibles avec une nouvelle version d'OS. Même s'il est très réactif et est assez proche de Limetech, ce n'est pas un employé et n'est pas forcement au courant des dates de sortie. Et il a des tonnes de plugin à gérer. C'est pour ça que j'attends au moins quelques heures, voir quelques jours pour toutes mise à jour (sauf bug critique).

You will not be able to mount EXT FS in either Array or Pool, but as Frank said you can mount it as an Unassigned Device (using the plugin with the same name) to access it's data.

Si on peut toujours utiliser UD et si on souhaite faire un passthrough du disque c'est toujours possible. Probablement plus performant qu'un vdisk sur une Pool. Et UD ne sert pas qu'à ça mais aussi à monter un dossier partagé réseau, un disque plug&play pour du backup, faire un preclear si on le souhaite, etc.

Please start you own thread.

Bonsoir, je sais que les personnes qui ont fait la mise à jour dans les toutes premières heures après la mise en ligne de la mise à jour ont eu des soucis (plugin pas à jour avec la 6.11), mais ich777 a très rapidement mis à disposition une mise à jour et un moyen pour les utilisateurs de son plugin qui avaient fait la MàJ avant la correction de corriger ça : Est-ce que tu as essayé cette manipulation ? Personnellement je n'ai pas eu de soucis avec mes containers qui utilisent ma Quadro P400. Mais j'ai attendu 1-2 jours pour lancer la MàJ (pour attendre que les plugins principaux soit à jour justement ^^). Si tu as toujours un soucis, je t'invite à demande sur le thread du plugin.

Until the first parity check/build.

I don't think you can expect more than 6 SATA ports on a x1 PCIE without some kind of port multiplier. So 10 or 20 is taking a big risk on transfer speed and dropped connections. Your motherboard already have 6 SATA ports, do you mean 6 additional disks ?

@daithi you should use the Update Assistant (in Tools). Of course backup the flashdrive.

Why 6.11.0rc5 and not 6.11.0 stable ? The stable is more recent and up to date.

Also, you should set the minimum free space for each Pool as something larger that any file you plan to use the cache for. That way, you should never fill up a pool because of files being cached.

C'est bien loin de ma zone de confort malheureusement. 😕

Please do not post several times about the same issue.

Your docker is not starting probably because your cache is full and the docker image is corrupted. That can be addressed later but first you have to make sure the cache does not fill-up. What is filling up your cache ?

I stand corrected then.

I am pretty sure that consument level Intel processor do not support ECC memory. For that, you would need a Xeon processor. That's wrong, see below