Jump to content

JorgeB

Moderators
  • Posts

    67,808
  • Joined

  • Last visited

  • Days Won

    708

Everything posted by JorgeB

  1. Try the NVMe device in a different PCIe/M.2 slot if available.
  2. Good find, but still looks to me like a BIOS bug. No, but look for "Power Supply Idle Control" (or similar) and set it to "typical current idle" (or similar).
  3. Those diags still show cache2 installed with related errors.
  4. There is but I would recommend first posting a set of diagnostics after the problem occurs.
  5. Jul 12 11:36:40 Tower emhttpd: error: share_luks_status, 6151: Operation not supported (95): getxattr: /mnt/user/lxc This appears to be the problem, you should not create any mountpoint in /mnt/user, those should be reserved for Unraid array/pools only. Also I believe ich777 recommendeds not using a FUSER path for LXC for performance reasons, use /mnt/cache/lxc or /mnt/disk#/lxc
  6. The title mentions that you cannot connect to the Plex GUI, or do you mean the Unraid GUI?
  7. VM section uses binary units, so 70G is 70GiB, and that's 75.16GB.
  8. That looks unrelated to the macvlan issue, but not sure where they come from.
  9. Try this: https://forums.unraid.net/topic/124890-gtx650ti-code-43-with-windows-10/?do=findComment&comment=1139615
  10. For now I would replace the cables and try to sync the new parity again. CRC errors are usually the SATA cable, for parity and like mentioned need to see the SMART report first, but for now looks like power/connection problem.
  11. Since data corruption has been detected by btrfs fist thing I would recommend is running memtest, after that there are some recovery options here.
  12. This you use the GUI or the console? If console type the command used. That won't fix anything.
  13. Logs are full of ATA errors for disks 1 and 4, check/replace cables, parity dropped offline, probably also a power/connection problem, but would need a SMART report after the disk comes back online to confirm.
×
×
  • Create New...