couzin2000

I'M currently running into the exact same issue. Didn't try to reboot yet, but I'm wondering how you guys got to get it back up and running? Right now I'M at 6.12.8, trying to update 2024.03.03.66 to 2024.03.31.76. Any ideas?

I know - but Preferences.xml is not part of the container if I'm not mistaken. It contains GUIDs and real settings for your specific server, and mine. Still not sure how to recup this file.

Check in /config/Plex Media Server. My Preferences.xml is present, but seems empty. Not sure how that could have happened. A permissions error? not sure how to regen the file as I do not have a backup of this (and this is the last time I don't have one).

I had a power outage last night. Power was only restored this morning. I am using a UPS so the system seems to have gracefully shut down. However, after rebooting the unraid server, I amd able to run all my Dockers except for binhex-plex. I've reinstalled the container and image. I seem to be unable to reach the PMS container. I've ran checks on my network and all the proper ports are still opened. Nothing seems out of place. Yet I cannot acces PMS. Anyone have an idea about what this can be?

I have a question about Host Path 2 on the template. this IS presumably where I store the Plex database files, right? I don't mean the edia itself, but all of the save files, the cuesheets where I decide to save where I'm at in a movie, which show ahs played and which hasnt... is that correct? If this is the case, my host path is set to /mnt/user. I'm gussing this is going to the array, or is it going onto the cache drive?

The solution in this post (resetting all data in browser) did not work at all for me. I'm also hoping we can all turn 2 columns back to 3. Somehow the Features video on unraid website shows 3 to 2 to 3 columns, yet I can't make that happen. #Bummed

I just had a chance to skim the surface of your post, but it looks like it would work for sure. I'll test this later today and report back. Thank you!!

The only disadvantage I can see is not being able to boot after a critical failure, therefore having to use the backup from the boot device without seeing what can be at fault in the log. This is why I'd rather have the log be removeable and readable elsewhere.

I kept searching for a few days but I can't seem to find the topic correctly. Currently using Unraid 6.11.5. Running smoothly but I still want to monitor the system log from time to time. However there is very little recorded onto my syslog, as it is only in RAM. I'd like to add a separate USB thumbdrive and point the syslog to record logs to it. I think my main issue here is that I can't create a Pool device out of that thumbdrive and then hotswap it whenever I need to read its contents. Because it's a pool, I keep thinking it will not be readable from my main Win10 workstation. So how do I send the syslog to the USB key so that I can remove it whenever I want and hard-read it from a different PC? I need configuration how-to steps, if they're available. Thank you!

OMG... I've been trying to fix my Unraid server for the last 3 months, and I thought I'd fixed it but all Dockers disappeared... and with this simple link, you solved all this for me! Thank you so much!!!

Well, I tried, but somehow memtest won't load. i'm starting to be very afraid of this. i lost my Docker vDisk last night, no way to find it again, it doesnt seem to exist anymore. so yes, corruption is definitely present. But I can't fix it with memtest right now. I may have no choice but to keep generating more for the moment. so in the meantime, how to I wipe this clean? Can't I just remove the btrfs disk and reformat it to xfs, then start fresh?

I am encountering data corruption on a single-disk btrfs pool. I moved my shares around so that Mover could place all of them on the other pool disk. Now, I am trying to re-enable my Docker containers (Plex, Crafty-4, etc) and Unraid is finding NONE. Only message I get is "No Docker containers defined". When moving with Mover, do I have to change the Docker data-root location? Is it preferable to have it as a folder or a Vdisk? I tried changing this setting to locate on the Vdisk where my files currently reside.... yet nothing. Please help!!

So I read this: Because I was trying to move an UNUSED hass VM. When I set it up to move it from my "Cache" pool to my array, this is what I got: Oct 21 00:50:58 sebunraid1 root: mover: started Oct 21 00:50:58 sebunraid1 move: file: /mnt/cache/downloads/vmstorage/haos_ova-10.0.qcow2 Oct 21 00:51:00 sebunraid1 kernel: BTRFS warning (device sdh1): csum failed root 5 ino 789 off 3631906816 csum 0x7983a069 expected csum 0x7983a061 mirror 1 Oct 21 00:51:00 sebunraid1 kernel: BTRFS error (device sdh1): bdev /dev/sdh1 errs: wr 0, rd 0, flush 0, corrupt 479, gen 0 Oct 21 00:51:00 sebunraid1 kernel: BTRFS warning (device sdh1): csum failed root 5 ino 789 off 3631906816 csum 0x7983a069 expected csum 0x7983a061 mirror 1 Oct 21 00:51:00 sebunraid1 kernel: BTRFS error (device sdh1): bdev /dev/sdh1 errs: wr 0, rd 0, flush 0, corrupt 480, gen 0 Oct 21 00:51:00 sebunraid1 kernel: BTRFS warning (device sdh1): csum failed root 5 ino 789 off 3631906816 csum 0x7983a069 expected csum 0x7983a061 mirror 1 Oct 21 00:51:00 sebunraid1 kernel: BTRFS error (device sdh1): bdev /dev/sdh1 errs: wr 0, rd 0, flush 0, corrupt 481, gen 0 Oct 21 00:51:00 sebunraid1 shfs: copy_file: /mnt/cache/downloads/vmstorage/haos_ova-10.0.qcow2 /mnt/disk7/downloads/vmstorage/haos_ova-10.0.qcow2.partial (5) Input/output error Oct 21 00:51:00 sebunraid1 kernel: BTRFS warning (device sdh1): csum failed root 5 ino 789 off 3631906816 csum 0x7983a069 expected csum 0x7983a061 mirror 1 Oct 21 00:51:00 sebunraid1 kernel: BTRFS error (device sdh1): bdev /dev/sdh1 errs: wr 0, rd 0, flush 0, corrupt 482, gen 0 Oct 21 00:51:01 sebunraid1 move: move_object: /mnt/cache/downloads/vmstorage/haos_ova-10.0.qcow2 Input/output error Oct 21 00:51:01 sebunraid1 kernel: XFS (sdi1): Metadata corruption detected at xfs_dinode_verify+0xa0/0x732 [xfs], inode 0x41ba27f dinode Oct 21 00:51:01 sebunraid1 kernel: XFS (sdi1): Unmount and run xfs_repair Oct 21 00:51:01 sebunraid1 kernel: XFS (sdi1): First 128 bytes of corrupted metadata buffer: Oct 21 00:51:01 sebunraid1 kernel: 00000000: 49 4e 41 ff 03 01 00 00 00 00 00 63 00 00 00 64 INA........c...d Oct 21 00:51:01 sebunraid1 kernel: 00000010: 00 00 00 03 00 00 00 00 00 00 00 00 00 00 00 00 ................ Oct 21 00:51:01 sebunraid1 kernel: 00000020: 35 27 21 3c 8b c9 b9 db 35 27 21 3c 8b c9 b9 db 5'!<....5'!<.... Oct 21 00:51:01 sebunraid1 kernel: 00000030: 35 27 21 3c 8b c9 b9 db 00 00 00 00 00 00 00 16 5'!<............ Oct 21 00:51:01 sebunraid1 kernel: 00000040: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ Oct 21 00:51:01 sebunraid1 kernel: 00000050: 00 00 00 02 00 00 00 00 00 00 00 00 40 f5 24 e0 ............@.$. Oct 21 00:51:01 sebunraid1 kernel: 00000060: ff ff ff ff 90 cc 1a ae 00 00 00 00 00 00 00 04 ................ Oct 21 00:51:01 sebunraid1 kernel: 00000070: 00 00 00 71 00 01 44 9e 00 00 00 00 00 00 00 08 ...q..D......... Oct 21 00:51:01 sebunraid1 kernel: XFS (sdi1): Metadata corruption detected at xfs_dinode_verify+0xa0/0x732 [xfs], inode 0x41ba27f dinode Oct 21 00:51:01 sebunraid1 kernel: XFS (sdi1): Unmount and run xfs_repair Oct 21 00:51:01 sebunraid1 kernel: XFS (sdi1): First 128 bytes of corrupted metadata buffer: Oct 21 00:51:01 sebunraid1 kernel: 00000000: 49 4e 41 ff 03 01 00 00 00 00 00 63 00 00 00 64 INA........c...d Oct 21 00:51:01 sebunraid1 kernel: 00000010: 00 00 00 03 00 00 00 00 00 00 00 00 00 00 00 00 ................ Oct 21 00:51:01 sebunraid1 kernel: 00000020: 35 27 21 3c 8b c9 b9 db 35 27 21 3c 8b c9 b9 db 5'!<....5'!<.... Oct 21 00:51:01 sebunraid1 kernel: 00000030: 35 27 21 3c 8b c9 b9 db 00 00 00 00 00 00 00 16 5'!<............ Oct 21 00:51:01 sebunraid1 kernel: 00000040: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ Oct 21 00:51:01 sebunraid1 kernel: 00000050: 00 00 00 02 00 00 00 00 00 00 00 00 40 f5 24 e0 ............@.$. Oct 21 00:51:01 sebunraid1 kernel: 00000060: ff ff ff ff 90 cc 1a ae 00 00 00 00 00 00 00 04 ................ Oct 21 00:51:01 sebunraid1 kernel: 00000070: 00 00 00 71 00 01 44 9e 00 00 00 00 00 00 00 08 ...q..D......... Oct 21 00:51:01 sebunraid1 root: find: '/mnt/docker/appdata/binhex-plex/Plex Media Server/Media/localhost/9/bb2e252632253f6ce86cf38df9c8762e9c23acd.bundle': Structure needs cleaning Oct 21 00:51:01 sebunraid1 kernel: XFS (sdi1): Metadata corruption detected at xfs_dinode_verify+0xa0/0x732 [xfs], inode 0x41ba27f dinode Oct 21 00:51:01 sebunraid1 kernel: XFS (sdi1): Unmount and run xfs_repair Oct 21 00:51:01 sebunraid1 kernel: XFS (sdi1): First 128 bytes of corrupted metadata buffer: Oct 21 00:51:01 sebunraid1 kernel: 00000000: 49 4e 41 ff 03 01 00 00 00 00 00 63 00 00 00 64 INA........c...d Oct 21 00:51:01 sebunraid1 kernel: 00000010: 00 00 00 03 00 00 00 00 00 00 00 00 00 00 00 00 ................ Oct 21 00:51:01 sebunraid1 kernel: 00000020: 35 27 21 3c 8b c9 b9 db 35 27 21 3c 8b c9 b9 db 5'!<....5'!<.... Oct 21 00:51:01 sebunraid1 kernel: 00000030: 35 27 21 3c 8b c9 b9 db 00 00 00 00 00 00 00 16 5'!<............ Oct 21 00:51:01 sebunraid1 kernel: 00000040: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ Oct 21 00:51:01 sebunraid1 kernel: 00000050: 00 00 00 02 00 00 00 00 00 00 00 00 40 f5 24 e0 ............@.$. Oct 21 00:51:01 sebunraid1 kernel: 00000060: ff ff ff ff 90 cc 1a ae 00 00 00 00 00 00 00 04 ................ Oct 21 00:51:01 sebunraid1 kernel: 00000070: 00 00 00 71 00 01 44 9e 00 00 00 00 00 00 00 08 ...q..D......... Oct 21 00:51:01 sebunraid1 move: error: move, 392: Structure needs cleaning (117): lstat: /mnt/docker/appdata/binhex-plex/Plex Media Server/Media/localhost/9/bb2e252632253f6ce86cf38df9c8762e9c23acd.bundle Oct 21 00:51:01 sebunraid1 root: mover: finished Why?? How can I fix this BTRFS error? If I remove the drive altogether (which is what I'm trying to do), will this mess up everything?

Never mind, I figured it out. Turns out, I have 2 cache pools: Cache and Docker. In the file example from above, I am trying to move /appdata/binhex-plex/ files. Those are located in the appdata share, and that is located in Docker pool. However, the share was set to "Use cache pool = Yes", BUT ALSO "select cache pool = Cache". After changing this to "select cache pool = Docker", Mover started moving the files. 😁

Running 6.11.5. I'm trying to use Mover to transfer all my files contained in appdata, domains, system and media shares from my Cache pool over to the array. I set all these shares to "use cache pool = Yes", disabled Docker and VMs, and I'm now running Mover. Mover gives me this when I check the log: Oct 20 22:41:00 sebunraid1 move: file: /mnt/docker/appdata/binhex-plex/Plex Media Server/Media/localhost/c/89e0b69a965e19b208c7765449e3687820dd2e6.bundle/Contents/GoP-1.xml Oct 20 22:41:00 sebunraid1 move: move_object: /mnt/docker/appdata/binhex-plex/Plex Media Server/Media/localhost/c/89e0b69a965e19b208c7765449e3687820dd2e6.bundle/Contents/GoP-1.xml File exists And this is for a SLEW of cached files - syslog can't keep up. What I understand from other posts is these files aren't being moved? What is wrong in this scenario? Anything I can do to set it up to work properly?

I've been reading this post. It's helpful some ways for me, but I'm trying to simply transfer my Docker images and containers stored on one pool to another - in the same machine. So can I simply shut down Docker, copy all files from one cache pool to the other, then instruct Docker to check the images in the new pool volume and run Docker again? Will this all work? is there a specific setting for copying the files, such as "cp -r -p" ?

I'm not sure how to go about fixing things here, so I'll explain what happened and you can help me solve this. I initially installed 2 SSDs as "cache" drives. I configured the cache so that both drives were codependent as BTRFS formats. But there were issues, BTRFS wasn't very reliable at the beginning, there were some write errors, and I was also very unfamiliar with this sort of setup. So when error messages started to show, I reacted oddly and I removed one of the drives from the BTRFS codependant scenario. Instead, I created a new pool called Docker, and installed the removed drive into this pool as an XFS format. The remaining drive in Cache was untouched. I basically assigned appdata to go to Docker, rather than leave it as it was. In my mind, this was all logical - using Cache for cacheing, and using Docker for all things Docker-related. Forward a year, and now I run into issues with a Minecraft server manager Docker app (Crafty-4). I'm running into error message saying that certain files have to be written to BTRFS but the folders are read-only. This is not part of my intended setup. I recently installed "Fix Common Problems". Here are the two errors I get which are related to this and which I'm not sure how to address: -Unable to write to Docker Image -- Docker image either full or corrupted. Investigate Here: [DOCKER SETTINGS] -Share appdata set to use pool Docker, but files / folders exist on the cache pool. Not sure how to address the first because at the Docker page, my BTRFS scrub error summary says "no errors found". The drive is far from full. Not sure where to go from here. For the second, I *am* willing to correct the issue but I want to make sure I have copies of everything first. I'm not sure how to go about and create a backup of all this. sebunraid1-diagnostics-20230909-2330.zip There. If anyone is up for it, please sound off here and let me know how I could proceed.

I hadn't had time to follow the instructions in the link. I went today to do it. As I'm following the first post's steps, I realize I'm reading a 2017 post. The options are not the same anymore. I went and ran the "Scrub" option in Docker. Didn't find any errors. However, I cam back to the man screen and saw my docker images all good and running, and I was able to delete the orphaned image that was still there. No corrections needed to the Docker.img file. Thanks anyway! (please pin the new version of these instructions, could be very useful)

Edit: I tried Scrub in the Docker tools. I get this in the syslog: Jun 12 Jun 12 16:40:54 sebunraid1 ool www[27058]: /usr/local/emhttp/plugins/dynamix/scripts/btrfs_scrub 'start' '/var/lib/docker' '-r' Jun 12 16:40:54 sebunraid1 kernel: BTRFS info (device loop2: state EA): scrub: started on devid 1 Jun 12 16:40:54 sebunraid1 kernel: BTRFS info (device loop2: state EA): scrub: not finished on devid 1 with status: -30

Before I jump in and recreate the Docker.img (I didn't understand we were referring to the actual Docker program's image, sorry), I'd like to ask if there is something underlying that I need to address. I wouldn't want to blast the image and recreate it only to end up with the same problem. Does this imply I must put the array offline? Is there an easy guide I can follow? As said prior, I am fairly uneducated when it comes to Unraid, I havent had it long, so I need some step-by-step guidance.

Can you be a little more precise with me? I don't wanna mess up anything here, i' kind of a noob at Unraid. you're talking about the "Crafty-4" Docker image that needs to be recreated? Or THE DOCKER image, i.e. the actual Docker program? if we're talking about Crafty, i'm not sure how to remove it because that is a part of the error I've been getting - during updating this app, the older Crafty container refused to remove itself, and the newer one was downloaded, ready to go. The old one still doesnt delete itslef vecause somehow the BTRFS is in read-only mode (which has never been the case, and I'm actually writing this image on an XFS drive) so the new one can't run a new container... And as for the scrub you're referring to, what exactly is this? A clean up how?

I'm finding a few things in here, I'm wondering if this suggests the failure of my SSD: Jun 8 08:32:03 sebunraid1 kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT4._GTF due to previous error (AE_NOT_FOUND) (20220331/psparse-529) Jun 8 08:32:03 sebunraid1 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT3._GTF.DSSP], AE_NOT_FOUND (20220331/psargs-330) Jun 8 08:32:03 sebunraid1 kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT3._GTF due to previous error (AE_NOT_FOUND) (20220331/psparse-529) Jun 8 08:32:07 sebunraid1 mcelog: failed to prefill DIMM database from DMI data Jun 8 08:33:06 sebunraid1 kernel: BTRFS error (device loop2): error loading props for ino 11884 (root 314): -5 Jun 8 08:33:47 sebunraid1 kernel: BTRFS error (device loop2): parent transid verify failed on 285835264 wanted 6628 found 6564 Jun 8 08:33:47 sebunraid1 kernel: BTRFS info (device loop2): failed to delete reference to python3.10.xpm, inode 11884 parent 3189 Jun 8 08:33:47 sebunraid1 kernel: BTRFS: error (device loop2: state A) in __btrfs_unlink_inode:4325: errno=-5 IO failure

I am having this same exact issue after having run a few updates to Docker images. I updated Unassigned devices, Recycle Bin, then I ran Dynamix File Manager. After Dynamix having updated correctly, I went in to update "Crafty-4" Docker package. The update is supposed to delete the current container and replace it with the new one... in this case, it refused to delete the original becaise somehow the "filesystem is now read-only"? It also says BTRFS, but the file it's pointing at is on an XFS format. Not sure what's going on here. I have also enclosed my diag file. As of right now, I cannot use any of my Minecraft servers (Crafty is the server manager) and it's stuck in "Removal in progress" status. The new image is currently "oprhan image" and I can't do anything with it. The update does not want to remove the older one. I can certainly run memtest, but I'd like to know HOW to change the drive's current state to one I can use. Should I copy files from my cache drives over to the array, and flush the SSD cache drive and start that whole process again? Please keep in mind I am running a Plex server and I want to make sure I don't have to start everything from scratch again. Thanks. sebunraid1-diagnostics-20230610-1459.zip

I am asking for the entire community, as I see that there isn't an actual post with these instructions listed. I've installed your driver and am using with a Docker package as a transcoder. When I recieve a notification about a new Nvidia driver plugin version, how do I update the package? I've already installed the plugin following the instructions contained here: https://www.youtube.com/watch?v=VkC5Hi-rO2c&t=1s If I simply click on "Update" in the package, is it supposed to work right out the box once the driver plugin has been updated?

OH MY GAWD you've just opened Pandora's box for me. Did nott know Crafty existed. This is a game-changer for me. Thank you, I have no sufficient words to express my gratitude.