Kohlelol

Alright. Thanks for that explanaition. Given that I "got my server back" and that I can access the data, I would call this issue solved. Again: I'm really, really thankful for your help and I'm glad that UNRAID has such a great and useful community. You can mark this as solved now, I'll pick a solution as well.

Thank god it works. I can access everything again. Thank you so much. You two really helped me out here. I just did that and below you can find the new Diagnostics. Yes, I made sure to do that. The users are still gone, but there weren't that much so it's just an inconvienience. Maybe some reconfig here and there. My Server also sent me some messages via the telegram-bot so that works too. My Windows-VM is back as well. It still didn't show any shares until I started the array "for the first time" again, though. That really put me off. I didn't want to start the thing and let it overwrite or format something. But I'm really glad I could reach out to everyone here. This was a rather quick fix for what I thought was a big problem. Thank you for your service. I thought I lost some really important data (which I should make some back-ups now) mimir-diagnostics-20221103-0214.zip

Yes. I took the entire "config" folder and used it to overwrite the one the UNRAID-Tool created when making the drive. It looks like this now (I left the FSCK folders in just to be sure):

I've created the new Thumbdrive and did a boot just now (took me a while, however). Now, Login still is with the "new password" as explained in the original post and UNRAID won't let me Start the array because of an GUID-Error. I fixed that by clicking Contact Support and blacklisting the old key. UNRAID itself seems to be working again now, but the issue with "no shares" or "no users" still persists. No case picture on the login and dashboard pages as well. There is one peculiar change, however: My "root" user now has the picture back, which I set a few months back. I don't want to risk starting the array because of that - or is it "safe" now?

Okay, thank you both. I just got to working on this, flashing it at the moment. To be sure I went and bought a new usb-drive for this. After I made an image from the old one and a copy, I feel like I should be able to restore. Yes, I didn't properly explain what I meant there. I just wanted to let you know that I can see the target maximum size and stuff like that. The "timemachine-air" for example has a size limit and the config still shows that. (luckily) Huh, it's really that easy? I did not expect such a fast solution to my issue. I really thought the stick would be fine, given that I can still read in terminal and on my windows machine... but I guess it's probably a good idea to switch it out anyways. It worked for about 3 years I think... (Intenso Ultra Line 32GB) I'll be back to report how my reinstall worked out. Thanks again to both of you. You really helped me out big time already.

Okay, thank you. I just removed Nerdpack and installed Nerdtools instead. After the List-Command you sent in your reply, it shows me the /boot folder with a lot of ".REC" Files created on Jan 1 1980. I already read in a different post, that this might have something to do with a crash. or a curruption... I can navigate through the folder and, in config/shares for example, to see the shares that existed before the issue. If you want the exact output, there you go: total 313M drwx------ 8 root root 16K Jan 1 1970 ./ drwxr-xr-x 19 root root 400 Nov 2 01:17 ../ drwx------ 3 root root 16K Oct 9 2019 EFI-/ -rw------- 1 root root 16K Jan 1 1980 FSCK0000.REC -rw------- 1 root root 16K Jan 1 1980 FSCK0001.REC -rw------- 1 root root 16K Jan 1 1980 FSCK0002.REC -rw------- 1 root root 16K Jan 1 1980 FSCK0003.REC -rw------- 1 root root 432K Jan 1 1980 FSCK0004.REC -rw------- 1 root root 16K Jan 1 1980 FSCK0005.REC -rw------- 1 root root 16K Jan 1 1980 FSCK0006.REC -rw------- 1 root root 16K Jan 1 1980 FSCK0007.REC -rw------- 1 root root 16K Jan 1 1980 FSCK0008.REC -rw------- 1 root root 16K Jan 1 1980 FSCK0009.REC -rw------- 1 root root 16K Jan 1 1980 FSCK0010.REC -rw------- 1 root root 16K Jan 1 1980 FSCK0011.REC -rw------- 1 root root 16K Jan 1 1980 FSCK0012.REC -rw------- 1 root root 16K Jan 1 1980 FSCK0013.REC -rw------- 1 root root 16K Jan 1 1980 FSCK0014.REC -rw------- 1 root root 16K Jan 1 1980 FSCK0015.REC -rw------- 1 root root 16K Jan 1 1980 FSCK0016.REC -rw------- 1 root root 16K Jan 1 1980 FSCK0017.REC -rw------- 1 root root 16K Jan 1 1980 FSCK0018.REC -rw------- 1 root root 16K Jan 1 1980 FSCK0019.REC -rw------- 1 root root 16K Jan 1 1980 FSCK0020.REC -rw------- 1 root root 16K Jan 1 1980 FSCK0021.REC -rw------- 1 root root 16K Jan 1 1980 FSCK0022.REC -rw------- 1 root root 16K Jan 1 1980 FSCK0023.REC -rw------- 1 root root 16K Jan 1 1980 FSCK0024.REC -rw------- 1 root root 16K Jan 1 1980 FSCK0025.REC -rw------- 1 root root 16K Jan 1 1980 FSCK0026.REC -rw------- 1 root root 16K Jan 1 1980 FSCK0027.REC -rw------- 1 root root 16K Jan 1 1980 FSCK0028.REC -rw------- 1 root root 16K Jan 1 1980 FSCK0029.REC -rw------- 1 root root 16K Jan 1 1980 FSCK0030.REC -rw------- 1 root root 16K Jan 1 1980 FSCK0031.REC drwx------ 2 root root 16K Oct 9 2019 System\ Volume\ Information/ -rw------- 1 root root 117M Oct 6 22:55 bzfirmware -rw------- 1 root root 65 Oct 6 23:01 bzfirmware.sha256 -rw------- 1 root root 5.9M Oct 6 22:55 bzimage -rw------- 1 root root 65 Oct 6 23:01 bzimage.sha256 -rw------- 1 root root 20M Oct 6 22:55 bzmodules -rw------- 1 root root 65 Oct 6 23:01 bzmodules.sha256 -rw------- 1 root root 150M Oct 6 23:01 bzroot -rw------- 1 root root 20M Oct 6 22:56 bzroot-gui -rw------- 1 root root 65 Oct 6 23:01 bzroot-gui.sha256 -rw------- 1 root root 65 Oct 6 23:01 bzroot.sha256 -rw------- 1 root root 16K Oct 6 22:55 changes.txt drwx------ 14 root root 16K Nov 2 13:50 config/ -r-------- 1 root root 120K Oct 9 2019 ldlinux.c32 -r-------- 1 root root 68K Oct 9 2019 ldlinux.sys -rw------- 1 root root 7.8K Oct 6 22:55 license.txt drwx------ 2 root root 16K Nov 1 17:17 logs/ -rw------- 1 root root 1.8K Oct 6 22:55 make_bootable.bat -rw------- 1 root root 3.3K Oct 6 22:55 make_bootable_linux -rw------- 1 root root 2.4K Oct 6 22:55 make_bootable_mac -rw------- 1 root root 147K Oct 6 22:55 memtest drwx------ 2 root root 16K Oct 16 00:48 previous/ drwx------ 2 root root 16K Dec 21 2019 syslinux/ -rw------- 1 root root 492 Oct 6 22:55 syslinux.cfg-

Thank you for your quick reply. I've attached the ZIP-File containing the Sytem Diagnostics from the Tools Tab. mimir-diagnostics-20221101-1717.zip

Hello everyone, This is my first time posting (on any forum, actually), but I have encountered a problem which is beyond me and I don't want to proceed accidentally destroying all my data. Sorry if this is a lot to read, but I don't want to leave out important details. Let me start by explaining what I did: Yesterday, I wanted to move some files from one PC in my Network to another utilizing my UNRAID-Server. We're talking a rather large amount of data here (Red Dead Redemption 2 Gamefiles, about 120GB). After moving all the files from my first machine to UNRAID, I needed to reset the ownership of the files, because the other PC couldn't access it. When I started the "new permissions" utility in the "tools" tab, I accidentally clicked on 2 shares being "cleared". I then closed the tab with the progress bar and did something else. When I came back, the files still weren't accessible, so I thought the "new permissions" tool wasn't done yet. Starting a new one didn't bring up the pop-up. So I thought "Go figure, I'll restart and try again.". Restarting turned out to be quite the mistake however, because when UNRAID came back, the Web-GUI asked me to put in a new password for root. After I did that, my UNRAID loaded the GUI, but with nearly all my config is gone. Also, UNRAID wasn't correctly registered anymore and it wanted me to enter a new UNRAID-Basic key. After restarting once, the licence-issue disappeared. After mounting the drives back where they were, I tried turning the array back on in maintenace-mode, but after that I got too worried I'll ruin all the data I got saved. I'll descibe the the issue some more: The config, which saves what share is which, how big they are, which users exist, which drives are storage or cache or pairity, even the little picture, showing the Case-design - all seems to be gone. My plug-ins and Apps, however, still exist and are (nearly all) up-to-date. Just as I left it. The thing is, I have a bit of an unusal setup. At the moment I use UNRAID as a rather basic NAS mostly. I got some shares for time-machines, a share for exchanging data, one for "Backup", a few others. They are all stored on 4 Disks. 3 of them are old (rather small) SSDs, that I just threw in there to have some faster storage for the Data-Exchange - I actually don't care about the data on those, it's not even 750 GB to begin with. The other drive I hold very dear, however. It's the drive housing all the backup (and games, but I can lose those). It's a 12TB WD-Gold I got just for this machine 3-4 years back. I wanted to buy a second one for parity, but never got to getting one. I also don't really have a Backup for that. (I always pushed doing that away from me) Now, my main priority is getting to the data on the 12TB drive, but I doubt that this will be possible without UNRAID working again. Secondly, I would love my UNRAID-machine to work again, obviously. I already tried a few things: I checked the USB-drive, containing UNRAID. It works fine on my Gaming machine, I already made a Backup. It actually also shows up in UNRAID. After opening the Web-GUI's Terminal, I cd'd into the config/shares folder and using nano I saw the same things I see on my windows machine. This means the Hardware seems to be working (right?). I also tried different USB-Ports. 3.0, 2.0, Front, Back - Doesn't matter. The BIOS also shows the BOOT-order only wanting to boot from my flash-drive. When looking at google's results for similar issues, I couldn't really get much more than this out of it. The hardware seems fine, UNRAID is registered (again, no clue why that wasn't the case at one point). Oh, and here are the Hardware-Specs: Unraid OS Basic M/B:ASUSTeK COMPUTER INC. SABERTOOTH Z170 MARK 1 Version Rev 1.xx BIOS:American Megatrends Inc. Version 1801. Dated: 03/24/2016 CPU:Intel® Core™ i5-6600K CPU @ 3.50GHz HVM:Enabled IOMMU:Disabled Cache:128 KiB, 128 KiB, 1 MB, 6 MB Memory:16 GiB DDR4 (max. installable capacity 64 GiB) Network:bond0: fault-tolerance (active-backup), mtu 1500 Kernel:Linux 5.19.14-Unraid x86_64 OpenSSL:1.1.1q Drives: 1x 120GB Samsung 850 EVO, 1x Kingston 240GB, 1x Kingston 480GB, 1x WD Gold 12 TB Boot-Device: Intenso Ultra-Line 32GB Flash Drive Thank you to everyone who read this far. It feels kinda dumb for me to ask for help, given that I literally worked and now study in IT, but I think it's the safest bet I got at the moment. Please let me know which config- or log-files you need to fix this. I'll keep the server turned off until there is anything I should try.