Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

unraid v7.1.2, 7.1.3, 7.1.4...

Featured Replies

Bonjour,

J'ai profité d'un moment de répit sur mon serveur pour le mettre à niveau de la version 7.1.2 à la version 7.1.4. Quelle erreur de ma part !

Je suis maintenant victime de "freezes" aléatoires. En gros, le serveur démarre et tout fonctionne normalement, puis deux ou trois heures plus tard, il plante soudainement. Plus rien ne répond.

J'ai donc configuré un serveur pour recevoir les journaux système sur mon Raspberry Pi. Voici les dernières lignes enregistrées avant le dernier "freeze" :

Aug 18 00:00:02 JKL-SERVER-2 root: /mnt/cache: 476.9 GiB (512109142016 bytes) trimmed on /dev/nvme1n1p1

Aug 18 00:00:18 JKL-SERVER-2 root: /mnt/secondary: 1.8 TiB (1970418360320 bytes) trimmed on /dev/sde1

Aug 18 00:00:19 JKL-SERVER-2 root: /var/lib/docker: 63.3 GiB (68000464896 bytes) trimmed on /dev/loop2

Aug 18 00:00:20 JKL-SERVER-2 root: /var/lib/docker/btrfs: 12.3 GiB (13206216704 bytes) trimmed on /dev/loop2[/btrfs]

Aug 18 00:00:20 JKL-SERVER-2 root: /etc/libvirt: 918.2 MiB (962777088 bytes) trimmed on /dev/loop3

Aug 18 00:02:06 JKL-SERVER-2 kernel: traps: gunicorn: worke[56304] general protection fault ip:14df51ffa544 sp:14df3c4ee628 error:0 in libpython3.13.so.1.0[1fa544,14df51e7f000+215000]

Aug 18 00:02:07 JKL-SERVER-2 plugin-manager: running: 'anonymous'

Aug 18 00:02:07 JKL-SERVER-2 plugin-manager: tips.and.tweaks.plg removed

Aug 18 00:03:17 JKL-SERVER-2 kernel: md: recovery thread: PQ corrected, sector=129030960

Aug 18 00:04:28 JKL-SERVER-2 plugin-manager: running: 'anonymous'

Aug 18 00:04:28 JKL-SERVER-2 plugin-manager: creating: /boot/config/plugins/dwmemtester/memtester-4.6.0_1-x86_64-2_dw.txz - downloading from URL https://raw.githubusercontent.com/desertwitch/memtester-unRAID/main/packages/memtester-4.6.0_1-x86_64-2_dw.txz

Aug 18 00:04:28 JKL-SERVER-2 plugin-manager: checking: /boot/config/plugins/dwmemtester/memtester-4.6.0_1-x86_64-2_dw.txz - MD5

Aug 18 00:04:28 JKL-SERVER-2 plugin-manager: running: upgradepkg --install-new /boot/config/plugins/dwmemtester/memtester-4.6.0_1-x86_64-2_dw.txz

Aug 18 00:04:28 JKL-SERVER-2 plugin-manager: creating: /boot/config/plugins/dwmemtester/dwmemtester-2025.04.12-x86_64-1.txz - downloading from URL https://raw.githubusercontent.com/desertwitch/memtester-unRAID/main/archive/dwmemtester-2025.04.12-x86_64-1.txz

Aug 18 00:04:28 JKL-SERVER-2 plugin-manager: checking: /boot/config/plugins/dwmemtester/dwmemtester-2025.04.12-x86_64-1.txz - MD5

Aug 18 00:04:28 JKL-SERVER-2 plugin-manager: running: upgradepkg --install-new /boot/config/plugins/dwmemtester/dwmemtester-2025.04.12-x86_64-1.txz

Aug 18 00:04:28 JKL-SERVER-2 plugin-manager: running: 'anonymous'

Aug 18 00:04:29 JKL-SERVER-2 plugin-manager: dwmemtester.plg installed

Aug 18 00:07:29 JKL-SERVER-2 kernel: md: recovery thread: PQ corrected, sector=211869864

Aug 18 00:11:43 JKL-SERVER-2 emhttpd: spinning down /dev/nvme2n1

Aug 18 00:11:43 JKL-SERVER-2 emhttpd: spinning down /dev/nvme0n1

Aug 18 00:11:43 JKL-SERVER-2 emhttpd: sdspin /dev/nvme2n1 down: 25

Aug 18 00:11:43 JKL-SERVER-2 emhttpd: sdspin /dev/nvme0n1 down: 25

Aug 18 00:16:27 JKL-SERVER-2 kernel: md: recovery thread: PQ corrected, sector=390188688

Aug 18 00:16:32 JKL-SERVER-2 emhttpd: spinning down /dev/sdh

Aug 18 00:25:24 JKL-SERVER-2 kernel: md: recovery thread: PQ corrected, sector=568765552

Aug 18 00:27:55 JKL-SERVER-2 emhttpd: spinning down /dev/sdd

Aug 18 00:27:55 JKL-SERVER-2 emhttpd: spinning down /dev/sde

Aug 18 00:36:22 JKL-SERVER-2 kernel: md: recovery thread: PQ corrected, sector=786403736

Aug 18 00:42:32 JKL-SERVER-2 kernel: md: recovery thread: PQ corrected, sector=908924456

Aug 18 00:57:07 JKL-SERVER-2 kernel: md: recovery thread: PQ corrected, sector=1195480144

Aug 18 00:58:27 JKL-SERVER-2 kernel: md: recovery thread: P corrected, sector=1221834080

Aug 18 01:23:13 JKL-SERVER-2 kernel: md: recovery thread: PQ corrected, sector=1706940528

Aug 18 01:24:19 JKL-SERVER-2 kernel: md: recovery thread: PQ corrected, sector=1728481352

Aug 18 01:32:44 JKL-SERVER-2 kernel: md: recovery thread: PQ corrected, sector=1893049152

Aug 18 01:36:04 JKL-SERVER-2 kernel: md: recovery thread: PQ corrected, sector=1957820248

Aug 18 01:38:39 JKL-SERVER-2 kernel: md: recovery thread: PQ corrected, sector=2007784408

Aug 18 01:46:14 JKL-SERVER-2 kernel: Oops: general protection fault, probably for non-canonical address 0xff2cea000dd5d410: 0000 [#1] PREEMPT SMP NOPTI

Aug 18 01:46:14 JKL-SERVER-2 kernel: CPU: 1 UID: 0 PID: 236182 Comm: smartctl_type Tainted: P     U     O       6.12.24-Unraid #1

Aug 18 01:46:14 JKL-SERVER-2 kernel: Tainted: [P]=PROPRIETARY_MODULE, [U]=USER, [O]=OOT_MODULE

Aug 18 01:46:14 JKL-SERVER-2 kernel: Hardware name: Gigabyte Technology Co., Ltd. Z790 AORUS MASTER X/Z790 AORUS MASTER X, BIOS F9e 05/27/2025

Aug 18 01:46:14 JKL-SERVER-2 kernel: RIP: 0010:__del_page_from_free_list.isra.0+0x18/0x60

Aug 18 01:46:14 JKL-SERVER-2 kernel: Code: 1f 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 66 90 eb 0c 48 8b 07 a8 08 74 05 48 0f ba 37 03 48 8b 47 10 48 8b 4f 08 <48> 89 41 08 48 89 08 48 b8 00 01 00 00 00 00 ad de 48 89 47 08 48

Aug 18 01:46:14 JKL-SERVER-2 kernel: RSP: 0000:ffffc9000b1bbab0 EFLAGS: 00010082

Aug 18 01:46:14 JKL-SERVER-2 kernel: RAX: ffff8890bfbfa950 RBX: ffffea0030176a80 RCX: ff2cea000dd5d408

Aug 18 01:46:14 JKL-SERVER-2 kernel: RDX: 0000000000000000 RSI: ffff8890bfbfa840 RDI: ffffea0030176a80

Aug 18 01:46:14 JKL-SERVER-2 kernel: RBP: 0000000000000000 R08: 0000000000000001 R09: ffff8890bfbfa840

Aug 18 01:46:14 JKL-SERVER-2 kernel: R10: 0000000000000000 R11: ffffea00131e34c0 R12: ffff8890bfbfa840

Aug 18 01:46:14 JKL-SERVER-2 kernel: R13: ffff88907f674c00 R14: ffff88907f674c30 R15: 0000000000000000

Aug 18 01:46:14 JKL-SERVER-2 kernel: FS:  00001536372ede00(0000) GS:ffff88907f640000(0000) knlGS:0000000000000000

Aug 18 01:46:14 JKL-SERVER-2 kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033

Aug 18 01:46:14 JKL-SERVER-2 kernel: CR2: 000015363ae84038 CR3: 0000000c4af82006 CR4: 0000000000772ef0

Aug 18 01:46:14 JKL-SERVER-2 kernel: PKRU: 55555554

Aug 18 01:46:14 JKL-SERVER-2 kernel: Call Trace:

Aug 18 01:46:14 JKL-SERVER-2 kernel: <TASK>

Aug 18 01:46:14 JKL-SERVER-2 kernel: __rmqueue_pcplist+0x269/0x4d0

Aug 18 01:46:14 JKL-SERVER-2 kernel: ? post_alloc_hook+0x13/0x70

Aug 18 01:46:14 JKL-SERVER-2 kernel: get_page_from_freelist+0x2c8/0x920

Aug 18 01:46:14 JKL-SERVER-2 kernel: __alloc_pages_noprof+0xe9/0x1c0

Aug 18 01:46:14 JKL-SERVER-2 kernel: alloc_pages_mpol_noprof+0xae/0x1e0

Aug 18 01:46:14 JKL-SERVER-2 kernel: folio_alloc_mpol_noprof+0x10/0x20

Aug 18 01:46:14 JKL-SERVER-2 kernel: vma_alloc_folio_noprof+0x56/0x90

Aug 18 01:46:14 JKL-SERVER-2 kernel: folio_prealloc+0x26/0x70

Aug 18 01:46:14 JKL-SERVER-2 kernel: do_wp_page+0x458/0x7f0

Aug 18 01:46:14 JKL-SERVER-2 kernel: ? __pte_offset_map+0x18/0xd0

Aug 18 01:46:14 JKL-SERVER-2 kernel: __handle_mm_fault+0x838/0x1060

Aug 18 01:46:14 JKL-SERVER-2 kernel: ? preempt_latency_start+0x1e/0x50

Aug 18 01:46:14 JKL-SERVER-2 kernel: ? up_write+0x38/0x50

Aug 18 01:46:14 JKL-SERVER-2 kernel: handle_mm_fault+0x140/0x1f0

Aug 18 01:46:14 JKL-SERVER-2 kernel: do_user_addr_fault+0x289/0x4a0

Aug 18 01:46:14 JKL-SERVER-2 kernel: exc_page_fault+0xfd/0x120

Aug 18 01:46:14 JKL-SERVER-2 kernel: asm_exc_page_fault+0x22/0x30

Aug 18 01:46:14 JKL-SERVER-2 kernel: RIP: 0033:0x15363b1b3cc4

Aug 18 01:46:14 JKL-SERVER-2 kernel: Code: 00 00 0f 1f 40 00 48 8b 31 8b 51 08 4c 01 fe 48 83 fa 26 74 0a 48 83 fa 08 0f 85 17 29 ff ff 48 8b 51 10 48 83 c1 18 4c 01 fa <48> 89 16 48 39 d9 72 d4 4d 8b 9a 08 02 00 00 4d 85 db 0f 84 64 0b

Aug 18 01:46:14 JKL-SERVER-2 kernel: RSP: 002b:00007ffc8cfcc620 EFLAGS: 00010202

Aug 18 01:46:14 JKL-SERVER-2 kernel: RAX: 000015363ad87938 RBX: 000015363ada4230 RCX: 000015363ad95c98

Aug 18 01:46:14 JKL-SERVER-2 kernel: RDX: 000015363ae51520 RSI: 000015363ae84038 RDI: 000015363ada45f0

Aug 18 01:46:14 JKL-SERVER-2 kernel: RBP: 00007ffc8cfcc730 R08: 000015363ada45f0 R09: 000015363ada7bf0

Aug 18 01:46:14 JKL-SERVER-2 kernel: R10: 000015363b19eab0 R11: 0000000000000000 R12: 00007ffc8cfcc6c0

Aug 18 01:46:14 JKL-SERVER-2 kernel: R13: 0000000000000000 R14: 000015363b19eab0 R15: 000015363ad84000

Aug 18 01:46:14 JKL-SERVER-2 kernel: </TASK>

Aug 18 01:46:14 JKL-SERVER-2 kernel: Modules linked in: xt_CHECKSUM ipt_REJECT nf_reject_ipv4 ip6table_mangle iptable_mangle vhost_net tun vhost vhost_iotlb tap veth nf_conntrack_netlink xt_nat xt_tcpudp xt_conntrack nfnetlink xfrm_user xfrm_algo xt_addrtype md_mod ntfs3 tcp_diag inet_diag it87(O) mei_gsc i915(O) intel_gtt zfs(PO) spl(O) ip6table_nat iptable_nat xt_MASQUERADE nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 wireguard curve25519_x86_64 libcurve25519_generic libchacha20poly1305 chacha_x86_64 poly1305_x86_64 ip6_udp_tunnel udp_tunnel libchacha ip6table_filter ip6_tables iptable_filter ip_tables x_tables efivarfs af_packet cfg80211 8021q garp mrp bridge stp llc intel_rapl_common iosf_mbi x86_pkg_temp_thermal intel_powerclamp coretemp xe kvm_intel kvm btusb btrtl btbcm btintel bluetooth drm_gpuvm drm_exec gpu_sched drm_buddy drm_ttm_helper ttm crct10dif_pclmul crc32_pclmul crc32c_intel i2c_algo_bit ghash_clmulni_intel drm_suballoc_helper sha512_ssse3 drm_display_helper sha256_ssse3 sha1_ssse3 aesni_intel crypto_simd cryptd

Aug 18 01:46:14 JKL-SERVER-2 kernel: mei_hdcp mei_pxp drm_kms_helper rfkill nvme rapl intel_cstate drm gigabyte_wmi wmi_bmof hwmon_vid intel_uncore atlantic mei_me i2c_i801 nvme_core tpm_crb agpgart mei i2c_smbus ahci tpm_tis i2c_core libahci tpm_tis_core tpm thermal fan video wmi libaescfb ecdh_generic ecc backlight acpi_pad acpi_tad button

Aug 18 01:46:14 JKL-SERVER-2 kernel: ---[ end trace 0000000000000000 ]---

Aug 18 01:46:14 JKL-SERVER-2 kernel: pstore: backend (efi_pstore) writing error (-28)

Aug 18 01:46:14 JKL-SERVER-2 kernel: RIP: 0010:__del_page_from_free_list.isra.0+0x18/0x60

Aug 18 01:46:14 JKL-SERVER-2 kernel: Code: 1f 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 66 90 eb 0c 48 8b 07 a8 08 74 05 48 0f ba 37 03 48 8b 47 10 48 8b 4f 08 <48> 89 41 08 48 89 08 48 b8 00 01 00 00 00 00 ad de 48 89 47 08 48

Aug 18 01:46:14 JKL-SERVER-2 kernel: RSP: 0000:ffffc9000b1bbab0 EFLAGS: 00010082

Aug 18 01:46:14 JKL-SERVER-2 kernel: RAX: ffff8890bfbfa950 RBX: ffffea0030176a80 RCX: ff2cea000dd5d408

Aug 18 01:46:14 JKL-SERVER-2 kernel: RDX: 0000000000000000 RSI: ffff8890bfbfa840 RDI: ffffea0030176a80

Aug 18 01:46:14 JKL-SERVER-2 kernel: RBP: 0000000000000000 R08: 0000000000000001 R09: ffff8890bfbfa840

Aug 18 01:46:14 JKL-SERVER-2 kernel: R10: 0000000000000000 R11: ffffea00131e34c0 R12: ffff8890bfbfa840

Aug 18 01:46:14 JKL-SERVER-2 kernel: R13: ffff88907f674c00 R14: ffff88907f674c30 R15: 0000000000000000

Aug 18 01:46:14 JKL-SERVER-2 kernel: FS:  00001536372ede00(0000) GS:ffff88907f640000(0000) knlGS:0000000000000000

Aug 18 01:46:14 JKL-SERVER-2 kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033

Aug 18 01:46:14 JKL-SERVER-2 kernel: CR2: 000015363ae84038 CR3: 0000000c4af82006 CR4: 0000000000772ef0

Aug 18 01:46:14 JKL-SERVER-2 kernel: PKRU: 55555554

Aug 18 01:46:14 JKL-SERVER-2 kernel: note: smartctl_type[236182] exited with irqs disabled

Aug 18 01:46:14 JKL-SERVER-2 kernel: note: smartctl_type[236182] exited with preempt_count 3

Pour information, c'est le troisième plantage de la journée. J'ai essayé de revenir à la version 7.1.2 en utilisant une sauvegarde de ma clé USB (j'ai simplement effacé la clé et restauré le contenu de la sauvegarde), mais le problème persiste.
Mon CPU : Intel Core i9 12900k

Quelqu'un pourrait-il m'aider à résoudre ce problème ?

Salut.

Ca ne semble pas lié à l'upgrade.

2 pistes:

  • un de tes disques

  • RAM

Pour les disques tu devrais passer pour chacun un:

smartctl -a /dev/sdX

ou sdX peut être sdb / sdc / ... selon le nombre de disques que tu as.

Te mettre donc à la recherche d'erreurs car il semblerait que la parité tente d'en reconstruire un mais rencontre des erreurs donc potentiellement un disque en fin de vie.

L'erreur "Oops: general protection fault" semble quand à elle plus liée à la RAM.

Edited by waazaa

Merci !
Après un memtest X2 réussis j'ai décider de faire une passe sur les disque durs et le NVME des services dockers étais bourrée d'erreur :(
J'ai tout corriger via le GUI d'Unraid et j'ai pas eu de freeze depuis 4h du matin.
En espérant que le problème ne resurgissent pas.

  • 2 weeks later...
  • Author
  • Community Expert

Tant mieux !

Alors que unraid v7.2 est en beta 2, je vais essayer de le tester sur une autre machine pour voir ce que ca donne...

J'ai fini par tenter d'installer la beta 2 ( pour avoir le responsiv UI), tout fonctionne très bien ( et quel plaisir d'y accéder via le téléphone maintenant !!

  • 3 weeks later...
  • Author
  • Community Expert

unraid v7.2 est en beta 3 depuis quelques jours.

  • 2 weeks later...
  • Author
  • Community Expert

...Et en RC1 maintenant ;)

Je suis passé sur la RC1 depuis hier, rien à redire pour ma part.

Le plugin OIDC est le bienvenue, j'ai branché ça sur Pocket ID, ça fonctionne très bien.

Edited by hot22shot

  • 3 weeks later...
  • Author
  • Community Expert

...Et en RC2 maintenant ;)

Pareil, RAS pour ma part, ça marche sans soucis.

  • 3 weeks later...
  • Author
  • Community Expert

Et maintenant en définitif. 7.2.0 Finale.

Du coups le sujet sera abandonné puisque nous parlions de 7.1.x ;)

Edited by PicPoc

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.