Jump to content

JorgeB

Moderators
  • Posts

    67,540
  • Joined

  • Last visited

  • Days Won

    707

Everything posted by JorgeB

  1. You'd need to use a different PC to flash, also look for option on your BIOS to not show the OPT ROM, though this is mostly available on server boards, but it might be there.
  2. You can also delete the HBA BIOS, it's not needed for Unraid.
  3. NIC is not being detected, this is a hardware issue.
  4. Try enabling it manually, by editing /boot/domain.cfg and changing SERVICE="disable" to "enable", then reboot, you should also update to latest release.
  5. You can use for example Midnight Commander (mc in the console)
  6. Flash drive problems, try running chkdsk on it.
  7. But you're still overclocking the RAM, respect max supported speeds here.
  8. Full diags might give some clues, but btrfs going corrupt multiple times without a reason usually indicates a hardware problem, like bad RAM.
  9. Like mentioned it only works for a pool, it looks like the partition layout isn't checked for pools, probably some oversight, or maybe on purpose, anyway you can have a single device btrfs "pool" if the pool slots are set to more than 1.
  10. When we ask for diagnostics we prefer the full diagnostics (tools -> diagnostics) but for this case the syslog is enough, it appears to be a controller problem/incompatibility, it's only detected as a two port controller, one of them is detecting a virtual device connected, the other no link, since you only need two ports I recommend you replace it with a 2 port Asmedia controller, those work fine.
  11. No, unless the device ID changed, like when using a RAID controller.
  12. Cancel and try again after updating xfsprogs to latest, you can see the instructions here, but use the current release here.
  13. Yes, if all members are there and in blue it will import any existing pool, though if you dind't already start the array once with no cache devices assigned to make sure pool config is "forgotten".
  14. Best way is to start the array with all the original pool members assigned.
  15. Replace/swap cables on that drive, can't see which one is ATA5 since log rotated.
  16. That controller has a SATA port multiplier and is not recommended, but it show detect the disks, diags might give some clues.
  17. This means the file already exists on dest, you need to delete one of them.
  18. Disk5 looks fine, there are a few CRC errors but those a connection problem, not disk, you can acknowledge them on the dashboard.
  19. I misunderstood your issue, sorry, not a network guy so something I can't help with.
  20. Everything looks correct to me, enable mover logging, run the mover and post new diags.
  21. You should still be able to use a different SATA end, Intel ATA errors are gone now, and since the emulated disk is mounting and if contents look correct you can rebuild on top.
×
×
  • Create New...