在 Macos 上,已修復的磁碟錯誤不斷出現,我需要一台新 Mac 嗎?

在 Macos 上,已修復的磁碟錯誤不斷出現,我需要一台新 Mac 嗎?

我正在嘗試確定是否需要更換 2019 年 12 月購買的 2018 Mac Mini(512 GB SSD,16 GB RAM)。當我運行急救時,我不斷收到以下錯誤。我在恢復模式下從下往上修復它,首先是卷,然後是容器,它說它已修復並且磁碟看起來正常,但幾個小時後,當我再次運行急救時,錯誤又回來了:


/dev/rdisk1s1: ** Checking snapshot 11 of 12 (com.apple.TimeMachine.2023-07-08-182610.local)
/dev/rdisk1s1: warning: mismatch between extentref entry reference count (0) and calculated fsroot entry reference count (-1) for extent (75965840 + 4)
/dev/rdisk1s1: warning: mismatch between extentref entry reference count (0) and calculated fsroot entry reference count (-1) for extent (76696330 + 8)
/dev/rdisk1s1: ** Checking snapshot 12 of 12 (com.apple.TimeMachine.2023-07-08-192548.local)
/dev/rdisk1s1: error: mismatch between extentref entry reference count (0) and calculated fsroot entry reference count (1) for extent (75965840 + 4)
/dev/rdisk1s1: error: mismatch between extentref entry reference count (0) and calculated fsroot entry reference count (1) for extent (76696330 + 8)
/dev/rdisk1s1: ** Checking the document ID tree.
/dev/rdisk1s1: ** Checking the fsroot tree.
/dev/rdisk1s1: ** Checking the extent ref tree.
/dev/rdisk1s1: ** Verifying volume object map space.
/dev/rdisk1s1: ** The volume /dev/rdisk1s1 was found to be corrupt and needs to be repaired.
/dev/rdisk1s1: ** Verifying allocated space.
/dev/rdisk1s1: ** Performing deferred repairs.
/dev/rdisk1s1: error: Unable to perform deferred repairs without full space verification
/dev/rdisk1s1: error: Try running fsck against the entire APFS container instead of a volume
/dev/rdisk1s1: ** The volume /dev/rdisk1s1 could not be verified completely.
/dev/rdisk1s1: Sat Jul  8 20:09:48 2023

從 smartmontools 我看到:

smartctl -a disk0
smartctl 7.3 2022-02-28 r5338 [Darwin 22.5.0 x86_64] (local build)
Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Number:                       APPLE SSD AP0512M
Serial Number:                      C078504002HJRFYAB
Firmware Version:                   1296.120
PCI Vendor/Subsystem ID:            0x106b
IEEE OUI Identifier:                0x000000
Controller ID:                      0
NVMe Version:                       <1.2
Number of Namespaces:               1
Local Time is:                      Sun Jul  9 20:22:36 2023 ADT
Firmware Updates (0x02):            1 Slot
Optional Admin Commands (0x0004):   Frmw_DL
Optional NVM Commands (0x0004):     DS_Mngmt
Maximum Data Transfer Size:         256 Pages

Supported Power States
St Op     Max   Active     Idle   RL RT WL WT  Ent_Lat  Ex_Lat
 0 +     0.00W       -        -    0  0  0  0        0       0

=== START OF SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

SMART/Health Information (NVMe Log 0x02)
Critical Warning:                   0x00
Temperature:                        49 Celsius
Available Spare:                    100%
Available Spare Threshold:          99%
Percentage Used:                    11%
Data Units Read:                    355,382,704 [181 TB]
Data Units Written:                 237,678,387 [121 TB]
Host Read Commands:                 7,371,234,957
Host Write Commands:                3,890,298,980
Controller Busy Time:               0
Power Cycles:                       449
Power On Hours:                     4,191
Unsafe Shutdowns:                   277
Media and Data Integrity Errors:    0
Error Information Log Entries:      0

Read 1 entries from Error Information Log failed:
GetLogPage failed: system=0x38, sub=0x0, code=745

bash-3.2$

答案1

我遇到了類似的錯誤,並對此進行了一些研究,我想我可以在這裡分享。一個重要的區別是,這與格式化為 APFS 的磁碟機有關。請謹慎遵循您發現的可能較舊且並非特定於 APFS 驅動器的建議。

  • 一些參考文獻(最近)指出 APFS 驅動器需要在容器上運行急救,而不是在磁碟區上。這顯然需要在系統未安裝時完成,例如在恢復模式下(啟動時使用命令 R)。關聯
  • 一位用戶表示,他在運行「急救」之前手動卸載了驅動器,並聲稱「磁碟工具」有時無法執行此操作。關聯
  • 同一 MacRumors 討論中的另一位用戶(擁有 68000 個身份點)表示,他不僅對主驅動器的「所有實例」運行了急救,還禁用了時間機器,然後使用終端刪除了所有本地快照。關聯
  • 此 Apple 支援文件討論了檢視和刪除 APFS 快照。關聯

驅動器運作狀況與資料損壞

  • 我看到的與此相關的問題似乎主要與資料損壞有關,而不是由於驅動器故障,儘管錯誤訊息看起來相當不祥。也就是說,即使您最近有備份,重新格式化磁碟機來解決損壞問題並非無足輕重。
  • 這篇文章指的是智慧工具作為免費的命令列 APFS 磁碟監控/評估解決方案。關聯
  • 另一篇文章提到了一個免費的基於 GUI 的 SSD 監視器,稱為 SSDReporter。關聯

從 smartmon 工具運行 smartctl

josh@joshuas-mini ~ % smartctl -a disk3s5
smartctl 7.3 2022-02-28 r5338 [Darwin 22.5.0 arm64] (local build)
Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Number:                       APPLE SSD AP1024Q
Serial Number:                      0ba0122c40a52e0b
Firmware Version:                   874.120.
PCI Vendor/Subsystem ID:            0x106b
IEEE OUI Identifier:                0x000000
Controller ID:                      0
NVMe Version:                       <1.2
Number of Namespaces:               3
Local Time is:                      Wed Jul 26 08:06:52 2023 CDT
Firmware Updates (0x02):            1 Slot
Optional Admin Commands (0x0004):   Frmw_DL
Optional NVM Commands (0x0004):     DS_Mngmt
Maximum Data Transfer Size:         256 Pages

Supported Power States
St Op     Max   Active     Idle   RL RT WL WT  Ent_Lat  Ex_Lat
 0 +     0.00W       -        -    0  0  0  0        0       0

=== START OF SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

SMART/Health Information (NVMe Log 0x02)
Critical Warning:                   0x00
Temperature:                        33 Celsius
Available Spare:                    100%
Available Spare Threshold:          99%
Percentage Used:                    10%
Data Units Read:                    653,815,670 [334 TB]
Data Units Written:                 495,164,729 [253 TB]
Host Read Commands:                 12,687,340,931
Host Write Commands:                6,148,184,985
Controller Busy Time:               0
Power Cycles:                       225
Power On Hours:                     5,760
Unsafe Shutdowns:                   79
Media and Data Integrity Errors:    0
Error Information Log Entries:      0

Read 1 entries from Error Information Log failed: GetLogPage failed: system=0x38, sub=0x0, code=745

答案2

我沒有更換 2018 年 Mac Mini。看來這可能是 MacOS 或急救中的錯誤,因為我不再收到錯誤訊息。

相關內容