m0rphl1ng

I'm just coming to bump this and try to add some SEO to the post (and to thank you @lp0101 !!!! You're a life saver!) I'm running Unraid with a remote Plex server. I was receiving a stale file handle error on my Plex server, and I was unable to read anything from the directories of my unraid shares. I started with nfs using fstab. I then went to nfs using autofs. I searched everywhere and tried a few options. I heard it was the mover. I heard that disabling hard links was the answer. But your post here was the key--utilizing both NFS and SMB simultaneously on an unraid share will result in stale file handle errors on your remote server that mounts the share using NFS. Disabling the SMB will resolve the issue.

Thanks @trurl and @itimpi I am back online. Summary for any posterity that comes across this thread: Initial problem: USB Flash Drive died and user did not have a valid backup. Solution: Get every file you can off your dead flash drive. Purchase new flash drive Run Unraid USB Flash Creator on new drive Copy over every old file you can Copy over any old files, like the /config/super.dat file that contains your array information (disk order) from your most recent diagnostics zip Delete any old .key files, only keeping the most recent Run the make_bootable.bat Start up unraid with your new flash drive installed Check to make sure your array is correct, and go through the wizard to assign your Unraid key to the new drive Set up automatic backups of your flash drive to be stored somewhere other than your Unraid server Thank the awesome community for bailing you out!!!

Thanks. All three were previously there on my old flash drive. During my Unraid journey, I purchased a plus license, then purchased an upgrade to pro. Just to clarify--I should have only the pro.key file there, even though it isn't linked to this flash drive?

Also, considering this is a new flash drive, what is the best way to go about getting my license changed over to the ID of the new flash drive? I currently have a Trial.key, Plus.key and Pro.key inside the /config/ directory of the boot drive, obviously all referencing the previous flash drive. Should I delete all three of these and reboot?

Ooh, I have a diagnostics from three weeks ago. It contains a super.dat Can I just shut down the server and copy this onto the flash drive, then reboot? tower-diagnostics-20240109-0151.zip

Thanks for the response trurl! I know that I should have automated backups of the flash--I think years ago I, very stupidly, set this up to backup to the array. It looks like /config/super.dat was one of the compromised files that did not transfer over. However, I do have a super.old How can I read this file? super.old

Hello, My USB Flash Drive died. Putting it into other computers, it had the dreaded write protection error, letting me know that it was unrecoverable. Luckily, I was able to get nearly all of the data off of it. I purchased a new flash drive, ran the Unraid USB Flash Creator on it, then copied over all the files I had (overwriting the files that were put in place), and finally ran the "Make Bootable" batch file. I then spun up my server--and it works! Server is online, I was able to login using my existing information. However, I now have a blank array. Is there any way to find out the order of disks in my previous array? I have 18 total disks, 2 of which are parity. I can try and upload any files as necessary. Thanks!