Jump to content

JorgeB

Moderators
  • Posts

    67,849
  • Joined

  • Last visited

  • Days Won

    708

Everything posted by JorgeB

  1. I usually only know what I need once I start looking at the diags, post the complete syslog and the SMART report for that disk, if those are enough great, if not I'm sorry but I'm not going to be asking file by file.
  2. Switching to ipvlan should also fix that (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enabled, top right))
  3. Not that I know of, but it's a newer kernel so it's worth trying.
  4. Sep 14 02:42:58 Tower kernel: be2net 0000:0d:00.0 eth0: Link is Down No link now.
  5. It's not a problem to mix different speed disks in the array, parity check/rebuilds will be limited by the speed of the slowest disk, other than that there are no issues.
  6. Yes, try that, post new diags if it doesn't work after changing eth5 to eth0
  7. That's not a general issue or there would be a lot of people complaining, did you ever create a bug report with the diagnostics after the problem occurs?
  8. Sep 13 15:24:39 Proliant-2 kernel: be2net 0000:0d:00.0 eth4: Link is Down Sep 13 15:24:39 Proliant-2 kernel: be2net 0000:0d:00.1 eth5: Link is Up Log does show link up on one of the ports, note that you should set it as eth0 (Settings -> Network Settings -> Interface Rules then reboot) if you want to use that NIC as the main one to manage Unraid.
  9. Cache disk looks OK, problem appear to start with this: Sep 13 07:10:40 deathstar kernel: DMAR: ERROR: DMA PTE for vPFN 0x70 already set (to 2e9b16001 not 20c994d002) This is the same error some users start seeing with the first v6.10 releases and that we then found it can cause data corruption, first time I see it with v6.9.x, but wasn't looking for it before, in any case you should update to v6.10.3 ASAP, that issue can no longer happen there.
  10. /tmp in Unraid uses half the available RAM, that's normal.
  11. Don't remember seeing a similar issue, and certainly not a common problem, temporarily remove any extra SMB settings if you have them and/or boot in safe mode, if issue persists boot with v6.10.3 in a trial key to see if it's config related.
  12. Please post the diagnostics
  13. Please retest with -rc5, it should be supported again.
  14. Download the v6.10.3 zip and extract al the bz* files to the flash drive overwriting existing ones.
  15. JorgeB

    Turbo write

    Start a new thread in the general support forum and include the diagnostics saved during a check.
  16. Still nothing, and the other Intel NIC is now also missing, upgrade to v6.10.3 since there were changes to the NIC rules script and post new diags, might also be a good idea to delete/rename network.cfg to use the default LAN settings.
  17. Not really a network guy but it won't take over unless you include eth0 and/or eth1 in that bridge, but why not just use the current bridge or pass-trough the NICs to the VMs directly?
  18. No link is being detect on either NIC, also eth1 is missing from network rules, delete network-rules.cfg, reboot and post new diags.
  19. Not very familiar with Quadro models, but looks like it's equivalent to a GTX1050, so no, not a problem.
  20. That's OK, as long as you assign all the pool devices the existing pool will be imported, there can't be a "data on this device will be deleted" warning in front of any pool device. That suggests the update isn't the problem.
  21. Yes, it should be fine, and x8 is enough for most GPUs.
  22. If you updated using the GUI you can downgrade by going to Tools -> Update OS
  23. Please go back to v6.8 and post the iperf results.
×
×
  • Create New...