Jump to content

JorgeB

Moderators
  • Posts

    67,540
  • Joined

  • Last visited

  • Days Won

    707

Everything posted by JorgeB

  1. One possibility is the one mentioned in the linked FAQ, system share is by default NOCOW, if the other device comes back online, even for a little while, it can corrupt the any NOCOW data with the out of sync device.
  2. It is, that's why cache was still working with a single device, but you still need to fix it.
  3. I didn't say to RMA the devices, but it's not the number of times it's written the matters, every SSD has a life counter on SMART, as long as that is still not at or over 100% they have to honor the warranty.
  4. Diags are after rebooting, what recovery option from the FAQ are you trying?
  5. That's the only way for now. For single cache yes, for pools no.
  6. You can install a Windows backup util and then create an image, e.g. Macrium Reflect or your favorite backup utility.
  7. Crazy number of reads/writes usually happen after a device drops offline, usually a cable issue, replace both cables on those disks.
  8. You could create an image with dd (with the VM off).
  9. It's not about that, if there is a hardware problem, some sectors were being wrongly corrected, so when that's solved it's normal for the 1st check to still find errors, but if the 2nd one still finds more then it's still not fixed.
  10. If there were issues before this check is expected to correct some errors, if the issue is fixed next one should find 0 sync errors.
  11. A report about that issue already exists:
  12. Cache pool is only one device, despite what the GUI shows, there are hardware issues with the other: Nov 11 10:18:57 Hal9000 kernel: BTRFS info (device sdb1): bdev (null) errs: wr 545786, rd 0, flush 87, corrupt 0, gen 0 See here for more info.
  13. Look for the controller manual/BIOS, it will never be supported with onboard SATA ports, or basic SATA port controllers.
  14. It's worth a try, there have been several issues with latest reiserprogs, though AFAIK latest one is working correctly.
  15. Some controllers have this option, usually called staggered spin up, but nothing that can be controlled directly by Unraid.
  16. You need to re-format the disk (and parity will be updated accordingly), to do that stop the array, click on that disk, change the filesystem to a different one, start array, that disk will appear unmountable and can be formatted next to array start stop button, then repeat the process, change the filesystem back to the original, start array, format once more, now you can restore the data.
  17. https://wiki.unraid.net/Upgrading_to_UnRAID_v6
  18. Most part is likely for the new reflink support, could be others, don't really follow xfs development.
  19. This means there's an unknown issue with the filesystem (or a bug with reiserfsck for this situation), either way not easy to fix, basically you'd need to ask for help to a reiserfs maintainer.
  20. Like I already posted on your other topic that error is fatal, the disk needs to e re-formatted.
  21. You have an invalid share name spamming the log, delete share restore2#015 and its cfg file (flash/shares/restore2#015.cfg), reboot and post new diags.
  22. You can get two 15 days extensions, so the free trial can be up to 60 days.
  23. That suggests you're trying to add a mounted disk, if you're trying to use multiple pools you should update to the latest beta that has native support for multiple pools.
×
×
  • Create New...