ds9

Can you try to either ; - set watch dog control to Disabled in the BIOS (as mentioned by Nascompares) - or add split_lock_detect=off as kernel boot option as mentioned on https://forum.endeavouros.com/t/has-anyone-run-into-split-lock-detect/51022/9 See on how to add a kernel boot parameter. in

I'm not familiar with creation & submission of new Docker Application / template. Lately I wanted to know my NAS power consumption. I know powertop can be used through plugins but I wanted a Docker based solution. I just discovered lately scaphandre : https://github.com/hubblo-org/scaphandre Sounds really great. Is someone able to make it available to Unraid / include it in the Docker Apps ? If not, I'll investigate how to get it done ..

Discovered lately cryptpad but I struggled to get it running. I had some rights issues reported for logs preventing from starting : [Error: EACCES: permission denied, mkdir '/cryptpad/data/logs'] { errno: -13, code: 'EACCES', syscall: 'mkdir', path: '/cryptpad/data/logs' } /cryptpad/lib/log.js:93 throw err; ^ I managed to fix through sudo chown -R 4001:4001 data customize config as documented on https://github.com/cryptpad/docker The Docker container IP is apparently 172.17.0.3 so I had to set in the configuration : httpUnsafeOrigin: 'http://172.17.0.3:3000', Now I will try to get it running through HTTPS as example.com ...

I have another QNAP model (cheap one with 2 drivers). Unfortunately your model does not have an HDMI ouput. Try to use another USB 3.x stick

Menu Settings ---> Syslog Server

On my side : - MFA support for improved security (and level 1 accounts (RO) if you target companies usage) - API (graphQL api is not public, can we have a roadmap - would be great for HomeAssistant) - I know S3 sleep is tricky/plenty of hardware don't support it well (facing issues right now with my QNAP) or don't support it at all. Maybe a partnership with a vendor company to have a validated solution that would be working for all releases. Would be great to have an official roadmap

Bonjour, Malheureusement je n'ai pas l'impression qu''il y ait une API en vue Pour les VM, il faudra se connecter par SSH et lancer des commandes : Il y avait une tentative d'utiliser Unraid via Home Assistant (qui a une application mobile) https://github.com/ElectricBrainUK/UnraidAPI https://wiki.selfhosted.show/home-automation/home-assistant/stats-monitoring/unraid-api-configuration/readme/ Le dernier message récent n'est pas optimiste Un post de 2022 sur la disponibilité d'API :

Hello. Je suis en 6.12.2 avec xfs (disque chiffré). Aucun problème lié à cette version. Depuis j'essaye de faire marcher le sleep S3 avec le plugin Dynamix, ma clé USB3 et mon QNAP (qui supporte S3). Pour l'instant, pas de solution - mais je n'ai pas essayé avec les version 6.11.x - et je n'ai pas eu de réponse dans la partie ad-hoc du forum.

Hi. I'm using 6.12.1 and I can see a trace on my QNAP NAS - but no crash of server / everything works fine : 192.168.1.11 : <4>Jun 24 05:39:35 Tower kernel: ------------[ cut here ]------------ 192.168.1.11 : <4>Jun 24 05:39:35 Tower kernel: WARNING: CPU: 1 PID: 14256 at net/netfilter/nf_conntrack_core.c:1210 __nf_conntrack_confirm+0xa4/0x2b0 [nf_conntrack] 192.168.1.11 : <4>Jun 24 05:39:35 Tower kernel: Modules linked in: udp_diag macvlan xt_nat xt_CHECKSUM ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle vhost_net tun vhost vhost_iotlb tap veth xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xt_addrtype br_netfilter xfs dm_crypt dm_mod md_mod zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) tcp_diag inet_diag ip6table_filter ip6_tables iptable_filter ip_tables x_tables efivarfs af_packet 8021q garp mrp bridge stp llc bonding tls i915 x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm iosf_mbi drm_buddy crct10dif_pclmul crc32_pclmul ttm crc32c_intel drm_display_helper ghash_clmulni_intel sha512_ssse3 mei_hdcp mei_pxp drm_kms_helper drm aesni_intel igb crypto_simd cryptd rapl intel_cstate ahci mei_me intel_gtt agpgart i2c_i801 i2c_algo_bit i2c_smbus i2c_core libahci mei syscopyarea sysfillrect sysimgblt 192.168.1.11 : <4>Jun 24 05:39:35 Tower kernel: fb_sys_fops thermal fan video wmi backlight intel_pmc_core button unix 192.168.1.11 : <4>Jun 24 05:39:35 Tower kernel: CPU: 1 PID: 14256 Comm: kworker/u8:2 Tainted: P O 6.1.34-Unraid #1 192.168.1.11 : <4>Jun 24 05:39:35 Tower kernel: Hardware name: Default string Default string/Default string, BIOS Q04WAR07 03/12/2020 192.168.1.11 : <4>Jun 24 05:39:35 Tower kernel: Workqueue: events_unbound macvlan_process_broadcast [macvlan] 192.168.1.11 : <4>Jun 24 05:39:35 Tower kernel: RIP: 0010:__nf_conntrack_confirm+0xa4/0x2b0 [nf_conntrack] 192.168.1.11 : <4>Jun 24 05:39:35 Tower kernel: Code: 44 24 10 e8 e2 e1 ff ff 8b 7c 24 04 89 ea 89 c6 89 04 24 e8 7e e6 ff ff 84 c0 75 a2 48 89 df e8 9b e2 ff ff 85 c0 89 c5 74 18 <0f> 0b 8b 34 24 8b 7c 24 04 e8 18 dd ff ff e8 93 e3 ff ff e9 72 01 192.168.1.11 : <4>Jun 24 05:39:35 Tower kernel: RSP: 0018:ffffc90000100d98 EFLAGS: 00010202 192.168.1.11 : <4>Jun 24 05:39:35 Tower kernel: RAX: 0000000000000001 RBX: ffff88810628c400 RCX: f5f194a9dae5fa12 192.168.1.11 : <4>Jun 24 05:39:35 Tower kernel: RDX: 0000000000000000 RSI: 0000000000000001 RDI: ffff88810628c400 192.168.1.11 : <4>Jun 24 05:39:35 Tower kernel: RBP: 0000000000000001 R08: 1b693dbe4dee8d35 R09: 1fc6fb5782e3218f 192.168.1.11 : <4>Jun 24 05:39:35 Tower kernel: R10: 0c6b8e75b627422c R11: ffffc90000100d60 R12: ffffffff82a11440 192.168.1.11 : <4>Jun 24 05:39:35 Tower kernel: R13: 000000000003a40a R14: ffff88813f4bd400 R15: 0000000000000000 192.168.1.11 : <4>Jun 24 05:39:35 Tower kernel: FS: 0000000000000000(0000) GS:ffff8881f9c80000(0000) knlGS:0000000000000000 192.168.1.11 : <4>Jun 24 05:39:35 Tower kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 192.168.1.11 : <4>Jun 24 05:39:35 Tower kernel: CR2: 0000000000453cd8 CR3: 000000000420a000 CR4: 0000000000350ee0 192.168.1.11 : <4>Jun 24 05:39:35 Tower kernel: Call Trace: 192.168.1.11 : <4>Jun 24 05:39:35 Tower kernel: <IRQ> 192.168.1.11 : <4>Jun 24 05:39:35 Tower kernel: ? __warn+0xab/0x122 192.168.1.11 : <4>Jun 24 05:39:35 Tower kernel: ? report_bug+0x109/0x17e 192.168.1.11 : <4>Jun 24 05:39:35 Tower kernel: ? __nf_conntrack_confirm+0xa4/0x2b0 [nf_conntrack] 192.168.1.11 : <4>Jun 24 05:39:35 Tower kernel: ? handle_bug+0x41/0x6f 192.168.1.11 : <4>Jun 24 05:39:35 Tower kernel: ? exc_invalid_op+0x13/0x60 192.168.1.11 : <4>Jun 24 05:39:35 Tower kernel: ? asm_exc_invalid_op+0x16/0x20 192.168.1.11 : <4>Jun 24 05:39:35 Tower kernel: ? __nf_conntrack_confirm+0xa4/0x2b0 [nf_conntrack] 192.168.1.11 : <4>Jun 24 05:39:35 Tower kernel: ? __nf_conntrack_confirm+0x9e/0x2b0 [nf_conntrack] 192.168.1.11 : <4>Jun 24 05:39:35 Tower kernel: ? nf_nat_inet_fn+0x123/0x1a8 [nf_nat] 192.168.1.11 : <4>Jun 24 05:39:35 Tower kernel: nf_conntrack_confirm+0x25/0x54 [nf_conntrack] 192.168.1.11 : <4>Jun 24 05:39:35 Tower kernel: nf_hook_slow+0x3a/0x96 192.168.1.11 : <4>Jun 24 05:39:35 Tower kernel: ? ip_protocol_deliver_rcu+0x164/0x164 192.168.1.11 : <4>Jun 24 05:39:35 Tower kernel: NF_HOOK.constprop.0+0x79/0xd9 192.168.1.11 : <4>Jun 24 05:39:35 Tower kernel: ? ip_protocol_deliver_rcu+0x164/0x164 192.168.1.11 : <4>Jun 24 05:39:35 Tower kernel: __netif_receive_skb_one_core+0x77/0x9c 192.168.1.11 : <4>Jun 24 05:39:35 Tower kernel: process_backlog+0x8c/0x116 192.168.1.11 : <4>Jun 24 05:39:35 Tower kernel: __napi_poll.constprop.0+0x28/0x124 192.168.1.11 : <4>Jun 24 05:39:35 Tower kernel: net_rx_action+0x159/0x24f 192.168.1.11 : <4>Jun 24 05:39:35 Tower kernel: __do_softirq+0x126/0x288 192.168.1.11 : <4>Jun 24 05:39:35 Tower kernel: do_softirq+0x7f/0xab 192.168.1.11 : <4>Jun 24 05:39:35 Tower kernel: </IRQ> 192.168.1.11 : <4>Jun 24 05:39:35 Tower kernel: <TASK> 192.168.1.11 : <4>Jun 24 05:39:35 Tower kernel: __local_bh_enable_ip+0x4c/0x6b 192.168.1.11 : <4>Jun 24 05:39:35 Tower kernel: netif_rx+0x52/0x5a 192.168.1.11 : <4>Jun 24 05:39:35 Tower kernel: macvlan_broadcast+0x10a/0x150 [macvlan] 192.168.1.11 : <4>Jun 24 05:39:35 Tower kernel: macvlan_process_broadcast+0xbc/0x12f [macvlan] 192.168.1.11 : <4>Jun 24 05:39:35 Tower kernel: process_one_work+0x1a8/0x295 192.168.1.11 : <4>Jun 24 05:39:35 Tower kernel: worker_thread+0x18b/0x244 192.168.1.11 : <4>Jun 24 05:39:35 Tower kernel: ? rescuer_thread+0x281/0x281 192.168.1.11 : <4>Jun 24 05:39:35 Tower kernel: kthread+0xe4/0xef 192.168.1.11 : <4>Jun 24 05:39:35 Tower kernel: ? kthread_complete_and_exit+0x1b/0x1b 192.168.1.11 : <4>Jun 24 05:39:35 Tower kernel: ret_from_fork+0x1f/0x30 192.168.1.11 : <4>Jun 24 05:39:35 Tower kernel: </TASK> 192.168.1.11 : <4>Jun 24 05:39:35 Tower kernel: ---[ end trace 0000000000000000 ]--- It happened during the night all of a sudden.

Anybody using 6.12 or 6.12.1 with S3 sleep plugin ? I wanted to give this plugin a try on my NAS on my QNAP. Seems this hardware support S3 : dmesg : [ 0.704022] ACPI: PM: (supports S0 S3 S5) I used a basic S3 configuration and I can wake up my device - I installed this program : https://github.com/sabhiram/go-wol to send WOL packet. But only ping is working (the Web interface / and i guess other processes) when server wakes up. I had unfortunately no logs after reboot. Issue occured 3 times I tried to use sleep. I gave it another try - after changing configuration to keep logs on USB key, and got can see the following message : Looking at logs I see : Jun 19 15:50:13 Tower kernel: usb 2-1: USB disconnect, device number 2 Jun 19 15:50:13 Tower kernel: device offline error, dev sda, sector 5802129 op 0x1:(WRITE) flags 0x0 phys_seg 7 prio class 2 Jun 19 15:50:13 Tower kernel: Buffer I/O error on dev sda2, logical block 5800081, lost async page write Jun 19 15:50:13 Tower kernel: Buffer I/O error on dev sda2, logical block 5800082, lost async page write Jun 19 15:50:13 Tower kernel: Buffer I/O error on dev sda2, logical block 5800083, lost async page write Jun 19 15:50:13 Tower kernel: Buffer I/O error on dev sda2, logical block 5800084, lost async page write Jun 19 15:50:13 Tower kernel: Buffer I/O error on dev sda2, logical block 5800085, lost async page write Jun 19 15:50:13 Tower kernel: Buffer I/O error on dev sda2, logical block 5800086, lost async page write Jun 19 15:50:13 Tower kernel: Buffer I/O error on dev sda2, logical block 5800087, lost async page write Jun 19 15:50:13 Tower kernel: device offline error, dev sda, sector 5802456 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 2 Jun 19 15:50:13 Tower kernel: device offline error, dev sda, sector 2049 op 0x1:(WRITE) flags 0x100000 phys_seg 1 prio class 2 Jun 19 15:50:13 Tower kernel: Buffer I/O error on dev sda2, logical block 1, lost async page write Jun 19 15:50:13 Tower kernel: device offline error, dev sda, sector 7714 op 0x1:(WRITE) flags 0x100000 phys_seg 1 prio class 2 Jun 19 15:50:13 Tower kernel: Buffer I/O error on dev sda2, logical block 5666, lost async page write Jun 19 15:50:13 Tower kernel: device offline error, dev sda, sector 22946 op 0x1:(WRITE) flags 0x100000 phys_seg 1 prio class 2 Jun 19 15:50:13 Tower kernel: Buffer I/O error on dev sda2, logical block 20898, lost async page write Jun 19 15:50:13 Tower kernel: device offline error, dev sda, sector 160848 op 0x1:(WRITE) flags 0x100000 phys_seg 1 prio class 2 Jun 19 15:50:13 Tower kernel: device offline error, dev sda, sector 160848 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 Jun 19 15:50:13 Tower kernel: device offline error, dev sda, sector 5802456 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 2 Jun 19 15:50:13 Tower kernel: FAT-fs (sda2): unable to read inode block for updating (i_pos 2540807) Jun 19 15:50:13 Tower kernel: FAT-fs (sda2): unable to read inode block for updating (i_pos 2540807) My USB key is no faulty : there is an Unraid 6.12 (kernel 6.1.x) + plugin combination issue ? Seems like USB disconnect/connect issue . I didn't have any issue with my key previously. My key still appears through lsusb : Bus 002 Device 004: ID 0781:558a SanDisk Corp. Ultra but there is no /dev/sda after suspend : root@Tower:~# fdisk -l /dev/sda fdisk: cannot open /dev/sda: No such file or directory Logs I gathered : [ 2150.829940] PM: suspend exit [ 2150.886828] sda: detected capacity change from 120176640 to 0 [ 2151.035860] usb 2-1: USB disconnect, device number 2 [ 2151.037738] device offline error, dev sda, sector 6693673 op 0x1:(WRITE) flags 0x0 phys_seg 7 prio class 2 I tried the following USB with no success : echo -1 > /sys/module/usbcore/parameters/autosuspend and also adding usbcore.autosuspend=-1 as boot option. I don't know how to solve this USB key & sleep issue.

No issue to report for my QNAP TS-251D upgrade from 6.11.5 to 6.12.0. 🙂 Great work. guys! 👍 I use firefox (on Fedora SilverBlue 38) but I don't have the underscore issue on my side

In case you didn't know : https://thehackernews.com/2022/12/samba-issues-security-updates-to-patch.html The high-severity flaws, tracked as CVE-2022-38023, CVE-2022-37966, CVE-2022-37967, and CVE-2022-45141, have been patched in versions 4.17.4, 4.16.8 and 4.15.13 released on December 15, 2022.

Il me semble que le Finder permet aussi d'accéder à des montages NFS via une URL de type nfs:// https://www.cyberciti.biz/faq/apple-mac-osx-nfs-mount-command-tutorial/

Smooth upgrade from 6.10.3 on a QNAP hardware👍🙂

J'ai commençé à utiliser Unraid et franchement je trouve ça top. Avec des bases de Linux, et Docker, après avoir compris l'approche d'Unraid. @RIYADO dans un premier temps défini bien tes besoins (capacité de stockage, besoins en terme de sécurité de données, applications que tu veux utiliser, ..) Il y a un bon suppport Unraid via ce forum mais aussi via la création de ticket dans des cas un peu plus complexes (j'ai eu des problèmes au départ avec un NAS QNAP d'occasion que j'avais acheté).