Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,412

  • Joined

  • Last visited

  • Days Won

    705

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    No NIC is being detected.
  2. JorgeB
    Also see here.
  3. JorgeB
    Check filesystem on disk3: https://wiki.unraid.net/Check_Disk_Filesystems#Checking_and_fixing_drives_in_the_webGui
  4. JorgeB
    Forgot to say reiserfs is not recommended for a long time, you should convert all disks still using it.
  5. JorgeB
    The errors on that disk can't have been caused by the controller, but they could have caused filesystem corruption, since the filesystem is now repaired keep monitoring the disk, any more similar issues in the near future best to replace it.
  6. JorgeB
    Sorry, don't known, you're already using latest LSI firmware, strange that this only happens to a few users, probably related to some hardware combination.
  7. JorgeB
    First thing you should do is to update the LSI firmware, it's using an ancient release. P.S. it might require a new config if the disks ID string changes.
  8. JorgeB
    Always good to run an iperf test to rule out network issues.
  9. JorgeB
    H310 not the same as 9240-8i, but both have no problems with 8TB (and larger) drives, also read only mode suggests a file system problem, not necessarily a disk problem, though filesystem issues can be caused by a failing disk, you should post the diagnostics.
  10. JorgeB
    Try clearing/commenting out all the extra stuff added to SMB settings.
  11. JorgeB
    Try booting in safe mode.
  12. JorgeB
    OK, so that's normal, when you started the array with a single cache device the pool is converted to single profile, and because of the bug with v6.7 it's not automatically convert back when a new device is added, you should also update to v6.8.3.
  13. JorgeB
    Disk2 dropped offline, looks more like a connection/power issue, replace/swap both cables with another disk and see how it goes.
  14. JorgeB
    Currently not, data is single profile, you can convert back to raid1, but it should have stayed raid1 during and after the upgrade, something is not right, if you still didn't reboot post diags.
  15. JorgeB
    Please post the diagnostics.
  16. JorgeB
    Depends on where you stored them and/or if the cache pool is redundant, but even with redundancy you should have backups of anything important, redundancy it's not a backup.
  17. JorgeB
    Wait for the parity sync to finish, even with turbo write performance isn't the same while parity disk is invalid.
  18. JorgeB
    If a new cable didn't help it might just be a compatibility issue, why it would be good to test it on a different controller.
  19. JorgeB
    Looks like they are spin down related, disable spin down for a few hours and see if they go way, some users with LSI HBA have a few errors during spin up or spin down, not sure why, but they look harmless.
  20. JorgeB
    Best bet would be the onboard SATA ports, or an AHCI controller like Asmedia/JMB, all LSI HBAs require SSDs with deterministic read zeros after trim or it won't work, most other 8 port HBAs/RAID controllers also don't support trim.
  21. JorgeB
    It will work but still won't trim an MX500.
  22. JorgeB
    raid1 will have some write performance as a single drive, it just adds redundancy, raid0 will be faster.
  23. JorgeB
    It won't hurt, especially if you get more similar errors in the future.
  24. JorgeB
    With PCIe 3.0 controllers like the ones I recommended you'll get around 2200MB/s usable per port, then divide that by the number of connected disks, you can see some more performance numbers here.
  25. JorgeB
    If you have UD installed you can mount each disk read only and keep your parity 100% in sync.
×
×
  • Create New...