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
    Replace the cable or swap with parity1 and try again.
  2. JorgeB
    I agree, this is mostly for when the user already posted diags or it's a clear answer, and you can always ask for diags before writing those linked words.
  3. JorgeB
    You can do a new config to keep the data in the remaing data drives.
  4. JorgeB
    It will still copy them with the error, but to avoid it just uncheck this:
  5. JorgeB
    👍 Those bar colors hurt my eyes
  6. JorgeB
    Yes, check/replace/swap.
  7. JorgeB
    Looks more like a connection problem, check/replace cables and re-sync. Make sure you enable system notifications.
  8. JorgeB
    Rebooting without the cache device connected should bring back the user shares.
  9. JorgeB
    This has been happening for some time, I changed how I work with the mover/array because of that.
  10. JorgeB
    Not used as often but I think still worth adding are parity swap and shrink array, though shrink array should be edited to remove the clear-me script that hasn't worked correctly for some time, manual option still works correctly.
  11. JorgeB
    Yes, that's the problem: shareUserInclude="disk1,disk2,disk3,disk4,disk5,disk6" Remove all disks from include so they are all used.
  12. JorgeB
    Just those drives, Unraid will only accept 512B or 4KB sector sizes.
  13. JorgeB
    Unfortunately there's nothing relevant logged, this usually suggests a hardware issue, 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 likely a hardware problem, if it doesn't start turning on the other services one by one.
  14. JorgeB
    Same thing, so assuming the power cable was also replaced it looks like a disk problem.
  15. JorgeB
    Please use the existing docker support thread:
  16. JorgeB
    Logical block size: 520 bytes You need to re-format to 512B sector size.
  17. JorgeB
    Optical could be OK, but the other ones should all be moved.
  18. JorgeB
    Parity check is unrelated to the cache drive, I would either try it with the onboard SATA controller or try a different disk.
  19. JorgeB
    You can also enable syslog mirror to flash then post that log after a crash.
  20. JorgeB
    Cache device dropped again, if you swapped both power and SATA cables it could be a device problem, you can also try connecting it to the onboard SATA ports, but I've used the same disk model with an LSI without issues.
  21. JorgeB
    Correct. Not sure why that device is not being decrypted, it's being detected so it should also be decrypted, but I've never used encryption, so not familiar that with how it works, could be an Unraid bug, if you have a different device test with that, if it works it was likely a device problem, if it's the same it's likely a bug.
  22. JorgeB
    Folder needs to be named EFI to allow UEFI boot, but CSM boot works either way.
  23. JorgeB
    Start here: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=819173
  24. JorgeB
    Problem with the onboard SATA controller, quite common with some Ryzen boards, if there's no BIOS update best bet is to use an add-on controller.
  25. JorgeB
    That's not a problem, it's normal that some files could be more optimized by "re-sparsifying", especially vdisks or similar, it won't damage any files by always using the sparse flag.
×
×
  • Create New...