jeradc

how do I find that? Anything indicating that in the logs? any tests you suggest?

Stopped array, removed drives from cache pool, set pool drive size to (0). rebooted. started array Ran this command "wipefs -af /dev/sdx" stopped array, created pool, added both devices, started array. cache came up, but drives were unformatted. Selected the box to format, and unraid then set it up as a BTRFS cache pool by default. I enabled a daily balance and a weekly scrub on this pool. Not sure what best practice is. Started docker. moved back my AppData directory. Recreated my "Scratch Space" share, and enabled visibility on it. Reinstalled all my docker containers from "Apps -> Previous Apps" ..... and so far, I think I'm back and functional. This is my 2nd failure on this cache pool in (6) months. First failure this past summer was on a btrfs pool, so when I rebuilt it, I chose ZFS. I guess they both suck. I had no errors for years, before setting it up as a pool for redundancy last year. Wish there was more stability to this system.

I assumed recreating the pool would do that. If you have specific commands for me, that would be appreciated. otherwise.... off to google I go.

copy AppData folder to main array for backup. disable docker reboot with array not started, remove disk 1 and 2 from cache pool, set cache pool # drives to (0). Start array, no cache pool. Shutdown, reboot and run memtest86+, it passes (2) runs: Start unraid, start array, everything is happy. Stop array, add pool, add both drives to pool. Start array...... and we get a Kernel panic / crash in the event log I can't run/download a Diagnostics bundle as it freezes on this line and wont complete: "/usr/sbin/zpool status 2>/dev/null|todos >>'/tower-diagnostics-20240202-1946/system/zfs-info.txt'"

attached tower-diagnostics-20240202-1312.zip

"Docker Service failed to start." Disabled docker, deleted vdisk, start docker.... wont start. Disable docker, reboot, delete vdisk, start docker.... wont start. The system just keeps saying "Array Started..... Starting services" in the corner, and when I click on the docker tab "Docker Service failed to start."

It's a temp folder for several of my docker containers (tdarr, sonarr, etc.). I recreated the share before trying to restart docker, so the apps wouldnt fail.

Setting Docker Enabled -> No, rebooting and running the 'zfs destroy' command was successful. Then, running a scrub was successful. However, the array never finishes coming completely online now after re-enabling docker and obviously docker does not start. There is nothing really in the log for me to go off of, to self trouble-shoot and get docker working again. tower-diagnostics-20240201-1410.zip

when I said "3 hours", I was only referring to the system not giving me feedback on success or failure from the scrub command, and wasn't sure how long a scrub could take. Here is the output:

clicking the scrub button has not changed anything in (3) hours now. Not sure what to do.

I don't know anything about snapshots. I don't know how to check metadata corruption. and I assume I just click this scrub button here?

The system wont fully boot up, I think it's hung bringing up the file shares? Lower left corner of the UI says "Array Starting - Starting Services..." Docker wont start Reading up on the link provided in the log to Openzfs github, I've run the recommend command: I don't care about anything in that folder ("Cache/Scratch Space"), and don't mind blowing it away completely. But... I don't know how to repair the ZFS filesystem to allow Unraid to continue booting and getting docker up again. Any next steps would be appreciated. tower-diagnostics-20240131-0009.zip

I dont understand how that can be true when I have (21) docker containers configured and running right now.... and the config folder is completely empty. I'm assuming the template folder is just a prettified version of a docker compose yaml file or something.

Thank you. re: Docker ------------------------------------- I was hoping to find the location of the docker compose yaml file, or whatever, that is currently storing my docker settings. I do NOT have the templates, but everything is configured and running as before. So somewhere on my server in unraid-land, these docker settings (port mappings, volume mappings, etc.) must be saved. I'll keep looking for it.