Jump to content

JorgeB

Moderators
  • Posts

    67,719
  • Joined

  • Last visited

  • Days Won

    708

Everything posted by JorgeB

  1. If parity swap is the adequate procedure for what you need you can disconnect the disabled disk.
  2. It's not, but ddrescue might still be able to recover most data. You can, though ddrescue might be have a better chance of recovering more data, especially if the disk keeps getting worse with access. If the disk is really failing like it looks that won't work because there will be read errors on disk1, so parity won't be able to sync correctly.
  3. To get the array back to running you can do a new config (with or without parity), new disk1 will need to be formatted, you can then try ddrescue on old disk1.
  4. v6.9.2 has some known issues with spin down, suggest going back to v6.9.1 or trying v6.10-rc2.
  5. There's a chance of recovery but only if you use a deleted file recovery util, like UFS explorer or similar. Docker image can easily be recreated.
  6. Forgot to mention, cache filesystem is corrupt, for btrfs is best to backup and reformat, I see that you're running Ryzen with overclocked RAM, that's a known cause of data corruption, see here and adjust RAM speeds accordingly.
  7. You formatted disk4, formatting is never part of s rebuild, there's a warning about it: When you have an unmountable this the correct thing to do is to check filesystem.
  8. Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enable, top right)
  9. Marvell controllers are not recommended, especially connected to a SATA port multiplier, avoid both.
  10. That means it's using RAID firmware, ideally you'd crossflash to IT mode, there's a thread about that, but it's more complicated than just an update, and it can't be done inside Unraid, alternatively update it with RAID firmware to 20.00.07 and see if it helps.
  11. You can try a full disk write, it might help or not.
  12. I would suggest upgrading to v6.10-rc, it includes newer xfs-progs, then try repairing the fs again.
  13. Please use the existing plugin support thread:
  14. No, they all will have the same exact capacity, brand/model doesn't matter, except some drives that come from USB enclosures.
  15. You can share the flash drive over SMB. It's a fairly safe procedure, maybe a power failure during could cause issues.
  16. Unraid won't detect that share (or shares), so there's also no warning, independent of the pool being redundant or not.
  17. That's OK if you mount the disk read only, you can do that with UD, don't mount read/write or some data will be changed just by mounting/unmounting and that can cause issues.
  18. Looks like it dropped offline, you can try power cycling the server, if the disk comes back online run the command again (check the drives identifiers are still the same, if not adjust as necessary), use the same log file and it will resume.
  19. Try v6.10-rc2, some hardware has issues with some kernel/Unraid driver releases.
×
×
  • Create New...