Chandelin

Well that did it. Odd that using the CLI alone did not work the second try. To be sure, this time I used zpool export and the UI as you instructed and it worked on the import. With Docker and scripts not running to be extra sure. It now shows up as expected in Main. Thank you.

You are describing as I did. I'll repeat to be sure and grab diagnostics. After the first fail I did import and status then export. I actually did the same to the mirrored pool and the single drive pool and got all is well replies. The single drive pool is running an older version of zfs I learned, which should not be bad because that pool mounted fine... correct? (Should I update that one?) From what I read around the subject I can't see why one pool mounted and the other didn't. Both have Shares assigned. Actually the one that succeeded has my Docker app data so if Docker was causing issues with the mirrored pool and not it's host drive my mind would be blown. The difference is the failed mount is mirrored. I've got half an hour until the parity finishes. Then it is crunch time. To be clear this screenshot is from after the first failure to mount.

I have two zfs pools. I upgraded one of my array drives by moving the data from it onto the new drive and then removed the smaller drive because of limited case space. I used reset config to remove the gap in the UI lineup. After, my single drive zfs pool came back no issue. My mirrored two drive zfs pool says unmountable wrong or no file system. I used zpool import and status and it showed no issues. I am able to view and access my mirrored zfs pool in Shares with the contents still present. I tried zpool export and then unselected the mirrored pool in Main with the array offline and then started the array to remove it. Then stopped the array and tried to remount it as a pool device. Still the same result. I read on another post that Docker or scripts can interfere with pool mounts because they grab the pool before unRAID can properly mount it. I turned off Docker and scripts to prepare. I have about an hour until my parity check finishes then I want to jump at this issue and correctly mount my mirrored two drive zfs pool. Any suggestions? Where did I go wrong before? diagnostics-20260410-0752.zip

I tried checking the box in Docker settings to delete the directory, but it didn't work. I manually deleted the folder then recreated the identical custom network and the apps are installing correctly now, with their old data intact.

I am discovering. So this is held on RAM then? So I would want at least more RAM than the number I set for the vDisk size? The standard being 20GB so I want more than 20GB in RAM in my system? Thank you for your assistance. Every time I want to change one thing about my system I have to learn three new things to fix the problems that creates.

Image being the BTRFS or XFS vDisk?

This explanation says to delete the Docker vdisk in the Docker settings. The settings only show delete directory as an option. Are these the same thing?

I can confirm that it will let me install apps I do not "have" installed. Anything that should be on my Docker list but isn't showing up gives me these errors.

janus-diagnostics-20251014-1747.zip I tried using Mover Tuner to sync my app data between my array and the cache drive it is kept on. I thought I selected everything in the Mover Tuner correctly, but I did not apparently, because while the settings said it would sync(copy files between the two locations), what it did was simply move all of my docker apps to the array. Yes I had "use Tuner filter" selected. I selected for it to undo it all, and it moved everything back, with broken app links of course. I was manually reinstalling all of the apps and they were working and being recognized. I restarted the server and now my docker page is empty. When I tried to reinstall any apps it gives me this screenshot error or another that states the file already exists so it failed to install. I can see all the correct data and files for my apps in the original cache drive since I moved it back. What do I do to get my Docker apps back and in good order, and is Mover Tuner hard to use or just bugged out?

I started my Unraid journey on 7.0, am on 7.1.4 now and I have a zfs pool that is giving me the option to "Upgrade Pool". As stated before: and with that question, should I be moving my data off this drive before hitting that upgrade pool button?

Hey, you bring up a good question, why does my Unraid say I'm running 6.12.24 when I send "uname -r" if I'm on Unraid 7.1.4? Is this explained somewhere, or am I a dunce? Though both could be true. Also is what you are saying refuting the customer service response of Unraid is a non-LTS kernal?

I am not sure if it will help the community, but this is what I got back from the customer support. Very encouraging, but not a problem solver. I did make note to them that the Amazon posting, which is where I ordered it from, does not say anything about not supporting non-LTS Linux kernels. It says it supports Linux 2.6.32 and up, and that it supports Linux. Nothing about certain version exceptions. "Thank you for reaching out and for providing such detailed information about your setup using the 8P6G-PCIE-SATA-CARD in your Unraid 7.1.4 server. We understand your concern regarding the drive errors when all eight SATA ports are in use. Based on your description—and similar feedback from other users—it’s likely that the issue stems from compatibility with non-LTS Linux kernels. As noted on our product page (https://www.startech.com/en-ca/cards-adapters/8p6g-pcie-sata-card), this card is officially supported only on Linux kernel 2.6.32 and up – LTS versions only. Since Unraid uses a custom Linux kernel, it’s possible that version 7.1.4 is not based on an official LTS release, which could lead to instability when all ports are active. Additionally, this card uses ASMedia ASM1061 controllers with port multipliers, which can sometimes result in bandwidth saturation or drive dropouts under load in certain Linux environments. Recommended Next Steps: Check your kernel version in Unraid using the command uname -r, and compare it against the official LTS kernel list here: https://www.kernel.org/category/releases.html. Limit usage to 6 drives, as you’ve already found this configuration to be stable. Disable IOMMU (VT-d) in your BIOS if it’s currently enabled—this has resolved similar issues for other users. Consider alternative SATA controllers if you plan to expand your server: → ASM1166 chipset based SATA cards (e.g., 6P6G-PCIE-SATA-CARD) → LSI SAS HBAs in IT mode (e.g., LSI 9201-8i or Dell H310) (Note: StarTech.com does not currently offer LSI-based SAS HBAs in IT mode so I provided third party options) Please note that while the card may function with non-LTS kernels, we only provide support for configurations using officially supported LTS versions. If possible, we recommend testing the card in an LTS-based environment to confirm stability."

https://a.co/d/7q9jmzD I called it the wrong brand before.

I rebuilt the drive and added the new parity drive separately. All is well. I have a running theory. I think it is my SATA PCIe card. It is StarTech brand. It works fine, and is intended for up to eight drives at once. I have it on a PCIe 3.0 x8 slot, but the two times I have had all eight drives plugged into it at once, I get two drives with errors. You helped me the last time when two drives disappeared. I shuffled my connections around and put only five connections on the PCIe and it hasn't given me issues or errors since then. Last week I got my new drives and just thought I'd use all eight connections again. Same issue. I emailed the brand support asking if this is a known issue. I'll probably end up getting it traded in or something. I need fully working parts I can trust.

Followed standard procedure for replacing one of my parity drives to a new larger drive. Received disk errors immediately after parity check start on the new parity drive and on one of my array drives. Stopped the parity check and restarted the server. The array drive emulates correctly. I removed the new parity drive since nothing was done on it. The system did not complain about the removal. I still have my remaining parity drive. I have re-seated power cables and replaced SATA cables. My guess is that it will be suggested that it is a bad PSU. I wish PSU's had half a brain and could take responsibility when they are in error, taking the guessing out of it. Is it safe to rebuild the array drive now, then if everything is good try to add the new parity drive again? janus-diagnostics-20251004-1138.zip