Jump to content

JorgeB

Moderators
  • Posts

    67,662
  • Joined

  • Last visited

  • Days Won

    707

Everything posted by JorgeB

  1. I have no idea, if the files were really moved source files would be deleted, if it was a specific fodler/share you can run rsync with --remove-source-files so any existing files on dest will be skipped but source files that already exist on dest will still be deleted from source.
  2. You might be able to use it again once v6.10 is released.
  3. Please post diagnostics grabbed during a slow transfer, also post the rsync command used.
  4. That's not uncommon with SSDs, they fail after a power off, and they fail much less than disks but when they fail they usually fail completely, no way that I know of recovering data other than using professional data recovery services.
  5. That's usually a USB thing, though some controllers/bridges work better than others. They look like a connection issue, usually it's a bad SATA cable, replacing them should help.
  6. That was normal because of the disks dropping, but you should worry about disks dropping in general, also there area lot of ATA errors on the log.
  7. Update to latest stable version, then post new diags after array start.
  8. This means that filesystem is already mounted, likely the USB device dropped offline without a clean unmount, rebooting the server should fix it, if it doesn't post the output of: blkid after rebooting.
  9. ? That's what the manual says, SATA1 will be disable if a SATA M.2 device is used, you're using an NVMe (PCIe) device.
  10. It counts as an overclock every time it's above AMD's max officially supported speeds, and it's a known source of data corruption with Ryzen. No because usually both copies are corrupted, if it could be a scrub would repair it, this means it can't:
  11. That will happen if the FS is set to "auto", the bigger issue is the superblock not being found on disk2, that suggests no valid filesystem is there.
  12. Both 8TB disks have the same serial number (and it's all zeros), that won't work with Unraid, each device needs a unique ID.
  13. Yep, still same error, if no one else has any ideas better to contact LT support.
  14. Look for one of the recommended LSI HBAs listed above.
  15. As you prefer, if it just started you can cancel and run it aftter.
  16. Enable syslog mirror to flash then post that log after a crash.
  17. Other than that I'm not seeing anything out of the ordinary, can you try without the Nvidia driver? One of just two google results I found about that error mentioned an issue with that.
  18. You have the same error, and I don't remember ever seeing that error before, if it's not the flash drive don't have more ideas.
  19. If you're removing parity do it before adding the new drives, or they will be cleared before they can be used. Before starting the array check "parity is already valid" or it will be resynced, you can still run a check after to confirm all is well.
  20. Pool replacement is broken in v6.9.x, you could remove the failed drive then add a new one, but like mentioned nothing for now points to bad drive.
×
×
  • Create New...