ChatNoir

Bonjour @ThomThom et bienvenue sur le forum. Comme le dit Kilrah, Unraid n'est pas une distribution linux utilisable directement par l'utilisateur avec les applications nécessaire à la vie de tous les jours. C'est prévu pour un accès depuis une machine tierce (Win, MacOC, Linux, etc.) ou par une VM utilisant un de ces OS. Ensuite, l'accès se fait directement sur les fichiers via les dossiers partagés, soit par une interface web vers une application qui tourne sur le serveur (Nextcloud, Plex, etc.) L'exemple de Nextcloud est probablement ce qui est le plus utilisé dans le cas que tu décris. Quoi qu'il en soit, n'hésite pas si tu as des questions sur certains points de configuration. Pas certain qu'on puisse toujours répondre dans le forum francophone, mais ça ne coute rien de demander.

This has nothing to do with the current topic. It would be best not to pollute or derail this thread. Please create a new thread in general support https://forums.unraid.net/forum/55-general-support/ Add as much details on your pool problems as you know as well as your diagnostics.

Bonjour Mickel et bienvenue sur le forum. Pas de soucis d'age ici, il y a des utilisateurs de tout age et notamment certains bien plus âgés (au moins côté anglophone). Toutes les versions de 6.10, sauf la 6.10.3. De mémoire des histoires de VT-d activé dans certains modes de gestion IOMMU qui pouvait causer de la corruption dans les dernières versions du kernel. Ca a été réglé dans les réglages par défaut de la 6.10.3. Plus de détails : Je ne suis pas certain de comprendre ta question, aussi je vais répondre aux deux interprétations possibles : On peut tout à fait utiliser des SSDs, de préférences dans des Pools (un ou plusieurs disques qui ne font pas partie de l'Array mais dont le contenu est tout de même visible dans les Shares via Fuse) On ne peut pas 'installer' Unraid sur un SSD. Il reste sur la clé et est chargé en mémoire au démarrage. La seule activité sur la clé en utilisation normale est ensuite la sauvegarde de changements de paramètres de l'OS faits dans le WebGUI pour pouvoir les retrouver au prochain démarrage. N'hésite pas si tu as d'autres questions. Je ne suis pas forcement super pointu en technique, mais je peux déjà t'orienter là ou je peux et d'autres pourront donner leur avis aussi.

The diagnostics only include the syslog from the last boot. The syslog server survive reboots/crashes and is more useful for diagnosing crashes. Hopefully, the C-States changes will solve your issue. 🤞🏼

Hello, you should probably look at this : You can also attach this syslog since you already have it (it is NOT included in the diagnostics).

Did you check in /boot/logs if the file was eventually generated ?

It does not. Switching to a new one is a good idea. SMART Extended Self-test Log Version: 1 (1 sectors) Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Completed: read failure 80% 49041 1752312968

It's possible indeed, but I am not knowledgeable enough to be sure. Let's seem what @ljm42 thinks about it. We can move the thread if that's confirmed.

Looks like the error starts here : Sep 7 06:29:09 Apollo unraid-api[5054]: ⚠️ Caught exception: Maximum call stack size exceeded Sep 7 06:29:09 Apollo unraid-api[5054]: ⚠️ UNRAID API crashed with exit code 1 Sep 7 06:40:53 Apollo nginx: 2022/09/07 06:40:53 [crit] 5329#5329: *407337 pwritev() "/var/lib/nginx/client_body/0000049031" has written only 4096 of 9051, client: unix:, server: , request: "POST /pub/disks?buffer_length=1 HTTP/1.1", host: "localhost" Sep 7 06:43:37 Apollo nmbd[23864]: [2022/09/07 06:43:37.650269, 0] ../../source3/lib/util.c:482(reinit_after_fork) Sep 7 06:43:37 Apollo nmbd[23864]: messaging_reinit() failed: NT_STATUS_DISK_FULL Sep 7 06:46:29 Apollo kernel: TCP: request_sock_TCP: Possible SYN flooding on port 32611. Sending cookies. Check SNMP counters. Sep 7 06:48:02 Apollo unraid-api[32346]: ✔️ UNRAID API started successfully! Sep 7 06:48:07 Apollo unraid-api[32346]: ⚠️ Caught exception: Maximum call stack size exceeded Sep 7 06:48:07 Apollo unraid-api[32346]: ⚠️ UNRAID API crashed with exit code 1 Sep 7 06:58:05 Apollo unraid-api[20466]: ✔️ UNRAID API started successfully! Sep 7 06:58:15 Apollo unraid-api[20466]: ⚠️ Caught exception: Maximum call stack size exceeded Sep 7 06:58:15 Apollo unraid-api[20466]: ⚠️ UNRAID API crashed with exit code 1 Sep 7 06:58:37 Apollo nmbd[23214]: [2022/09/07 06:58:37.656692, 0] ../../source3/lib/util.c:482(reinit_after_fork) Sep 7 06:58:37 Apollo nmbd[23214]: messaging_reinit() failed: NT_STATUS_DISK_FULL Sep 7 07:13:37 Apollo nmbd[18929]: [2022/09/07 07:13:37.660920, 0] ../../source3/lib/util.c:482(reinit_after_fork) Sep 7 07:13:37 Apollo nmbd[18929]: messaging_reinit() failed: NT_STATUS_DISK_FULL Sep 7 07:18:09 Apollo unraid-api[27759]: ✔️ UNRAID API started successfully! Sep 7 07:18:12 Apollo unraid-api[27759]: ⚠️ Caught exception: Maximum call stack size exceeded Sep 7 07:18:12 Apollo unraid-api[27759]: ⚠️ UNRAID API crashed with exit code 1 Sep 7 07:28:37 Apollo nmbd[15440]: [2022/09/07 07:28:37.667499, 0] ../../source3/lib/util.c:482(reinit_after_fork) Sep 7 07:28:37 Apollo nmbd[15440]: messaging_reinit() failed: NT_STATUS_DISK_FULL Sep 7 07:28:42 Apollo smbd[15577]: [2022/09/07 07:28:42.980566, 0] ../../source3/lib/util.c:482(reinit_after_fork) Sep 7 07:28:42 Apollo smbd[15577]: messaging_reinit() failed: NT_STATUS_DISK_FULL Sep 7 07:43:37 Apollo winbindd[8829]: [2022/09/07 07:43:37.655531, 0] ../../source3/lib/util.c:482(reinit_after_fork) Sep 7 07:43:37 Apollo winbindd[8829]: messaging_reinit() failed: NT_STATUS_DISK_FULL Sep 7 07:43:37 Apollo nmbd[8830]: [2022/09/07 07:43:37.670856, 0] ../../source3/lib/util.c:482(reinit_after_fork) Sep 7 07:43:37 Apollo nmbd[8830]: messaging_reinit() failed: NT_STATUS_DISK_FULL Sep 7 07:43:43 Apollo smbd[8972]: [2022/09/07 07:43:43.084651, 0] ../../source3/lib/util.c:482(reinit_after_fork) Sep 7 07:43:43 Apollo smbd[8972]: messaging_reinit() failed: NT_STATUS_DISK_FULL Sep 7 07:59:35 Apollo nginx: 2022/09/07 07:59:35 [crit] 5329#5329: *450673 pwritev() "/var/lib/nginx/client_body/0000049032" failed (28: No space left on device), client: unix:, server: , request: "POST /pub/disks?buffer_length=1 HTTP/1.1", host: "localhost" Sep 7 08:09:46 Apollo unraid-api[21794]: ✔️ UNRAID API started successfully! Sep 7 08:11:45 Apollo unraid-api[21794]: ⚠️ Caught exception: Maximum call stack size exceeded Sep 7 08:11:45 Apollo unraid-api[21794]: ⚠️ UNRAID API crashed with exit code 1 Sep 7 08:28:37 Apollo winbindd[25498]: [2022/09/07 08:28:37.669425, 0] ../../source3/lib/util.c:482(reinit_after_fork) Sep 7 08:28:37 Apollo winbindd[25498]: messaging_reinit() failed: NT_STATUS_DISK_FULL Sep 7 08:28:37 Apollo nmbd[25499]: [2022/09/07 08:28:37.700896, 0] ../../source3/lib/util.c:482(reinit_after_fork) Sep 7 08:28:37 Apollo nmbd[25499]: messaging_reinit() failed: NT_STATUS_DISK_FULL Sep 7 08:43:37 Apollo winbindd[17959]: [2022/09/07 08:43:37.674478, 0] ../../source3/lib/util.c:482(reinit_after_fork) Sep 7 08:43:37 Apollo winbindd[17959]: messaging_reinit() failed: NT_STATUS_DISK_FULL Sep 7 08:43:37 Apollo nmbd[17960]: [2022/09/07 08:43:37.709682, 0] ../../source3/lib/util.c:482(reinit_after_fork) Sep 7 08:43:37 Apollo nmbd[17960]: messaging_reinit() failed: NT_STATUS_DISK_FULL Sep 7 08:43:43 Apollo smbd[18115]: [2022/09/07 08:43:43.459556, 0] ../../source3/lib/util.c:482(reinit_after_fork) Sep 7 08:43:43 Apollo smbd[18115]: messaging_reinit() failed: NT_STATUS_DISK_FULL Sep 7 08:58:37 Apollo winbindd[11312]: [2022/09/07 08:58:37.678150, 0] ../../source3/lib/util.c:482(reinit_after_fork) Sep 7 08:58:37 Apollo winbindd[11312]: messaging_reinit() failed: NT_STATUS_DISK_FULL Sep 7 08:58:37 Apollo nmbd[11313]: [2022/09/07 08:58:37.721422, 0] ../../source3/lib/util.c:482(reinit_after_fork) Sep 7 08:58:37 Apollo nmbd[11313]: messaging_reinit() failed: NT_STATUS_DISK_FULL Sep 7 09:10:07 Apollo root: error: /webGui/include/Notify.php: uninitialized csrf_token Sep 7 09:10:07 Apollo root: error: /plugins/community.applications/scripts/notices.php: uninitialized csrf_token Sep 7 09:10:07 Apollo root: error: /webGui/include/Report.php: uninitialized csrf_token Sep 7 09:10:15 Apollo unassigned.devices: PHP Warning: syntax error, unexpected end of file, expecting TC_DOLLAR_CURLY or TC_QUOTED_STRING or ''' in /usr/local/emhttp/state/disks.ini on line 270 in /usr/local/emhttp/plugins/unassigned.devices/include/lib.php on line 49 Sep 7 09:10:15 Apollo unassigned.devices: PHP Warning: Invalid argument supplied for foreach() in /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(528) : eval()'d code on line 21 Sep 7 09:10:15 Apollo root: error: /webGui/include/Notify.php: uninitialized csrf_token Sep 7 09:10:15 Apollo root: error: /webGui/include/Report.php: uninitialized csrf_token Sep 7 09:10:15 Apollo root: error: /plugins/community.applications/scripts/notices.php: uninitialized csrf_token Sep 7 09:10:15 Apollo root: error: /plugins/dynamix.plugin.manager/scripts/PluginAPI.php: uninitialized csrf_token Sep 7 09:10:15 Apollo root: error: /plugins/unassigned.devices/UnassignedDevices.php: uninitialized csrf_token Sep 7 09:10:15 Apollo root: error: /plugins/unassigned.devices/UnassignedDevices.php: uninitialized csrf_token Sep 7 09:10:18 Apollo root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token Sep 7 09:10:21 Apollo root: error: /webGui/include/Report.php: uninitialized csrf_token Sep 7 09:10:21 Apollo root: error: /plugins/unassigned.devices/UnassignedDevices.php: uninitialized csrf_token Sep 7 09:10:22 Apollo unassigned.devices: PHP Warning: file_put_contents(): Only -1 of 114 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/unassigned.devices/include/lib.php on line 92 Sep 7 09:10:22 Apollo unassigned.devices: PHP Warning: file_put_contents(): Only -1 of 2420 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/unassigned.devices/include/lib.php on line 210 Sep 7 09:10:22 Apollo unassigned.devices: PHP Warning: file_put_contents(): Only -1 of 114 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/unassigned.devices/include/lib.php on line 92 Sep 7 09:10:22 Apollo unassigned.devices: PHP Warning: file_put_contents(): Only -1 of 2225 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/unassigned.devices/include/lib.php on line 210 Sep 7 09:10:23 Apollo unassigned.devices: PHP Warning: file_put_contents(): Only -1 of 114 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/unassigned.devices/include/lib.php on line 92 and then the php errors from UD continue. They might be the consequence of the previous errors, not the cause ?

If I am not mistaking 'remotes' would be a network path to another system. An external USB drive attached to your server would be at /mnt/disks/xxx I think (or simply 'disks' in the plugin).

Since you are on 6.10, you could use the great File Manager plugin to copy data.

That's probably some app changing/writing files with improper permissions. You sure can 'new permission' the share, but that would probably not solve the root problem. You should investigate on what's actually using/changing those permissions. Maybe some 'arrs app or something.

Maybe @SpaceInvaderOne would consider making a new updated video for 6.10 or 6.11 ? I'm sure it would be super helpful for new users. Maybe linking it to other helpful starter videos on recent version ?

You should try the File Manager plugin since you are on 6.10. You should be able to delete what you want from any share.

Not sure if you are using the correct terms here between Pool and Array ? In any case, while you can select what drives to use or not for the Array, multi drives Pools are RAID volumes and you cannot select specific drives, only one Pool or another.

I would start by reverting to a raisonnable memory transfer speed. Configured Memory Speed: 4600 MT/s See if Memtest passes with lower speed.

If it comes back, please attach your diagnostics.

No, Memtest only checks RAM. Once we know that RAM is good, we can work on the SSD.

Please either post in German in the German subforum or if you want to post in the general section of the forum, post in English.

This user seems to have solved his problems and looks to be working for others :

You can use the plugin Unassigned Devices to mount those USB drives if you prefer that rather than accessing them over the network.

Limetech does not care what license is running on what server ; and has no way of verifying that. The license is only attached to the GUID of the flashdrive. Not any other hardware. As long as each server as it's license, you are fine.

Yes

Did you try to disable VM and Dockers in Settings ?

If you have notifications activated for daily array health report, your disk assignement is listed in the message. (email or other method)