Jump to content

JorgeB

Moderators
  • Posts

    67,831
  • Joined

  • Last visited

  • Days Won

    708

Everything posted by JorgeB

  1. Delete/rename /boot/config/network.cfg and reboot, note lan settings will go back to defaults.
  2. Sep 14 17:09:48 otfgserver kernel: Trying to write to read-only block-device sdg (partno 0) This is a first, please reboot and try again to see if it's the same error.
  3. Yes, use a new Unraid install, you don't need to assign devices or start the array, just export the flash drive and see if you can access it.
  4. Strange error, please try this: Unassign all cache devices, start array to make Unraid "forget" current cache config, stop array, reassign all cache devices (there can't be an "All existing data on this device will be OVERWRITTEN when array is Started" warning for any cache device), start array, post new diags if it still doesn't mount.
  5. No driver being loaded, Realtek 2.5GbE Linux support is iffy, you can try v6.11.0-rc5 to see if the newer kernel includes one.
  6. Enable the syslog server, start a parity check and post that after a crash.
  7. 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.
  8. Switching to ipvlan should also fix that (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enabled, top right))
  9. Not that I know of, but it's a newer kernel so it's worth trying.
  10. Sep 14 02:42:58 Tower kernel: be2net 0000:0d:00.0 eth0: Link is Down No link now.
  11. 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.
  12. Yes, try that, post new diags if it doesn't work after changing eth5 to eth0
  13. 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?
  14. 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.
  15. 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.
  16. /tmp in Unraid uses half the available RAM, that's normal.
  17. 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.
  18. Please post the diagnostics
  19. Please retest with -rc5, it should be supported again.
  20. Download the v6.10.3 zip and extract al the bz* files to the flash drive overwriting existing ones.
  21. JorgeB

    Turbo write

    Start a new thread in the general support forum and include the diagnostics saved during a check.
  22. 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.
×
×
  • Create New...