blocks|key|4856390|text|是的，这非常简单：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4856391|停止instance.|4856392|Detach根EBS卷。|unordered-list-item|4856393|
|4856394|将备用EBS卷附加为根:instance.|4856395|4856396|Detach|4856397|4856398|。|4856399|4856400|这是以您的备用EBS卷是可引导的为前提的-它必须包含可引导的OS映像。|4856401|entityMap^0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|W|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|X|8|@]|9|@]|A|$]]|$1|G|3|H|5|6|7|Y|8|@]|9|@]|A|$]]|$1|I|3|J|5|F|7|Z|8|@]|9|@]|A|$]]|$1|K|3|H|5|6|7|10|8|@]|9|@]|A|$]]|$1|L|3|M|5|F|7|11|8|@]|9|@]|A|$]]|$1|N|3|H|5|6|7|12|8|@]|9|@]|A|$]]|$1|O|3|P|5|F|7|13|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|14|8|@]|9|@]|A|$]]|$1|R|3|S|5|6|7|15|8|@]|9|@]|A|$]]|$1|T|3|-4|5|6|7|16|8|@]|9|@]|A|$]]]|U|$]]

Yep, it's dead easy:

<ol>
<li>Stop the instance.</li>
<li>Detach the root EBS volume.</li>
<li>Attach the alternate EBS volume as the root: <code>/dev/sda1</code></li>
<li>Start the instance.</li>
</ol>

This presupposes that your alternate EBS volume is bootable, of course - it has to contain the bootable OS image.

blocks|key|2783861|text|我没有足够的代表来为选择的答案添加评论，但我确实想指出，对我来说，/dev/sda1不起作用(没有作为根附加)，但使用/dev/xvda起作用(附加作为根)。该实例是使用HVM的较新的t2.micro实例之一。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2783862|entityMap^0|X|9|1N|9|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|M|8|@]|D|@]|E|$]]]|G|$]]

I don't have enough rep to add a comment to the selected answer, but I do want to point out that for me, <code>/dev/sda1</code> did not work (did not attach as root), but using <code>/dev/xvda</code> worked (attached as root). The instance is one of the newer t2.micro ones using HVM.

blocks|key|3069635|text|为了详细说明Diomidis+Spinellis在接受答案的评论线程中的评论，检查您试图作为新的根设备切换到的设备的文件系统标签是很重要的。在对我自己的服务器迁移进行故障排除时，我必须执行以下操作才能启动我的实例：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3069636|使用e2label命令更改为新根设备创建的ext2/ext3/ext4文件系统上的标签。|offset|length|style|CODE|3069637|首先，检查当前根设备的文件系统标签。|3069638|$+sudo+e2label+/dev/xvda1
cloudimg-rootfs|code-block|syntax|javascript|3069639|将新设备设置为具有相同的文件系统标签。|3069640|$+sudo+e2label+/dev/xvdg+'cloudimg-rootfs'|3069641|在我的例子中，标签是cloudimg-rootfs。有时它会简单地被称为/。|3069642|了解e2label的工作原理很重要；请检查您机器上的man+e2label或访问http://linux.die.net/man/8/e2label以获取更多信息。|3069643|entityMap|0|LINK|mutability|MUTABLE|url|http://linux.die.net/man/8/e2label^0|0|2|7|0|0|0|0|0|A|F|10|1|0|Q|B|14|Y|0|0^^$0|@$1|2|3|4|5|6|7|14|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|15|8|@$D|16|E|17|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|18|8|@]|9|@]|A|$]]|$1|J|3|K|5|L|7|19|8|@]|9|@]|A|$M|N]]|$1|O|3|P|5|6|7|1A|8|@]|9|@]|A|$]]|$1|Q|3|R|5|L|7|1B|8|@]|9|@]|A|$M|N]]|$1|S|3|T|5|6|7|1C|8|@$D|1D|E|1E|F|G]|$D|1F|E|1G|F|G]]|9|@]|A|$]]|$1|U|3|V|5|6|7|1H|8|@$D|1I|E|1J|F|G]]|9|@$D|1K|E|1L|1|1M]]|A|$]]|$1|W|3|-4|5|6|7|1N|8|@]|9|@]|A|$]]]|X|$Y|$5|Z|10|11|A|$12|13]]]]

To elaborate on Diomidis Spinellis's comment in the the accepted answer's comments thread, it's important to check the filesystem label of the device you're attempting to switch in as your new root device. While troubleshooting my own server migration, I had to do the following before my instance would boot up:

Use the <code>e2label</code> command to change the label on the ext2/ext3/ext4 filesystem you've created for your new root device.

First, check the filesystem label for your current root device.

<pre><code>$ sudo e2label /dev/xvda1
cloudimg-rootfs
</code></pre>

Set the new device to have the same filesystem label. 

<pre><code>$ sudo e2label /dev/xvdg 'cloudimg-rootfs'
</code></pre>

In my case, the label was <code>cloudimg-rootfs</code>. Sometimes it will simply be <code>/</code>.

It's important to understand how e2label works; check <code>man e2label</code> on your machine or visit <a href="http://linux.die.net/man/8/e2label">http://linux.die.net/man/8/e2label</a> for more information.

blocks|key|2783921|text|这是aws建议的解决方案，您可以在停止根卷后将其与原始实例分离。根卷附加在/dev/sda1。分离后，请将其附加到新实例。附加卷后，您可能需要从操作系统挂载它。挂载后，您应该可以看到其中的数据。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2783922|添加完新密钥后，可以将其分离并附加到/dev/sda1处的原始实例。|2783923|我建议在进行任何更改之前创建根卷的快照。|2783924|在尝试任何解决方案之前，只需在不重要的实例或spot实例中尝试|2783925|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

This is the aws suggested solution 
You can detach the root volume from the original instance after stopping it. The root volume is attached at /dev/sda1. Once this is detached, please attach it to the new instance. After the volume is attached, you may have to mount it from the OS. After it's mounted, you should see the data within it. 

After you've done adding the new key, you can detach it and attach to the original instance at /dev/sda1. 

I suggest creating a snapshot of the root volume before making any changes.

Before trying out any solutions just try out in the not important instances or spot instances

blocks|key|3069870|text|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3069871|停止EC2实例。|ordered-list-item|3069872|在导航面板上，单击“+existing+Volumes”下的“Volumes”，然后单击“Actions”和“分离卷”。完成新卷的实例，在confirmation.|offset|length|style|BOLD|3069873|Choose+Attach+>>对话框中单击'Actions‘Attach+volume’|3069874|，然后输入Instance+ID|unordered-list-item|3069875|Device：Enter+/dev/sda1|CODE|3069876|3069877|3069878|3069879|entityMap^0|0|0|A|20|1|0|19|2|0|G|2|0|M|D|9|2|1|0|0^^$0|@$1|2|3|-4|4|5|6|W|7|@]|8|@]|9|$]]|$1|A|3|B|4|C|6|X|7|@]|8|@]|9|$]]|$1|D|3|E|4|C|6|Y|7|@$F|Z|G|10|H|I]]|8|@]|9|$]]|$1|J|3|K|4|C|6|11|7|@$F|12|G|13|H|I]]|8|@]|9|$]]|$1|L|3|M|4|N|6|14|7|@$F|15|G|16|H|I]]|8|@]|9|$]]|$1|O|3|P|4|N|6|17|7|@$F|18|G|19|H|I]|$F|1A|G|1B|H|Q]]|8|@]|9|$]]|$1|R|3|-4|4|5|6|1C|7|@]|8|@]|9|$]]|$1|S|3|-4|4|5|6|1D|7|@]|8|@]|9|$]]|$1|T|3|-4|4|5|6|1E|7|@]|8|@]|9|$]]|$1|U|3|-4|4|5|6|1F|7|@]|8|@]|9|$]]]|V|$]]

<ol>
<li>Stop the EC2 instance.</li>
<li>On Navigation panel, click 'Volumes' under 'Elastic Block Store'.</li>
<li>Choose the existing volume, click 'Actions' and 'Detach volume'. Complete the confirmation.</li>
<li>Choose the new volume, click 'Actions' &gt;&gt; 'Attach volume'
<ul>
<li>In the Attach Volume dialogue box,</li>
<li>Instance: Enter Instance ID</li>
<li>Device: Enter <code>/dev/sda1</code></li>
</ul>
</li>
</ol>

blocks|key|4856644|text|如果您希望通过CloudFormation执行此操作，则需要执行以下操作：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4856645|4856646|从现有根卷创建快照(通过控制台或命令行界面)|ordered-list-item|4856647|从此快照创建新的AMI+-在此处增加根卷大小，确保您选择了正确的虚拟化时间(准虚拟或虚拟)。|4856648|在您的AWS：：ec2：：实例资源上，将ImageId参数设置为您刚刚创建的新AMI+|4856649|4856650|部署堆栈。这将重新创建实例，因此请确保您使用的是弹性IP地址或拥有DNS访问权限。|4856651|您必须执行此解决方法的原因是，CF不允许您调整EC2+BlockDeviceMappings上的根卷大小，或调整根卷的SnapshotId。|4856652|entityMap^0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|R|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|S|8|@]|9|@]|A|$]]|$1|F|3|G|5|E|7|T|8|@]|9|@]|A|$]]|$1|H|3|I|5|E|7|U|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|V|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|W|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|X|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|P|$]]

If you are wanting to do this via CloudFormation you will need to do the following:

<ol>
<li>Create snapshot from existing root volume (via console or CLI)</li>
<li>Create new AMI from this snapshot - increase the root volume size here, make sure you select correct virtualisation time (paravirtual or HVM).</li>
<li>On your AWS::EC2::Instance resource, set the ImageId parameter to the new AMI you have just made</li>
</ol>

Deploy your stack. This will recreate your instance, so make sure you are using an Elastic IP address or have DNS access.

The reason you have to do this workaround is because CF will not let you adjust root volume size on EC2 BlockDeviceMappings, or to adjust SnapshotId of Root Volume.

blocks|key|2783955|text|当你的卷被挂载时，它会得到一个带有数字的后缀，例如:当/dev/sda被挂载时，它被挂载为/dev/sda1,+/dev/sda2，这取决于你创建的分区。因为我们正在挂载根设备本身，所以它假定该设备已经挂载，所以我们需要为将卷挂载为根设备提供/dev/sda1。注意:不应该附加任何根卷。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2783956|请执行以下步骤:+1)转到您的卷，选择从操作中附加卷。2)选择您的实例3)作为根目录挂载，指定设备名称为/dev/sda1+4)启动实例。|2783957|entityMap^0|R|8|19|K|3D|9|0|1G|9|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]|$9|M|A|N|B|C]|$9|O|A|P|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|Q|8|@$9|R|A|S|B|C]]|D|@]|E|$]]|$1|H|3|-4|5|6|7|T|8|@]|D|@]|E|$]]]|I|$]]

When your volume is mounted, it gets a post-fix with numbers, eg: when <code>/dev/sda</code> is mounted, its mounted as <code>/dev/sda1, /dev/sda2</code> depending on the partitions you make.
As we are mounting the root device itself, it assumes the device is already mounted, so we need to give <code>/dev/sda1</code> for mounting the volume as root device.
Note: There shouldn't be any root volume attached.

Follow these steps:
1) Go to your volumes, select attach volumes from Action.
2) Select your instance
3) For mounting as root, give the device name as <code>/dev/sda1</code>
4) Start your instance.

I have an EBS backed Amazon EC2 instance. I would like to change the root device on this instance. Can you please advise the best way to go about this?
I only find documentation on changing several attributes of block devices, but they don't seem to include setting it as the root device.

Can I change the root EBS device of my amazon EC2 instance?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我有一个EBS支持的亚马逊EC2实例。我想要更改此实例上的根设备。你能告诉我做这件事最好的方法吗？我只找到了关于更改块设备的几个属性的文档，但它们似乎不包括将其设置为根设备。

问我可以更改我的亚马逊EC2实例的根EBS设备吗？
EN

回答 7

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问我可以更改我的亚马逊EC2实例的根EBS设备吗？EN

回答 7

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问我可以更改我的亚马逊EC2实例的根EBS设备吗？
EN