lovingHDTV

Members
  • Posts

    603
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

lovingHDTV's Achievements

Enthusiast

Enthusiast (6/14)

4

Reputation

  1. I've two containers that have shown No Available for a couple weeks now. Both are available when I go to the docker page. One is the official ESPHome: https://hub.docker.com/r/esphome/esphome The other is my own here: ghcr.io/dpeart/heatmaster:main How do I figure out why? I know that ESPHome has been updated and I need the update. Not as concerned about mine as I've not changed it. thanks david
  2. guess I'll order a new usb. I bought a 256GB one and apparently UnRaid is limited to 32GB.
  3. as in I should replace my flash? I bought a new one a while ago with the intent to swap it out, just haven't figured out how to do it now that it is automated. I guess it is time to figure that out.
  4. I saw this in the sylog I attached. This is the syslog from before the hang/reboot. Dec 19 02:42:34 tower emhttpd: Unregistered - flash device error (ENOFLASH7) Dec 19 02:42:34 tower emhttpd: error: device_read_smart, 8372: Cannot allocate memory (12): device_spinup: stream did not open: sdj Dec 19 02:42:34 tower emhttpd: error: device_read_smart, 8372: Cannot allocate memory (12): device_spinup: stream did not open: sdk Dec 19 02:42:34 tower emhttpd: error: device_read_smart, 8372: Cannot allocate memory (12): device_spinup: stream did not open: sdh
  5. This AM the server was unresponsive. I could ping it, but could not log in. Even when trying to log in via the console, it would accept the user name, then just return to the login prompt. I had a bunch of messages on the console that said something about monitor_nchan had issues with local resources. I had to hard reboot it, ugh, it is back up. Attached are the diagnostics. I looks like there are some drive errors, like for all the drives. Any help appreciated. I had the syslog server going so here is the syslog. thanks tower-diagnostics-20221219-0623.zip syslog-192.168.1.107.log
  6. OK, moved to ipvlan. Hopefully this resolves the random system hangs, and BTRFS issues. thanks for your help
  7. I recreated the docker.img and it reports no errors. However the container that was marked as unhealthy is still marked unhealthy. Here is the new diagnostics. I did move the docker.img from cache_hdd to cache_nvme. Wow the performance gain is crazy. Is the change to ipvlan a simple change in the docker settings or do I have to do something additional? I manually set all my container IPs. thanks david tower-diagnostics-20221213-0721.zip
  8. Ran scrub on the docker.img and it has 4 unrecoverable errors. I guess it is time to create a new docker img.
  9. I am still getting BTRFS issues. Last night I noticed the new cache pool had issues. I had also seen some CRC issues earlier. In the past when I saw CRC errors it was caused by power issues. I also noticed that several dockers had stopped, as the cache_hdd pool has all the dockers and it was set read only by the BTRFS errors. The array stopped, but I couldn't shutdown because one of the dockers, even though docker had shutdown, was still running. So I had to hard shutdown. I moved the two newly added cache_hdd drives to sata ports on the motherboard and off the SAS port. I also put them on their own power connection. This AM, I see that there are BTRFS errors on loop2, which is now read only, and dockers are screwed up. The errors are not on the cache_hdd devices, just loop2. I also see that two dockers are marked as unhealthy. I did notice that one was marked unhealthy yesterday. I'm beginning to think that docker.img is screwed up? Here are the diags.tower-diagnostics-20221213-0616.zip
  10. I had a bit of time, so I decided to try upgrading again. For whatever reason it is working just fine now.
  11. I didn't try that. I did notice that on 6.11.1 it has the same mac address, which isn't the original one. I have my router setup to static DHCP the IP. I think this has been an issue for a while, because I had to statically apply the IP within RunRaid a while ago tp get a consistent IP.
  12. Just upgraded from 6.11.1 and lost connectivity to the internet. I can access UnRaid, but on a terminal I cannot ping outside the local network. I got my first notification of this when fix common problems reported github was unreachable. Not sure if this matters, but the mac address changed. And I didn't move the network cable. reverting back to 6.11.1 fixed the networking issue. tower-diagnostics-20221210-1950.zip
  13. I use tiny media manager. There is a doctor for it Sent from my SM-A536U1 using Tapatalk
  14. When I run docker build, it created temporary images, then reports that it deletes them. However, when I look at the docker in the UI I see the images, and have to remove them manually. When I do I get three different results. 1. it removes 2. I get a message saying it cannot remove becuase it is used by another image, then it removes it anyway 3. I get a message the image doesn't exist. I know that when I build dockers using the UI, none of the happens. What do I need to do , for my manual docker builds to make them clean? thanks
  15. I was able to get things back up and running. There were a few files I couldn't copy off the corrupted drive, fortunately they were debug logs. I then replace the drive with two 4TB drives and created a cache pool, managed to get all my dockers setup using the new cache pool and everything is up and running. The good news is that I was meaning to fix all this, as my setup is based on UnRaid prior to cache pools. So now everything should work better. thanks