ChatNoir

As stated in the link, you can also get the diagnostics by typing 'diagnostics' on the server if you have a keyboard attached (and ideally a monitor). Then you can 'poweroff' and recover the zip file on the flash drive.

Concernant ce point, c'est causé par Dec 1 21:56:28 Nagano emhttpd: unclean shutdown detected C'est lors du reboot précédent Unraid n'arrive pas arrêter l'Array dans les temps ET écrire sur chaque disque de l'Array que tout s'est bien passé. C'est peut-être lié à tes soucis de cache non reconnu, mais peut-être pas. (oui ça aide ) En tout cas, une piste pour améliorer ça : Concernant ton problème principal ce n'est pas quelque chose avec lequel je suis très à l'aise et de toute façon il faudrait un diagnostics de 6.11.5 pour espérer voir ce qui n'est pas correct. Je vois deux options : pour une raison la 6.11.5 a du mal avec ta config/serveur/disks sur la 6.11.5 un soucis préalable est détecté (qui ne l'était pas jusque là) par les outils BTRFS qui ont été mis à jour sur la 6.11.4 Je peux voir qu'au démarrage le système de fichier de ton cache (1) n'est pas content Dec 1 21:56:40 Nagano kernel: BTRFS info (device sdg1): bdev /dev/sdf1 errs: wr 0, rd 0, flush 0, corrupt 4390, gen 6265 puis Dec 1 21:58:08 Nagano kernel: BTRFS info (device sdg1): balance: ended with status: 0 Dec 1 22:19:52 Nagano kernel: BTRFS info (device sdg1): scrub: finished on devid 1 with status: 0 Possible que ça signifie que c'est maintenant OK ? Y a pas beaucoup d'experts sur les subtilités du BTRFS et aucun à ma connaissance dans le forum francophone. Je te conseille de plutôt faire un post dans le forum général anglophone et de joindre un diagnostics où le problème apparait (6.11.5).

Not sure I my previous answer was answering perfectly the OP's question or not. Regarding your question @Astire : to my knowledge, there is nothing built-in that would monitor disk activity over time. You might have that kind information with the docker container Netdata.

If you are using the File Integrity plugin, there is an option for that. But if you are not, I am not sure it is the best solution.

But I do not use the Unread content or Activity sections. I only navigate the forum the old fashion way.

I still have it.

You should set up a syslog server and post the file after a crash. Hopefully it will catch something.

Please attach your diagnostics to your next post.

That's part of the Plugin Fix Common Problems I think. If you don't have it, you can use the built-in Tools / New Permissions. In that case, you should not select you appdata share as it will screw up the applications permissions.

And if you only stream to local clients, there is no need to bother with transcoding.

Remember that the forum mostly represent the people having some problems, not the large majority that update without issues.

Mounting drives outside of the Array and Pools is handled by the Unassigned Devices plugin. You should look for assistance on it's support thread : https://forums.unraid.net/topic/92462-unassigned-devices-managing-disk-drives-and-remote-shares-outside-of-the-unraid-array/#comments

Please attach your diagnostics to your next post.

What I think happens is : either there are files, shares, whatever with bad permissions copied from somewhere and/or you have containers that are not configured properly and actually writing stuff with bad permissions and somehow it still works up to 6.9.x 6.10, 6.11 are probably more strict on permissions and security and show the problems already existing (but not shown by 6.9). You can stay with 6.9 but I doubt that any future release will magically fix that for you. At some point, people facing this issue will have to go to the bottom of this and fix it if they want to get over 6.9. Then, I would suggest posting in General support.

Never did that myself, but you should probably start there : https://forums.unraid.net/topic/97870-how-to-upgrade-an-lsi-hba-firmware-using-unraid/#comments

Please attach your diagnostics to your next post.

You should check that: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=819173 If it does not solve your issue, you should set up a syslog server and post the output after the next crash.

Please attach your diagnostics to your next post. Can't be sure without looking at it, but if you say XFS errors (not disk errors) then rebuilding the drive will not solve the issue.

I think I remember reading about a way of doing that properly. But since it is not something I do or plan on doing, I don't remember the details. You should read up in this subforum.

Hey, @MyUnraidName, I am not doing it myself but I know that some users are doing it successfully. The thread was moved in the appropriate subforum where people discuss Virtualizing Unraid.

As already stated several times elsewhere, mounting network shares in Unraid is handled by the plugin Unassigned Devices. Please post in the plugin's support thread with your diagnostics.

You are right, I said that based on the description from dtempleton that explicitly mentioned Marvell. Surprise, surprise, the Amazon seller kept the same link but changed the description !!! https://web.archive.org/web/20200831194618/https://www.amazon.com/Ziyituod-Controller-Expansion-Profile-Non-Raid/dp/B07SZDK6CZ Anyhow, ASM1062 is a two ports controller. If the card offer more, there is something sketchy. Either a port multiplier or it's another chip. And since the seller has shown he is clearly trustworthy ...

Marvell controller are not recommended in Unraid.

In your situation, I would update from 6.11.2 since it has issues with some disk operations with drives over 2TB.