Jump to content

JorgeB

Moderators
  • Posts

    67,416
  • Joined

  • Last visited

  • Days Won

    705

Everything posted by JorgeB

  1. Server restarting by itself during a check suggests a hardware problem, you can try enabling the syslog server, it might catch something.
  2. That is strange, but as long as it's working...
  3. Try this: Edit config/ident.cfg on the flash drive and change USE_SSL from "auto" to "no", then reboot.
  4. You should post the diagnostics, ideally from v6.7 and v6.8, though it's likely a driver issue, might get fixed on a future kernel.
  5. Yes, cache is showing as correctly mounted, though is completely full, you can't access via shares or console? Syslog is spammed with syslog server related errors (possibly because it's writing to cache and it ran out of space) so can't see if there are more serious issues.
  6. There's no advantage in using USB 3.0 ports, and they are known to drop out frequently.
  7. I already suspected that, since it had the same UUID has the emulated disk, someone/something deleted/formatted all data on that disk before.
  8. It should mount now, if it doesn't post new diags.
  9. You need to check filesystem on that disk, on the console type: xfs_repair -v /dev/sdj1 note the 1 in the end, if it asks for -L use it: xfs_repair -vL /dev/sdj1
  10. It's been requested before, for now the usual workaround is to set the higher temps in the general settings, then set lower temps for each array device.
  11. Trial can be extended twice for an additional 15 days.
  12. Go to Settings -> Unassigned Devices and change the UUID of that filesystem, it's the last option in the UD settings page.
  13. https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=545988
  14. Is this data to data disk, or cache to data? Like mentioned data to data disk will always be slower.
  15. That's not possible, either disk8 was already empty or it was formatted. Best bet now is to mount the original disk8 with UD and copy whatever you can to the array, you'll still need to do a new config and resync parity to get rid of the emulated disk8.
  16. Disk8 is completely empty, did you format it at any time during this?
  17. Cache filesystem is corrupt, backup, re-format pool and restore data. P.S. if not using ECC RAM good idead to run memtest since the were checksum errors.
  18. Post new diags, but better to reboot first since syslog was already incomplete on the latest ones.
  19. Did you update the LSI HBA? Do you have another controller you can test with? Other than that don't have more ideas.
×
×
  • Create New...