Jump to content

JorgeB

Moderators
  • Posts

    67,452
  • Joined

  • Last visited

  • Days Won

    706

Everything posted by JorgeB

  1. That's a RAID controller (though it might be flashable to IT mode) better to use any of the recommended LSI HBAs instead. Yes, but only SAS devices support 12Gb/s, SATA is still 6Gb/s max.
  2. It shouldn't make any other drives link at lower then supported speeds, also note that you shouldn't have any performance issues because of that, SATA2 is enough for spinners, SSDs are a different story.
  3. If they are mounting correctly they should be fine but it's also OK to run xfs_repair again to make sure.
  4. There was an shfs segfault, rebooting should fix it.
  5. You should post the diagnostics, they might provide some clues.
  6. That's not a good idea, one SATA port should be split in two max, SATA plug is only ratted for 4.5A, a single disk can use 2.5A during startup.
  7. The damage (if any) is already done, you'll need to run xfs_repair once it finishes, you can also cancel and run xfs_repair now then start rebuilding again from the start, this way you know if it's worth rebuilding and can also access the data during it. There's something else using the array, in the screenshot you can see extra reads on disk6, and on the diags there extra reads on disk3.
  8. Also look for an available expander firmware update.
  9. Possibly a backplane issue, you could try connecting a drive directly to the miniSAS cable to see if it makes any difference, also next time please post the complete diags: tools -> diagnostics.
  10. You need to use --rebuild-tree, it will take several hours.
  11. Note that because of the old firmware you might need to do a new config since all disks identifier string will likely change, this you be easier to do with all disks enable, if you can get them like that.
  12. HBA is running a very old firmware (p05), first thing to try is to update it to current one (p16).
  13. Check filesystem on disk3: https://wiki.unraid.net/Check_Disk_Filesystems#Checking_and_fixing_drives_in_the_webGui
  14. Don't mess with the disks/filesystem for now, not until the problem is fixed. That would be my next step, start with the one easier/cheaper to replace/swap, then run another read check.
  15. It's affecting multiple devices, start by checking/replacing all cables, both SAS/SATA and power.
  16. Constant ATA errors on both disk3 and parity, check cables.
  17. Media share is set to split level 1, so if the folder where you're trying to copy to already exists on disk2 all new files will go there, split level overrides allocation method.
  18. Changed Status to Closed Changed Priority to Other
  19. This is likely a general support issue. most likely split level related, please start a thread on the general support forum, enable mover logging, run the mover and then download the diagnostics and attached them to your post.
  20. It should be fine to remove as long as "power supply idle control" is correctly set in the BIOS, see here: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=819173
  21. https://wiki.unraid.net/Troubleshooting#Re-enable_the_drive
  22. This is only for when the cache if fully allocated but there's still free space, your pool is completely full so you need to move or delete some files. If the VMs are Windows this helps to keep the vdisks as small as possible.
  23. LSI SAS3 models like the 9300-8i support trim as long as the SSDs support deterministic read zeros after trim. e.g, 860 EVO, WD Blue 3D, etc
  24. No. You can use the default RAID1 profile but only 256GB total will be usable (and be aware that the free space shown on the GUI will be wrong) or create a single profile pool where full space will be available but without redundancy.
  25. You can, up to six devices total, all devices can be disk or flash based want and assigned to array or cache, or even used unassigned.
×
×
  • Create New...