ehcorn

tower-diagnostics-20220105-2145.zip pulled the drive and made a backup of all the files at least, checkdisk didn't show anything bad and on a new boot I was able to pull the logs. Never posted these before so I hope this is right. update: I deleted all docker containers again and started from scratch this time, my problem appears to be resplved but if someone with more knowledge than me feels like looking at the logs for anything abnormal that would be appreciated. update2: I can reproduce the error by firing up Machinaris an setting it to plot, when I do the web UI goes completely bonkers and the system more or less stops responding until reboot, even if I shut down the Machinaris docker. I'm now getting a specific error: Warning: file_pib_contents():Only -1 of XXX (the number of bytes changes) written, possible out of free disk space in /user/local/emhttp/plugins/unassigned.devices/include/lib.php on line 75 Final update and solution (so far): Machinaris is mapped to plot using a ramdisk, this script was interrupted when I switched my cache for some reason so /mnt/ram didn't exist, and the docker container dumped the files to who knows where, causing something that wasn't big enough for the files to fill up nearly instantly. So this is all related to some core directory of the unraid install running out of space and that caused the issues.

I can't. when I try to download the logs, it just sits at download... /boot/logs

I don't really know where to start with this, so I've got a screenshot of what I see, the errors I get from unraid are literally "undefined error" showing in red from time to time. this is right after a cache drive replacement, I tried to follow spaceinvader one's instructions online of set the shares to "no", the I used appdatabackup to take a full docker backup, and then shutdown once everthing seemed fine, then swap the drives. That's when I noticed a few of my dockers were missing. I tried nuking all my docker containers, deleting my docker image and re-installing everything from the CA store and initially it looked fine but I've got the same error now. oddly enough if I go to the docker page, it says my array must be started for docker to work... even though containers are clearly running and I can interact with them in between weird errors. I've now tried to go back into settings to disable docker, but I can't for some reason. I don't get any errors, the buttons appear normal just when I click apply nothing happens. my gut feeling is my boot USB is fried as there are errors across my whole install and settings aren't saving on anything I try. edit: It seems I can't download diagnostics either, before anyone else asks.

I'm posting a problem and solution, I found this exact error in a few other places but not here: /usr/bin/perl: /lib64/libc.so.6: version `GLIBC_2.33' not found (required by /usr/lib64/perl5/CORE/libperl.so) is what I get when I try running any znapzend command, to fix this I had to install the nerd pack then enable perl. Maybe obvious to others but it took me a bit to figure out.

currently running version 6.9.2 2021-04-07, is that new enough? edit: update to my situation with the port being taken already and other files not being found in plotman, etc. I've wiped it and started from scratch and made sure to drop some plots in the drives, all seems to work best when I leave well enough alone. Once I go into the shell and start running things manually stuff breaks... big surprise. So once I remove the foot from my mouth I'm sure everything shall be fine! The original problem, after some more reading, appears to be rooted in the chia dust storms

excellent suggestion, seems to help but with some caveats. I can run the console, chia seems to be syncing correctly but plotman won't start properly. If I try from the console it tells me that "chia_plot" can't be found and in the UI my buttons to start plotting or farming aren't showing up so farming stays offline... even though it's clearly syncing the blockchain.

I get an error "OSError: [Errno 98] error while attempting to bind on address ('::', 8444, 0, 0): address already in use" this results in my chia farm not starting properly and can't sync at the start. I have no idea where to start here and I've been trying to trim my config down and get it as close as possible to stock but it's still throwing this error.

I'm having an issue with container size, for some reason this container is 1.5gb and growing. Has this happened to anyone else?