急救人员发现腐败需要修复，但救援急救并没有解决问题

我试图在运行Sierra 10.12.1的Macbook Pro 2012上解决这个问题。我从恢复中运行急救并没有发现任何腐败，一切都很好。我从我的操作系统再次运行它，我仍然遇到如下问题：

Verifying storage system
Checking volume
disk0s2: Scan for Volume Headers
disk0s2: Scan for Disk Labels
Logical Volume Group 04B93861-2D39-432E-A393-50AD1CE83BFE on 1 device
disk0s2: Scan for Metadata Volume
Logical Volume Group has a 24 MB Metadata Volume with double redundancy
Start scanning metadata for a valid checkpoint
Load and verify Segment Headers
Load and verify Checkpoint Payload
Load and verify Transaction Segment
Incorporate 0 newer non-checkpoint transactions
Load and verify Virtual Address Table
Load and verify Segment Usage Table
Load and verify Metadata Superblock
Load and verify Logical Volumes B-Trees
Logical Volume Group contains 1 Logical Volume
Load and verify 55E94947-EFBC-473A-A314-5EBEFF0A949A
Load and verify F9FAD274-A819-4CDC-9F05-F519DA8DBED2
Load and verify Freespace Summary
Load and verify Block Accounting
Load and verify Live Virtual Addresses
Newest transaction commit checkpoint is valid
Load and verify Segment Cleaning
The volume 04B93861-2D39-432E-A393-50AD1CE83BFE appears to be OK
Storage system check exit code is 0.
Verifying file system.
Using live mode.
Performing live verification.
Checking Journaled HFS Plus volume.
Checking extents overflow file.
Checking catalog file.
**Incorrect block count for file processing-3.2.3-macosx.zip.f0fd203b-064b-4fd7-bce4-89d8c693971e**
**(It should be 6452 instead of 28451)
Incorrect block count for file USB_LUCA.zip.40b230dc-a016-4312-afcd-c1a087fcd8a2
(It should be 4630 instead of 530384)**
Checking multi-linked files.
**Incorrect number of file hard links**
Checking catalog hierarchy.
Checking extended attributes file.
Checking volume bitmap.
**Volume bitmap needs minor repair for orphaned blocks**
Checking volume information.
**Invalid volume free block count**
**(It should be 19383016 instead of 9221304)**
*The volume Macintosh HD was found corrupt and needs to be repaired.*
File system check exit code is 8.
Operation successful.

有人有同样的问题吗？

当重复尝试修复文件系统失败时，下一步是备份所需的所有文件并清除分区。

设置新的文件系统，然后在恢复中重新测试修复。如果失败 - 您的硬件需要修复。如果通过干净检查成功 - 您可以设置新帐户和/或从备份恢复。

实时修复不值得信任，但实时错误是值得关注的。我会尝试在实时模式下进行验证，以确保在进入擦除/重新分区步骤之前遇到问题，因为这可能需要一些时间，所以在开始沿着这条路径前你肯定要确定。