Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,878

  • Joined

  • Last visited

  • Days Won

    708

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    Do you mean it reboots during booting Unraid? If yes try booting CSM or UEFI, and normal and with the GUI mode, sometimes it makes a difference.
  2. JorgeB
    Still looks like a power/connection problem, suggest replacing/swapping both cables.
  3. JorgeB
    Probably you've already tried it but just in case this helped with some Nvdia GPUs and that error: https://forums.unraid.net/topic/124890-gtx650ti-code-43-with-windows-10/?do=findComment&comment=1139615
  4. JorgeB
    SATA controller is bound to vfio-pci, this was likely a GPU before, adding/removing hardware can change the device IDs, remove the bind and reboot.
  5. JorgeB
    Like mentioned if you have two failed drives with single parity you cannot rebuild either of them, but you can do a new config with the remaining drives.
  6. JorgeB
    If it's already using a USB 2.0 port the flash drive could be failing, try a different USB controller if available, if there's isn't one or it's the same replace the flash drive.
  7. JorgeB
    Yes.
  8. JorgeB
    Downloading torrents, or possibly high i/o, could be contributing factors, but it's for users getting an identical call trace as the ones posted in the 1st post.
  9. JorgeB
    Make sure you are using a USB 2.0 port.
  10. JorgeB
    Yep, sometimes the problem is not enough contiguous RAM.
  11. JorgeB
    Nope, just any new files will not be written to that disk.
  12. JorgeB
    Formatted with type 2 protection You need to remove this, more info below: https://forums.unraid.net/topic/93432-parity-disk-read-errors/?do=findComment&comment=864078 https://forums.unraid.net/topic/110835-help-with-a-sas-drive/
  13. JorgeB
    You just create a new VM with the same settings and in the vdisk path select the existing vdisk.
  14. JorgeB
    There's an OOM error at that time.
  15. JorgeB
    That means neither of those images are the original ones, possibly something went wrong during the backup/restore, the docker image can easily be recreated, do you have a backup of libvirt.img? If not you can create new VM(s) and point to the old vdisk(s).
  16. JorgeB
    I can confirm it's a bug, but it's kind of a corner case, and this is #1 for the procedure you've followed: "Make sure that the drive or drives you are removing have been removed from any inclusions or exclusions for all shares, including in the global share settings. Shares should be changed from the default of "All" to "Include". This include list should contain only the drives that will be retained." So as long as the instructions are followed there won't be a problem.
  17. JorgeB
    Stop docker and VM services and set both paths to /mnt/disk2/system/etc, then start them again and see if they are back.
  18. JorgeB
    Great Yes, it does sound like a bug.
  19. JorgeB
    Nothing in the logs that I can see, but they are just after rebooting, was it already showing corrupt flash drive?
  20. JorgeB
    It dropped again, try using a different port/controller, if it keeps happening it could be the device.
  21. JorgeB

    Boot error

    JorgeB replied to Dosc's topic in General Support

    Backup current /config folder, recreate the flash drive using the USB tool, see if it boots, if yes restore the config folder.
  22. JorgeB
    Please post the diagnostics.
  23. JorgeB
    Both docker and libvirt images look pretty recent, see if there's more than one, post output of: find /mnt -name libvirt.img and find /mnt -name docker.img
  24. JorgeB
    Good it worked but would still have liked to see the diags form the 2nd try.
  25. JorgeB
    Those are OK, think I've found the problem, click on Settings -> Global Share settings and remove disk2 from the included disks.
×
×
  • Create New...