July 21Jul 21 My unraid license just automatically renewed. I logged into the server to check and it showed the old expire date, but when I clicked "manage unraid account" it did some negotiation with the unraid website and as part of that it updated the expiry date. This process took my array offline with no notification and took down roughly 12 VMs using unraid for storage. Furthermore, the array got stuck in a stopping state (Presumably since all 12 VMs were still trying to use the array) and I eventually had to reboot the box and then the proxmox nodes.Is this expected behaviour (stopping the array with no user notice) and how do I stop it ever changing its license so this doesn't happen again?
July 21Jul 21 Community Expert I don't think that is expected; please post the diagnostics. Even if you rebooted once, as long as the save previous syslog to the flash drive is enabled, it should have the previous syslog.
July 21Jul 21 Community Expert 6 hours ago, jfitzell said:Is this expected behaviour (stopping the array with no user notice) and how do I stop it ever changing its license so this doesn't happen again?I have not confirmed this with any staff but...I believe limetech changed how the array runs, and yes when the license expires the array is stopped to prevent it from running indefinitely on an expired timer. Ive noticed this behavior on trials and when the USB is removed while only acting as a license and not a boot device. Edited July 21Jul 21 by MowMdown
July 21Jul 21 Community Expert You are correct, but it's different having an expired trial, which cannot be used, or having a paid license with updates expired, where you just cannot update, but can still use the current release.
July 21Jul 21 Author Thanks all, it's definitely something related to the key expiring (but I was on a paid starter key that auto-renewed, not the trial). The bottom section (trying to delete /mnt/user) then repeats in the logs until I rebooted the box. To be honest, it's scared me off unraid and I spent last night moving all my VMs onto a new ZFS setup.Jul 21 12:23:52 J1900 emhttpd: error: get_key_info, 741: Invalid argument (22): stat: /boot/config/Starter.key Jul 21 12:23:53 J1900 emhttpd: Unregistered Trial - expired (EEXPIRED) Jul 21 12:23:53 J1900 emhttpd: error: malloc_share_locations, 8649: Operation not supported (95): getxattr: /mnt/user/appdata Jul 21 12:23:53 J1900 emhttpd: EEXPIRED: Stopping array Jul 21 12:23:53 J1900 emhttpd: Starter key detected, GUID: ***** FILE: /boot/config/Starter.key Jul 21 12:23:53 J1900 emhttpd: error: malloc_share_locations, 8649: Operation not supported (95): getxattr: /mnt/user/appdata Jul 21 12:23:53 J1900 kernel: mdcmd (47): nocheck cancel Jul 21 12:23:54 J1900 emhttpd: Spinning up all drives... Jul 21 12:23:54 J1900 emhttpd: read SMART /dev/sdb Jul 21 12:23:54 J1900 emhttpd: read SMART /dev/sdc Jul 21 12:23:54 J1900 emhttpd: read SMART /dev/sda Jul 21 12:23:54 J1900 emhttpd: Stopping services... Jul 21 12:23:54 J1900 emhttpd: shcmd (126): /etc/rc.d/rc.samba stop Jul 21 12:23:54 J1900 rc.samba: Stopping Samba server daemon... Jul 21 12:23:54 J1900 rc.samba: kill 1856963 Jul 21 12:23:55 J1900 rc.samba: killall --ns 2053439 smbd nmbd wsdd2 winbindd Jul 21 12:23:56 J1900 wsdd2[1856977]: 'Terminated' signal received. Jul 21 12:23:56 J1900 wsdd2[1856977]: terminating. Jul 21 12:23:56 J1900 winbindd[1856981]: [2026/07/21 12:23:56.004299, 0, traceid=1] ../../source3/winbindd/winbindd_dual.c:1984(winbindd_sig_term_handler) Jul 21 12:23:56 J1900 winbindd[1856981]: Got sig[15] terminate (is_parent=1) Jul 21 12:23:56 J1900 rc.samba: Samba server daemon... Stopped. Jul 21 12:23:56 J1900 emhttpd: shcmd (127): rm -f /etc/avahi/services/smb.service Jul 21 12:23:56 J1900 avahi-daemon[1856899]: Files changed, reloading. Jul 21 12:23:56 J1900 avahi-daemon[1856899]: Service group file /services/smb.service vanished, removing services. Jul 21 12:23:56 J1900 emhttpd: shcmd (129): /etc/rc.d/rc.nfsd stop Jul 21 12:23:56 J1900 rc.nfsd: Stopping NFS server daemon... Jul 21 12:23:56 J1900 rc.nfsd: /usr/sbin/rpc.nfsd 0 Jul 21 12:23:57 J1900 rpc.mountd[1856497]: Caught signal 15, un-registering and exiting. Jul 21 12:23:57 J1900 rc.nfsd: /usr/sbin/exportfs -au Jul 21 12:23:57 J1900 rc.nfsd: NFS server daemon... Stopped. Jul 21 12:23:57 J1900 emhttpd: Stopping mover... Jul 21 12:23:57 J1900 emhttpd: shcmd (130): /usr/local/sbin/mover stop Jul 21 12:23:57 J1900 root: mover: not running Jul 21 12:23:57 J1900 emhttpd: Sync filesystems... Jul 21 12:23:57 J1900 emhttpd: shcmd (131): sync Jul 21 12:23:57 J1900 emhttpd: shcmd (132): /usr/sbin/zfs unmount -a Jul 21 12:23:57 J1900 emhttpd: shcmd (133): umount /mnt/user Jul 21 12:23:57 J1900 root: umount: /mnt/user: not mounted. Jul 21 12:23:57 J1900 emhttpd: shcmd (133): exit status: 32 Jul 21 12:23:57 J1900 emhttpd: shcmd (134): rmdir /mnt/user Jul 21 12:23:57 J1900 root: rmdir: failed to remove '/mnt/user': Directory not empty Jul 21 12:23:57 J1900 emhttpd: shcmd (134): exit status: 1 Jul 21 12:23:57 J1900 emhttpd: shcmd (136): rm -f /boot/config/plugins/dynamix/mover.cron Jul 21 12:23:57 J1900 emhttpd: shcmd (137): /usr/local/sbin/update_cron Jul 21 12:23:57 J1900 emhttpd: Retry unmounting user share(s)... Jul 21 12:24:02 J1900 emhttpd: shcmd (138): umount /mnt/user Jul 21 12:24:02 J1900 root: umount: /mnt/user: not mounted.
July 22Jul 22 Community Expert 7 hours ago, jfitzell said:Jul 21 12:23:52 J1900 emhttpd: error: get_key_info, 741: Invalid argument (22): stat: /boot/config/Starter.keyThis means the key was not valid. Possibly it caught the new key in the process of being written.7 hours ago, jfitzell said:Jul 21 12:23:53 J1900 emhttpd: Unregistered Trial - expired (EEXPIRED)Since the paid key was invalid, it looked for another one and found an expired trial, but this by itself is not a problem, since it would not matter if a valid key was installed.7 hours ago, jfitzell said:Jul 21 12:23:53 J1900 emhttpd: Starter key detected, GUID: ****** FILE: /boot/config/Starter.keyIt then detected the correct new key, but the array had already started to stop.7 hours ago, jfitzell said:Jul 21 12:23:53 J1900 emhttpd: error: malloc_share_locations, 8649: Operation not supported (95): getxattr: /mnt/user/appdataThe array failing to stop is unrelated to the key issues and likely related to this, which suggests something is writing something to appdata outside Unraid.This is the first time I ever seen this happening, so possibly an isolated/timing issue, but I'll test myself and will forward this issue to LT even if I can't repro in case this can be improved.
7 hours ago7 hr On 7/22/2026 at 8:50 AM, JorgeB said:This is the first time I ever seen this happening, so possibly an isolated/timing issue, but I'll test myself and will forward this issue to LT even if I can't repro in case this can be improved.I just had this happen too unfortunately. My license renewed on the 28th of august. This morning my array had stopped, there was a notification from early in the morning about the license have been updated, curiously the notification text something about the notification being invalid. I tried just staring the array but that did nothing so had restart. Same get_key_info error for me but no expired trial involved.Aug 31 00:11:04 NAS emhttpd: error: get_key_info, 767: Invalid argument (22): stat: /boot/config/Starter.key Aug 31 00:11:04 NAS emhttpd: Unregistered Missing key file (ENOKEYFILE2) Aug 31 00:11:04 NAS emhttpd: ENOKEYFILE2: Stopping array Aug 31 00:11:04 NAS kernel: mdcmd (36): nocheck cancel Aug 31 00:11:05 NAS emhttpd: Spinning up all drives... Aug 31 00:11:05 NAS emhttpd: read SMART /dev/sdb Aug 31 00:11:05 NAS emhttpd: read SMART /dev/sdc Aug 31 00:11:05 NAS emhttpd: read SMART /dev/nvme0n1 Aug 31 00:11:05 NAS emhttpd: read SMART /dev/mmcblk0 Aug 31 00:11:05 NAS emhttpd: read SMART /dev/sda Aug 31 00:11:05 NAS emhttpd: Stopping services... Aug 31 00:11:06 NAS emhttpd: Starter key detected, GUID: 0..8 FILE: /boot/config/Starter.key Aug 31 00:11:06 NAS emhttpd: shcmd (144): /etc/rc.d/rc.samba stop Aug 31 00:11:06 NAS rc.samba: Stopping Samba server daemon... Aug 31 00:11:06 NAS rc.samba: kill 2110 Aug 31 00:11:07 NAS rc.samba: killall --ns 1808939 smbd nmbd wsdd2 winbindd Aug 31 00:11:07 NAS winbindd[2128]: [2026/08/31 00:11:07.392940, 0, traceid=1] ../../source3/winbindd/winbindd_dual.c:1984(winbindd_sig_term_handler) Aug 31 00:11:07 NAS winbindd[2128]: Got sig[15] terminate (is_parent=1) Aug 31 00:11:07 NAS wsdd2[2124]: 'Terminated' signal received. Aug 31 00:11:07 NAS wsdd2[2124]: terminating. Aug 31 00:11:07 NAS rc.samba: Samba server daemon... Stopped. Aug 31 00:11:07 NAS emhttpd: shcmd (145): rm -f /etc/avahi/services/smb.service Aug 31 00:11:07 NAS avahi-daemon[2073]: Files changed, reloading. Aug 31 00:11:07 NAS avahi-daemon[2073]: Service group file /services/smb.service vanished, removing services. Aug 31 00:11:07 NAS emhttpd: shcmd (147): /etc/rc.d/rc.nfsd stop Aug 31 00:11:07 NAS rc.nfsd: Stopping NFS server daemon... Aug 31 00:11:08 NAS rpc.mountd[3781640]: Caught signal 15, un-registering and exiting. Aug 31 00:11:08 NAS rc.nfsd: /usr/sbin/rpc.nfsd 0 Aug 31 00:11:08 NAS rc.nfsd: /usr/sbin/exportfs -au Aug 31 00:11:08 NAS rc.nfsd: NFS server daemon... Stopped. Aug 31 00:11:08 NAS emhttpd: Stopping mover... Aug 31 00:11:08 NAS emhttpd: shcmd (148): /usr/local/sbin/mover stop Aug 31 00:11:08 NAS root: mover: not running Aug 31 00:11:08 NAS emhttpd: Sync filesystems... Aug 31 00:11:08 NAS emhttpd: shcmd (149): sync Aug 31 00:11:08 NAS emhttpd: shcmd (150): /usr/sbin/zfs unmount -a Aug 31 00:11:08 NAS emhttpd: shcmd (151): umount /mnt/user0 Aug 31 00:11:08 NAS emhttpd: shcmd (152): rmdir /mnt/user0 Aug 31 00:11:08 NAS emhttpd: shcmd (153): umount /mnt/user Aug 31 00:11:08 NAS emhttpd: shcmd (154): rmdir /mnt/user Aug 31 00:11:08 NAS emhttpd: shcmd (156): rm -f /boot/config/plugins/dynamix/mover.cron Aug 31 00:11:08 NAS emhttpd: shcmd (157): /usr/local/sbin/update_cron Aug 31 00:11:08 NAS emhttpd: Unmounting disks... Aug 31 00:11:08 NAS emhttpd: shcmd (159): umount /mnt/disk1 Aug 31 00:11:09 NAS kernel: XFS (md1p1): Unmounting Filesystem 5d959a1a-41f9-4ee0-bd6e-3c83f09aeb47 Aug 31 00:11:09 NAS emhttpd: shcmd (160): rmdir /mnt/disk1 Aug 31 00:11:09 NAS kernel: mdcmd (37): stop Aug 31 00:11:09 NAS kernel: md1p1: stopping Aug 31 00:11:09 NAS kernel: md: unRAID driver removed Aug 31 00:11:09 NAS emhttpd: shcmd (163): /sbin/modprobe md-mod super=/boot/config/super.dat Aug 31 00:11:09 NAS kernel: md: unRAID driver 2.9.40 installed Aug 31 00:11:10 NAS kernel: mdcmd (1): import 0 sdc 64 15625879500 0 ST16000NM001G-2KK103_ZL2KVSCE Aug 31 00:11:10 NAS kernel: md: import disk0: (sdc) ST16000NM001G-2KK103_ZL2KVSCE size: 15625879500 Aug 31 00:11:10 NAS kernel: mdcmd (2): import 29 Aug 31 00:11:10 NAS kernel: md: import_slot: 29 empty Aug 31 00:11:10 NAS kernel: mdcmd (3): import 1 sdb 32000000 15609878528 0 ST16000NM001G-2KK103_ZL2J8Z87 Aug 31 00:11:10 NAS kernel: md: import disk1: (sdb) ST16000NM001G-2KK103_ZL2J8Z87 size: 15609878528 Aug 31 00:11:10 NAS kernel: mdcmd (4): import 2 Aug 31 00:11:10 NAS kernel: mdcmd (5): import 3 Aug 31 00:11:10 NAS kernel: mdcmd (6): import 4 Aug 31 00:11:10 NAS kernel: mdcmd (7): import 5 Aug 31 00:11:10 NAS kernel: mdcmd (8): import 6 Aug 31 00:11:10 NAS kernel: mdcmd (9): import 7 Aug 31 00:11:10 NAS kernel: mdcmd (10): import 8 Aug 31 00:11:10 NAS kernel: mdcmd (11): import 9 Aug 31 00:11:10 NAS kernel: mdcmd (12): import 10 Aug 31 00:11:10 NAS kernel: mdcmd (13): import 11 Aug 31 00:11:10 NAS kernel: mdcmd (14): import 12 Aug 31 00:11:10 NAS kernel: mdcmd (15): import 13 Aug 31 00:11:10 NAS kernel: mdcmd (16): import 14 Aug 31 00:11:10 NAS kernel: mdcmd (17): import 15 Aug 31 00:11:10 NAS kernel: mdcmd (18): import 16 Aug 31 00:11:10 NAS kernel: mdcmd (19): import 17 Aug 31 00:11:10 NAS kernel: mdcmd (20): import 18 Aug 31 00:11:10 NAS kernel: mdcmd (21): import 19 Aug 31 00:11:10 NAS kernel: mdcmd (22): import 20 Aug 31 00:11:10 NAS kernel: mdcmd (23): import 21 Aug 31 00:11:10 NAS kernel: mdcmd (24): import 22 Aug 31 00:11:10 NAS kernel: mdcmd (25): import 23 Aug 31 00:11:10 NAS kernel: mdcmd (26): import 24 Aug 31 00:11:10 NAS kernel: mdcmd (27): import 25 Aug 31 00:11:10 NAS kernel: mdcmd (28): import 26 Aug 31 00:11:10 NAS kernel: mdcmd (29): import 27 Aug 31 00:11:10 NAS kernel: mdcmd (30): import 28 Aug 31 00:11:10 NAS emhttpd: /sbin/blkid /dev/sda1 2>&1 Aug 31 00:11:10 NAS emhttpd: /dev/sda1: LABEL_FATBOOT="UNRAID" LABEL="UNRAID" UUID="11EE-1C4B" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="aaa9d678-01" Aug 31 00:11:10 NAS emhttpd: import 30 flash device: (/dev/sda1) Aug 31 00:11:10 NAS emhttpd: shcmd (165): rm -f /boot/config/forcesync Aug 31 00:11:10 NAS emhttpd: shcmd (166): sync Aug 31 00:11:10 NAS emhttpd: shcmd (170): /etc/rc.d/rc.samba start Aug 31 00:11:10 NAS rc.samba: Starting Samba server daemon... Aug 31 00:11:10 NAS rc.samba: /usr/sbin/smbd -D Aug 31 00:11:10 NAS rc.samba: /usr/sbin/wsdd2 -d -4 Aug 31 00:11:10 NAS wsdd2[1809221]: starting. Aug 31 00:11:10 NAS rc.samba: /usr/sbin/winbindd -D Aug 31 00:11:10 NAS rc.samba: Samba server daemon... Started. Aug 31 00:11:10 NAS emhttpd: shcmd (171): cp /tmp/emhttp/smb.service /etc/avahi/services/smb.service Aug 31 00:11:10 NAS avahi-daemon[2073]: Files changed, reloading. Aug 31 00:11:10 NAS avahi-daemon[2073]: Loading service file /services/smb.service. Aug 31 00:11:11 NAS emhttpd: shcmd (173): /etc/rc.d/rc.nfsd start Aug 31 00:11:11 NAS rc.nfsd: Starting NFS server daemon... Aug 31 00:11:11 NAS rc.nfsd: /usr/sbin/exportfs -r Aug 31 00:11:11 NAS rc.nfsd: /usr/sbin/rpc.nfsd -u -H 10.10.1.4 -H 127.0.0.1 -s 8 Aug 31 00:11:11 NAS avahi-daemon[2073]: Service "NAS" (/services/smb.service) successfully established. Aug 31 00:11:12 NAS kernel: NFSD: Using UMH upcall client tracking operations. ### [PREVIOUS LINE REPEATED 1 TIMES] ### Aug 31 00:11:12 NAS kernel: NFSD: starting 90-second grace period (net effffff9) Aug 31 00:11:12 NAS rc.nfsd: /usr/sbin/rpc.mountd Aug 31 00:11:12 NAS rpc.mountd[1809330]: Version 2.9.1 starting Aug 31 00:11:12 NAS rc.nfsd: NFS server daemon... Started. Aug 31 00:11:12 NAS emhttpd: shcmd (175): /etc/rc.d/rc.avahidaemon reload Aug 31 00:11:12 NAS avahi-daemon[2073]: Got SIGHUP, reloading.
4 hours ago4 hr Community Expert 2 hours ago, Leonick said:I just had this happen too unfortunately.This has been fixed for 7.4, with 7.3 a single verification error would stop the array, and although I couldn't reproduce, I think it happened if the key was being written at exactly the time of the verification, from 7.4 the array only stops if the key is invalid for more than 30 seconds.
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.