Jump to content

JorgeB

Moderators
  • Posts

    67,976
  • Joined

  • Last visited

  • Days Won

    709

Everything posted by JorgeB

  1. So you are using the old parity drives? And yes it's normal for the speed to be slower when it's correcting errors.
  2. For now I would recommend not using Firefox with the GUI, might be resolved with a newer Firefox release.
  3. If you're using v6.11.2 it's a known issue, v6.11.3 with that fixed should be available very soon, but for now you can downgrade to v6.11.1
  4. If you're using v6.11.2 it's a known issue, v6.11.3 with that fixed should be available very soon, but for now you can downgrade to v6.11.1
  5. You can do a parity check after the sync, but if the sync completes at a normal speed without any errors all should be OK.
  6. Log is lost after every reboot, if it keeps happening enable the syslog server and post that after a crash.
  7. That suggests a vdisk already exists in that path (/mnt/user/domains/Windows 10/vdisk1.img)
  8. If you are using v6.11.2 it's a known issue, you need to wait for v6.11.3 or downgrade to 6.11.1 to format any disks >2TB.
  9. No, SATA controller does not work with a SAS expander, in some Intel chipsets the 4 SCU ports support SATA and SAS, those could be connected to a SAS expander, e.g., Supermicro X9DR3-LN4F+.
  10. It's detecting new errors after the correcting check, start by running memtest.
  11. The GUI does not reflect the checkbox, but parity won't be overwritten if it is checked.
  12. If there's no reason to suspect issues with any of the data drives you can replace the parity drives now, but in that case do not check "parity is already valid", parity will be synced after first array start.
  13. There's no HBA/IT mode for the onboard SATA, it's a regular AHCI SATA controller, but it can be used with Unraid without any issues, and the Intel SATA controller is one of the best you can use.
  14. Redoing the flash drive should solve it in that case, backup, recreate, restore the config folder.
  15. You can use the onboard SATA controller for 10 devices, but if the backplane include a SAS expander you cannot connect it to the onboard SATA controller, you need a SAS HBA, like the LSI 9211-8i, 9207-8i, etc in IT mode, MegaRAID models are not recommended.
  16. If the backplane includes a SAS expander you just need one miniSAS cable from the HBA to access all devices, chek the model, it should be printed on the backplane. That's a MegaRAID controller and those usually cannot be flash to IT mode.
  17. Try with a different flash drive with a stock v6.11.2 install, no key needed, just to see if it boots.
  18. That looks OK, grab the diags during the next check if it's still slow.
  19. Not sure it's a plugin, but they are easy to rule out, you can also uninstall them if you prefer.
  20. Should still look into those settings, there are also reports that with some boards you need to completely disabling C-states to make it stable with Linux.
  21. Sorry, cannot really help, never used Plex, maybe try posting in the appropriate docker support thread in the forum, or even the Plex forum, there might be some known issues with specific hardware.
  22. Nothing obvious, enable the syslog server, it might catch more.
  23. There's nothing relevant logged, since it's a Ryzen CPU did you already see this? https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=819173
  24. No, there's no need to start in maintenance mode, after doing a new config there will be a checkbox with "parity is already valid" next to the array start button, just check that before first array start.
  25. That's the regular syslog, it starts over after every reboot, we need the permanent syslog, it will be in the share it's set to save to, or just enable the mirror to flash option, then it will be saved in the flash drive, /logs folder.
×
×
  • Create New...