Jump to content

JorgeB

Moderators
  • Posts

    67,826
  • Joined

  • Last visited

  • Days Won

    708

Everything posted by JorgeB

  1. If the disk is precleared Unraid will recognize that and add it to the array immediately, you just need to format it.
  2. Please post the diagnostics.
  3. Update to latest stable and if issues persist enable the syslog server and post that after a crash.
  4. It is, if you used it before it's now using the fist 15 day extension.
  5. Start here: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=819173
  6. Copy super.dat for the array assignments, also the pools folder if there are any.
  7. I suppose it's based on the server time, but AFAIK it won't start if server time is wrong.
  8. Create a new share called Media and move the other shares inside that folder, shares are just top level folders.
  9. It's still an issue, with v6.10 or even v6.11-rc, I assume that it happens because of FUSE and it might not be an easy fix from LT side.
  10. This is usually a flash drive problem, recreate a new flash drive using the USB tool or manually and before restoring anything from the backup see if it boots.
  11. Still rather strange, and you're sure there are no disconnects without the VM running?
  12. That's not failed, it's aborted, it can happen for example if the disk spins down during the test.
  13. Start by running a single stream iperf test to check network bandwidth.
  14. Replace the parity drives first, once the parity sync is done you can add new drives.
  15. Not clear from your previous answer if you had any VM already configured, if you don't, or it's not important, delete libvirt.img and create a new one, any configured VMs will be lost.
  16. Post new diags after array start in normal mode.
  17. Usually relatively recent Nvidia GPUs work the best, 10 series or newer.
  18. Array disks are not yet formatted, you should formatted them, though most likely unrelated. Did you have any VMs created or was the libvirt.img new?
  19. Try switching to ipvlan (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enable, top right))
  20. Unfortunately there's nothing relevant logged, this usually points to a hardware issue, one thing you can try is to boot the server in safe mode with all docker/VMs disable, let it run as a basic NAS for a few days, if it still crashes it's likely a hardware problem, if it doesn't start turning on the other services one by one.
  21. What drive(s) exactly do you want to replace?
  22. Enable the syslog server and post that after a crash.
×
×
  • Create New...