Jump to content

JorgeB

Moderators
  • Posts

    67,588
  • Joined

  • Last visited

  • Days Won

    707

Everything posted by JorgeB

  1. If it server shuts down it's likely a hardware probable, like a overheating CPU or a PSU problem.
  2. After restoring appdata to its original location see here: https://forums.unraid.net/topic/57181-docker-faq/?do=findComment&comment=564309
  3. I wanted the output with the array started, but usually duplicate UUID means the disk you're trying to mount is already mounted, so reboot, start the array, and if you still get the same errors post new diags and the output of blkid with the array started.
  4. Parity doesn't have data, so not needed, and the flash drive can't be encrypted.
  5. Click on the docker and look for the support link, more likely to get help if you post there.
  6. Stop all dockers then start one at a time until you find the culprit.
  7. JorgeB

    Darwins

    Please post the diagnostics: Tools -> Diagnostics
  8. I would, since there are several bug fixes and it's very easy to do.
  9. It is in IT mode, but latest firmware is 16.00.10.00.
  10. These are SAS only for now and the foreseeable future, also, and as far as I understand, they are presented to the OS as two 7TB drives, using dual LUNs, so no performance gains with Unraid and if one disk failed you'd lose two assigned drives.
  11. Disk dropped offline, change/replace cables to rule them out see if it happens again to the same disk, disk will need to be rebuilt.
  12. You can still use the new alignment with v6.8 if you use a cache pool, a single device cache can be a "pool" as long as cache slots are set to more than 1.
  13. There are multiple duplicate UUIDs, please post output of blkid
  14. You can do a new config if you want to do it all at the same time, array will be unprotected until the sync finishes.
  15. I would try a different power supply and/or connecting the Seagates to a different controller, like the onboard SATA ports.
  16. It's up to you, btrfs works great with good hardware, and unlike xfs it will easily detect data corruption, but if you don't need any of its features and plan to use a single device you can switch to xfs. Data will remain corrupt, and possibly the filesystem, might be better to recreate.
  17. That rules out the network, or at least it's not the only problem, have you tried copying large files to the array with turbo write enable?
  18. And btrfs is much more sensitive to RAM errors than for example xfs, so much more likely for problems to be detected there first, and a couple of bit flips in the wrong place can destroy a btrfs filesystem.
  19. Yep, try with just one dimm to find the problem one.
  20. Feb 26 09:58:52 Trashnet kernel: BTRFS info (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 0, rd 0, flush 0, corrupt 12722, gen 0 Feb 26 09:58:52 Trashnet kernel: BTRFS info (device nvme0n1p1): bdev /dev/nvme1n1p1 errs: wr 0, rd 0, flush 0, corrupt 17619, gen 0 Both devices are detecting a lot of data corruption, start by running memtest.
  21. https://forums.unraid.net/topic/86337-are-my-smart-reports-bad/?do=findComment&comment=800888
  22. I have two of these: https://www.coolerguys.com/products/lian-li-hdd-mount-kit-model-ex-23n-black-or-silver You could install 6 disks on the 4 bays, but got them a long time ago, so probably discontinued, though there should be something similar.
  23. Nothing else, but one thing I forgot to mention is before doing that make sure cache backups are up to date, just in case.
×
×
  • Create New...