Jump to content

JorgeB

Moderators
  • Posts

    67,877
  • Joined

  • Last visited

  • Days Won

    708

Everything posted by JorgeB

  1. This helps in some cases, so worth trying first, also look for a BIOS update.
  2. It's a known issue with different size devices, used and free space will be correct.
  3. Make sure the go file is stock, any docker containers could also be worth checking/re-creating.
  4. Only if you get the same call trace as posted in the 1st post.
  5. You didn't mention, nothing was written to the array since old disk1 was removed?
  6. I'm not an advanced docker user, can you easily install something like fio and run it in a docker?
  7. You can recreate the array with old disk1, but it will only work to rebuild disk3 if the array is unchanged since the disk was removed, i.e., no writes done to the array, though note that a small number of writes is always made by just starting the array, so even without any extra writes there are no guarantees, but it might be worth trying if the disk is not very damaged.
  8. Oct 27 10:04:54 core kernel: ahci 0000:02:00.0: AHCI controller unavailable! Problems with the Marvell controller, make sure it's well seated or try a different PCIe slot if available, also note that Marvell controllers are not recommended so if it continues causing problems best to replace it.
  9. It's not difficult to generate high i/o, it would be more difficult to replicate if it's docker with high i/o, anyone having this issue without using docker, or at least without using high i/o docker containers, like torrents, etc?
  10. That suggests high i/o might not be the cause, unless it's a delayed crash.
  11. Looks more like a power/connection problem but since the disk dropped offline there's no SMART, check/replace cables and see if it comes back online, then post new diags.
  12. Stop and restart the array, if it still doesn't expand post new diags.
  13. Flash drive problems: Oct 20 18:19:39 CoppaNAS kernel: FAT-fs (sda1): error, fat_get_cluster: invalid start cluster (i_pos 0, start d82b2156) Run chkdsk on it, also uninstall the Nerdpack plugin, not compatible with v6.11.
  14. SMART test failed, you should replace the disk.
  15. Is this disk1 or disk10? No disk10 is assigned and there are no disk related errors on the syslog. Disk11 is failing and needs to be replaced.
  16. Assuming all was done correctly that suggests parity was far from valid with that config.
  17. Did you save the diags, or didn't reboot? Those errors must be logged.
  18. For the docker containers you just need to copy the appdata folder, docker image can be recreated and the rest is in the flash drive.
×
×
  • Create New...