Jump to content

JorgeB

Moderators
  • Posts

    67,696
  • Joined

  • Last visited

  • Days Won

    707

Everything posted by JorgeB

  1. Diags might show something, but please create a new thread.
  2. Macvlan call traces are usually the result of having dockers with a custom IP address, upgrading to v6.10 and switching to ipvlan might fix it, or more info below. https://forums.unraid.net/topic/70529-650-call-traces-when-assigning-ip-address-to-docker-containers/ See also here: https://forums.unraid.net/bug-reports/stable-releases/690691-kernel-panic-due-to-netfilter-nf_nat_setup_info-docker-static-ip-macvlan-r1356/
  3. Several thousand are perfectly normal, more if server was writing when it lost power.
  4. There are multiple ATA errors for cache2, and it's logged as a device problem, so you should keep an eye on that: Sep 12 00:37:48 NAS kernel: res 51/40:20:40:2e:3d/00:00:12:00:00/e0 Emask 0x9 (media error) Sep 12 00:37:48 NAS kernel: ata6.00: status: { DRDY ERR } Sep 12 00:37:48 NAS kernel: ata6.00: error: { UNC } Sep 12 00:37:48 NAS kernel: ata6.00: configured for UDMA/133 Sep 12 00:37:48 NAS kernel: sd 6:0:0:0: [sdf] tag#30 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=0s Sep 12 00:37:48 NAS kernel: sd 6:0:0:0: [sdf] tag#30 Sense Key : 0x3 [current] Sep 12 00:37:48 NAS kernel: sd 6:0:0:0: [sdf] tag#30 ASC=0x11 ASCQ=0x4 Sep 12 00:37:48 NAS kernel: sd 6:0:0:0: [sdf] tag#30 CDB: opcode=0x28 28 00 12 3d 2e 40 00 00 20 00
  5. A few sync errors are normal, even expected, after an unclean shutdown, just run a correcting check.
  6. Changed Status to Closed Changed Priority to Other
  7. RAM is still overclocked, after fixing that run a couple of correcting checks without rebooting and post new diags.
  8. Reboot, start array, format disk15, please post new diags if it still doesn't work.
  9. VMs pausing is usually when they run out of space, and your cache pool is completely full, that's also what is causing issues with libvirt.img, it might recover after you free up some space on cache and reboot.
  10. It's up to you: speed vs redundancy.
  11. Unless you care about snapshots and/or checksums xfs is the best option for the typical user, to change you need to backup/move the data from each disk and re-format, it can be done one at a time.
  12. Best bet is to make a feature request so it can be added to a future release.
  13. Also note that if it works it's not supported, and it might stop working in a future release.
  14. It's not possible, Unraid requires one partition using the entire device, it might work if you change to a pool, and you can have a single device pool, just need pool slots set to >1, pools require btrfs.
  15. It's not your fault, default should be enable, it's a bug, already fixed for next rc.
  16. Settings -> Global Share settings -> User shares -> Enable
  17. Not for now or Unraid will complain they are wrong, it's not a problem having them like that and once you replace/upgrade those disks it will be gone.
  18. Yes, then format after array start.
  19. For single device pools and If you don't care about the extra btrfs features, like snapshots or checksums, you should use xfs.
  20. Forgot to mention, you have other disks with HPA enable, but don't remove it on those or Unraid will also complain the disks are wrong, but now because they are larger than they should be, only remove on disk3 and disable that feature on the board BIOS so more are not created.
  21. Sep 16 20:26:05 Tower kernel: ata3.01: HPA detected: current 5860531055, native 5860533168 Sep 16 20:26:05 Tower kernel: ata3.01: ATA-9: WDC WD30EFRX-68EUZN0, WD-WCC4N6VXN8P2, 82.00A82, max UDMA/133 Your board is creating these: Also change SATA controller from IDE to AHCI/RAID.
×
×
  • Create New...