• Posts

  • Joined

  • Last visited

  • Days Won


JorgeB last won the day on September 22

JorgeB had the most liked content!


  • Member Title
    On vacation, back in a week or so


  • Gender

Recent Profile Visitors

36283 profile views

JorgeB's Achievements

Grand Master

Grand Master (14/14)




Community Answers

  1. It is if you disable bridging, or just use ipvlan which is usually the best option for most users.
  2. Disk3 appears to be failing, run an extended SMART test to confirm, that should not cause lockups, but this will: Sep 23 11:46:57 Odyssey kernel: macvlan_broadcast+0x10a/0x150 [macvlan] Sep 23 11:46:57 Odyssey kernel: ? _raw_spin_unlock+0x14/0x29 Sep 23 11:46:57 Odyssey kernel: macvlan_process_broadcast+0xbc/0x12f [macvlan] Switching to ipvlan should fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enabled, top right)).
  3. One more thing you can try is to boot the server in safe mode with all docker/VMs disabled, let it run as a basic NAS for a few days, if it still crashes it's likely a hardware problem, if it doesn't start turning on the other services one by one.
  4. If the log spam is fixed use the syslog server and post that log after a crash.
  5. If this started out of the blue it could be a hardware issue, but enable the syslog serve and post that after a crash, also make sure this has been taken care of.
  6. Did you try these ports: PORT="280" PORTSSL="2443" If the issue is with SSL you can also try disabling, change USE_SSL="yes" to "no" (/boot/config/ident.cfg) and reboot.
  7. Those errors suggests a RAID controller was in use before or now, see if those disks mount with the UD plugin
  8. Diags are after rebooting so we can't see what happened but the disks look healthy, so most likely a power/connection problem, check/replace cables and re-sync. That suggests system notifications are disabled.
  9. Cache is full, you can check with btrfgs fi usage -T /mnt/cache du is not always reliable with btrfs (and zfs), you can move some that or can try to defragment, if you don't use snapshots.
  10. LSI was bought by Broadcom, it's the same, and you don't need a new firmware, you can just delete the installed BIOS.
  11. Yes, sorry, missed that, media is read only, so backup what you can, replace the device, create new pool and restore the data, if the current pool is not mounting post new diags.
  12. Btrfs is detecting data corruption and there are several apps segfaulting, start by running memtest.
  13. You have the turbo write plugin installed, and the video shows turbo write enabled, it's faster at the expense of spinning up all disks for writes.