-
-
License transfer
Hi, I am about to sell my License (and the associated USB Device) on the secondary market. Is there a way to change the associated EMail address or is there any process to follow in such a case? Thanks
-
License: Possible to wipe USB Stick, extract Unraid, copy saved license file back?
Thanks, @JorgeB
-
License: Possible to wipe USB Stick, extract Unraid, copy saved license file back?
Hi i am planning to restart my Unraid system from scratch. Rather than fiddling with files on the USB-Stick, i was planning to copy the license file to a safe place, wipe the stick, extract UNRAID onto it again and copy back the saved license. Is this supposed to work? I tried using "New Config", but it kept a few things i'd like to recreate (like mnt/system, docker.img, etc) from scratch. Alternatively, is it valid to just replace the /config from the USB device with the one from the install archive and add the license file? thx
-
doc-unraid started following [6.12.6] Does not start as USB Devices apparently switched ids?
-
[6.12.6] Does not start as USB Devices apparently switched ids?
Hi I have an (Basic license) unraid system with * 1 (fake) array device (USB) * 1 NVMe (cache) ZFS single device pool * 4 SSD zfs raidz2 pool attached via USB-C (Raidsonic device) After reboot, almost every second time, the Array does not start as it finds one or more disks from the USB attached pool missing. If i go to the console and import the pool via `zpool import` ZFS immediately imports the pool as instructed. Turns out that the problem is the ID for some SSDs that seem to change randomly (see screencast). A drive formerly identified as `Samsung_SSD_870_QVO_4TB_S5STNF0WA03436P -` is now for some reason identified as `Samsung_SSD_870_QVO_0000000000000002-0:0 ` When i try `smartctl -x /dev/sd[a-d] |grep -i Serial` all the serial numbers are there and plausible. After rebooting several times (no change in USB configuration) the drives return to their original IDs. Wouldn't it be good for UNRAID to include the smartctl returned data from the disk to identify them rather than what the kernel decides to provide as /dev/disk/by-id ? Any help appreciated, as i was willing to use unraid with scheduled poweron/off, which of course is not reliably working right now. cu Screencast from 2024-01-07 18-37-23.webm
doc-unraid
Members
-
Joined
-
Last visited