jmcskis

Thanks, @JorgeB. Looks like things are back up and running.

Right, I knew there were some corrupts, which was part of my reason for swapping out drives. Given the corrupts should I have recreated the pool from the start instead of trying to replace drives? Just to make sure I've got my steps right for recreating the pool: Copied the data I could to the array (I did copy my docker.img but I know it's better to just recreate the .img file) Backed up appdata using CA Backup Disable docker Set all shares to not use cache Run mover From here I'm a bit unclear on the correct steps to follow, but think the process would be: stop the array unassign all pool devices restart the array stop the array set pool slots to 0 (trying to completely remove cache) restart array stop array set pool slots to 2 assign new drives to pool (sdh and sdi) restart the array format new drives to create new btrfs cache pool restore appdata recreate docker.img and restore dockers from templates copy any data back onto cache, as required

That appears to have done the trick. Although I think it's still expecting there should be 3 drives? New diags attached tower-diagnostics-20231216-0847.zip

It seems to be expecting that I have 3 drives in the cache pool even though I never changed from a 2 drive pool. Is this suggesting that it's expecting /dev/sdd (currently unassigned) to be included as a 3rd drive in the pool?

And that gives: sdd is unassigned and one of my old cache drives. sdh is the other new cache drive.

Here's what that gives me:

Looks like it can't find the drives?

I have a 2 drive cache pool and was trying to swap out both drives with new larger drives following this procedure: I missed the last step about stopping and restarting the array if I had replaced with a larger drive after the btrfs replace appeared to complete for the first drive. Instead I stopped the array and repeated the process to swap in the other new device. After I thought the btrfs replace process was complete for the second drive I was getting a "Unmountable: Invalid pool config" error. I stopped the array and swapped the old drive back into the cache pool hoping this would go back to what I thought was a working pool after the first disk swap. This gave me the same error again, so I stopped the array and swapped back to the new drive and restarted the array with the same error. I then rebooted the server and started the array. Now I'm getting an "UNMOUNTABLE: TOO MANY MISSING/MISPLACED DEVICES" error for the cache pool with the 2 new drives installed and I'm being told I need to format the drives. Unfortunately I forgot to grab my diagnostics before rebooting, but have included the diagnostics following the reboot. Is there any way to recover the data from the old cache pool configuration? I ran mover before swapping discs so I think my docker image and appdata should be the only info saved to the cache pool. If I can't recover the old data, what is the correct procedure to get my cache pool back up and running? tower-diagnostics-20231213-1931.zip

Yep. I called things quits right there until I could replace it.

Thanks. After forcing a reboot, I was able to get the parity rebuilt and moved on to replacing data drives. Same thing again, everything froze up partway through, forced a reboot, got the drive replaced fine. Moved on to preclear my next drive and what do you know...things freeze up again. Ok, time to check everything. Did the usual checks of all my connections, ran a check on the flash, etc. After searching a bit more, it seems like my RAM could be at fault so I ran a memtest and oh boy. Given that I'm getting 1000's of errors, I'm guessing that I found my issue... I did pull diagnostics before my server hung up on me the last time. Not sure if there's anything in there that would tell me I have failing RAM. tower-diagnostics-20220216-1250.zip

I'm in the process of increasing the storage in my server. During the parity rebuild after adding the new parity drive, I lost all access to the server. I can't access the web gui, I can't SSH in, and now it's not even showing as connected to my network. I also tried connecting a monitor and keyboard to the server, but all I get is a blank screen and no response. As a result, I'm unable to get the diagnostics or the syslog. The only indication I have that my server is even on is that the CPU and case fans are still running. All HDD activity has stopped (or at least the HDD activity LED has stopped flashing). It seems like my only option is to perform an unclean shutdown, but given this happened during a rebuild I'm terrified that this will just screw things up even more. My system only has a single parity drive. I do have the old parity drive, which I can reinsert if required. Any ideas what may have caused this? Could this be an indication of an issue with my usb drive? What steps can I take to limit data loss from this? Also, I don't know if it matters, but during the rebuild, I was also preclearing a new data drive.

I've got the same issue here, however the /dynamix.plg file doesn't exist on my flash. Based on the above, I'm running the built-in version of the webGUI (now showing as v2016.09.15). I've rebooted my system, but I'm still seeing the same error. How can I revert back to a version that works with 6.1.9 if I don't have the /dynamix.plg file to delete?

Thanks Squid that fixed it. I would still like to know why no templates show up when I go to setup a docker the "official" way.

I keep getting the warnings shown in the attached picture. Warning: simplexml_load_file(): /tmp/plugins/community.applications.plg:1: parser error : Document is empty in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 193 Warning: simplexml_load_file(): in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 193 Warning: simplexml_load_file(): ^ in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 193 Warning: simplexml_load_file(): /tmp/plugins/community.applications.plg:1: parser error : Start tag expected, '<' not found in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 193 Warning: simplexml_load_file(): in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 193 Warning: simplexml_load_file(): ^ in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 193 plugin: xml parse error

I'm trying to setup a Plex docker using the limetech repository, but I run into issues at step one. When I click the drop-down list for the templates, nothing shows up, when I'm expecting to see templates for Plex and Sync. To see if this was just something weird with the Limetech official repository, I added binhex's repository to same effect. Any ideas why no templates are showing up? Based on the docker setup guides I've seen, this isn't normal behavior. Currently I've got a cache pool setup, a 12Gb docker image at /mnt/cache/docker.img, and a docker data share at /mnt/user/appdata set to cache only. Note: I also tried to install Squid's Community Applications plugin, but that gave me different problems.