> For the complete documentation index, see [llms.txt](https://docs.verge.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verge.io/learn-the-platform/zh/mo-kuai-3-an-zhuang/03-installation.md).

# 概述

生产部署的裸机准备、VergeOS 安装演示以及安装后验证。

## 学习目标

在本模块结束时，你将能够：

* **准备裸机硬件** 用于 VergeOS 安装（BIOS 设置、磁盘控制器、网络）
* **执行完整的 2 节点 VergeOS 安装** 使用 USB 启动介质
* **完成安装后验证检查清单** 以确认系统健康
* **排查常见安装问题** 并知道何时升级处理

## 前置条件

* 完成 [模块 1：架构基础](/learn-the-platform/zh/mo-kuai-1-jia-gou-ji-chu/01-architecture.md) —— 了解节点角色、核心架构和集群概念
* 完成 [第 2 模块：容量规划与设计](/learn-the-platform/zh/mo-kuai-2-rong-liang-gui-hua-yu-she-ji/02-sizing-design.md) —— 已选择并确定了硬件范围

## 预计时间

**2.5 小时** （1 小时阅读 + 1.5 小时实验）

## 主题

* [**安装前检查清单**](/learn-the-platform/zh/mo-kuai-3-an-zhuang/01-pre-installation.md) —— BIOS 配置、磁盘控制器模式、网络接口识别以及启动介质准备。
* [**控制器安装**](/learn-the-platform/zh/mo-kuai-3-an-zhuang/02-controller-installation.md) —— 逐步安装节点 1（控制器）和节点 2（控制器），包括网络配置和集群组建。
* [**添加节点**](/learn-the-platform/zh/mo-kuai-3-an-zhuang/03-adding-nodes.md) —— 扩展节点、仅存储节点和仅计算节点。将集群扩展到初始的 2 节点部署之外。
* [**安装后验证**](/learn-the-platform/zh/mo-kuai-3-an-zhuang/04-post-install-verification.md) —— 仪表板健康检查、vSAN 验证、网络连通性、初始配置以及最终部署测试。
* [**实验：2 节点安装**](/learn-the-platform/zh/mo-kuai-3-an-zhuang/lab.md) —— 使用 Terraform playground 或物理硬件在 2 节点集群上执行完整的 VergeOS 安装。


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.verge.io/learn-the-platform/zh/mo-kuai-3-an-zhuang/03-installation.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.