JorgeB

Moderators
 View Profile  See their activity

  • Posts

    61513

  • Joined

  • Last visited

  • Days Won

    648

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    Docker image is corrupt, delete and re-create: https://docs.unraid.net/unraid-os/manual/docker-management/#re-create-the-docker-image-file Also see below if you have any custom docker networks: https://docs.unraid.net/unraid-os/manual/docker-management/#docker-custom-networks
  2. JorgeB
    Enable mover logging, run the mover, look at the syslog. Reboot, if it still gets created it's pretty sure there's a container mapped to that.
  3. JorgeB
    Check filesystem on disk1, run it without -n, and if it ask for -L use it.
  4. JorgeB
    That looks like a hardware problem, but it can be difficult to troubleshoot remotely, if you have some more spare parts you can try besides the PSU do it.
  5. JorgeB
    If it doesn't boot it's a different issue, that line won't affect booting.
  6. JorgeB
    Did you run the server with either stick and it still crashed?
  7. JorgeB
    Pool is not set as redundant in the cfg, but that can sometimes be incorrect, assuming it is redundant, it should mount if you do this: unassign the pool device start array stop array re-assign the pool device start array If it doesn't mount post new diags.
  8. JorgeB
    I would assign both as pools, so that trim is supported, and assign an old flash drive as the required array device.
  9. JorgeB
    That would be OK, assuming a single stream iperf test, still, if the Windows explorer transfer graph still looks like the above, it still points to a network problem (or the client PC), when the network is not the issue, you see full speed for the first few seconds of a transfer, while its being cached to RAM, and if it slows after that then it would be the devices not being able to keep up with the required write speed.
  10. JorgeB
    Usually a power cycle is required for NVMe devices, not just a restart. Instead of that, which will wipe the other device, I would recommend physically removing the device, in case you still need it.
  11. JorgeB
    Please post the diagnostics.
  12. JorgeB
    Can still be a disk issue, they can have slower zones.
  13. JorgeB
    It doesn't look to me like device problem. it just dropped offline, but you can try to remove it to see if it's better with just the other one.
  14. JorgeB
    If you have a key problem you need to contact support, forum can't help with license issues.
  15. JorgeB
    The diags posted only have a rebuild, and there weren't any disk errors, but if it's for example RAM problem nothing would be logged anyway.
  16. JorgeB
    Yes, that's fine.
  17. JorgeB
    No errors logged, and SMR disks should perform normally on reads, could be an issue with one of them, you can pause the sync and run the diskspeed docker to see if they are performing normally there.
  18. JorgeB
    Btrfs usually work fine with good hardware, but try zfs, if you also have issues with that, there could be an underlying hardware problem.
  19. JorgeB
    https://forums.unraid.net/topic/57181-docker-faq/page/2/#comment-566088
  20. JorgeB

    Dashy

    JorgeB replied to jag5cof's topic in General Support

    See if there's a support thread for that container:
  21. JorgeB
    You could change them, but probably best to just wait.
  22. JorgeB
    Apr 25 04:47:34 PLEX-PROD kernel: BTRFS: error (device nvme0n1p1: state A) in __btrfs_free_extent:3072: errno=-2 No such entry Apr 25 04:47:34 PLEX-PROD kernel: BTRFS info (device nvme0n1p1: state EA): forced readonly Cache pool went read only, with btrfs recommend backing up and reformatting the pool.
  23. JorgeB
    Run it again without -n, and if it asks for -L use it.
  24. JorgeB
    If it's a RAM problem, all data can be affected, but since you don't have any other btrfs or zfs filesystems, only the docker image is detecting data corruption.
  25. JorgeB
    Start by running memtest, that could be a RAM problem.