Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,696

  • Joined

  • Last visited

  • Days Won

    707

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    Unfortunately there's nothing relevant logged before the crash, this usually suggest a hardware problem, one thing you can try it to boot the server in safe mode with all docker/VMs disable, let it run as a basic NAS for a few days, if it still crashes it's most likely hardware, if it doesn't start turning on the other services one by one.
  2. JorgeB
    This is likely a client issue.
  3. JorgeB
    Ryzen with overclocked RAM is known to corrupt data in some cases, respect max officially supported RAM speed for your config then run a couple of parity checks, first one is still likely to find errors, but if the problem is solved second one should not find any, if it does run memtest.
  4. JorgeB
    This suggests a flash drive problem, try redoing it.
  5. JorgeB
    If it is encrypted yes.
  6. JorgeB
    Was that disk formatted before?
  7. JorgeB
    You have 3 connected 2TB disks, all 3 are assigned to the array, don't understand what exactly is the problem.
  8. JorgeB
    Before getting a new PSU swap cables with different disks, if the same disks remain missing it's not the PSU.
  9. JorgeB
    Disks 1 and 3 are still missing, you can't do anything else until they are detected.
  10. JorgeB
    It's normal since the other disk is smaller, parity check for that one ended at the 8TB mark. Total size refers to parity size.
  11. JorgeB
    You should only do that if the missing disks are detected and can be mounted correctly.
  12. JorgeB
    Similar to these: You can, changing cables won't change anything like that, disks are assigned using their serial numbers.
  13. JorgeB
    If the disks are still missing try a new PSU, and check that any power/reset errors are gone before attempting rebuilds.
  14. JorgeB
    Try new cables and/or a different PSU.
  15. JorgeB
    Since the SMART test was successful disk should be OK, replace/swap cables to see if there's any difference.
  16. JorgeB
    Most of that used space will be filesystem overhead, did you format the disk before or after rebuilding?
  17. JorgeB
    Click on the disk and set the filesystem to xfs.
  18. JorgeB
    If you didn't start the array after unassign it you just need to assign it back, if you did please post the diagnostics: Tools -> Diagnostics
  19. JorgeB
    RAID controllers are not recommended.
  20. JorgeB
    This usually happens if the drive dropped and reconnected with a different letter.
  21. JorgeB
    Yes, dashboard includes iowait.
  22. JorgeB
    If Docker/VM services are using the cache/pool disable them, unassign all cache devices, start array to make Unraid "forget" current cache config, stop array, reassign all cache device(s) (there can't be an "All existing data on this device will be OVERWRITTEN when array is Started" warning for any cache device), re-enable Docker/VMs if needed, start array.
  23. JorgeB
    This should be fixed on v6.10-rc1
  24. JorgeB
    Yes, because parity need to be updated simultaneously, if you need to do this for a large amount of data best to temporarily disable parity, of course array will be unprotected.
  25. JorgeB
    Not without the persistent syslog, set it to mirror to the flash drive then post that after a crash.
×
×
  • Create New...