Jump to content

JorgeB

Moderators
  • Posts

    67,588
  • Joined

  • Last visited

  • Days Won

    707

Everything posted by JorgeB

  1. That would only happen if you also lost the appdata folder.
  2. Rebuild was successful, because you have dual parity, and disk8 appears to be really failing so it needs replacing. It's ratter common since all drives are read during a rebuild, including parity, dual parity saved your butt here.
  3. The dual in the table refers to the rank, but yes, since your dimms are dual rank max speed is 2400Mhz. Parity check is also a pretty good test, only acceptable result is 0 errors, note that it's normal for the first check after the problem is solved to still find errors.
  4. Not sure, but it suggests the backup wasn't OK, you'll likely need to re-create the VM, you can use the existing vdisk if you use the same configuration.
  5. Libvirt if for VMs, for dockers you can just restore them: https://forums.unraid.net/topic/57181-docker-faq/?do=findComment&comment=564309
  6. Ryzen with above spec RAM is known to corrupt data, see here, if just lowering to max supported speeds doesn't solve it run memtest.
  7. Disk3 having the same UUID as disk2 can't be a coincidence, so something happened there, only possible recovery option would probably be a file recovery util.
  8. copy /mnt/disk2/Documents/backups/domains_backup/libvirt.img to /mnt/disk3/system/libvirt/libvirt.img
  9. The one from /mnt/user and /mnt/disk3 is the same file, if the current one is empty worth trying the backup one, just copy over it, but first disable VM service.
  10. There's only one on disk3, so older one was deleted/replaced, do you know if the one from the backup is recent? Worth trying.
  11. Appdata is set to only use disk4, and there isn't a disk4, remove that.
  12. Log suggests you are using new docker and libvirt images, please post output of: find /mnt -name libvirt.img
  13. Nothing jumps out, you can try re-creating the docker image.
  14. Yes. It's difficult to say, it could get better, it could get worse, one thing you can do is to clone the that disk with ddrescue after the parity is built, if no errors great, if there are errors you can find out which files are affected.
  15. That suggests a network issue, though strange if iperf is normal.
  16. Do you mean it was also slow transferring from a USB device? And it was USB 3.0? Since you don't have parity try a transfer form one array disk to the other, you can do that with Windows after enabling disk shares ( Settings -> Global Share Settings), note only transfer from a disk share to another disk share.
  17. Feb 23 15:16:40 HakkaFarm kernel: XFS (md3): Filesystem has duplicate UUID 7ef05469-45c6-4921-be50-a5c727615728 - can't mount This is why it's not mounting, post output of blkid
  18. Syslog starts over after a crash, if it continues to happen try this.
  19. I also have a few HDD based raid pools, and depending on what you're going to use them performance can be good, like for reading or writing large files, it's just never has good as an SSD for IOPS.
  20. Doesn't make much sense, if it's not the network you shouldn't get the same speed with all devices, if possible try with a different source PC.
  21. That's expected, once a disk is disable it needs to be rebuilt., disk itself looks OK, emulated disk is mounting and if data looks correct you can rebuild on top, I would still recommend replacing/swapping the cables to rule them out before rebuilding.
  22. If it happens always to the same filesystem I would recommend backing up that disk (or moving the data to other disks) and re-formatting.
  23. Disk dropped offline, so most likely a power/connection issue, but because of that there's no SMART report, so check connections and post new diags.
×
×
  • Create New...