Disk Utility scan failed on "Container disk1"?

Question

Level 1

39 points

Disk Utility scan failed on "Container disk1"?

I just upgraded to the new macOS High Sierra today(9/28/17)
Prior to updating i decided to run a quick disk utility scan to make sure everything is fine on my internal hard drive for my Macbook Air.

When my Disk Utility opened i notice that there was only one disk avaliable; on sierra there was technically two if dropped down. I found out to show all the devices avaliable and saw a new disk called "Container disk1"; i never seen the disk before and decided to run a scan on it but it failed.

Ive never seen this "Container disk1" before and my iMac doesnt have a container disk when all devices are selected.

I ran disk utility in safe mode and it still failed; in recover mode however it ran a successful scan with no problems detected.

Why is Disk Utility unable to scan this "Container disk1" when is regular startup? Where did "Container disk1" even come from?

Does anyone else see a similar disk in thier Disk Utility when showing all devices? Especially if on a Macbook?

MacBook Air (13-inch Mid 2013), macOS High Sierra (10.13)

Posted on Sep 28, 2017 9:47 PM

Reply

Answer 1

Best reply

leroydouglas

Community+ 2024

Level 10

184,692 points

Sep 28, 2017 9:54 PM in response to SebasT14

If your run First Aid on the Container it will generate the error.

You need to boot into Recovery and run the DiskUtility>First Aid there on your Macintosh HD This is where it counts.

http://support.apple.com/kb/HT4718

Reply

Answer 2

Mart_K

Level 1

4 points

Oct 18, 2017 11:39 AM in response to leroydouglas

Hi people,

Is it possible since the release of High Sierra and the system change to APFS that my bootcamp in Windows can't find the Mac OS harddrive anymore cause my harddrive no falls under container disk1?

If so, does anyone know a solution? Sorry for my bad English I'm dutch 😉

Greetz Mart

Reply

Answer 3

Nov 11, 2017 6:58 AM in response to SebasT14

I have this as well. Never saw it before updating to High Sierra. Tried running First Aid on it which failed, but I don't think it's a problem. Just a part of the new APFS (Apple File System) as opposed to an actual disk.

APFS comes with a range of "solid" features including support for 64-bit inode numbering, and improved granularity of object time-stamping. "APFS supports nanosecond time stamp granularity rather than the 1-second time stamp granularity in HFS+." It also supports copy-on-write metadata scheme which aims to ensure that file system commits and writes to the file system journal stay in sync even if "something happens during the write -- like if the system loses power." The new file system offers an improvement over Apple's previous full-disk encryption File Vault application. It also features Snapshots (that lets you throw off a read-only instant of a file system at any given point in time), and Clones. According to the documentation, APFS can create file or directory clones -- and like a proper next-generation file system, it does so instantly, rather than having to wait for data to be copied. From the report:

Reply