解决成像问题

  • 2021年12月17日
  • 0答复
  • 67意见
r
秩
UserLevel 2
徽章 +4

当群集中一个或多个节点的成像失败时，进度条将变红，并出现红色检查，将出现在Hyprovisor地址字段旁边的任何未成功成像的节点。失败的可能原因包括以下内容：

  • 检测到一种故障。检查与IPMI（裸机工作流程）的连接。

  • 存在网络连接问题，例如以下内容：

    • 连接间歇性下降。如果间歇性失败持续存在，请寻找冲突的IP。

    • [仅Hyper-V] Samba服务没有运行。如果Hyper-V显示警告说它无法安装安装共享，请重新启动SAMBA命令“ Sudo Service SMB重新启动”。

  • 在管理程序或凤凰制备阶段，粉底耗尽了磁盘空间。通过删除不需要的ISO图像来释放一些空间。此外，基础崩溃可能会留下A /TMP /TMP*目录，其中包含可以卸载（如有必要）并删除的ISO映像的副本。基础需要9 GB的Hyper-V和3 GB的自由空间，用于ESXI或AHV。

  • 主机启动但返回错误，指示达到基础VM的问题。该消息的消息有所不同。例如，在ESXI上，您可能会看到一个ks.cfg：第12行：“ /.pre”脚本带有错误错误消息。确保将主机分配给与基础VM或Multihoming配置的同一子网上的IP地址。还要检查IP地址冲突。

要识别和解决成像问题，请执行以下操作：

  1. 有关该问题的信息，请参见单个日志文件。

    • 基础日志的控制器VM位置：〜/data/logs/foundation和〜/data/logs/fistival.out [.timestamp]

    • 基础日志的裸金属位置：/home/nutanix/fistival/log

  2. 解决问题后，请单击图像节点（裸金属工作流）按钮。

  3. 图像节点按钮（裸金属）_Tlj4MK8uA7QsukNsrvhh5z50fsD8DYRyg_ReT2UYZXffF42z_ND0tlkeVCFu0NrExKxlcXS9jTEN_YREUQx5rVKyKvsBSG4IzqRY9n6Q-fLQNA8zwK7V2t5EvCLj3TSS63fPCUL

  4. 根据需要重复上述步骤，以解决任何其他成像错误。
    如果您无法解决一个或多个节点的问题，则可以一次对这些节点进行映像（联系支持）。

拉阿吉
\u00a0<\/h1>

When imaging fails for one or more nodes in the cluster, the progress bar turns red and a red check appears next to the hypervisor address field for any node that was not imaged successfully. Possible reasons for a failure include the following:<\/span><\/p>

  • \t

    A type of failure was detected. Check connectivity to the IPMI (bare-metal workflow).<\/span><\/p>\t<\/li>\t

  • \t

    There are network connectivity issues such as the following:<\/span><\/p>\t

    • \t\t

      The connection is dropping intermittently. If intermittent failures persist, look for conflicting IPs.<\/span><\/p>\t\t<\/li>\t\t

    • \t\t

      [Hyper-V only] SAMBA service is not running. If Hyper-V displays a warning that it failed to mount the install share, restart SAMBA with the command \"sudo service smb restart\".<\/span><\/p>\t\t<\/li>\t<\/ul><\/li>\t

    • \t

      Foundation ran out of disk space during the hypervisor or Phoenix preparation phase. Free up some space by deleting unwanted ISO images. In addition, a Foundation crash could leave a \/tmp\/tmp* directory that contains a copy of an ISO image that you can unmount (if necessary) and delete. Foundation requires 9 GB of free space for Hyper-V and 3 GB for ESXi or AHV.<\/span><\/p>\t<\/li>\t

    • \t

      The host boots but returns the error indicating an issue with reaching the Foundation VM. The message varies per hypervisor. For example, on ESXi you might see a ks.cfg:line 12: \"\/.pre\" script returned with an error error message. Ensure that you assign the host an IP address on the same subnet as the Foundation VM or multihoming is configured. Also check for IP address conflicts.<\/span><\/p>\t<\/li><\/ul>

      To identify and resolve imaging problems, do the following:<\/span><\/p>

      1. \t

        See the individual log file for any failed nodes for information about the problem.<\/span><\/p>\t

        • \t\t

          Controller VM location for Foundation logs:~\/data\/logs\/foundation and~\/data\/logs\/foundation.out[.timestamp]<\/span><\/p>\t\t<\/li>\t\t

        • \t\t

          Bare metal location for Foundation logs:\/home\/nutanix\/foundation\/log<\/span><\/p>\t\t<\/li>\t<\/ul><\/li>\t

        • \t

          When the issue is resolved, click the <\/span>Image Nodes<\/strong> (bare metal workflow) button.<\/span><\/p>\t<\/li>\t

        • \t

          Image Nodes Button (bare-metal)<\/strong>\"_Tlj4MK8uA7QsukNsrvhh5z50fsD8DYRyg_ReT2UYZXffF42z_ND0tlkeVCFu0NrExKxlcXS9jTEN_YREUQx5rVKyKvsBSG4IzqRY9n6Q-fLQNA8zwK7V2t5EvCLj3TSS63fPCUL\"<\/span>
          \t\u00a0<\/p>\t<\/li>\t

        • \t

          Repeat the preceding steps as necessary to resolve any other imaging errors.<\/span>
          If you are unable to resolve the issue for one or more of the nodes, it is possible to image these nodes one at a time (Contact Support for help).<\/span><\/p>\t<\/li><\/ol>

          \u00a0<\/p>","quoteUsername":"raaji","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">

0答复

做第一个回复的人！

回复


条款和条件
Learn more about our cookies.<\/a>","cookiepolicy.button":"Accept cookies","cookiepolicy.button.deny":"Deny all","cookiepolicy.link":"Cookie settings","cookiepolicy.modal.title":"Cookie settings","cookiepolicy.modal.content":"We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.<\/a>","cookiepolicy.modal.level1":"Basic
Functional","cookiepolicy.modal.level2":"Normal
Functional + analytics","cookiepolicy.modal.level3":"Complete
Functional + analytics + social media + embedded videos"}}}">
Baidu