Jump to content

JorgeB

Moderators
  • Posts

    67,504
  • Joined

  • Last visited

  • Days Won

    706

Everything posted by JorgeB

  1. Run xfs_repair on disk14, you might also try it on the emulated disk18.
  2. If it happens again please post diags, before rebooting.
  3. You can try btrfs restore, if that doesn't help you can look for help on IRC or the mailing list, also mentioned on the same FAQ entry.
  4. Showing "Pool" for single device cache is normal with the new beta.
  5. That can't be since no disks are mounted, reboot (force it needed) and start in safe mode but not maintenance mode, post new diags if they still don't mount.
  6. Please post the complete diagnostics: Tools -> Diagnostics, ideally before rebooting.
  7. You are having multiple disk errors, you need to fix that first or it will make any rebuild difficult, looks more like a power/connection problem, if you have it try another PSU and/or another controller, also check/replace all cables.
  8. You can use the Unassigned Devices plugin, note that it requires UD+ add-on to support HFS+
  9. You can use true HBAs like the LSI, that HP is a raid controller, even when in HBA mode, and those can have issues, one of them you just experienced, changing the disks identification, that doesn't mean you can't use it, just should be aware of the implications.
  10. It might work but it's not recommended, we don't recommend using Marvell controllers and same goes for SATA port multipliers, that one has both.
  11. Run chkdsk on the flash drive, if it doesn't help try also booting in safe mode.
  12. No, this just means the pool itself wasn't the reason for the performance issues.
  13. At least you now know where the problem is, if you can try a different NIC on the PC, it can also be an OS issue, re-install might help.
  14. Assuming the pool is raid1 you could remove one of the old devices first, then add the new one, then repeat.
  15. I'll close it now, please re-open if needed.
  16. You need to re-enable the disk, also good idea to replace the SATA cable first since there are a few CRC errors.
  17. We don't recommend using RAID controllers, this is one of the reasons, doing a new config and re-assigning all the disks should solve the problem, but note that some RAID controllers also interfere with the MBR/partitions, in that case you'll get all unmountable disks, if that happens it can usually be resolved by rebuilding one disk at a time so Unraid can recreate the partitions but you'll run into the same issue if you replace the controller with a different one in the future.
  18. Since the partition info is outside parity and can be recreated by Unraid, rebuilding one disk at a time should work, assuming only the partition info was damaged, try this, stop the array, unassign one of the data disks, start the array, if the emulated disk mounts and contents look correct rebuild on top, when done repeat for the other disks, always one at a time.
  19. See here if you can have both old and new devices connect at the same time, you can have the pool online during the replacements.
  20. Macvlan call traces are usually the result of having dockers with a custom IP address:
  21. Check that "power supply idle control" is correctly set, more info here.
  22. Similar problem, assuming it's well seated best bet would be to try the latest Unraid beta, newer kernel might help, if it doesn't get a different model NVMe device, if possible.
  23. Sounds more like a controller problem, what controller are you using?
  24. Problem with the HBA: Aug 29 15:15:20 Tower kernel: mpt2sas_cm0: SAS host is non-operational !!!! Make sure it's well seated and sufficiently cooled, you can also try a different PCIe slot if available.
×
×
  • Create New...