The most common error encountered when using First Aid in Disk Utility to check and repair disks is that the procedure fails because the volume or container to be checked can’t be unmounted, as required by fsck_apfs when it’s run by Disk Utility.
If you can, use that from macOS 13.4 or a more recent version. The latest release of Disk Utility, version 22.6, also fixes most of the bugs that have in the past made First Aid unreliable. Older repair tools may not cope well with newer features of the file system: for best results, always use the versions of Disk Utility and fsck supplied with that version of macOS, or newer versions of those tools. Apple recommends performing checking and repair first on volumes, then on containers, and finally on the disk itself, although that may result in repeated checks of volumes and their snapshots.īecause APFS is a relatively new file system, its capabilities have changed rapidly over the last few years. The only tools that can check and repair them at present are Disk Utility and fsck (calling fsck_apfs), although there are some third-party tools that can recover the contents of corrupt disks. APFSĪPFS volumes are variable-size file systems within fixed-size partitions or containers of the disk.
Use of a good repair tool such as DiskWarrior can normally rebuild the file system on even quite damaged volumes. Journalling was introduced to reduce their frequency, and has proved effective. In the past, HFS+ has been prone to accumulate minor disk errors resulting from incomplete file system changes. By convention, checking and repair is performed first on the disk itself, to ensure that its partition table is correct, then on the individual volumes within that. HFS+ volumes are fixed-size partitions of the disk, and enjoy the support of a range of mature third-party tools including DiskWarrior, as well as Disk Utility and fsck.
Diskwarrior 6 professional#
When you’ve considered these often conflicting factors, and whether the disk needs a professional recovery service (see below), you can decide whether to attempt to repair it yourself, and how best to do that.
Diskwarrior 6 mac#
The contents of disks can only be checked and repaired when the Mac recognises that disk: if it doesn’t appear in Disk Utility, then you can’t run First Aid on it. Attempting to fix a live file system is dangerous, and, even when supported, is often doomed to fail unless the errors are only minor. Volumes and disks can only be effectively checked and repaired when they’re unmounted from the Mac. As a result, they can’t boot unless their internal SSD has a reasonable degree of function, and won’t boot at all if that is badly damaged. Apple silicon Macs can always start up from suitably prepared external bootable disks, but only do so after starting their boot process from the internal SSD. One action that can make it easier to access an ailing Intel Mac with a T2 chip is to start up in Recovery mode, open Startup Security Utility and enable that Mac to boot from an external disk: that’s disabled by default. You don’t have that option when the problem is on the Mac’s internal storage, particularly the SSD in an Apple silicon or T2 Mac. When the error occurs on an external disk, your first action should normally be to unmount and disconnect that disk, to avoid using it any further and possibly worsening the error to the point where its contents become unrecoverable. While Disk Utility and its command tool sibling fsck can check and repair other formats, they’re best at dealing with the Mac’s two native formats, HFS+ and APFS.
Diskwarrior 6 Pc#
If it’s a PC format such as ExFAT or another non-native disk format, then you’re best off attempting to repair that disk on a computer with more extensive tools and utilities to support that, such as a PC. The first thing you need to establish is which disk is affected, which volume on that disk, and what format that volume uses.
0 kommentar(er)
