Jump to content

JorgeB

Moderators
  • Posts

    67,428
  • Joined

  • Last visited

  • Days Won

    706

Everything posted by JorgeB

  1. If there are sync errors you'll need to run a correcting check, auto check is non correct, that can be done before or after the filsystem check.
  2. Is that an SMB mount? Try to another local device first.
  3. rsync isn't built for speed, try pv
  4. User or disk share? If user try a disk share.
  5. Pleas post the diagnostics: Tools -> Diagnostics.
  6. Same, I have a 6 SSD RAID5 pool, get around 800MB/s each way.
  7. That will happen if the fs for that device is set to the original filesystem, set them to auto by clicking on the device on the main page.
  8. Like mentioned on the link above with SSDs it's usually a cable/connection issue
  9. And it's not the first time it dropped, see here for better pool monitoring.
  10. It's likely a faster model, or the other ones are under performing.
  11. Every rebuilt disk will have the same filesystem as the disk it's replacing, it can only be like that, the default fs is for added drives.
  12. Are both detected on the system devices? Also, please post the diagnostics: Tools -> Diagnostics
  13. It's a known issue and it should be corrected on the next release.
  14. Docker image is corrupt, delete and re-create, see docker FAQ if needed, cache filesystem seems OK for what I can see.
  15. Scrub can't help in this case, see the FAQ, btrfs restore is the most likely to work for this.
  16. Filesystem is corrupt, you can try btrfs restore on the same FAQ entry.
  17. Yes, but only shares set to cache="yes" will be moved.
  18. 9207 is plug'n play, devices are tracked by serial number, not where they are connected, just don't use RAID controllers.
  19. Unraid doesn't stripe data, it writes to a single disk (plus parity) so max write speed is the speed of the slowest disk involved (using turbo write).
  20. Same users have issues getting a DHCP address with latest release, try setting a static address.
  21. Just for future reference, the cache problem was because you went from 4 devices to 1, you can only remove one device at a time from a redundant pool, and after that you re-assigned the old devices but without "forgetting" the existing pool, so they were erased.
  22. Note that the total read speed is this high because you have turbo write and it reads all disks when there are array writes, you just need to find who/what is doing that, what @jonathanmsuggested is the first thing to try, you can also boot with GUI mode to still have the GUI after disconnecting the server form the LAN.
×
×
  • Create New...