blocks|key|1226381|text|实在帮不了什么忙，但我找到了这里的谷物表格：http://www.vmware.com/support/developer/vddk/VirtualDiskAPIprogramming.pdf+(第16页)|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1226382|就像用户mailq说的，你的虚拟驱动器好像坏了。也许可以检查vmdkck工具(在这个页面上是http://datto.org/projects/vmdk-tools+)来重复检查它是否坏了？|entityMap|0|LINK|mutability|MUTABLE|url|http://www.vmware.com/support/developer/vddk/VirtualDiskAPIprogramming.pdf|1|http://datto.org/projects/vmdk-tools^0|M|22|0|0|1A|10|1^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@$A|P|B|Q|1|R]]|C|$]]|$1|D|3|E|5|6|7|S|8|@]|9|@$A|T|B|U|1|V]]|C|$]]]|F|$G|$5|H|I|J|C|$K|L]]|M|$5|H|I|J|C|$K|N]]]]

Can't really help, but I found what the grain tables are here:
<a href="http://www.vmware.com/support/developer/vddk/VirtualDiskAPIprogramming.pdf" rel="noreferrer">http://www.vmware.com/support/developer/vddk/VirtualDiskAPIprogramming.pdf</a> (page 16)

Like the user mailq says, looks like your virtual drive is broken. Maybe check the vmdkck tool (on this page <a href="http://datto.org/projects/vmdk-tools" rel="noreferrer">http://datto.org/projects/vmdk-tools</a> ) to double check it's broken?

blocks|key|1226479|text|VMware有一个名为vmware-vdiskmanager的工具，位于"/Applications/VMware+Fusion.app/Contents/Library/"中，安装时与/usr/local/bin有符号链接。您也可以使用此工具修复VirtualBox+VMDK磁盘。它已经救了我几次。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1226480|安装|header-two|1226481|a.您可以安装vmware-融合+(需要macOS+Catalina；使用vmware-fusion10用于较旧的macOS版本)|1226482|brew+install+vmware-fusion|code-block|syntax|javascript|1226483|也可以直接从本页底部的附件部分下载vmware-vdiskmanager实用程序：|1226484|1226485|http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1023856|1226486|使用|1226487|vmware-vdiskmanager+-R+<your_disk>.vmdk|1226488|在不使用参数的情况下调用可提供帮助：|1226489|Usage:+vmware-vdiskmanager+OPTIONS+<disk-name>+%7C+<mount-point>
Offline+disk+manipulation+utility
...
+++++-R+++++++++++++++++++:+check+a+sparse+virtual+disk+for+consistency+and+attempt
++++++++++++++++++++++++++++to+repair+any+errors.
...|entityMap|0|LINK|mutability|MUTABLE|url|http://www.vmware.com/products/fusion.html|1^0|B|J|10|1F|2L|E|0|0|11|F|7|9|0|0|0|H|J|0|0|0|2T|1|0|0|0|0^^$0|@$1|2|3|4|5|6|7|1A|8|@$9|1B|A|1C|B|C]|$9|1D|A|1E|B|C]|$9|1F|A|1G|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|1H|8|@]|D|@]|E|$]]|$1|I|3|J|5|6|7|1I|8|@$9|1J|A|1K|B|C]]|D|@$9|1L|A|1M|1|1N]]|E|$]]|$1|K|3|L|5|M|7|1O|8|@]|D|@]|E|$N|O]]|$1|P|3|Q|5|6|7|1P|8|@$9|1Q|A|1R|B|C]]|D|@]|E|$]]|$1|R|3|-4|5|6|7|1S|8|@]|D|@]|E|$]]|$1|S|3|T|5|6|7|1T|8|@]|D|@$9|1U|A|1V|1|1W]]|E|$]]|$1|U|3|V|5|H|7|1X|8|@]|D|@]|E|$]]|$1|W|3|X|5|M|7|1Y|8|@]|D|@]|E|$N|O]]|$1|Y|3|Z|5|6|7|1Z|8|@]|D|@]|E|$]]|$1|10|3|11|5|M|7|20|8|@]|D|@]|E|$N|O]]]|12|$13|$5|14|15|16|E|$17|18]]|19|$5|14|15|16|E|$17|T]]]]

VMware has a tool called <code>vmware-vdiskmanager</code> located in <code>&quot;/Applications/VMware Fusion.app/Contents/Library/&quot;</code> and symlinked to <code>/usr/local/bin</code> when installed. You can use this tool to repair VirtualBox VMDK disks as well. It saved me a couple of times already.
<h2>Installation</h2>
a. You can install <a href="http://www.vmware.com/products/fusion.html" rel="nofollow noreferrer">vmware-fusion</a> (requires macOS Catalina; use <code>vmware-fusion10</code> for older macOS versions)
<pre><code>brew install vmware-fusion
</code></pre>
b. Or you can download the <code>vmware-vdiskmanager</code> utility directly from Attachments section at the bottom of this page: 
<a href="http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;cmd=displayKC&amp;externalId=1023856" rel="nofollow noreferrer">http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;cmd=displayKC&amp;externalId=1023856</a>
<h2>Usage</h2>
<pre><code>vmware-vdiskmanager -R &lt;your_disk&gt;.vmdk
</code></pre>
Invoking without parameters gives help usage:
<pre><code>Usage: vmware-vdiskmanager OPTIONS &lt;disk-name&gt; | &lt;mount-point&gt;
Offline disk manipulation utility
...
 -R : check a sparse virtual disk for consistency and attempt
 to repair any errors.
...
</code></pre>

blocks|key|1226332|text|你的虚拟硬盘坏了。谷物表是虚拟化环境中的一些内部内容。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1226333|在谷歌上搜索确切的术语可以发现，恢复的可能性并不多：https://forums.virtualbox.org/viewtopic.php?f=6&t=40049|offset|length|entityMap|0|LINK|mutability|MUTABLE|url|https://forums.virtualbox.org/viewtopic.php?f=6&t=40049^0|0|Q|1J|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@$D|O|E|P|1|Q]]|A|$]]]|F|$G|$5|H|I|J|A|$K|L]]]]

Your virtual hard drive is broken. Grain tables are some internal stuff of virtualization environments.

Googling for the exact term reveals that there are not many possibilities to recover:
<a href="https://forums.virtualbox.org/viewtopic.php?f=6&amp;t=40049" rel="nofollow noreferrer">https://forums.virtualbox.org/viewtopic.php?f=6&amp;t=40049</a>

blocks|key|3537353|text|我用CloneVDI来解决这个问题。我做了一个克隆，新文件运行得很好。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|entityMap|0|LINK|mutability|MUTABLE|url|https://forums.virtualbox.org/viewtopic.php?t=22422^0|2|8|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@$A|L|B|M|1|N]]|C|$]]]|D|$E|$5|F|G|H|C|$I|J]]]]

I used <a href="https://forums.virtualbox.org/viewtopic.php?t=22422" rel="nofollow noreferrer">CloneVDI</a> to solve this problem. I made a clone and the new file works very well.

blocks|key|1226630|text|在将~/VirtualBox\+VMs从Linux移到MacOS之后，我犯了这个错误。我试过@mens解决方案vmware-vdiskmanager，但对我来说失败了。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1226631|在从linux迁移到MacOS期间，我将所有的*.vbox文件添加回Virtualbox中，它们都未能以相同的错误启动(使用迷航符)：|1226632|There+was+an+error+while+executing+`VBoxManage`,+a+CLI+used+by+Vagrant+for+controlling+VirtualBox.+The+command+and+stderr+is+shown+below.

Command:+["startvm",+"<UUID+1>",+"--type",+"headless"]

Stderr:+VBoxManage:+error:+Could+not+open+the+medium+'/path/to/box-disk1.vmdk'.
VBoxManage:+error:+VMDK:+inconsistency+between+grain+table+and+backup+grain+table+in+'/path/to/box-disk1.vmdk'+(VERR_VD_VMDK_INVALID_HEADER).
VBoxManage:+error:+VD:+error+VERR_VD_VMDK_INVALID_HEADER+opening+image+file+'/path/to/box-disk1.vmdk'+(VERR_VD_VMDK_INVALID_HEADER)
VBoxManage:+error:+Details:+code+NS_ERROR_FAILURE+(0x80004005),+component+MediumWrap,+interface+IMedium|code-block|syntax|javascript|1226633|我验证了数据传输是否正确，md5+box-disk1.vmdk为两个文件返回了相同的内容。|1226634|通过将vmdk文件转换为vdi，我成功地使vm再次启动，执行以下操作。(需要qemu，brew+install+qemu)|1226635|#+Convert+from+`.vmdk`+to+`.bin`
qemu-img+convert+box-disk1.vmdk+box-disk1.bin

#+Convert+from+`.bin`+to+`.vdi`
VBoxManage+convertdd+box-disk1.bin+box-disk1.vdi|1226636|更新了.vdi和机器引导的卷路径。|1226637|在我的例子中，vdi文件稍微大一点，不要忘记删除.bin，因为它很大。哦，而且它在第一次运行时就无法验证。无论如何，如果可能的话，也许您应该从头开始创建一个新的vm。|entityMap|0|LINK|mutability|MUTABLE|url|https://serverfault.com/a/575058/191935^0|2|H|1J|J|1A|S|0|0|N|6|0|0|D|I|0|3|4|C|3|12|4|17|H|0|0|3|4|0|O|4^^$0|@$1|2|3|4|5|6|7|13|8|@$9|14|A|15|B|C]|$9|16|A|17|B|C]]|D|@$9|18|A|19|1|1A]]|E|$]]|$1|F|3|G|5|6|7|1B|8|@$9|1C|A|1D|B|C]]|D|@]|E|$]]|$1|H|3|I|5|J|7|1E|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|1F|8|@$9|1G|A|1H|B|C]]|D|@]|E|$]]|$1|O|3|P|5|6|7|1I|8|@$9|1J|A|1K|B|C]|$9|1L|A|1M|B|C]|$9|1N|A|1O|B|C]|$9|1P|A|1Q|B|C]]|D|@]|E|$]]|$1|Q|3|R|5|J|7|1R|8|@]|D|@]|E|$K|L]]|$1|S|3|T|5|6|7|1S|8|@$9|1T|A|1U|B|C]]|D|@]|E|$]]|$1|U|3|V|5|6|7|1V|8|@$9|1W|A|1X|B|C]]|D|@]|E|$]]]|W|$X|$5|Y|Z|10|E|$11|12]]]]

I had this error after moving my <code>~/VirtualBox\ VMs</code> from Linux to MacOS. I tried <a href="https://serverfault.com/a/575058/191935">@mens solution using <code>vmware-vdiskmanager</code></a>, but it failed for me.

During my migration from linux to MacOS, I added all of the <code>*.vbox</code> files back into Virtualbox and they all failed to boot with the same error (using vagrant):

<pre><code>There was an error while executing `VBoxManage`, a CLI used by Vagrant for controlling VirtualBox. The command and stderr is shown below.

Command: ["startvm", "&lt;UUID 1&gt;", "--type", "headless"]

Stderr: VBoxManage: error: Could not open the medium '/path/to/box-disk1.vmdk'.
VBoxManage: error: VMDK: inconsistency between grain table and backup grain table in '/path/to/box-disk1.vmdk' (VERR_VD_VMDK_INVALID_HEADER).
VBoxManage: error: VD: error VERR_VD_VMDK_INVALID_HEADER opening image file '/path/to/box-disk1.vmdk' (VERR_VD_VMDK_INVALID_HEADER)
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component MediumWrap, interface IMedium
</code></pre>

I verified that the data transfered correctly, <code>md5 box-disk1.vmdk</code> returned the same thing for both files. 

I managed to get a vm to boot again by converting the <code>vmdk</code> files to <code>vdi</code> doing the following. (Requires <code>qemu</code>, <code>brew install qemu</code>)



<pre><code># Convert from `.vmdk` to `.bin`
qemu-img convert box-disk1.vmdk box-disk1.bin

# Convert from `.bin` to `.vdi`
VBoxManage convertdd box-disk1.bin box-disk1.vdi
</code></pre>

Updated path to volume for <code>.vdi</code> and machine booted.

In my case, vdi file is slightly larger, don't forget to delete <code>.bin</code> as it's huge. Oh and it fails to authenticate on first run. Anyway, if possible, maybe you should spin up a new vm from scratch instead.

The setup in question is as follows: Windows 7 64bit host running VirtualBox. The guest machine is running Windows XP 32bit.

After a power failure on the host box, the guest machine cannot boot and complains that

<blockquote>
 inconsistency between grain table and backup grain table
</blockquote>

Any help to boot the guest machine without reinstalling it appreciated.

PS: What is a grain table anyway?

VirtualBox: grain table inconsistency

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

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

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

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

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

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

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

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

所讨论的设置如下:运行VirtualBox的Windows 7 64位主机。客户机器正在运行WindowsXP32bit。在主机上发生电源故障后，客服机器无法启动，并抱怨粮表与后备粮表的不一致性任何帮助引导客人的机器，而不重新安装它感谢。PS:粮食桌到底是什么？

问VirtualBox:粮表不一致
EN

回答 5

Server Fault用户

Server Fault用户

安装

使用

Server Fault用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问VirtualBox:粮表不一致EN

回答 5

Server Fault用户

Server Fault用户

安装

使用

Server Fault用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问VirtualBox:粮表不一致
EN