ChatNoir

Je suppose que c'est parce que ton cache est un disque simple sans redondance. Pour enlever ce message, il faudrait ajouter un autre SSD de même taille en RAID1. Ce n'est pas forcement nécessaire, mais ça peut être bien d'avoir une sauvegarde récente de ces shares. Tu peux utiliser le plugin Appdata Backup/Restore v2 pour ça.

the containers and VMs individually or the services in settings ?

C'est parfait.

Bonsoir, Je pense que là, tu as eu le coup que linux essaye d'abord de changer le chemin dans un "déplacer" et un "couper / coller" doit être considéré comme un "déplacer". Dans ce cas, il fait au plus simple et ne passe pas par le système de shares ou d'allocation. Ton opération a dû avoir lieu super vite du coup vu qu'il n'a pas vraiment touché aux fichiers. Si tu avais fait un "copier/effacer" ça aurait certainement recréé les fichiers en considérant l'allocation. Maintenant que c'est fait, il te faut bouger le dossier de plus haut niveau (share) d'un disque à un autre. Si tu es sur la 6.10, je te conseille d'utiliser le nouveau plugin Dynamix File Manager. C'est bien intégré dans Unraid et ça évite certaines erreurs qui endommagent les fichiers. C'est plutôt intuitif, mais si tu as des questions, n'hésite pas. Sinon Unbalance peut faire la même chose. Si tu préfères utiliser un autre outil, fait juste bien attention à déplacer de disque à disque ou de share à share et de ne jamais mélanger les deux. L'allocation n'est considéré par Unraid que lors de la première écriture du fichier sur l'Array. Si tu veux mettre de vieux fichiers en concordance avec des modifications dans les allocations, tu devras faire ça manuellement. Comme expliqué plus haut. Globalement comme expliqué plus haut, sauf qu'il te faudra d'abord désactiver les services VM et Docker dans Settings. Après, si tu as la place sur ton cache, je te conseillerai même de mettre cette Share sur le cache étant donné que les fichiers dans systems sont utilisés en permanence, ça devrait améliorer les performances. Dans ce cas, désactive toujours les services mais c'est encore plus simple ensuite de modifier les paramètres de ta share avec Use cache "Prefer" et lancer le mover.

You should probably get an UPS and have the server shutdown gracefully when it happens.

Even with 6.10's Cumulative parity check ?

Works too, but the videos are probably predating the plugin (it is only available for a few months).

Your diagnostics might provide more information. Please attach the full zip file to your next post. Is it only Sonarr that stops ?

Please attach your diagnostics to your next post.

Your backup should be available here :

@SpencerJ

Seems like there are errors on your cache drive and consequently with your docker image. Jun 14 14:01:06 Server kernel: BTRFS error (device sdg1): bdev /dev/sdg1 errs: wr 189, rd 9526, flush 1, corrupt 0, gen 0 Jun 14 14:01:06 Server kernel: BTRFS warning (device sdg1): direct IO failed ino 16006543 rw 0,0 sector 0xb9db660 len 0 err no 10 Jun 14 14:01:06 Server kernel: blk_update_request: I/O error, dev loop2, sector 1614912 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Jun 14 14:01:06 Server kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 16, rd 4697, flush 0, corrupt 0, gen 0 Jun 14 14:01:06 Server kernel: sd 7:0:0:0: [sdg] tag#12 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 cmd_age=0s Jun 14 14:01:06 Server kernel: sd 7:0:0:0: [sdg] tag#12 CDB: opcode=0x28 28 00 0a 97 da e0 00 00 08 00 Jun 14 14:01:06 Server kernel: blk_update_request: I/O error, dev sdg, sector 177724128 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0

There are many ways to loose data. The most common risk is user error, its possible that someone with access to the server accidentally deletes important information. And realize its mistake, or not. We also regularly also hear on the forum about floods/power surge/etc. killing a server. In those cases, Parity or ECC will not help you.

Could be that, or maybe they have a 'helpful' antivirus / antimalware trying to scan the network for vulnerabilities.

This is part of the Unassigned Devices plugin. Not Unraid's Array. You can delete unused historical devices.

There should not be any information about the network if it was working properly. I understand that there are hardware checksum failures and reception errors.

Not sure if your i7 930 is the issue, but I see a call trace a the very beginning of the log Jun 12 11:16:34 Prime kernel: ------------[ cut here ]------------ Jun 12 11:16:34 Prime kernel: Your BIOS is broken; DMA routed to ISOCH DMAR unit but no TLB space. Jun 12 11:16:34 Prime kernel: BIOS vendor: American Megatrends Inc.; Ver: 1501 ; Product Version: System Version Jun 12 11:16:34 Prime kernel: WARNING: CPU: 0 PID: 1 at drivers/iommu/intel/iommu.c:5802 intel_iommu_init+0xa60/0x109f Jun 12 11:16:34 Prime kernel: Modules linked in: Jun 12 11:16:34 Prime kernel: CPU: 0 PID: 1 Comm: swapper/0 Tainted: G I 5.15.43-Unraid #1 Jun 12 11:16:34 Prime kernel: Hardware name: System manufacturer System Product Name/P6X58D PREMIUM, BIOS 1501 05/10/2011 Jun 12 11:16:34 Prime kernel: RIP: 0010:intel_iommu_init+0xa60/0x109f Jun 12 11:16:34 Prime kernel: Code: 49 89 c6 e8 41 08 f6 fe bf 01 00 00 00 49 89 c4 e8 34 08 f6 fe 4c 89 f1 4c 89 e2 48 c7 c7 39 ba 11 82 48 89 c6 e8 af 27 11 ff <0f> 0b 83 0d 34 72 1e 00 04 eb 0c 48 c7 c7 ad ba 11 82 e8 32 30 11 Jun 12 11:16:34 Prime kernel: RSP: 0000:ffffc90000023de0 EFLAGS: 00010282 Jun 12 11:16:34 Prime kernel: RAX: 0000000000000000 RBX: ffffffff82325180 RCX: 0000000000000003 Jun 12 11:16:34 Prime kernel: RDX: 000000000000020d RSI: ffffc90000023c68 RDI: 0000000000000001 Jun 12 11:16:34 Prime kernel: RBP: ffffc90000023ea0 R08: ffffffff822b4e28 R09: 0000000000000000 Jun 12 11:16:34 Prime kernel: R10: 726556206d657473 R11: 7953203a6e6f6973 R12: ffffffff82a0001c Jun 12 11:16:34 Prime kernel: R13: 0000000000000000 R14: ffffffff82a00060 R15: 0000000000000000 Jun 12 11:16:34 Prime kernel: FS: 0000000000000000(0000) GS:ffff888333a00000(0000) knlGS:0000000000000000 Jun 12 11:16:34 Prime kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Jun 12 11:16:34 Prime kernel: CR2: 0000000000000000 CR3: 000000000220a000 CR4: 00000000000006f0 Jun 12 11:16:34 Prime kernel: Call Trace: Jun 12 11:16:34 Prime kernel: <TASK> Jun 12 11:16:34 Prime kernel: ? __raw_spin_unlock+0x5/0x6 Jun 12 11:16:34 Prime kernel: ? __queue_work+0x27a/0x289 Jun 12 11:16:34 Prime kernel: ? __down_write_common+0x31/0x42e Jun 12 11:16:34 Prime kernel: ? _raw_spin_unlock_irqrestore+0x19/0x1b Jun 12 11:16:34 Prime kernel: ? e820__memblock_setup+0x7b/0x7b Jun 12 11:16:34 Prime kernel: pci_iommu_init+0x16/0x3f Jun 12 11:16:34 Prime kernel: do_one_initcall+0x78/0x178 Jun 12 11:16:34 Prime kernel: kernel_init_freeable+0x1d5/0x21f Jun 12 11:16:34 Prime kernel: ? rest_init+0xbb/0xbb Jun 12 11:16:34 Prime kernel: kernel_init+0x16/0x115 Jun 12 11:16:34 Prime kernel: ret_from_fork+0x22/0x30 Jun 12 11:16:34 Prime kernel: </TASK> Jun 12 11:16:34 Prime kernel: ---[ end trace c35b66859ac47c1f ]--- There are also a lot of network errors later : Jun 12 23:30:41 Prime kernel: sky2 0000:06:00.0 eth0: rx error, status 0x7ffc0001 length 1020 Jun 12 23:30:41 Prime kernel: sky2 0000:06:00.0 eth0: rx error, status 0x7ffc0001 length 940 Jun 12 23:30:41 Prime kernel: sky2 0000:06:00.0 eth0: rx error, status 0x7ffc0001 length 1388 Jun 12 23:30:55 Prime kernel: sky2 0000:06:00.0: error interrupt status=0x40000008 Jun 12 23:30:55 Prime kernel: sky2 0000:06:00.0 eth0: rx error, status 0x7ffc0001 length 700 Jun 12 23:30:55 Prime kernel: sky2 0000:06:00.0 eth0: rx error, status 0x7ffc0001 length 1510 Jun 12 23:30:55 Prime kernel: sky2 0000:06:00.0: error interrupt status=0x40000008 Jun 12 23:30:55 Prime kernel: sky2 0000:06:00.0 eth0: rx error, status 0x7ffc0001 length 1468 Jun 12 23:30:55 Prime kernel: sky2 0000:06:00.0: error interrupt status=0x40000008 Jun 12 23:30:55 Prime kernel: sky2 0000:06:00.0 eth0: rx error, status 0x7ffc0001 length 1020 Jun 12 23:30:55 Prime kernel: sky2 0000:06:00.0 eth0: rx error, status 0x7ffc0001 length 428 Jun 12 23:30:55 Prime kernel: sky2 0000:06:00.0 eth0: rx error, status 0x7ffc0001 length 236 Jun 12 23:30:55 Prime kernel: sky2 0000:06:00.0: error interrupt status=0x40000008 Jun 12 23:31:49 Prime kernel: net_ratelimit: 1 callbacks suppressed Probably not the cause of your parity issues, but maybe the connections issue ? That's probably related : Jun 13 03:02:12 Prime kernel: br0: hw csum failure Jun 13 03:02:12 Prime kernel: skb len=750 headroom=78 headlen=750 tailroom=772 Jun 13 03:02:12 Prime kernel: mac=(64,14) net=(78,20) trans=98 Jun 13 03:02:12 Prime kernel: shinfo(txflags=0 nr_frags=0 gso(size=0 type=0 segs=0)) Jun 13 03:02:12 Prime kernel: csum(0xc301ddf4 ip_summed=2 complete_sw=0 valid=0 level=0) Jun 13 03:02:12 Prime kernel: hash(0x9a7cdc9c sw=0 l4=0) proto=0x0800 pkttype=0 iif=12 Someone with more knowledge can probably chime in.

Your diagnostics might provide additional information. Please attach it to your next post.

@SpencerJ, @AndrewZ I see the same behavior. Not only from the download link, but for the main Unraid website.

I hope it matches the

Please, il you want to post in the General support forum, use English. If you cannot / would not, then post in your native language sub section.

That's weird, I just installed the container, changed no options and I do have the webui option. Your diagnostics might show something, even if I am not sure. Any error on the container's log ?

Things work then doesn't anymore. Maybe it's not that, but I wouldn't want to run any computer on faulty RAM.