kennelfort

Thank you very much. I will test a few more things and see if I can figure it out.

Yes. Running vanilla Minecraft. I replaced the jar because the launcher wasn't seeing the server and perhaps the update had failed. Logs are attached. The TXT file is the Unraid Docker log output. The other two are today's logs from \appdate\minecraft\logs Let me know if you need anything else. FYI, this is a very old world I'm running. I think I ran it successfully with this docker last year, but honestly I can't recall if I ever got it running (too many things happened at once and I never got to play). Thanks again. Legolad Server Log.txt 2020-10-06-1.log.gz 2020-10-06-2.log.gz

Hello, @ich777. Thanks so much for the excellent MinecraftBasicServer docker for Unraid and all the great support you provide. I have just installed the docker. I allowed it to run as instructed, then I stopped the docker and replaced the jar with the latest jar. I also copied my old minecraft world files into the folder including the server.properties file which points to that old world. Lastly, I forwarded the ports (25565 and 25575) in my router. The server appears to launch just fine. When I look for the server in the Minecraft Launcher, I cannot find it. I'm sure I just missed something simple. Is there a way for me to figure out what I missed?

Thanks. I have seen that but haven't been able to find any documented process specific to Unraid and XFS. If I have to I'll try that, but I am hoping for some input based on direct experience with 6.8.x. Thanks!

I was using the console in 6.8.3 and accidentally deleted an entire folder of media files. I immediately stopped the array and started searching these forums and others. Unfortunately there isn't very much recent information about recovering deleted files. The older posts (10 years old) all reference older non-XFS file systems and their tools. The newer posts mention XFS but don't provide enough detail or specific tools to use. The Unraid docs all reference Reiser, not XFS. (https://wiki.unraid.net/index.php?title=FAQ#How_do_I_recover_data_from_an_unRAID_disk.3F) I know exactly which disk needs the recovery. Is there a current method of file recovery for XFS file system that you folks would trust?

Is this still a valid process with the latest UNRAID build?

You know, I remember reading this page when I first set up my server nearly a year ago, but most of it was Greek to me. Reading through it again now I can understand a LOT more of it. Thanks for reminding me this exists. Sometimes the old adages are correct: RTFM. 🙂

Ok. My Min. Free was set to 0, so I bumped it to 50GB. I did the same for all the other shares except appdata which I set to 10GB. Anything else look amiss?

Hey folks, I'm a bit of a novice, but I've managed to get my Unraid system up and running pretty well with help from you all. Unfortunately I'm now seeing something that I just don't understand. I got an Unraid error this morning that Disk1 was 100% full. There are 10 disks in my system (including the parity drive). Disks 2-5 each have about half TB free. Disks 6 & 7 have about 4 TB free each. Disks 8 & 9 are both empty. Is there a threshold I can set that prevents Disk1 from hitting a state that yields this Unraid error? Is this something I should just ignore?

Will do. Thanks again!

Hey @itimpi, my parity sync is up to 80% now. Last night I got this error and I wondered if you think it's something I need to do anything about: This morning my array shows as healthy:

Currently, the message "Parity is invalid. Click to spin down device." is displayed when a user adds a parity drive where none existed before. It is paired with the call to action "Click to spin down the drive" which appears in the hover for all drives. This has the undesired effect of looking like the drive is in an errored state and needs to be spun down. I suggest the Parity Invalid message read "Parity is invalid." I further suggest that the option to spin down the drive be replaced with "Click for more details.". When users click the message, display a help page that explains invalid parity including the fact that new parity drives show as invalid until the first parity sync is completed.

Oh. Thanks!!! Now that seems like something that could be fixed pretty easily. Perhaps, instead of "Parity is invalid. Click to spin down device." it could say "Parity is invalid. Click for more details." And then have a help page that explains the valid reasons for having invalid parity. I'll go look for the right place to make this suggestion.

Sorry to ressurect this ancient thread, but this is the closest issue to mine that I've seen so far. If either of you is still around, @sureguy, @itimpi, I'd appreciate your insights on my post here:

EDIT/SOLVED! Your first parity sync always shows as invalid until it is complete. DO NOT SPIN DOWN THE DRIVE or cancel the parity sync. Just wait for 100% completion. Hey folks, I'm out of my depth and hoping for a little help here. TL;DR: Just added my first parity drive (never had one before now) and it's showing a Parity Invalid error even though the brand new drive tests out fine in SMART and WDDiags. LONG VERSION My server has been running fine for 6 months. I'm running Unraid v6.8.3. SMART Tests Attached. Yesterday I added my first ever parity drive to my server. Here is what I did: 1. I added 5 new HDDs to increase capacity and begin the parity process. 2. Tested all drives using the WD diag tools and the long test (took about 5 days). 3. Assigned the first 4 HDDs and started the array. Everything checked out fine. 9 HDDs working. 4. I stopped the array again and assigned the 5th HDD (12TB) as a parity drive. 5. Started the array and the parity drive started running a parity sync. 6. I shut down Radarr, Sonarr, and everything else except PLEX. The parity check was running and I let it run over night. 7. When I woke up I saw a single error message: 8. I also noticed that there was an alert on the drive: 9. As you can see here, UNRAID thought it was running Parity-Sync all night and had gotten to 61.4% complete and was still going. 10. I was tempted to allow it to finish the parity sync, but after reading some posts on Reddit and here, I cancelled the check. Stopped the Array. Unassigned the parity drive. And Started the array again. The status of the array was fine. No errors. 11. The drive showed up as unmounted and unassigned: 12. I stopped the array again. Assigned the parity drive. And started the array again. I got the same Parity Invalid error as above. There are so many posts that talk about parity invalid as a GUI issue, but I'm loathe to try any of those solutions since the things that led to the error are not things I'm seeing. This is a fresh drive on a system that has never had a parity drive before. The drive tested fine under WD DIAG before I installed it in the server. The SMART tests (both long and short) were fine as well. kennelfort-smart-20200324-0747.zip

So I'm trying to restore a backup of my server and the first thing I'm supposed to do is add the shares that I had before. But when I enter the name and settings and click Add Share, the share does not appear in the Shares tab. This is all in service of another post I made asking for some help: Any idea what I'm doing wrong here? I've attached my diagnostics: kennelfort-diagnostics-20191126-2127.zip

Cool. Last question for now. I've seen several mentions of creating my appdata share appropriately. What precisely is meant by that? Do I just create a folder called AppData and make it a share? Do I need to recreate the entire folder structure?

Ok. Sorry to be so dense, but I'm trying to make sure I don't make any assumptions and mess this up even more. I've got 2 SSDs now: The original SSD cache that I wiped and is now unmountable The new SSD - which hasn't yet been used as a cache drive - that is mounted and ready to use as cache. When you say "don't change anything when you want to restore", does that include the SSDs?

Thanks. I can do that tonight. Just to be clear, there's no problem hitting restore and pointing to the new Cache drive I put in? (assuming it can find the Restore Set)

Perfect. Before we continue, allow me to say thanks for your help. I really appreciate it. So here is what I see: DRIVE 1 the other 2 backups are also here, but the one for BACKUP_USB is empty and there is an empty APPDATA folder here: DRIVE 2 No backup or appdata DRIVE 3 No backup or appdata DRIVE 4 No backup or appdata DRIVE 5 No backup or appdata DRIVES 6-8 Not mounted yet. Need to tape over the pins to get them to read. So, what's the process for restoring from this backup? Or is there one?

Hmmmm. So I did have some stuff hitting the cache. That was why I was planning to replace the cache. It was getting pegged all the time as I transferred lots of data or and I downloaded lots. So the cache was definitely active, but when it crashed, I hadn't moved or downloaded anything in a day or so, certainly enough time for the Mover to have run (it's set to 1 hour). Still, the mover would only have moved content and not the APPDATA folder. So APPDATA would not be recoverable without the backup data set, right? I guess what I don't understand is that I watched the backup complete and it was set to back up to the a folder called BACKUP_APPDATA on a share called DATA. Shouldn't that still be there? I mean, assuming I can pull the HDDs and read them individually, I would expect to find that BACKUP_APPDATA folder on one or more HDDs with the files that make up the backup spread across them. In other words, it's not breaking individual files into multiple parts across drives is it?

TL;DR I accidentally erased my SSD cache drive after I backed it up. How should I recover the contents of the cache drive? DETAILS I was working on my server this weekend and made a stupid mistake. I'm really hoping the smart folks here can tell me the best way to fix this. SYSTEM Dell PowerEdge 520 UNRAID 6.7.2 16 GB RAM 8 HDDs 1 SSD Cache (120 GB) No Parity Drives (still moving files over from old setup, so haven't turned on parity yet) WHAT HAPPENED A few days ago my server went offline (I run it headless). I rebooted without even attaching a monitor. After reboot it didn't come up so I attached a monitor, figured out it was a Kernel Panic caused by Flash OS corruption, and rebuilt the flash drive. On reboot everything came back up fine. After fixing the corruption issue, I wanted to replace my 120 GB SSD cache with a new 1 TB SSD cache (to make copying large data sets easier). Here is what I did next: updated all dockers and plugins made a backup using CA Backup / Restore Appdata shut down the server installed the new 1 TB SSD forgot to plug in the SSD sata cable booted the server saw a cache drive listed that needed to be formatted assumed it was the new drive started the format noticed that this was my original cache drive, NOT my new 1 TB SSD YIKES! Shut down Attached the cable to the new SSD Rebooted Now the old cache drive now shows as unmountable, no UUID Now I see this: I really don't need the old SSD. I was planning on copying over everything from the old SSD to the new SSD. But now that I wiped the old cache drive, I'm not sure what the best recovery path is. I have the backup, but not sure if I should restore to the old SSD or the new one. Also not sure if the backup will have everything I need to restore the original cache files. Here is the CA BACKUP setup I had: And here is what shows in the backup plugin under the Restore tab: When I read this Restore page I went to the Shares tab and saw that all my shares were gone. I'm assuming they were part of the cache setup. I'm still very new to UNRAID so I just stopped and created this post. If you have any insight that can help me get things running again, I'd appreciate it. Many thanks!