JorgeB

Moderators
  • Posts

    60018
  • Joined

  • Last visited

  • Days Won

    627

Everything posted by JorgeB

  1. If you can, I would recommend replacing that controller, since it's a common issue with them.
  2. Yes, there are other issues, with btrfs it's better to backup and re-format.
  3. Post new diags, but likely the filesystem has other issues, and in that case recommend backup and re-format.
  4. If the log tree is the only issue this may help: btrfs rescue zero-log /dev/nvme0n1p1 Then restart the array.
  5. You should not need to copy anything from the flash drive, just assign the pool devices to a new pool on the other server, in the same order as zpool import/status. To send the data back, and if you have snapshots you want to keep, you can use zfs replication over ssh.
  6. Diags are after rebooting so we can't see what happened, but the disk looks healthy, since the emulated disk is amounting, and assuming contents look correct, you can rebuild on top, recommend replacing the cables first to rule that out, if it happens again to the same disk.
  7. Enable the syslog server and post that after a crash.
  8. Syslog starts over after every boot, also it usually won't have anything logged for that kind of issue anyway, just see if the server runs stable now.
  9. AFAIK you cannot, at least not without causing issues, /mnt/user is reserved for Unraid.
  10. If it worked for one it should work for the other ones, except maybe disk1, since that one was rebuilt.
  11. You can try this, not sure it will work, but it might, and if it doesn't, it won't cause anymore harm, with the array stopped, and assuming disk1 is still sdb, type: sgdisk -o -a 8 -n 1:32K:0 /dev/sdb The restart the array.
  12. If you already recovered the data it's not a big deal, but it will also prevent us to try and see if it was recoverable or not, since the rebuild will overwrite the old disk.
  13. I would recommend using the form again, try a different brwoser, until you get an automatic reply, AFAIK there's no direct email you can use.
  14. Use cp, mc won't make the new copy sparse, at least not AFAIK.
  15. You can copy the VM to the array, then copy back with cp --sparse=always, that will "re-sparsify" the vdisk, then do the changes.
  16. No. You need to trim de vdisk by running Windows defrag, after making that change, trimming the SSD won't do anything.
  17. Constant ATA errors from disk3, replace cables and post new diags.
  18. You can rename the *.plg files, then reboot, to reinstall rename back.
  19. If it doesn't crash in safe mode with the same containers running it could be a plugin.
  20. This may help https://forums.unraid.net/topic/51703-vm-faq/?do=findComment&comment=557606
  21. Correct. It should help, as long as compatible, using a different brand board where it would work in the GPU slot would also solve the issue. Yep.