Jump to content

JorgeB

Moderators
  • Posts

    67,541
  • Joined

  • Last visited

  • Days Won

    707

Everything posted by JorgeB

  1. Are you asking me? If it's a parity check then please post diags.
  2. Flash drive troubles, try running chkdsk first, if it doesn't fix it redo it, if it still doesn't replace it.
  3. It will if it's a parity sync, parity is invalid until the sync is done.
  4. Please post the diagnostics: Tools -> Diagnostics
  5. You can also post the diags, just to check that the HBA is being initialized correctly.
  6. Make sure you're using the correct cables, you need forward breakout cables, reverse breakout look the same but won't work for this.
  7. Those are normal, one thing to keep an eye on for SAS devices is this: Elements in grown defect list: 0 It should be 0 or a low number and stable, large number and/or it keeps rising it's a very bad sign.
  8. Unlikely that any filesystem resize will work due to being damaged, you can resize the partition by creating a new one on top of the existing one, same start sector but using the full disk.
  9. According to one photo it's 4 x a 2 port Asmedia controllers, if that's the case it should be fine, but description is all over the place, one place mentions 6 port controller and x2 while the picture is clearly of an x4 controller.
  10. Similar to rebuilding, since the disk is being emulated if there are problems in another disk there also will be during the copy, but at least you'll know which files have problems, since you'll get an i/o error on those.
  11. Nothing obvious on the log, you should post the error on the CA support thread like asked.
  12. Make sure you enable UEFI boot during flash creation, or enable CSM (legacy) boot on the board.
  13. You can rebuild first if you do it to a new disk, keep the old one intact, but if there are errors during the rebuild no way of knowing what files are corrupt, unless you have pre-existing checksums or are using btrfs.
  14. Please post the diagnostics: Tools -> Diagnostics
  15. You can also use ddrescue to clone the disk(s) and identify any corrupt data.
  16. SATA controller is bound to vfio-pci: 08:00.0 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] [1022:7901] (rev 51) Subsystem: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] [1022:7901] Kernel driver in use: vfio-pci Kernel modules: ahci Unbind it.
  17. Unlikely to help, but you could try updating.
  18. Thinking more on this not sure resizing the partition will be enough, might also need to resize the filesystem, you should be able to do that by recreating the superblock after the partition is resized, but try just the partition first and post back.
  19. Though I never tried it I would guess best bet would be to clone that disk to a larger one with dd, then manually resize the partition, then run rebuild tree again, that should work.
×
×
  • Create New...