☰

系统事件日志中出现一系列 8 个 Ntfs 类型 134 警告

tag-icon • tag-icon windows-8.1 backup ntfs vss
系统事件日志中出现一系列 8 个 Ntfs 类型 134 警告

我有一台 Windows 8.1 工作站，几天前我开始在系统事件日志中查看一系列 8 个类型 134 Ntfs 警告消息在我定期安排的 VSS 集成系统映像备份开始后 1 分 43 秒记录，该备份通过以下命令完成：

wbadmin 开始备份 -allCritical -vssFull -quiet -backupTarget:G:\

在我重新连接并重新格式化外部 USB MyBook 备份驱动器后，出现了不需要的警告（如下所列），该驱动器以前曾用于常规系统映像备份的目标，但我用更大的驱动器替换了它。几个星期以来，这个驱动器一直闲置在桌子上。我怀疑，在旧快照仍在那里的情况下将其重新插入（在重新格式化之前）可能会导致系统对其备份卷快照数据结构所在的位置感到困惑。

我不知道如何重置卷快照子系统以“重新开始”，但我怀疑这样做并备份完整的系统映像可以解决这个问题。自从我开始看到警告以来，我甚至没有重新启动系统；这可能就是它所需要的。

然而，在盲目尝试之前，我想在这里问一下。

以下是系统日志消息的序列，在系统映像备份期间每晚都会重复：

Information  2:00:00 AM  Virtual Disk Service  3: "Service Started"

Information  2:01:21 AM  Ntfs (Microsoft-Windows-Ntfs)  98:  "Volume System Reserved (\Device\HarddiskVolumeShadowCopy198) is healthy.  No action is needed."

Information  2:01:42 AM  volsnap  33:  "The oldest shadow copy of volume C: was deleted to keep disk space usage for shadow copies of volume C: below the user defined limit."

Warning  2:01:43 AM  Ntfs (Ntfs)  134:  "The transaction resource manager on volume C - NoelC4 SSD encountered an error during recovery.  The resource manager will continue recovery."
Warning  2:01:43 AM  Ntfs (Ntfs)  134:  "The transaction resource manager on volume C - NoelC4 SSD encountered an error during recovery.  The resource manager will continue recovery."
Warning  2:01:43 AM  Ntfs (Ntfs)  134:  "The transaction resource manager on volume C - NoelC4 SSD encountered an error during recovery.  The resource manager will continue recovery."
Warning  2:01:43 AM  Ntfs (Ntfs)  134:  "The transaction resource manager on volume C - NoelC4 SSD encountered an error during recovery.  The resource manager will continue recovery."
Warning  2:01:43 AM  Ntfs (Ntfs)  134:  "The transaction resource manager on volume C - NoelC4 SSD encountered an error during recovery.  The resource manager will continue recovery."
Warning  2:01:43 AM  Ntfs (Ntfs)  134:  "The transaction resource manager on volume C - NoelC4 SSD encountered an error during recovery.  The resource manager will continue recovery."
Warning  2:01:43 AM  Ntfs (Ntfs)  134:  "The transaction resource manager on volume C - NoelC4 SSD encountered an error during recovery.  The resource manager will continue recovery."
Warning  2:01:43 AM  Ntfs (Ntfs)  134:  "The transaction resource manager on volume C - NoelC4 SSD encountered an error during recovery.  The resource manager will continue recovery."

Information  2:01:45 AM  Kernel-General  11:  "TxR init phase for hive \??\GLOBALROOT\Device\HarddiskVolumeShadowCopy199\Windows\system32\config\SYSTEM (TM: {a4c8ef04-9431-11e8-83b0-1803734ec99c}, RM: {a4c8ef03-9431-11e8-83b0-1803734ec99c}) finished with result=0xC00000A2 (Internal code=7)."
Information  2:01:45 AM  Kernel-General  11:  "TxR init phase for hive \??\GLOBALROOT\Device\HarddiskVolumeShadowCopy199\Windows\system32\config\DRIVERS (TM: {a4c8ef06-9431-11e8-83b0-1803734ec99c}, RM: {a4c8ef05-9431-11e8-83b0-1803734ec99c}) finished with result=0xC00000A2 (Internal code=7)."

Information  2:01:51 AM  Kernel-General  15:  "Hive \??\Volume{ef97e822-4c7d-11e3-824b-806e6f6e6963}\System Volume Information\SPP\SppCbsHiveStore\{cd42efe1-f6f1-427c-b004-033192c625a4}{0B5EFEA9-A4AA-4F43-8C5C-F4FD287CA71F} was reorganized with a starting size of 117997568 bytes and an ending size of 118042624 bytes."
Information  2:01:51 AM  Kernel-General  15:  "Hive \??\Volume{ef97e822-4c7d-11e3-824b-806e6f6e6963}\System Volume Information\SPP\SppCbsHiveStore\{cd42efe1-f6f1-427c-b004-033192c625a4}{18046E51-7164-4705-BF94-E607CE13F8E0} was reorganized with a starting size of 12558336 bytes and an ending size of 11460608 bytes."

Information  2:01:54 AM  Kernel-General  16:  "The access history in hive \??\GLOBALROOT\Device\HarddiskVolumeShadowCopy199\Users\default\ntuser.dat was cleared updating 4 keys and creating 2 modified pages."

Information  3:05:00 AM  Virtual Disk Service  4:  "Service stopped."

备份成功，没有证据表明磁盘（内部或外部）存在任何实际问题。这些基本检查已通过：

C:\TEMP>chkdsk c：

The type of the file system is NTFS.
Volume label is C - NoelC4 SSD.

WARNING!  F parameter not specified.
Running CHKDSK in read-only mode.

Stage 1: Examining basic file system structure ...
  2686208 file records processed.
File verification completed.
  18601 large file records processed.
  0 bad file records processed.

Stage 2: Examining file name linkage ...
  3150960 index entries processed.
Index verification completed.
  0 unindexed files scanned.
  0 unindexed files recovered.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
  232377 data files processed.
CHKDSK is verifying Usn Journal...
  37457544 USN bytes processed.
Usn Journal verification completed.

Windows has scanned the file system and found no problems.
No further action is required.

1874999295 KB total disk space.
1323380116 KB in 2275913 files.
    693288 KB in 232378 indexes.
         0 KB in bad sectors.
   2928387 KB in use by the system.
     65536 KB occupied by the log file.
 547997504 KB available on disk.

      4096 bytes in each allocation unit.
 468749823 total allocation units on disk.
 136999376 allocation units available on disk.

C:\TEMP>证监会/verifyonly

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

在此先感谢您分享的有关如何清除导致这些警告的状况的任何见解。

答案1

事实证明，删除几个文件然后重新启动操作系统显然已经重置了导致重复警告的条件。

该文件夹中的文件是隐藏的，扩展名为 .regtrans-ms 和 .blf，其日期比我开始看到警告消息的日期早几个月。

C:\Windows\System32\SMI\Store\Machine

值得注意的是，VSS 集成备份仍然是增量的（实际备份驱动器上仍有足够的空间）。

进一步的研究发现了微软员工的模糊指示，引导我查看该文件夹，而这些文件的日期是几个月前的，这让我觉得它们可能是之前未完成的某个操作遗留下来的。我不喜欢用“重新启动”来解决一个长期存在的问题，我真的没想到它会起作用，但是嘿，我会记录一个干净的日志。

答案2

只是要进行 necropost，以便至少在某处记录这个解决方案。

我遵循了在线找到的所有建议，但仍然定期记录多个 NTFS 134 错误。每次 Windows 尝试进行备份并调用 VSS 时。

事实证明，这次当我将磁盘克隆到新驱动器时，我包含了系统卷信息文件夹。

不要那样做。

如果您这样做了，请在安全模式下删除该文件夹，这样它就不会不断尝试重建不需要重建的东西，从而产生这些错误。

相关内容