Kameechewa

Great news! I got it! I ran this command btrfs-select-super -s 1 /dev/sdj1 from here and was able to mount the disk! After mounting I just copied all the folders from it to my new cache pool, rebooted, and bam! Everything loaded up like before and was happy.

I recently built a new server and wanted to move my cache pool of 2 ssds to a new one of 2 NVMes. I first booted the server and started the array with just one of the 2 ssd installed. There was a lot of activity on the disk and I then went to stop the array. It told me there was a btrfs operation in progress and would not let me. So I waited for it to finish. Once finished I stopped the array and followed instructions here. After following these instructions, if I recall correctly, nothing happened. I know that sounds bad, like I wasn't paying attention, but at this point I've tried so many things and what feels like an eternity has passed that I can't remember. So I then stopped the array yet again. I thought ok I'll just go back to the original ssd. When I picked it from the list it told me this device was wrong. I started the array anyways and it tells me it's unmountable. I then tried all the commands here. Which all resulted in the following: mount: /temp: wrong fs type, bad option, bad superblock on /dev/sda1, missing codepage or helper program, or other error. dmesg(1) may have more information after failed mount system call. When running btrfs check --repair /dev/sda1 I get the following: Starting repair. Opening filesystem to check... No valid Btrfs found on /dev/sda1 ERROR: cannot open file system Finally, I ran the command btrfs check -s 1 /dev/sda1 as suggested here and got the following: using SB copy 1, bytenr 67108864 Opening filesystem to check... warning, device 2 is missing Checking filesystem on /dev/sda1 UUID: 6e29690f-b1c4-44e7-82ea-69b91542a53f [1/7] checking root items [2/7] checking extents [3/7] checking free space tree [4/7] checking fs roots [5/7] checking only csums items (without verifying data) [6/7] checking root refs [7/7] checking quota groups skipped (not enabled on this FS) found 79680425984 bytes used, no error found total csum bytes: 37951400 total tree bytes: 188710912 total fs tree bytes: 75956224 total extent tree bytes: 55312384 btree space waste bytes: 37890887 file data blocks allocated: 389775470592 referenced 70950273024 At this point I don't know what else to try. Before send ing this I did reboot the server and try all the commands but there was no change. I do still have both disks but at this point they've both been through the exact same processes. Edit: I have just plugged in both SSDs and tried to mount the only mountable one by clicking mount with Unassigned Devices. I got the following: Feb 3 20:59:04 DuckyServer unassigned.devices: Mount of 'sdi1' failed: 'mount: /mnt/disks/WD-WCC4M0429617: mount(2) system call failed: Structure needs cleaning. dmesg(1) may have more information after failed mount system call. ' Feb 3 20:59:04 DuckyServer unassigned.devices: Partition 'WD-WCC4M0429617' cannot be mounted. AND IN THE LOG [ 665.697291] XFS (sdi1): Corruption detected. Unmount and run xfs_repair [ 665.697653] XFS (sdi1): log has mismatched uuid - can't recover [ 665.697657] XFS (sdi1): empty log check failed [ 665.697658] XFS (sdi1): log mount/recovery failed: error -117 [ 665.697844] XFS (sdi1): log mount failed duckyserver-diagnostics-20230203-2054.zip

Thank you for your reply. Unfortunately I have no idea what these vm_dirty values that you speak of are. I have never heard of them and therefore have likely not modified them. I do have a cache pool made of two 240GB SSDs, WDBAGU2400ANC-WRBB, and most shares are set to use it. The writes are indeed happening on this pool when copying data. I can't honestly say when I first noticed this issue, maybe when going from 6.10 to 6.11? I hadn't done any large transfers for a while before this so I'm not sure.

I am using Unraid 6.11.2. I am transferring files from my MacBook on Ventura, but have also tried in a Win11 VM on my Mac. When I copy a Season to my Plex Share there is unexpected behavior. Let's say each episode is 100MB. When copying the Season folder I will get the expected transfer speed up until 100MB has been copied. The transfer then pauses, 0bps for 3-8 seconds, before continuing again only to pause again after the next 100MB has been transferred. I can copy files successfully but this adds quite a bit of time when copying many files. I have tried turning cache off and on, reconstruct write on and off, ethernet over wireless, copying vs moving, and MacOS and Windows. I even created two dummy files with mkfile 2G testfile1.txt and mkfile 2G testfile2.txt, where it's the same story. Copies the first 2GB just fine and then pauses before copying the second. Then after all files are copied it sits for about 5 seconds and the completes. I have also tried copying to a different share and got the same results. Granted these shares are setup basically the same and use the same cache pool. Granted I don't really know how to begin troubleshooting this nor do I fully understand SMB. But I did observe that during the copy both the servers CPU usage and Memory usage were nothing out of the ordinary.

Thank you so much for explaining everything is in such good detail and answering each of my questions! I really appreciate it. I think I have a pretty good grasp on things now and that video really helped too. You were right, it really was that easy! No errors anymore 🥰

Thank you for replying! Before I do anything I want to understand more of what happened. I see where the image is and it's 21.5 GB, is that the default? I also see that under Shares the system tab is set to prefer cache. When I initially setup Plex I had copied all my Plex Media over the same day, before the mover would have had a chance to run. I also made the mistake of forgetting to set a minimum size on that share and ended up filling up the cache and getting the disk full error. Do you think that has anything to do with it? I just want to make sure I don't do whatever I did beforehand to cause the same issue. I also just don't understand how Docker is setup. There's the image, but what's in it? I thought Plex was under system? Are Plex settings stored in appdata? The biggest thing I'm worried about right now is basically redoing my entire server. Based on what you said, to me it sounds like I'm basically doing that. So stop Docker, delete my image, start Docker, then reinstall Plex and everything under the apps tab? Are those apps stored in that image too or something? I'm confused when you say "Followed by Apps, Previous Apps and check off the apps you were running", what apps, do you mean Plex or do you mean the Apps section for things installed from Community Apps? Then say "It should fix you right up in a matter of seconds". For me I think this will be a lot more than a few seconds. Will I lose my Plex server settings or are those stored in appdata? I just want to make sure I know what needs to be done before I go deleting things. Lastly, does what I have here look ok to you? Is there something here that caused my issue? Should transcode be in cache? Your post in the FAQ said it should not be in the Docker container, is that just the image or is the container something else? If I do that do I need to set a minimum size for system since it's using the cache? I know I'm asking a lot of questions but I know so little I don't even know how to look for answers. I just get caught in a loop of what's this and what's that and then I'm even more confused and have even more questions. I've retyped this about 5 times because I keep reading other posts and then answer my own question but then have 5 more.

I know there's a lot of other posts on this but none seem to match mine. The ones I'm seeing are people saying they're also having issues with their Docker. Mine is only running Plex and Plex is working just fine. I'm very new to all this, as in just started my server like 4 days ago. I really have no idea what Docker even is, I just followed guides on setting up Plex. However, I was reading through the Unraid wiki and under Tips it suggested I install the Fix Common Problems Plugin. It keeps telling me "Docker Image either full or corrupted" but I don't understand. I don't know where I would check to see the size to know if it's full. And since Plex is working I assume it's not corrupt? duckyserver-diagnostics-20220210-1454.zip