kentb

Thanks for responding.

I deactivated the old USB drive, copied the old key across. First error. I then downloaded the excising key (see images above) and the error occurred again. Have read a number of articles dealing with Error 4, and key not working, and have downloaded, rebooted and renamed several times as per most articles.

Nothing works. Have tried manual download, auto download, delete, rename etc. Any help very much appreciated., Unfortunately the licensing process is a black box, so I can't brute force solve it like I usually do.

Tried to purchase or get a trial license. GUID is licensed. But cannot download. Could have been due to the 2d clock error that was fixed after the license issues

I've done that several times, and renamed the old key to Basic.key.old .old2 ertc. Rebooted about 5 times with different downloads and copies.

My motherboard went haywire and corrupted my drives with SATA errors. My new motherboard would not boot my old USB, so I made a new one, and copied my Basic.key from my old USB /config to the new USB. It told me it was successful, but I am getting error 4 (fixed by changing date time), and now getting a successful copy key, with an error. I use the Install Key To install a registration key, paste the key file URL in the box below and click Install Key. Key file URL: and get the following error message: Error Something went wrong Basic Key Recovered Successfully Any help ? I'm trying to rebuild my server after a few weeks downtime, and this is sending me batty. Followed several guides, error messages no help.

I've just had the same issue. Docker refused to start. I changed th eimage file to an actual folder to help diagnose it, and this error occurred.

OK ... more on this one ... I pulled everything out and put a new switch, cables and laptop on my bench and re-ran with minimal services etc, with either the same result, or a massive slow down to 4kiB after a few Gigabytes of data writes. So not the cable, not the switch, and most likley Unraid. I then installed TrueNAS Scale, and with ZFS, got 112MiB a second transfer for over 30GiB of data transferred across both NIC cards. Much faster then Unraid, and no crashing after a few gig of data. It has run flawlessly for a week now. My preference, however, is to continue to run Unraid due to the simplicity of Docker containers vs Truecharts, and the awesome ecosystem the has been created. Playing around, the issue may be caused by Unraid running out of memory to cache the transfer (I am runnig 3xSSD and no cacheDrives and only 8GB RAM) then writing direct to the Unraid SSD array, which somehow clobbers the machine. I am hoping there may be a simple fix, or potentially will have to wait for Unraid with ZFS to fix the issue. Any suggestions ot fix the crash on this setup.

Apple compatibility is set to on ... it indicates potential issues with win clients. This must be on by default, as I certainly did nto turn it on. will wait for partity to complete and change setting.

@Squid Copied files from PC to unraid ... speed was around 107MiB ... crashed on the first file of about 1.5GiB. PC Network stayed up, but unraid unresponsive (web not working, file transfer not working). Rebooted unraid, network still all good. While parity checks are running, copied about 12GiB to synology ... averaged about 60GiB, but worked fine. No crashes, as always. I'm at a loss ... advice on next test steps appreciated.

also @Squid, during testing last night, I took all devices other than a laptop, and the pc off the network so only the unraid, pc and lappy were plugged in, so unlikely to be a cable, although I'll keep it in mind as the switch to router cable was repurposed as the pc to router cable - it's only a few years old and is cat6 and is not pinched or twisted, and I never got failures when copying equally large files to my soon to be replaced synology.

Hey there @Squid ! Thanks for the quick reply. I opened the unraid box up, then ran a memtest (Fresh off the website, not the unraid version) and stress test using ubcd. The memory tests were all OK ... a big green success and the stress tests had reasonable CPU Temps and all tests worked. (I underclock the i7 slightly) I have replaced the network cable between the router and unraid box (I have one gigabit connection in the 192.168/16 space, and another in the 10/8 DMZ space and bridge most docker containers to the area I want them to communicate on). I just rebuilt my IP address ranges and built a network diagram of all IP Addreses as I did it (it's not that large), and if it is not DHCP (192.168.50/24 then it is on my list). No clashes, .. unraid is guaranteed a unique fixed IP, and during my testing the other night, the PC was changed back to DHCP. Asus DHCP log confirms no clashes, and all non .50 devices were audited again I'll rerun a transfer of large files and see what happens (unraid has just finalised booting), and report back.

My unraid server is crashing the network (likely flooding) is a strange manner. Brand new unraid build - 1-2 days max. latest version. I had to rebuild as a newly purchased parity SSD was a few hundred meg smaller than the other disks of the same brand, so reset and rebuilt the lot as wanted to do it properly. First shares I created are the file shares, so I begin copying ... When copying a number of large files from Windows --> unraid, the network is beautifully and fully utilised, then the network crashes. The entire ethernet network stopped working, but the wifi continued to work (I have some level of isolation - which seems to be pertinant). By saying the network stopped working - the windows network adapter showed the globe with the coss, saying no internet, and when the adapter was reset, it hung saying attempting to configure, then goes into an unknown network state where IP4 is unavailable and IP6 is semi functional. anotyher PC on the network also had the same symptoms. Pulling out the network cablke, and pluggin back in did the same hang in configuring the network. appeared to be a complete hardware failure somewheter in the PC, network infra or router+switch. I assumed it was an older network switch I have between the unraid server and the windows PC not handling the amount of data, so I connected directly to the router (unraid server plugged into router as well). Nope - network down for all clients. Assuming it was my windows PC, i eventually reset my network completely in Windows - blowing away all vpn, drivers and config etc. No joy. Assuming it was my router (Asus beast with Asus-WRT merlin which I updated firmware a few days ago), I eventually factory reset the router and rebuilt using mostly defaults.. At this stage I was looking at somethig broken hardware wise ... buying a new router, or perhaps a new network adapter. Plug in a laptop, network works, then goes down. then works, then goes down.Assume the Router has blown the ethernet chip and is overheated. Pulliung out all network cables, restart router ... lappy only device ... it works. And is stable. Plug in my PC ... still works. Wow. Run video on laptop and PC - still works. Plug in the printer ... still works, plug in unraid ... CRASH ... entire network down. Reboot unraid. Network is working. Build parity and wait for parity to complete building. Make some folders, start copying multiple large files win --> unraid (no network switch, directly plugged in to the newly factory reset and built asus merlin router). Copy about 6GiB, CRASH !!! !!!!!!!!!!!!!!!! Network down. Unplug unraid server ... all is working. Plug un unraid, the array is down, and have to rebuild the parity disk all over again. Machine looks to have rebooted. SO ... when copying a large amount of files over SMB using win --> SMB, unraid crashes and breaks my entire network. Confirmed it is unraid, and a very clean, recently built machine. happy to diagnose, play with and otherwise look at why this is happening. (edit ... 12 hours later and it is rick solid stable, running onedrive downloading 500G quietly in the bacckground, but I have not yest copied lots of large files across again yet as don't want to keep rebuilding parity. Thanks in advance for your help. raider-diagnostics-20230129-0009.zip

My unraid server is crashing in a very similar manner. Brand new build (newly purchased parity SSD is a few hundred meg smaller than the other disks of the same brand, so reset and rebuilt the lot). First shares I created are the file shares, so I begin copying ... When copying a number of large files from Windows --> unraid, the network is fully utilised, then the network crashes. The entire ethernet network stopped working, but the wifi continued to work (I have some level of isolation - which seems to be pertinant) I assumed it was a switch I have between the unraid server and the windows PC, so I connected diretly to the router (unraid server plugged into router as well). Nope - network down for all clients. Assuming it was my windows PC, i eventually reset my network completely in Windows - blowing away all vpn, drivers and config etc. No joy. Assuming it was my router (Asus beast with Asus-WRT merlin which I updated firmware a few days ago), I eventually factiry reset the router. At this stage I was looking at buying a new router, or perhaps a new network adapter. Plug in a laptop, network works, then goes down. then works, then goes down.Assume the Router has blown the ethernet chip and is overheated. Pulliung out all network cables, restart router ... lappy only device ... it works. And is stable. Plug in my PC ... still works. Wow. Run video on laptop and PC - still works. Plug in the printer ... still works, plug in unraid ... CRASH ... entire network down. Reboot unraid. Network is working. Build parity and wait for parity to complete building. Make some folders, start copying multiple large files win --> unraid (no switch, direct in the newly built asus router). Copy about 6GiB, CRASH !!! !!!!!!!!!!!!!!!! Unplug unraid server ... all is working. Plug un unraid, the array is down, and have to rebuild the parity disk all over again. Machine looks to have rebooted. SO ... when copying a large amount of files over SMB using win --> SMB, unraid crashes and breaks my entire network. Confirmed it is unraid, and a very clean, recently built machine. raider-diagnostics-20230129-0009.zip