Partitioning Error

Question

Level 1

18 points

Partitioning Error

I start up Boot Camp, select the Windows ISO file (Win10_1809Oct_v2_English_x64), and start the process. After downloading supporting files, an error is displayed stating that the partition failed and that the disc utility should be run to correct the error. I run the First Aid, and the result is that no error was found. If I run Boot Camp again, I get the same result.

I am running an iMac from late 2017 with Mojave up to date. I have a 1T drive which is about half full.

I don't know what else to do.

Thanks.

iMac 27", macOS 10.14

Posted on Apr 18, 2019 4:12 PM

Reply

Answer 1

Top-ranking reply

Loner T

Level 9

59,536 points

Apr 19, 2019 12:24 PM in response to KFR3

Start up your Mac in single-user mode or verbose mode - Apple Support and run

fsck_apfs -s -o -y /dev/rdisk1

If you get any errors, see the footnote under step 6. You may need to use Command+S on older Macs to get into Single User Mode.

Reply

Answer 2

Loner T

Level 9

59,536 points

Apr 18, 2019 6:07 PM in response to KFR3

Please try with W10 1803 (April) ISO.

See If Boot Camp Assistant stops responding or says 'Boot Camp installation failed' - Apple Support.

Reply

Answer 3

Loner T

Level 9

59,536 points

Apr 19, 2019 6:49 AM in response to KFR3

Post the output of

sudo fsck_apfs -n -l /dev/rdisk1

from macOS Terminal.

Reply

Answer 4

Loner T

Level 9

59,536 points

Apr 20, 2019 6:18 AM in response to KFR3

Can you re-run the Singe-User Mode fsck command and post a photograph of the output?

Reply

Answer 5

Loner T

Level 9

59,536 points

Apr 21, 2019 4:00 PM in response to KFR3

This is not Single-User Mode. Boot and hold Command+S.

Reply

Answer 6

KFR3 Author

Level 1

18 points

Apr 19, 2019 6:38 AM in response to Loner T

Did not help. Same error.

Reply

Answer 7

KFR3 Author

Level 1

18 points

Apr 19, 2019 7:09 PM in response to Loner T

I did this, and I received this message.

Error: container /dev/rdisk3 is mounted for write access.

Fred

Reply

Answer 8

Loner T

Level 9

59,536 points

Apr 19, 2019 7:21 PM in response to KFR3

Do you have a black screen which looks like a Console? If you do not, then you are not in Single User Mode. Your 2017 Mac uses the Command+S method. The Apple T2 Macs use the newer method.

Reply

Answer 9

KFR3 Author

Level 1

18 points

Apr 21, 2019 3:53 PM in response to Loner T

Here you go.

Reply

Answer 10

KFR3 Author

Level 1

18 points

Apr 21, 2019 9:05 PM in response to Loner T

Everything works now. The command you gave me yielded a long list of actions, and I think, found one error. The text was so small I could hardly read it. Thanks for help. I was able to run bootcamp.

Reply

Answer 11

Loner T

Level 9

59,536 points

Apr 22, 2019 3:49 AM in response to KFR3

Excellent.

Reply

Answer 12

KFR3 Author

Level 1

18 points

Apr 19, 2019 7:41 AM in response to Loner T

Here you go.

** Checking the container superblock.

** Checking the fusion superblock.

** Checking the EFI jumpstart record.

** Checking the space manager.

** Checking the space manager free queue trees.

** Checking the object map.

** Checking the Fusion data structures.

** Checking volume.

** Checking the APFS volume superblock.

** The volume Macintosh HD was formatted by hfs_convert (945.200.129) and last modified by apfs_kext (945.250.134).

** Checking the object map.

** Checking the snapshot metadata tree.

** Checking the snapshot metadata.

** Checking snapshot 1 of 1.

** Checking the extent ref tree.

** Checking the fsroot tree.

** Checking volume.

** Checking the APFS volume superblock.

** The volume Preboot was formatted by hfs_convert (945.200.129) and last modified by apfs_kext (945.250.134).

** Checking the object map.

** Checking the snapshot metadata tree.

** Checking the snapshot metadata.

** Checking the extent ref tree.

** Checking the fsroot tree.

** Checking volume.

** Checking the APFS volume superblock.

** The volume Recovery was formatted by diskmanagementd (945.200.129) and last modified by apfs_kext (945.250.134).

** Checking the object map.

** Checking the snapshot metadata tree.

** Checking the snapshot metadata.

** Checking the extent ref tree.

** Checking the fsroot tree.

** Checking volume.

** Checking the APFS volume superblock.

** The volume VM was formatted by apfs.util (945.200.129) and last modified by apfs_kext (945.250.134).

** Checking the object map.

** Checking the snapshot metadata tree.

** Checking the snapshot metadata.

** Checking the extent ref tree.

** Checking the fsroot tree.

error: found file extent gap (id 16) at logical address 2010804224 (expected 0)

** Verifying allocated space.

** Performing deferred repairs.

error: found file extent gap (id 16) at logical address 0+2010804224

Insert missing file extent object? NO

Deferred repairs failed.

** The volume /dev/rdisk1 could not be verified completely.

I see one error at end. Thanks for the ongoing help.

Reply

Answer 13

KFR3 Author

Level 1

18 points

Apr 20, 2019 4:31 AM in response to Loner T

The screen was black.

Reply

Partitioning Error

Similar questions