jeradc

Members
  • Posts

    37
  • Joined

  • Last visited

Everything posted by jeradc

  1. 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.
  2. 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.
  3. 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'"
  4. "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."
  5. 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.
  6. 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
  7. 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:
  8. clicking the scrub button has not changed anything in (3) hours now. Not sure what to do.
  9. 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?
  10. 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
  11. 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.
  12. 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.
  13. Setting Export to yes, enabled the shares to be remotely accessible. That issue is resolved. I'm not able to manage the files from the GUI though, like I used to. I thought that was native behavior, and not a plugin. Previously I was able to choose the files/folders, and then take actions that were listed across the bottom (or all the way on the right had side via a drop down. Still no progress on finding the docker settings....
  14. 1) I guess since I don't know what a share export is.... they are not. 2) I don't have a backup. Is there a way to access their current configuration for me to manually write down their settings before I reinstall? Everything is running correctly, but remembering each share, port, etc. is impossible. Maybe in a super.dat file I've read a bit about? Thanks.
  15. I assume the downstream port on your networking device supports > 1 G connection?
  16. Hey folks - I've rebuilt my server on 6.12.6 using the config folder and syslog information from a diagnostics zip that I had from a month ago, onto a new USB key with a new License. I promise to back it up from now on. But (2) things are still problematic: I can no longer edit my docker containers. My SMB shares are no longer viewable from my Window desktop, are not editable when I browse them from the GUI, and show nothing under the SMB column when viewing the Share Tab. Any suggestions for getting either of these back to "normal"? Thanks!
  17. I only read the release notes, the new FAQ, and the github repo. I didn't read the notes on the (3) realtek drivers in Community Apps.
  18. Tools -> System shows my onboard motherboard NIC driver as "Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller" Fix Common Problems says "Realtek R8168 NIC found". But nothing I'm reading says anything about 8411. So... do I install the 8111/8168 drivers, or not? Thanks!
  19. Is it? darn, I knew to look out for that issue, but I guess I didnt know what to look for in the syslog. I can make that change.
  20. Upgraded yesterday (09/01/23) from a 6.11.x with no issues. Deleted and rebuilt my docker image, to recover 10 GB of space. Beyond that, haven't really done anything else with the system. So far, just the single crash today (09/02, around 6 pm) , but I'm not sure how to interpret the syslog, or if there is anything I should do / be concerned about. Syslog, to me, actually shows 3-4 different errors happening this afternoon. Dunno. FYI. syslog tower-diagnostics-20230902-1904.zip
  21. I re-setup everything 3 days ago, and my user and Org's are gone.... again for like the 3rd time. What is going on. The logs are just full of "authorization not found" (of course, because the user is gone). Why do I keep losing everything here.
  22. I literally have about 50 tabs open, but this was probably the one that I ended up following: https://tfahl.com/2017/08/04/graphing_snmp_data_with_prometheus_and_grafana.html Thanks to him and you, I have both Prometheus and the Prometheus SNMP exporter running in (separate) containers, talking to each other, collecting data..... and I've produced graphs in Grafana, also in a separate container. So, success! Thanks GilbN!