[Replacement key]

Trurl, you're a genius.  Yes I can see, for instance, DISK_ASSIGNMENTS.txt -- I'll bet that's useful, huh?  It's weird that both Unraid and Window says the flash drive is bad, but I seem to be able to read it.  I won't complain -- I'll just copy the data I need.

[Replacement key]

Yup, thank you -- I'm reading that now.

[Replacement key]

Yes, it would appear that I have successfully replaced the key.  I got a new email with a new URL, which I copied and pasted into Tower, and it appears to be happy (no red errors in the upper right corner)

 

[Replacement key]

Thanks again, trurl.  I should have checked my old emails first (in my defense, I didn't even remember what I was looking for).  Now to see if the various readme's can help me with my disk assignments, etc.

[Replacement key]

Thank you for the quick response, trurl.  I've found the five year old email with the order confirmation, but that doesn't contain the key.  I also seem to be able to access the "dead" USB drive, and I see a file in /config named Basic.key.  Honestly, I don't even remember what I'm looking for.  A URL?  A SHA256 key?  Yes, I have the key!

[Replacement key]

I'm not sure how badly I've screwed up, but my USB stick apparently died (w/o backup, of course).  I've purchased a new USB stick, installed Unraid, pluged it in to my server, and rebooted.  But rather than going to Tools -> Registration and hitting Replace Key, I clicked on Trial.  Now I don't have a "replace key" option, and I don't know how to proceed.  Do I need to buy a new USB stick and start over?  I'll probably have other questions after I get past this, but the first thing I need to do is to get my key onto that flash drive.

[Unraid OS version 6.9.2 available]

15 hours ago, Squid said:

I just tried it and the md5 is working properly for me.  I'd suggest to reboot and try again, after that run a memtest if only to rule it out.

Thank you, Squid.  I don't understand why, but the reboot fixed the problem.

[Unraid OS version 6.9.2 available]

I'm unable to update from 6.8.3 to 6.9.2 via the GUI.  I consistently get

Quote

plugin: updating: unRAIDServer.plg
plugin: downloading: https://s3.amazonaws.com/dnld.lime-technology.com/stable/unRAIDServer-6.9.2-x86_64.zip ... done
plugin: downloading: https://s3.amazonaws.com/dnld.lime-technology.com/stable/unRAIDServer-6.9.2-x86_64.md5 ... done
wrong md5
plugin: run failed: /bin/bash retval: 1

What's the problem here, and how can I fix it?

I'm not sure if this is the proper forum or thread; kindly direct me if I should post this elsewhere.

[RDP to Win 10 VM]

10 hours ago, BRiT said:

Did you try using the IP address instead of the name?

What a great idea!  That worked perfectly, so I thank you for the advice.  I still don't understand why 'DESKTOP-AR3CLUV' stops working, but as long as I have this workaround, that's all I need.

[RDP to Win 10 VM]

I have created a Windows 10 VM on my unraid server.  It all seems to be working satisfactorily, with one exception: When I first boot the VM, I have no trouble connecting to in from a Windows 10 host on my network.  However, once my host goes to sleep/hibernate or once it restarts, I can no longer connect to the VM.  The error message is

Quote

Remote Desktop can't find the computer 'DESKTOP-AR3CLUV'.  This might mean that 'DESKTOP-AR3CLUV' does not belong to the specified network.  Verify the computer name and domain that you are trying to connect to.

 

I can still connect to the VM with VNC, so I know that it is still running.  But the only way I have found to reconnect with RDP is to restart the VM.  I am hoping that somebody out there can help me figure out how to get RDP to reliably connect to my VM.