ChatNoir

With 10 SATA ports, it must be using a port multipler since ASM1166 can only manage 6 ports. I was mistaking above, ASM1061 is NOT a good option for 6 ports either, it's a 2 SATA ports controller. I'll correct my initial post (and your quote as not to induce confusion). If you want 6 ports, select a controller that can handle 6 ports. There is not way to magically handle more without port multipler on SATA cards.

Yes.

It seems that the changes.txt files should also be copied.

This is exactly what is recommended against. It uses a JMB575 port multiplier that is known for bad performance. Since you would be using that on a single 2.0 lane, I would guess that is would be even worse. On the very same page you linked, I saw options for only ASM1166 or ASM1061 on a x1. You should go with that. https://www.amazon.com/MZHOU-Profile-Bracket-Support-Devices/dp/B097RBLM9G/ref=sr_1_3?keywords=MZHOU%2BPCIe%2BSATA%2BCard&qid=1654493546&sr=8-3&th=1 edit : I did not try that card myself, my answer is purely based on what is indicated on the Amazon page.

That's a question only JorgeB can answer. I would suggest that you wait for him to connect.

Could be the CPU too, as that memory controller is in the CPU, not the Motherboard. Hopefully, it's only the MB.

Your first step would be to look at that : For both memory speed and power state. As for FCP reports, the MCE seems harmless, but you should probably act on those : Jun 5 04:41:06 Tower root: Fix Common Problems: Other Warning: Mover logging is enabled Jun 5 04:41:07 Tower root: Fix Common Problems: Other Warning: Background notifications not enabled Mover logging is only useful for debugging why mover does not do what you want. It should be OFF otherwise as it tends to spam the log for no reason. You should really set up notifications so that you are alerted immediately when Unraid detects an issue. Acting soon will keep your data safer than doing nothing and realizing too late that the system had issues for weeks and finally failed. If the issues continue after the changes from the FAQ, you should set up a syslog server and post that file after the next crash/reboot.

You should probably read the release details : Certain combinaison of hardware, drivers and possibly BIOS were corrupting data. 6.10.2 was pushed to prevent data loss for the users at risk while investigations are on going. If you require more information, ask away. I will not be able to answer, but someone with more knowledge probably can.

I do not use RSYNC but the result would probably change depending of the command you are using. You should share an exemple of your command. Did you set up a Minimum free space for your cache Pool ? This should solve your problem As a general rule, you should not cache a share if you regularly add more data than the cache pool can hold.

That's probably a question that @ljm42 can clarify.

He has no internet at home and hopes to update both Unraid plus dockers and plugins at a friend's house using only the flashdrive. I do not think it is possible. Maybe the plugins ? For the containers though, the "program" is installed on the drives themselves.

Your syslog is being spammed by : Jun 4 04:43:06 mnemosyne kernel: usb 1-14: new full-speed USB device number 75 using xhci_hcd Jun 4 04:43:06 mnemosyne kernel: Bluetooth: hci0: Reading Intel version information failed (-22) Jun 4 04:43:06 mnemosyne kernel: Bluetooth: hci0: Intel Read version failed (-22) Jun 4 04:43:06 mnemosyne kernel: Bluetooth: hci0: Intel reset sent to retry FW download Jun 4 04:43:06 mnemosyne kernel: usb 1-14: USB disconnect, device number 75 Are you trying to use a BT device ?

Is the BIOS set up to boot automatically ? In any case, you can start to check the power states and update BIOS if its not the latest. I see that you did set up a syslog server, I did not see anything relevant there, but maybe someone else can.

Works on my Chrome too, but not on my Firefox. (I'm accessing by IP in both case)

Mon conseil serait de faire le filesystem check pour récupérer un maximum de données et les déplacer sur d'autres disques si tu as de la place. Selon la place que tu as disponible, tu peux faire ça tout de suite ou attendre d'avoir ton nouveau disque. Si tu n'es pas sûr, n'hésite pas à poster les résultats des opérations, j'essayerai de te guider.

Bonjour @walloux1981 et bienvenue sur le forum. J'ai regardé ton diagnostics et je pense que tu as un gros soucis avec ton disk1. Beaucoup d'erreurs de ce type dans le log Jun 4 08:38:49 Tower kernel: XFS: metadata IO error: 20 callbacks suppressed Jun 4 08:38:49 Tower kernel: XFS (md1): metadata I/O error in "xfs_imap_to_bp+0x4e/0x6a [xfs]" at daddr 0x2cff8e0 len 32 error 5 Jun 4 08:38:50 Tower emhttpd: error: get_filesystem_status, 6265: Input/output error (5): scandir Input/output error C'est signe d'une corruption du système de fichier. Mais en regardant de plus près, il me semble que la cause racine est certainement le fait que c'est un vieux disque qui a énormément d'erreurs SMART : Device Model: WDC WD20EZRZ-00Z5HB0 Serial Number: WD-WCC4M3ZKLN9L ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE 1 Raw_Read_Error_Rate POSR-K 195 195 051 - 275347 5 Reallocated_Sector_Ct PO--CK 179 179 140 - 638 196 Reallocated_Event_Count -O--CK 192 192 000 - 8 197 Current_Pending_Sector -O--CK 197 197 000 - 1290 198 Offline_Uncorrectable ----CK 197 197 000 - 1293 200 Multi_Zone_Error_Rate ---R-- 194 194 000 - 2474 Tu n'as pas de 👎 sur le tableau de bord d'Unraid ? Pour le future, note que les disques Western Digital gèrent les attributs 1 et 200 de SMART différemment de Seagate, et autres. Ces valeurs doivent être configurées manuellement pour que Unraid les surveille. Il suffit d'aller sur le disque depuis l'onglet Principal, d'entrer les attributs et de valider avec Apply. Autre point important, est-ce que tu as bien configuré les notifications pour t'alerter quand le système détecte des erreurs ? C'est mieux d'être prévenu dès que le système détecte un problème pour intervenir rapidement. Ca évite des soucis en cascade. Maintenant, pour essayer de te dépanner. Tu peux toujours essayer de faire un filesystem check, mais il y a tout de même des risques de perte de donnée compte tenu de l'état du disque. J'espère que tu as des sauvegardes de tous tes fichiers importants. Si l'explication du Wiki n'est pas clair ou si tu n'es pas à l'aise avec l'anglais, je pourrais te faire un résumé.

People will have a hard time making relevant suggestions without your diagnostics. Please attach the full zip to your next post.

There is no up to date definitive guide. You would probably have better suggestions if you clearly define your requirements at least in use case.

Please create a thread in the General Support section with your diagnostics.

I splitted the post in its own thread.

I don't do VMs, but I guess that the function would need to be enabled in the VM BIOS/UEFI also ? Hopefully, someone who actually knows VMs can chime in.

Mounting of a remote share is generally handled by the Unassigned Devices plugin. You should probably ask questions about that on the plugin's support thread : But the share should pop back up when available if you set it to automount.

Unraid is not RAID, RAID controllers are not recommended.

You should ask that in the Unassigned Devices support thread.