Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,554

  • Joined

  • Last visited

  • Days Won

    707

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    Marvell controllers AND port multipliers, two things you should avoid, especially together, one of the port multipliers appear to be having extra trouble initializing the disks, you can try disconnecting the port multiplier from the Marvell 9235 and connect it to the other 9215 instead, those usually have less issues, but I would really recommend getting rid of those and using LSI HBAs instead.
  2. JorgeB
    Sorry, never needed to use it so idea if it's well configured, maybe someone else can help, according to Tom remote server is still working.
  3. JorgeB
    Should be OK.
  4. JorgeB
    You can, the current problem points to an issue with that disk.
  5. JorgeB
    I believe remote still works.
  6. JorgeB
    I forgot there's currently a problem with the beta and this, it should be fixed on the next one.
  7. JorgeB
    Yes, it's in the link above.
  8. JorgeB
    Since a couple of the DIMMs are dual rank you should use 1866Mhz, also make sure Power Supply Idle Control is correctly set in the BIOS.
  9. JorgeB
    That would not invalidate parity, invalid means the disk was disabled in the past. Filesystem corruption can be caused by the hard reset.
  10. JorgeB
    Check filesystem on both disks, also parity is invalid.
  11. JorgeB
    You can take the opportunity to format it XFS, as reiser is not recommended for a long time, also, if not to late, make sure the data looks correct on the USB disk before formatting.
  12. JorgeB
    Not because it's COW, all my btrfs data is COW, but if it's just the docker image there might be another reason for the corruption, and not be hardware.
  13. JorgeB
    Start here: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=819173
  14. JorgeB
    You can just format the unmountable array disk and then move the data there from UD.
  15. JorgeB
    Unfortunately diags after rebooting are not much help, you can try this.
  16. JorgeB
    See if the USB disk mounts with the UD plugin.
  17. JorgeB
    Yep, I was talking about an SSD only array.
  18. JorgeB
    This is not good for Unraid, look for a regular LSI HBA instead, not megaRAID models. Also have some 2.5" drive cages: but for HDDs, the SSDs are in a controller like this one, only 4 data devices, like mentioned it's a small server (parity is NVMe).
  19. JorgeB
    I would think (and hope) so. No, it just means there could be some write performance deterioration with time, I have a small SSD array and for now it's performing normally even without trim.
  20. JorgeB
    You can use the one built in, it doesn't work with UEFI boot though, only legacy/CSM.
  21. JorgeB
    Trim is supported for any pool devices, currently not supported for array devices.
  22. JorgeB
    It's filesystem corruption, can't see an apparent reason, and if it's not the first time it might indicate a hardware issue, good idea to run memtest.
  23. JorgeB
    Don't see much point, though just to confirm you can start one and stop as soon as there are errors. Yep, no need.
  24. JorgeB
    Yes, by clicking on it (if it's an assigned device), if you have unassigned devices than run hotter the current workaround is to set the general settings to that temp and then click on each assigned device and set lower temp thresholds.
  25. JorgeB
    You can do that, or just clone disk2 to a new disk then rebuild parity with that one, note that either way some data corruption is expected.
×
×
  • Create New...