December 3, 20214 yr Author I ran the xfs_repair command sans arguments and it completed quickly. ***** Check Filesystem Status xfs_repair status: Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... - scan filesystem freespace and inode maps... Metadata CRC error detected at 0x43cfad, xfs_bnobt block 0x2ffffffd8/0x1000 btree block 6/1 is suspect, error -74 bad magic # 0 in btbno block 6/1 Metadata CRC error detected at 0x43cfad, xfs_bnobt block 0x27fffffe0/0x1000 btree block 5/1 is suspect, error -74 bad magic # 0 in btbno block 5/1 . . . resetting inode 7018382593 nlinks from 14 to 8 resetting inode 72238548 nlinks from 6 to 4 resetting inode 7018382623 nlinks from 17 to 11 resetting inode 72238576 nlinks from 11 to 6 done ***** After running the command I received the message that Disk 11 has returned to normal utilization level. Disk 11 now shows more free data than before but I can view folders and files there. There is a lost+found folder now but I can view files under the TV Shows folder. I confirmed in Windows that I can now view files in the TV Shows share. I have plenty of content in the lost+found directory but no big worries. I have the original drives I replaced and may try to recover some data from them. I don't have any dockers installed even though I can see the folders and files in my cache drive at /mnt/cache/appdata I will proceed to reinstall those. I'm attaching the latest diagnostics logs for reference. Thanks all for your help. I really appreciate it. tower-diagnostics-20211202-2310.zip
December 3, 20214 yr Community Expert 10 hours ago, Dradder1 said: reinstall those. Be sure to use the Previous Apps feature on the Apps page.
December 3, 20214 yr Author Instead of using the Previous Apps feature I reinstalled the same linuxserver Plex docker from the Apps page. I had it point to my media shares. Installation is fine and the docker is started per the GUI. When I go to launch the docker it is unable to connect. I then checked the cache appdata folder and see a Plex folder there with an older timestamp. Do I need to remove this old plex folder from the cache drive then try to reinstall? If so is Krusader a viable option to do so via GUI? Attaching latest diagnostics. tower-diagnostics-20211203-1007.zip Thanks,
December 3, 20214 yr Author It appears that my Plex instance on Unraid is running. I simply cannot reach the WebUI directly from the docker page. I have an older system with another Plex instance that I booted up. I saw my Plex shares available on my Unraid system and am able to view the media. I tried to launch from a different browser on the same system and received the following message: When I view the docker logs this is what I see? Is this more a docker-provider issues versus Unraid? If so I can go that path. Thanks
December 3, 20214 yr Community Expert You may have to start over with your plex docker (delete its appdata) since you didn't use Previous Apps though it should have worked if you had set it up exactly as you had it before.
December 7, 20214 yr Author I deleted the appdata folder and restarted my server. I reinstalled the plex docker and set all media paths (I appended a V2 to the plex path make sure no old data was being used) When trying to launch I still get the XML error. Docker logs after launch. Looking at other posts on this forum for similar issues I found a suggestion to add '/manage' to the end of the plex docker URL to gain access. My URL looks like this: http://x.x.x.x:32400/manage and it did load. I was then able to create the Plex instance/server name and it's started adding libraries. I could access my media that has been scanned so far from a client system via a test stream. I then tried to relaunch the Plex docker and after going through the initial setup/configuration it did load. No tricks needed. Thought I was almost done. I was in the Plex GUI, not Unraid, and set transcode to use RAM in settings. Another step closer to being finished... When I was streaming from my backup Plex instance I noticed the new server shares showed offline. The Plex Server was offline. I checked logs and see BTRFS serrors. I tried to restart the docker and it failed. This is the message I got. Looking at other similar posts on the forum seems to indicate bad memory. I will attempt to run a memtest to see the results. Attaching latest diagnostics after running into these last issues. Thanks tower-diagnostics-20211206-2023.zip Edited December 7, 20214 yr by Dradder1 Adding specific configuration done before issues reappeared.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.