BlueSialia

Members
  • Posts

    28
  • Joined

  • Last visited

Recent Profile Visitors

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

BlueSialia's Achievements

Noob

Noob (1/14)

1

Reputation

2

Community Answers

  1. So the root of the issue was obvious and so was the solution as well. The docker and libvirt images where precisely in the disk with the least free space. Literaly less than 1 MB. Moving a couple files from that disk to another fixed everything. I was a little bit afraid of doing that while the data recovery was taking place, but everything went well from what I can tell.
  2. I had 4 disks in my array. One parity drive of 8TB, two 8TB drives and a 2TB drive. I was rapidly approaching max usage on them so I bought a 16TB drive. Replaced the parity drive with the new drive and recalculated parity. Then, because I didn't monitor it properly I reached 100% of usage on my array. So with the recalculated parity finished less than 24 hours ago I replaced the 2TB drive with the 8TB that I was using as parity before. But now, as the replacement drive is being filled with the data from the replaced drive I have the issues of Docker not starting and no VMs showing in the VMs panel. Extra information: I've also replaced a NVIDIA 1060 GPU with a NVIDIA 4070 GPU at the same time I replaced the 2TB drive. And also enabled the option in Docker about keeping user-defined networks. I've been using a user-defined network for months with that disabled without issue (I think) but I enabled it now because I noticed it was a thing. unblue-diagnostics-20231024-2022.zip
  3. Did you figure it out? I just replaced an old and small disk from my array with a larger one and I have the same issue as you. Same libvirt log, just different VMs names, as you would expect.
  4. Recently I've discovered that my server was crashing/freezing because the Ryzen CPU doesn't play nice with Linux's c-states. So I disabled them in the BIOS. Which means my server has a power consumption of 150 watts while idle. My system information: M/B: ASUSTeK COMPUTER INC. ROG STRIX X570-F GAMING Version Rev X.0x - s/n: 190754725200579 BIOS: American Megatrends Inc. Version 4021. Dated: 08/09/2021 CPU: AMD Ryzen 9 3900X 12-Core @ 3800 MHz HVM: Enabled IOMMU: Enabled Cache: 768 KiB, 6 MB, 64 MB Memory: 64 GiB DDR4 (max. installable capacity 128 GiB) Network: bond0: fault-tolerance (active-backup), mtu 1500 Kernel: Linux 5.19.17-Unraid x86_64 OpenSSL: 1.1.1s Attached is my BIOS settings. Any clue of what to do to reduce the power consumption? BIOS_setting.txt
  5. I finally found a solution. But a very undesirable one. The issue was this. My Ryzen CPU doesn't support Unraid's (Linux) c-states. I disabled them in the BIOS. Now, as it is expected, my server has a very high power consumption even at idle.
  6. One year since this started happening to me and the issue is still the same. At some point, the server just dies somehow. The hardware is still on but the system is not even part of the network. And I have no idea about how to debug this problem. I think the only thing I can do is turn off every docker and VM that is not critical, wait and see if it exhibits the same behavior. If by any chance it manages to reach an uptime of a month then I can enable what I turned off slowly. Like one per 2 weeks or something. Even if this works it'll mean months of having most of my things disabled. I'm just hopeless.
  7. I didn't upload the entire file. Just posted the log entries of one of the days the server crashed.
  8. I still face this issue. I replaced the USB, reformated the drives, new settings. I basically setup Unraid from zero again. I cannot get an uptime past 15 days. It ends up crashing. I am now on vacation and I cannot access my Plex or any other services hosted on it because it is down. I connect to my home network with a VPN and can't even ping the server. I have no idea about how to debug this. There is nothing in the syslog server.
  9. I was suspecting that. Specially because of my config change, which makes me think the flash drive may be dying. How would go to try to determine that? It's not possible to run any of the tests that can be executed on a cache or array drive on the flash drive, isn't it?
  10. I'll check the BIOS settings. Although, would it even make sense that this is the cause when I've used the same BIOS settings for years and this crashing has started to happen a month and a half ago? Nope, nothing. At least not while knowing that I was doing so. I actually don't remember changing anything in Unraid for a long while. I have my Plex, my VMs that I start with Wake Up on LAN... I have the Dashboard opened all the time, but just because I like looking at it haha.
  11. So it happened again. It happened on the 12th and this is every log entry from that day: Aug 12 01:01:34 UnBlue emhttpd: read SMART /dev/sdd Aug 12 01:02:23 UnBlue root: /etc/libvirt: 27.6 MiB (28966912 bytes) trimmed on /dev/loop3 Aug 12 01:02:23 UnBlue root: /var/lib/docker: 2.9 GiB (3095732224 bytes) trimmed on /dev/loop2 Aug 12 01:02:23 UnBlue root: /mnt/cache: 242.4 GiB (260238061568 bytes) trimmed on /dev/nvme0n1p1 Aug 12 02:00:01 UnBlue crond[1341]: exit status 1 from user root /usr/local/sbin/mover &> /dev/null Aug 12 02:03:55 UnBlue emhttpd: spinning down /dev/sdd Aug 12 02:40:55 UnBlue emhttpd: read SMART /dev/sdd Aug 12 03:42:45 UnBlue emhttpd: spinning down /dev/sdd Aug 12 17:52:17 UnBlue emhttpd: read SMART /dev/sdd Aug 12 18:52:40 UnBlue emhttpd: spinning down /dev/sdd As far as I know. There is nothing weird there. The next log entry is from today (I was away so I couldn't restart the server earlier). There is one thing that did caught my eye. On restart I have the notification: unassigned.devices.plg: An update is available. Click here to install version 2022.08.12. I can't say it for sure, but I believe every time my server has crashed I've found a pending update for that same plugin.
  12. Things got weird. I don't know why but my VM settings changed. The VM manager tells me my default VM storage path does not exist. It's set to `/mnt/user/domains/` and, in fact, that share does not exist. I used `/mnt/user/vdisks/` (Yup, I got into this because of Linus Tech Tips). Setting it back to vdisks fixes it but the fact that my configuration just changed scares me. I feel like the system is slowly dying.
  13. After noticing the word "diagnostics" turned into an hyperlink I discovered the persistent logs feature of Unraid. Neat trick of the forums! Hopefully that will tell me more next time it happens.