Jump to content

JorgeB

Moderators
  • Posts

    67,452
  • Joined

  • Last visited

  • Days Won

    706

Everything posted by JorgeB

  1. 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.
  2. 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.
  3. 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:
  4. 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.
  5. That suggests a hardware issue, but not easy to diagnose if sometimes it takes so long to crash.
  6. 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.
  7. Then it could be an SSD issue. Also make sure you replaced both cables, not just the SATA cable.
  8. Try a different controller, sometimes there's a compatibility issue.
  9. Because you're supposed to use the existing plugin support thread:
  10. 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
  11. It dropped offline, most likely a connection issue, replace both cables.
  12. 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.
  13. Fastest way would be to rebuild one drive at a time outside the enclosure, or 2 if you have dual parity.
  14. Checksum errors mean data corruption, posting the diags might show some clues, also a good idea to run memtest.
  15. Recommend one or more LSI HBAs with SAS expanders as needed, you can reliably use many devices with these.
  16. 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.
  17. This should have been posted on the UD support thread but you just need to click on the name to change it.
  18. Upgrade to v6.9-rc1 when available and see how it goes.
  19. The original problem wouldn't disable disk1, that was something else you did, I'd suggest at least start with disk1 unassigned to make sure the emulated disk1 is mounting and showing the expected data, if yes then re-assign it to rebuild.
  20. No No, but it's worth trying, I would suggest backing up current flash, re-creating it with latest release then restore just the config folder.
  21. Never seen it before, just changing the Unraid IP should never cause this. Do you have any VMs? No idea if it would help but you could try recreating libvirt.img but that would mean re-creating all VMs, though you could backup current image first.
  22. If doing it then also look for the AMD IDE driver "pata_atiixp", since that one can be even more problematic, sometimes disks can't even be used in the array when it's in use.
×
×
  • Create New...