Jump to content

JorgeB

Moderators
  • Posts

    67,600
  • Joined

  • Last visited

  • Days Won

    707

Everything posted by JorgeB

  1. First try to mount it with the UD plugin (with the array stopped).
  2. Is the drive that failed still intact? And are you sure it actually failed, i.e., is is dead or still detected? Also keep in mind that Unraid (or any RAID) is not a backup, you should still have backups of any important data.
  3. Please post the diagnostics: Tools -> Diagnostics
  4. That suggests there were errors on another drive(s) during the rebuild, and the sync errors found after the parity check also support that.
  5. Already replied in your other thread:
  6. Use -L for disk7, disk8 on the other hand appears unfixable, likely there were read errors on a different disk during the rebuild.
  7. With turbo write enable it's possible to get 200MB/s+, I get that when writing to the outer tracks of an array disk in some of my servers.
  8. Syslog is full of CPU NMI events, looks for a BIOS update, also try v6.9.x
  9. It's logged as a disk problem, but there's no SMART report, post a SMART report for disk7.
  10. Log is full of task abort errors, and not just for those disks, any change if you disable disk spin down?
  11. Yep. No, but before you change that data that it refers to snapshots don't take any space.
  12. Initial snapshot need to be sent in full to the dest server: btrfs send /mnt/data/1st_snaphot | ssh root@ip "btrfs receive /mnt/backups" After that you send only the changes: btrfs send -p /mnt/data/1st_snaphot /mnt/data/2nd_snaphot | ssh root@ip "btrfs receive /mnt/backups" and so on.
  13. There's some info here on how btrfs snapshots and send/receive work, difference is there it's sending locally, to send changes to another server you'd use for example: btrfs send -p /mnt/data/old_snaphot /mnt/data/new_snaphot | ssh root@ip "btrfs receive /mnt/backups" There's no GUI support, so you have to use the console or a script.
  14. Yes, you can use btrfs send/receive over ssh, that's how I backup all my servers.
  15. Note it's only not moving from array to pool, it still does from pool to array, even with a space in the name.
  16. It's a bug, mover isn't working for shares with a space in the name, you should create a bug report. As a workaround you can rename the share, using for example an underscore.
  17. Unfortunately you rebooted since the rebuild, did you save those diags by any chance? Still the errors suggest the rebuilt was corrupt.
  18. Share doesn't yet exist on that disk, once it does space will be correct.
  19. According to the mover log there's nothing to be moved, from what share are you trying to move data?
  20. If any rebuild was done after the controller dropping that disk will be corrupt, GUI would show errors on multiple disks, and you'd be notified if system notifications are enable.
×
×
  • Create New...