Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,600

  • Joined

  • Last visited

  • Days Won

    707

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    Also make sure you try without the mover plugin installed.
  2. JorgeB
    There can't be a share named cache, private share is correctly configured, so enable mover logging, run the mover an post new diags.
  3. JorgeB
    I saw parity, disk0, didn't check for more disk errors after that.
  4. JorgeB
    Disk disconnected and reconnected again, this is usually a connection/power problem.
  5. JorgeB
    Please post the diagnostics: Tools -> Diagnostics and also list the share names you expect data to be moved to the array.
  6. JorgeB
    Unfortunately there's nothing logged about the crash, one thing you can try it to boot the server in safe mode with all docker/VMs disable, let it run as a basic NAS for a few days, if it still crashes it's likely a hardware problem, if it doesn't start turning on the other services one by one.
  7. JorgeB
    This issue can usually be fixed by doing the following: -stop array -unassign the problem cache pool member -start array -stop array -re-assign it to the pool -start array This is fairly safe to do but always good to make sure backups are up to date just in case, and if that doesn't work post new diags.
  8. JorgeB
    That's what I said, disk will get disable sooner or later, and you'll get a notification then, if if you have disks regularly disconnecting you have other issues.
  9. JorgeB
    9211 is perfectly capable for 8 disks, it can only be a bottleneck with SSDs or SAS expanders.
  10. JorgeB
    This should be posted in the existing plugin support thread, but you'll need to have some patience as bonienl was away for some months and is still catching up with the forums.
  11. JorgeB
    You can do that, but need to copy the files manually, since the mover can't do it from pool to pool
  12. JorgeB
    It's logged as as disk problem, run an extended SMART test on disk7 and/or swap cables with a different disk
  13. JorgeB
    Please post the diagnostics: Tools -> Diagnostics
  14. JorgeB
    It's not officially supported but it woks, with the lack of trim limitation. Plugin doesn't help, it can't trim array devices. I have a small SSD only array, parity plus 4 data devices, mostly for testing.
  15. JorgeB
    Please be patient, he's just one guy doing this for free in his spare time and probably still has a lot of catching up to do.
  16. JorgeB
    Yes, that's normal, it's in the release notes, but glad you sorted it.
  17. JorgeB
    Moved to a more appropriate forum. You can see some real world performance numbers below, they were done using Unraid but should be very similar with any OS. https://forums.unraid.net/topic/41340-satasas-controllers-tested-real-world-max-throughput-during-parity-check/
  18. JorgeB
    You get a notification when a disk is disabled and/or there were read or write errors.
  19. JorgeB
    That suggest the destination filesystem doesn't support permissions, e.g. exFAT
  20. JorgeB
    Click in "Add Pool"
  21. JorgeB
    Do you mean for a cache disk? Array disk will get disable, sooner or later after that.
  22. JorgeB
    AFAIK there's nothing on v6.9.x that makes the server more vulnerable, here's one example of a user who got hacked still on v6.8.x, what I suspect is that there is currently one or more hackers actively looking for open Unraid servers.
  23. JorgeB
    Both crashes appear to be related to the NVMe device, look for a BIOS update.
  24. JorgeB
    Mar 23 10:33:20 unNAS emhttpd: shcmd (1726): umount /mnt/cache Mar 23 10:33:20 unNAS root: umount: /mnt/cache: target is busy. Something was still using /mnt/cache, it failed to unmount without forcing.
  25. JorgeB
    Unclean shutdown saves the diags in the flash drive (logs folder), they might give a clue for the reason.
×
×
  • Create New...