optavia

Members
  • Posts

    5
  • Joined

  • Last visited

optavia's Achievements

Noob

Noob (1/14)

1

Reputation

  1. I moved my VMs off the docker br0 to br1 on a second ethernet port and now no errors.
  2. I'm seeing the same thing here. Keeps filling up /var/log Edit: This was happening a lot more when I had gso off on some interfaces. Nothing has changed. I'm regularly running rm /var/log/syslog && killall -HUP rsyslogd to keep /var/log clean
  3. Here's some more info: /dev/md1 931G 772G 159G 83% /mnt/disk1 /dev/md2 931G 776G 155G 84% /mnt/disk2 /dev/md3 279G 211G 69G 76% /mnt/disk3 /dev/md4 279G 72G 207G 26% /mnt/disk4 root@unraid:~# du -hs /mnt/disk1/* 0 /mnt/disk1/appdata 50G /mnt/disk1/system sdb/disk1 is the one with the problem
  4. I should have mentioned they are on a Perc 6i, so no SMART.
  5. I'm seeing this: /var/log/syslog.2:May 30 00:41:50 unraid kernel: BTRFS: error (device loop2) in btrfs_replay_log:2277: errno=-5 IO failure (Failed to recover log tree) /var/log/syslog.2:May 30 00:42:57 unraid kernel: BTRFS: error (device md1) in btrfs_finish_ordered_io:3069: errno=-5 IO failure /var/log/syslog.2:May 30 00:43:01 unraid kernel: BTRFS: error (device loop2) in btrfs_commit_transaction:2236: errno=-5 IO failure (Error while writing out transaction) The drive is an SSD. The server got unplugged while doing lots of I/O. Logs attached. If it comes down to it, I believe I've got a good backup from a few days prior, but I'd rather try to recover from this than go through that. unraid-diagnostics-20190607-1954.zip