Jump to content

JorgeB

Moderators
  • Posts

    67,459
  • Joined

  • Last visited

  • Days Won

    706

Everything posted by JorgeB

  1. 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.
  2. 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
  3. https://wiki.unraid.net/Troubleshooting#Re-enable_the_drive
  4. 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.
  5. 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
  6. 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.
  7. 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.
  8. They'll turn green as soon as the parity sync finishes, independent of the disks being formatted or not, though you need to format them before use, and that can be done at any time, before or after the sync finishes.
  9. Yes Sir! That's good, also probably a good idea to create an international section in the forums, with a sub-forum for each supported language.
  10. It should work fine but make sure you confirm by checking if the emulated disk mounts correctly before rebuilding on top, more details on the procedure here:
  11. That suggests fs corruption, see if you can get the diags on the console by typing "diagnostics", then type "reboot" and if it doesn't do it after 5 minutes you'll need to force it.
  12. That suggests a hardware issue, but not easy to diagnose if sometimes it takes so long to crash.
  13. This one should work in any board but it's for SATA m.2 devices, not NVMe This one is for NVMe and it should work in a x16 slot that supports PCIe bifurcation, check board manual.
  14. Then it could be an SSD issue. Also make sure you replaced both cables, not just the SATA cable.
  15. Try a different controller, sometimes there's a compatibility issue.
  16. Because you're supposed to use the existing plugin support thread:
  17. Diags after rebooting aren't much help, you can try this: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=781601
  18. It dropped offline, most likely a connection issue, replace both cables.
  19. The problem is the way the RAID controller is identifying the devices: Unraid considers that those 3 devices have the same serial number so you can only use one of them, see if that identifier can be changed or better yet don't use a RAID controller.
  20. Fastest way would be to rebuild one drive at a time outside the enclosure, or 2 if you have dual parity.
  21. Checksum errors mean data corruption, posting the diags might show some clues, also a good idea to run memtest.
  22. Recommend one or more LSI HBAs with SAS expanders as needed, you can reliably use many devices with these.
  23. By default only 20% free RAM is used for write cache, after that you're limited by the device, you're also a little limited by network and/or shfs as initial speed should be closer to 1GB/s.
×
×
  • Create New...