JorgeB

Moderators
  • Posts

    60386
  • Joined

  • Last visited

  • Days Won

    630

JorgeB last won the day on March 25

JorgeB had the most liked content!

Retained

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

Converted

  • Gender
    Male

Recent Profile Visitors

43876 profile views

JorgeB's Achievements

Grand Master

Grand Master (14/14)

7.4k

Reputation

3.1k

Community Answers

  1. Mar 29 10:06:31 Tower kernel: macvlan_broadcast+0x10a/0x150 [macvlan] Mar 29 10:06:31 Tower kernel: ? _raw_spin_unlock+0x14/0x29 Mar 29 10:06:31 Tower kernel: macvlan_process_broadcast+0xbc/0x12f [macvlan] Macvlan call traces will usually end up crashing the server, switching to ipvlan should fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enabled, top right)), then reboot. Also, the docker image is corrupt, it should be recreated: https://docs.unraid.net/unraid-os/manual/docker-management/#re-create-the-docker-image-file Also see below if you have any custom docker networks: https://docs.unraid.net/unraid-os/manual/docker-management/#docker-custom-networks
  2. Enable the syslog server and post that after a crash/reboot, in case it catches something.
  3. Same as this: https://forums.unraid.net/bug-reports/stable-releases/6129-disks-missing-after-upgrading-to-6129-r2922/?do=getNewComment&d=2&id=2922
  4. Try booting in safe mode and/or closing any browser windows open to the GUI, only open when you need to use it then close again.
  5. Nothing obvious in the logs, check to see if there's a write cache option in the BIOS, if yes set it to enabled, you can also run a test with the diskspeed docker to confirm disks are performing OK.
  6. It depends, but generally any call trace means that there is a problem, hardware or software, though some can be more serious than others.
  7. If none of the containers is restarting, you can disable one at a time to see if you find the culprit.
  8. Nothing in the logs, maybe it's just copying smaller files? Those will be slower.
  9. Everything looks OK so far, maybe it was a fluke, though strange that the server tried to suspend without the plugin.
  10. This issue will happen with any Asmedia 1064 with more than 4 ports, or any Asmedia 1166 controller with more then 6 ports, i.e., controllers that use SATA port multipliers, any devices on ports that come from a PM will not be detected, this is a kernel issue, they have already reverted this change but it didn't make to kernel 6.1.x., so possibly LT will need to apply the patches themselves.
  11. Try swapping cables between the two devices and see where the problem follows.
  12. Then the call traces would not be about macvlan. Yes.
  13. Did you get an automated email reply? If not use the contact form again.