rutherford

@scytherbladez the reddit comment below looked pretty helpful for repairing databases. But as you said you rolled back and it's working again. My setup: Repository: lscr.io/linuxserver/plex then in the Plex UX: Settings > General: Version 1.32.1.6999 Ah there are the versions you're talking about, github. https://github.com/linuxserver/docker-plex Releases 1.32.1.6999-91e1e2e2c-ls167 But if going from one version to a newer breaks it, there still may be something going on with only your database. Are you going to stay on ls163 from here on out? How about nuking and rebuilding? The most annoying part about that is losing the watched/unwatched statuses; but it would probably get you back up and running.

Interesting. Huh. I’ll try that out!

What does that look like on the Main page? Is that a second disk cache drive?

I was thinking this yes. In what manner should I add this extra cache drive to array (mark it as not included or something)? Or leave as unassigned device?

I'd like to split out my plex data folder to another hard drive. I added another SSD to the server, it's currently under Unassigned Devices. What's the best way to set this up? thanks! Plex docker > Settings Repository: lscr.io/linuxserver/plex Appdata: /mnt/user/appdata/plex appdata user share settings: Use cache pool: Only Select cache pool: Cache

Swapped out some memory, moved a couple of the stick from server into my desktop and ran memtest86 last night. Still going in the morning! Good grief. But apparently enough to tell: FAIL. haha, love the font and schtick of this usb bootable test. I can't tell if this is both sticks or ram, or one of them: which one? Not that I wouldn't want a pair, but for selling them, I should know. https://www.memtest86.com/troubleshooting.htm looks like I just Chuck em both. Or I’ll sell them as FAIL memory. <shrug> I’m so happy I found a smoking gun. MemTest86-Report-20230408-235658.html

Got this wrapped up, and finished and we're all good. Seems to be back up and running AOK. The backup, format, and restore was a bit stressful. My Plex library had to get rolled back a couple days - I don't remember setting that backup up <shrug> thank goodness it worked out. Ed's video here walked me through those steps. This project is done. I will setup weekly CA Backups V2, and keep an occasional eye on the logs for more errors. Thank you very much @JorgeB !

@couzin2000 hmmm looks like you can specify large Java versions. Third (?) sticky post on this thread talks about Java versions at the binhex documentation here https://github.com/binhex/documentation/blob/master/docker/faq/minecraftserver.md does any of that help? I moved on to Crafty 4 where you can host multiple servers at once, and use any Java version you like. I think. It’s been a year or so since I’ve messed with it.

I didn't see the format option for assigning the xfs/btrfs drive. Found it. Click on the blue "Cache" then you can select the format of the drive. For me I changed it to XFS, hit Apply, Done, Start Array. Format all unmountable disks. Stop array, change format back to btrfs, format it, copy the goods back. My Unassigned Devices drive wasn't coming up default because I had to re MOUNT the drive. Then it came up and I used the following command to get it all back <fingers crossed>: rsync --progress -avzh /mnt/disks/6VM78N1T/cache-drive-thurs/ /mnt/cache/ Takes me about 45 minutes to copy over 7GB of uncompressed files.

Also on this topic, I used rsync to copy the whole cache drive to another unused drive in my system with this command rsync /mnt/user/appdata --progress -avzh /mnt/user/appdata /mnt/disks/6VM78N1T/appdata-thurs/ I think I got rsync from Nerd Tools

Over here I'm troubleshooting this issue. I amazon'ed a CPU and RAM ... and additional cache drive, so I'm going to git'er'dun. You suggest using the additional drive for drive to store the appdata backups? from Backup, via CA Backup, and leave those tar files over there? Sounds good! thank you.

I've ran into an issue of some btrfs file corruption on my primary cache drive, includes appdata. Will installing a second drive as a cache pool help avoid this sort of thing in the future? I'm not concerned with speed, only reliability.

After running for a bit, errors continue. The syslog from GUI Apr 2 14:44:22 rubble kernel: verify_parent_transid: 9 callbacks suppressed Apr 2 14:44:22 rubble kernel: BTRFS error (device nvme0n1p1): parent transid verify failed on 7715749888 wanted 198424 found 214808 Apr 2 14:44:22 rubble kernel: BTRFS error (device nvme0n1p1): parent transid verify failed on 7715749888 wanted 198424 found 214808 Apr 2 14:44:22 rubble kernel: BTRFS error (device nvme0n1p1): parent transid verify failed on 7715749888 wanted 198424 found 214808 Apr 2 14:44:22 rubble kernel: BTRFS error (device nvme0n1p1): parent transid verify failed on 7715749888 wanted 198424 found 214808 Apr 2 14:44:22 rubble kernel: BTRFS error (device nvme0n1p1): parent transid verify failed on 7715749888 wanted 198424 found 214808 Apr 2 14:44:22 rubble kernel: BTRFS error (device nvme0n1p1): parent transid verify failed on 7715749888 wanted 198424 found 214808 Apr 2 14:44:22 rubble kernel: BTRFS error (device nvme0n1p1): parent transid verify failed on 7715749888 wanted 198424 found 214808 Apr 2 14:44:22 rubble kernel: BTRFS error (device nvme0n1p1): parent transid verify failed on 7715749888 wanted 198424 found 214808 Apr 2 14:44:22 rubble kernel: BTRFS error (device nvme0n1p1): parent transid verify failed on 7715749888 wanted 198424 found 214808 Apr 2 14:44:22 rubble kernel: BTRFS error (device nvme0n1p1): parent transid verify failed on 7715749888 wanted 198424 found 214808 no errors reported on BTRFS scrub. I've also heard, from a hardware buddy of mine, that the CPU I use has had issues with poor memory usage allocation error stuff. CPU AMD Ryzen 7 1700 Eight-Core @ 3000 MHz, YD1700BBAEBOX cpu-world details Mobo ASUSTeK COMPUTER INC. ROG STRIX B350-F GAMING, bios updated March 2023. For troubleshooting I've purchased new CPU and RAM that I'll try out next week, one at a time to see if it fixes issues. CPU AMD Ryzen 7 5800X amazon RAM Teamgroup DDR4 2x16GB amazon I hope I (we!) can get this licked.

a while back I did install and have been running a pihole Docker with dedicated static IP. Fox Common Problems popped that up today, so I affected this change here. https://forums.unraid.net/topic/120220-fix-common-problems-more-information/page/2/#comment-1243020 rebooted, rescrubbed. Here is diag. rubble-diagnostics-20230402-0831.zip

@JorgeB Got the server back up. Removed four files that were throwing errors with the btrfs scrub. Now it reads UUID: ddbfaa94-f0d2-4f5c-96cc-2289a26b703d Scrub started: Sat Apr 1 17:33:09 2023 Status: finished Duration: 0:01:19 Total to scrub: 125.89GiB Rate: 1.59GiB/s Error summary: no errors found In my system log it's still throwing loads of this: Apr 1 17:35:39 rubble kernel: BTRFS error (device nvme0n1p1): parent transid verify failed on 7715749888 wanted 198424 found 214808 Apr 1 17:35:39 rubble kernel: BTRFS error (device nvme0n1p1): parent transid verify failed on 7715749888 wanted 198424 found 214808 Apr 1 17:35:39 rubble kernel: BTRFS error (device nvme0n1p1): parent transid verify failed on 7715749888 wanted 198424 found 214808 Apr 1 17:35:39 rubble kernel: BTRFS error (device nvme0n1p1): parent transid verify failed on 7715749888 wanted 198424 found 214808 Apr 1 17:35:39 rubble kernel: BTRFS error (device nvme0n1p1): parent transid verify failed on 7715749888 wanted 198424 found 214808 Apr 1 17:35:39 rubble kernel: BTRFS error (device nvme0n1p1): parent transid verify failed on 7715749888 wanted 198424 found 214808 Apr 1 17:35:39 rubble kernel: BTRFS error (device nvme0n1p1): parent transid verify failed on 7715749888 wanted 198424 found 214808 Apr 1 17:35:39 rubble kernel: BTRFS error (device nvme0n1p1): parent transid verify failed on 7715749888 wanted 198424 found 214808 Apr 1 17:35:39 rubble kernel: BTRFS error (device nvme0n1p1): parent transid verify failed on 7715749888 wanted 198424 found 214808 Apr 1 17:35:39 rubble kernel: BTRFS error (device nvme0n1p1): parent transid verify failed on 7715749888 wanted 198424 found 214808 Apr 1 17:35:54 rubble kernel: verify_parent_transid: 9 callbacks suppressed I'm ready to start replacing stuff. Just need to know what to replace! Hopefully short of building a new machine

I'll do that when it comes back up. I had a hard freeze and crash today.

Got the ram slowed down, problem persists. Still scratchin' my head. Main > cache > scrub btrfs, with "fix errors" checked. Oh, and I pulled two sticks of RAM and left two sticks in slot 2,4 from the CPU. UUID: ddbfaa94-f0d2-4f5c-96cc-2289a26b703d Scrub started: Thu Mar 30 14:41:51 2023 Status: finished Duration: 0:02:48 Total to scrub: 224.02GiB Rate: 1.28GiB/s Error summary: csum=4 Corrected: 0 Uncorrectable: 4 Unverified: 0 System log shows lots and lots of this: Mar 31 01:15:43 rubble kernel: verify_parent_transid: 9 callbacks suppressed Mar 31 01:15:43 rubble kernel: BTRFS error (device nvme0n1p1): parent transid verify failed on 7715749888 wanted 198424 found 214808 Mar 31 01:15:43 rubble kernel: BTRFS error (device nvme0n1p1): parent transid verify failed on 7715749888 wanted 198424 found 214808 Mar 31 01:15:43 rubble kernel: BTRFS error (device nvme0n1p1): parent transid verify failed on 7715749888 wanted 198424 found 214808 Mar 31 01:15:43 rubble kernel: BTRFS error (device nvme0n1p1): parent transid verify failed on 7715749888 wanted 198424 found 214808 Mar 31 01:15:43 rubble kernel: BTRFS error (device nvme0n1p1): parent transid verify failed on 7715749888 wanted 198424 found 214808 Mar 31 01:15:43 rubble kernel: BTRFS error (device nvme0n1p1): parent transid verify failed on 7715749888 wanted 198424 found 214808 Mar 31 01:15:43 rubble kernel: BTRFS error (device nvme0n1p1): parent transid verify failed on 7715749888 wanted 198424 found 214808 Mar 31 01:15:43 rubble kernel: BTRFS error (device nvme0n1p1): parent transid verify failed on 7715749888 wanted 198424 found 214808 Mar 31 01:15:43 rubble kernel: BTRFS error (device nvme0n1p1): parent transid verify failed on 7715749888 wanted 198424 found 214808 Mar 31 01:15:43 rubble kernel: BTRFS error (device nvme0n1p1): parent transid verify failed on 7715749888 wanted 198424 found 214808 rubble-diagnostics-20230331-0115.zip

This Docker that you’re posting on is the Java server. You were on Microsoft before, windows version, that was bedrock. Refer to the sticky posts at the beginning of this thread for the bedrock version. It’s this version. It would probably be easier for you to stick with bedrock. Unless you intend to switch versions, then you should follow different steps. Like these… https://www.reddit.com/r/Minecraft/comments/jo91kw/you_can_convert_a_bedrock_world_to_a_java_world

@Kedryn sounds like “player state” info. When you did the world transfer, did you get ALL the files in there? Previously, we’re you logged into the (now) Microsoft servers? The username will need to be an exact match to what it was before. If you’re having issues, it might be that something small has changed, like Mojang login previously and Microsoft login this time. I’m not specifically aware of which files are player state, but I do recall seeing a bunch of stuff in there with a long text string that I believe was attached to my character. Not positive here on where you issues might be coming from, but that’s what comes to mind as places to check & things to Google.

<face palm> I didn't! I'll do it, do a restart and see we go, and post here. Thanks so much @JorgeB

Made the two changes to bios: Global C-state Control: Disabled Power Supply Idle Control: Typical Current Idle Did a btrfs scrub on the one cache drive I have (nvme0n1p1), rebooted, errors persist. I'll attach a few screen grabs, and a log. Ah here my latest system log https://hastebin.com/share/saleyadehi.yaml Ah yeah, the cache drive has some uncorrectable errors. Perhaps I did that "scrub" incorrectly? I checked the Fix It box, errors persisted. I didn't see any documentation/wiki on this Scrub operation.

rubble-diagnostics-20230322-0708.zip

Looks like I'm getting some BTRFS errors on my nvme0n1p1 https://hastebin.com/share/wifurixani.yaml I saw on another post that bad memory was sometimes a culprit there. I'll do a memtest86 USB boot and see if that turns anything up. Getting an appdata backup done here... SMART test from the ssd https://hastebin.com/share/caleferado.yaml

I seem to remember it being a little more stable for like months at a time. Recently, I'll notice one or two of my dockers aren't responsive. When I go to restart them, they fail and red square, with general error message. Other green running dockers, when restarted will also fail and not come back up after being restarted. I restart the whole server, that seems to sort stuff out. Just hoping a guru out there could take a peek at my diagnostics and we can anticipate a failure before it all comes crashing down. thanks! rubble-diagnostics-20230314-2102.zip

When you first run the Roon client, you are presented with a screen that says "Choose your Roon Core" where it will try and find a running Roon Core on the network, or you can "Set up a Roon Core on this PC" If you've already selected the Set up a Roon Core on this PC, then you can get into the software and start listening to music: BUT that wasn't the right move. As you've set up your Roon Core on the network already, you need to backup the local installation process. Open your Roon Software, go to Settings, then logout. Close the software. Re-run the software and hopefully it'll find your Roon Core on the network. After you hit Connect to core, you'll be presented with the username/password to get authenticated with Roon registration software. You've already started the free trial (I can see that from your screen shot up there).