Jump to content

johnnie.black

Moderators
  • Content Count

    25075
  • Joined

  • Last visited

  • Days Won

    308

johnnie.black last won the day on July 7

johnnie.black had the most liked content!

Community Reputation

2817 Hero

About johnnie.black

  • Rank
    tee-tee jorge

Converted

  • Gender
    Male

Recent Profile Visitors

10059 profile views
  1. See here, it should be enough to run a stable Ryzen based server.
  2. Max officially supported RAM speed with 4 DR DIMMs is 2667Mhz, make sure you won't go above that.
  3. This would be a question to ask on the UD support thread:
  4. The files failing to move have checksum errors, i.e., are corrupt, btrfs gives an i/o error when corruption is detected so you now something is wrong, you need to delete those files and restore from backups, this can't happen out of the blue, so if it keeps happening you might have a hardware problem, like bad RAM.
  5. Format button is next to the start/stop array buttons.
  6. It appears to be a GUI problem, clear process concluded: Jul 10 00:36:30 Tower kernel: md: recovery thread: clear ... ... Jul 10 12:56:51 Tower kernel: md: sync done. time=44421sec Jul 10 12:56:51 Tower kernel: md: recovery thread: exit status: 0 Not sure the disk was added to the array though, you'll need to reboot to find out.
  7. All files on the diags are empty, reboot and try to get new diags as soon as the issue starts.
  8. That process is normal and part of Unraid's user shares, you need to try and find what is causing it to use a lot of CPU, anything mapped or using /mnt/user/xxx will be using that process.
  9. You can do a new config, you won't lose anything except what was on those disks, including any docker data/appdata if it was there.
  10. Can't see any errors on the log, it's like they aren't even connected until you replug them, try a different USB controller if available, also anything changed hardware or software in the last week when this issue started?
  11. Yes, though you'd still want devices with deterministic read zeros after trim support, since when support does get implemented it will likely only work with those devices.
  12. It won't be wiped as long as it was formatted with a relatively recent UD release, like in the last couple of years or so, and even if an older release was used it won't be, it will just be unmountable due to invalid partition layout.
  13. First thing would be this again, I assume you've run before when it was detecting 1 or 2 errors, now it appears to be worse and the errors are on different sectors which is consistent with a RAM issue, with more errors it might be easier to detect any RAM issue.
  14. No, each array data disk is still an independent filesystem, what you can do with the latest betas is to have multiple btrfs storage pools, each pool is independent and can use one of the available btrfs profiles, they behave like the normal cache pool.
  15. Yep, that's one of the reasons you don't recommend RAID controllers with Unraid, also note that if you change those disks to a different controllers they will likely need to be rebuilt, or at least require a new config.