Jump to content

JorgeB

Moderators
  • Posts

    63,486
  • Joined

  • Last visited

  • Days Won

    673

Community Answers

  1. JorgeB's post in SSD Cache move to 2 SSDs was marked as the answer   
    By default it will create a mirror.
  2. JorgeB's post in Disk with read errors was marked as the answer   
    It's logged as a disk error, even if SMART looks good, run another extended test, but even if it passes, if there are any more errors I would consider replacing it.
  3. JorgeB's post in Trying to get to an old topic on the Forum was marked as the answer   
    @Frank1940Since there's some interesting and still relevant info in that thread I've created a copy here:
     
     
  4. JorgeB's post in Just added a cache drive, used mover to move files ... and the shares have disappeared was marked as the answer   
    Stop the array, click on the pool and set "Enable user share assignment" to Yes.
  5. JorgeB's post in unclean shutdown parity and 1 disk disabled was marked as the answer   
    Emulated disk1 is mounting, if contents look correct you can rebuild on top and sync parity at the same time:
     
    https://docs.unraid.net/unraid-os/manual/storage-management#rebuilding-a-drive-onto-itself
  6. JorgeB's post in 2 disabled disks was marked as the answer   
    It's not logged as a disk problem and SMART looks fine, most likely a power/connection issue.
  7. JorgeB's post in Can't add cache drive - says it's unmountable. was marked as the answer   
    Device was busy, reboot and try to format again, that should do it.
  8. JorgeB's post in Unassigned Device after old Backup restored & No docker containers was marked as the answer   
    You can do a new config: Tools - New config - Preserve all
     
    Then assign disk3 and check "parity is already valid" before array start, still a good idea to run a parity check after, and if you started the array without disk3 there will be some sync errors.
  9. JorgeB's post in [solved] Do I have XFS corruption on my cache partition or no? was marked as the answer   
    The filesystem should be fixed now, reboot to clear the logs.
     
    Don't recommend using -L unless xfs_repair asks for it.
  10. JorgeB's post in Moving cache to different drive was marked as the answer   
    You can use this:
    https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=511923
     
  11. JorgeB's post in Random Crashing in 6.12 and after reverting back to what was stable 6.11 crashing again was marked as the answer   
    That suggests the updated was not the problem, it may have just been a coincidence, with all those different apps segfaulting I would start by running memtest.
  12. JorgeB's post in Disk Read Error on parity check was marked as the answer   
    If the SMART test passed the disk is OK for now, you can click on the thumbs down to acknowledge the current errors, it will then only change if more appear.
     
     
     
  13. JorgeB's post in Corrupted Docker Image -> Parity Drive Errors? was marked as the answer   
    The XML is missing from the diags, but looks like the SATA controller (and a USB controller) are bound to the opensense VM, so Unraid lost connection with all disks when it tried to start..
  14. JorgeB's post in New unraid install loses remote connection randomly was marked as the answer   
    The NIC is detecting a link change/drop:
     
     
    Try a different NIC if possible.
  15. JorgeB's post in Parity and 3 array drives all stopped functioning at once was marked as the answer   
    Check filesystem on the unmountable disks, run it without -n
  16. JorgeB's post in Data Loss Mitigation Help was marked as the answer   
    Since parity is invalid it won't be able to emulated the disabled disk, if you think disk3 is healthy, and the rebuild was being done on the old disk, you can do a new config to re-enable that disk and then re-sync parity, but note that any data written to that disk after it got disabled would be lost.
     
     
  17. JorgeB's post in New User, New Build. System not staying up for more than a couple hours was marked as the answer   
    Make sure this has been taken care of:
    https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=819173
     
    But the server rebooting on its own usually means a more serious hardware issue.
  18. JorgeB's post in nvme on cache pool shows up also on unassigned devices was marked as the answer   
    If the docker image is the only corrupt file you can recreate it:
     
    https://docs.unraid.net/unraid-os/manual/docker-management/#re-create-the-docker-image-file
    Also see below if you have any custom docker networks:
    https://docs.unraid.net/unraid-os/manual/docker-management/#docker-custom-networks
     
    Then run another scrub to confirm no more errors.
  19. JorgeB's post in Does Unraid still offer a trial extension after the new pricing model. was marked as the answer   
    AFAIK nothing changed with that, you should still have 30 days initially plus two 14 day extensions.
  20. JorgeB's post in Extremely slow Parity Check recently. was marked as the answer   
    Check/replace cables for disks 13 and 14, also a good idea to run a SMART long test on 13 at least, 14 is not giving a full SMART report.
  21. JorgeB's post in Unable to Format 2 Re-purposed Hard Drives was marked as the answer   
    There are constant disk errors for both, try connecting them to the onboard SATA controller instead.
  22. JorgeB's post in Issue starting Docker Engine was marked as the answer   
    Docker image is corrupt, delete and re-create:
     
    https://docs.unraid.net/unraid-os/manual/docker-management/#re-create-the-docker-image-file
    Also see below if you have any custom docker networks:
    https://docs.unraid.net/unraid-os/manual/docker-management/#docker-custom-networks
  23. JorgeB's post in Unraid server debug help, daily crashes and reboots (Solved) was marked as the answer   
    Server rebooting on its own is almost always a hardware issue, but can be caused by different components, start by running memtest, but note that memtest is only definitive if it finds errors, if you have multiple sticks you can also try with just one, if the same try with a different one, that will basically rule out bad RAM, next suspects after that would be PSU, board, CPU.
  24. JorgeB's post in BTRS errors - sometimes coming back - help wanted was marked as the answer   
    If you can return that one I would try using a controller with a different chip, like a JMB585, in case it's some compatibility issue with your board.
  25. JorgeB's post in Unable run parity check on brand new build. Attached Diagnostics. was marked as the answer   
    Yes, if that works it suggest an issue with the other controller, you can try one of the recommended ones:
     
     
×
×
  • Create New...