简体繁体 English

将新磁盘附加到Azure IAAS VM导致重新启动？

[英]Attaching a new disk to Azure IAAS VM caused a reboot?

原文 2014-09-19 18:06:40 2 1 azure/ iaas

I recently attached a new empty data disk to an Azure IAAS VM running Windows Server 2012 datacenter. 我最近将一个新的空数据磁盘连接到运行Windows Server 2012数据中心的Azure IAAS VM。 As soon as the disk was added. 一旦添加磁盘。 Windows rebooted. Windows重新启动。 This surprised me greatly, as I didn't expect added a data disk to cause a reboot. 这让我感到非常惊讶，因为我没想到添加数据磁盘会导致重启。 I looked in the event log and didn't see any errors, the event log indicated NT AUTHORTIY\\SYSTEM initiated the reboot. 我查看了事件日志，没有看到任何错误，事件日志指示NT AUTHORTIY \\ SYSTEM启动了重新启动。

I attached another disk after it came back up, and it behaved as expected, the disk was added without a reboot. 备份后，我附加了另一个磁盘，并且其行为与预期的一样，没有重新引导就添加了该磁盘。

Does anyone know why/what circumstances would cause an operation like that to make the system trigger a reboot? 有谁知道为什么/在什么情况下会导致类似的操作使系统触发重启？

Thank you! 谢谢！

1 个解决方案

This isn't expected behaviour, and isn't anything I've seen before. 这不是预期的行为，也不是我以前见过的任何东西。

I've added numerous data disks to numerous IaaS VMs on Azure, in both Windows 2008 R2 and Windows 2012 R2, and I've never seen a VM reboot automatically as a result of that action. 在Windows 2008 R2和Windows 2012 R2中，我已将大量数据磁盘添加到Azure上的多个IaaS VM中，而且从未见过由于该操作而导致VM自动重新启动的情况。

Is there any chance you were doing anything else at same time which may have caused the reboot, such as a silent software installation? 您是否有机会同时进行可能导致重新引导的其他任何事情，例如无提示安装软件？ Alternatively you might have been particularly unfortunate if it coincided with a scheduled Azure maintenance window (although you would normally see something in the Event Log if that was the case). 另外，如果它与计划的Azure维护窗口同时发生，您可能会特别不幸（尽管在这种情况下，您通常会在事件日志中看到某些内容）。