Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,662

  • Joined

  • Last visited

  • Days Won

    707

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    There are some known spin down issues with v6.9.2, you can downgrade to v6.9.1 to see if it helps.
  2. JorgeB
    Moved from Guides forum since this isn't a guide, also please use the existing docker support thread:
  3. JorgeB
    No.
  4. JorgeB
    Next time it happens please post the diagnostics: Tools -> Diagnostics (before rebooting)
  5. JorgeB
    It's possible, but first I would swap those disk with others from different slots and see if the problem follows the disks or stays with the slots.
  6. JorgeB
    Please post the diagnostics: Tools -> Diagnostics
  7. JorgeB
    Diags are just after rebooting so not much to see, post new ones if you get more issues.
  8. JorgeB
    Parity disk dropped offline so there's no SMART, this is usually a connection/power problem, but best to check or post SMART report first.
  9. JorgeB
    Pool is using the single profile, so 2TB total is correct for that, you can convert to raid1.
  10. JorgeB
    Please post the diagnostics: Tools -> Diagnostics
  11. JorgeB
    The disk itself might generate errors if it gets very hot, but Unraid never disables a disk because it's hot, that's not possible, it only disables a disk if there are write errors. If the disk mounts it should show the data, if there was serious filesystem corruption it wouldn't mount, but you can still run xfs_repair, if the disk is unassigned it would be: xfs_repair -v /dev/sdX1 Replace X with correct letter.
  12. JorgeB
    For the pool errors start by running a scrub and check all errors are corrected, if not check the syslog for the list of corrupt files, those will need to be deleted/replaced. For the crashing enable syslog mirror to flash then post tat log after a crash.
  13. JorgeB
    Forgot to mention pool needs rebalancing since it has multiple data profiles, you should have gotten a notification about that.
  14. JorgeB
    Cache pool is completely full and gone read only, reboot, don't stat docker and try to immediatly free up some space, only after that is done start docker engine.
  15. JorgeB
    There could be some compatibility issue with the HBA and that disk model.
  16. JorgeB
    Don't see anything relevant logged before the last boot, this suggests a hardware problem.
  17. JorgeB
    The listed files are the corrupt files:
  18. JorgeB
    There are disk errors even before attempting to format, try connecting the disk to the onboard SATA controller to see if there's any difference
  19. JorgeB
    Sometimes just the filesystem structure is corrupt, i.e., the moved files are OK, but if you can get them again it would be better.
  20. JorgeB
    No, those are RED Pro (7200rpm), but they are also CMR.
  21. JorgeB
    Would need current diags.
  22. JorgeB
    That is to clone to an array device, use the first option to clone to an unassigned device. This is the destination path after mounting it, in this case you could only do this after mounting the pool.
  23. JorgeB
    You need to post the mirrored syslog, it won't be in the diags.
  24. JorgeB
    Share floor is set to 10TB, remove 3 zeros, or use 10G
  25. JorgeB
    That shows serious filesystem corruption, best bet is to backup cache and re-format, make sure RAM is running at or below max supported speed and also good idea to run memtest.
×
×
  • Create New...