You can make a difference in the Apple Support Community!

When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Windshadow99 Author

Level 1

34 points

More boot camp problems new 5k imac 3 tera fusion drive

there seems to be problems with Yosemite and boot camp assistant

i'm cross posting this to the iMac forum but I spent hours online with apple tech today and none of the several foks I talked to there had even seen a 5k 27" yet and my call back from Cupertino and engineering is no till tomorrow so I thought I should post here too

MMy bto 5k shipped from China sunday night and arrived in Maine this morning.... Amazing when you think about it for a bto

iinstallation and set up we're going fine and I started up boot camp assistant to create a temp boot camp while I wait for my thunder bay 4 box to take the drives for my old Mac pro when boot camp will have a1 tera SSD all to itself....

so carved off a 700 gig boot camp partition which the assistant formatted fat I then plugged is the lighting to FW adapter in a LaCie 2 tera fw 800 drive to act as a bridge to my LaCie DVD burner which uses the old fw400 cables and inserted my new shrink wrap win 8.1 retail 64 DVD and up comes the win 8 install in very tiny type in a tiny window which got a bit of a laugh out of me.

And I go through it to the point of selecting that boot camp partition and then said it could not use a fat partition and I should reformat it from the win 8.1 installer which I did and then it said it could not use and unknown partition so I said great and booted back to 10-10 and the boot camp tool to put things back and it said it could not I then went to disk tools and it also said the 3tera fusion could not be either reformatted or put back to a single partition I was on with tech support where I went up through 4 levels of support due to the 5k bto which most had no knowledge of. We tried the optioncommand r to get to DT and the same problem as did going to reinstall from the net which after a 30 min down load could not reformat either it is now kicked to Cupertino with a call back tomorrow

( At this point all I want to do is put the computer back in the condition it was in when i started with a plain Yosemite on an unpartitioned 3 tera fusion... Then deal with boot camp when it can have its own drive)

am betting it will take a Unix comand line to reformat but be aware there may be boot camp issues with my configuration

and any help here will be great fully received

iMac, OS X Yosemite (10.10)

Posted on Oct 21, 2014 4:04 PM

Top-ranking reply

Loner T

Level 9

59,513 points

Posted on Oct 21, 2014 6:04 PM

There is a much easier and cleaner method on the new iMac 5K, because it is a full UEFI machine and Windows 8.1 is UEFI compliant. The traditional bootcamp Hybrid MBR is a travesty on such a beautiful machine.

Please see this thread - Re: Problem installing Windows (7, 8.0, 8.1) on BOOTCAMP - Mavericks.

Initializing the internal disk may not be necessary at all but Command+Opt+R and DU is needed, if you really need to initialize the internal Fusion HD.

This thread can help you initialize the internal drive - Re: Can't format former Boot Camp partition

View in context

138 replies

Windshadow99 Author

Level 1

34 points

Oct 23, 2014 11:41 AM in response to Loner T

well after those pages at microsoft turned my brains to mush

(my real computer work as in orignal programing and totally understanding the hardware dates to the 60s PDP1o and punchcard fortran programs and grew to 6502 assembler fitting programs into 4k of ram on early apple][ computers i did a centronics printer driver back then for it.. but 2 things have kept me from proceeding today

1 heavy storms and flickering lights all day

2 the whole mush brain thing so i will attack tomorrow after i get over this headache caused by stuffing new info into my aging brain

i sure wish i could send you something for all your help... case of good beer or a bottle or 2 of good wine... without your help i would be up the creek or schlepping the computer to the nearest apple genius bar down in portland over an hours drive away.

cheers

Windy

Loner T

Level 9

59,513 points

Oct 23, 2014 11:47 AM in response to Windshadow99

Take your time, no rush. I grew up on DEC-10 TOPS (Hollerith cards and a DecWriter) and PDP-11s, VAX-11/7x0s, Burroughs6800s, FANUCs, TI,...

Have some good strong brewed tea (or coffee). I will be here. 😉

Windshadow99 Author

Level 1

34 points

Oct 27, 2014 5:06 AM in response to Loner T

ok it is time to byte the bullet and go for this thunderbolt external thunder bay box with a pair of 2 tera drives is ready to be installed and a copy of everything will be made with CCCloner before i start

Loner T wrote:

Thanks for posting this. It helps a lot and when you roll out of bed, you can implement what I suggest. If you notice, none of the virtual disks are now showing up in your diskutil list output. You stop at disk4, not disk19, etc..

Let me first provide an explanation, and then proceed further. The Windows MSR is a FAT partition. A FAT partition beyond the 2TB boundary cannot be addressed, by design of FAT. This mandates that the MSR partition should be within the first 2TB of the disk. the 600GB for Windows is past the 2TB at 2.4TB+. The W8.1 installer creates but cannot access it once created, so it never works.

Since you already have CoreStorage defined, there is no need to destroy it again. The physical disk (PV) which is the HD, needs to removed, re-partitioned and the higher chunk starting at 600GB+ till 3TB should be given to the CS volume for OSX. You need to make sure the next steps are executed ONLY if the disk space used in OSX is less than 120GB (as that is the limit of the SSD). If the HDD is removed, all data for Yosemite MUST fit on the SSD temporarily, till the HDD can be added back.

1. Verify that Macintosh HD is less than 120GB. It can be done by right-clicking on it in Finder and using "Get Info" or Command+I.

2. If #1 is true, then remove the PV (3TB HDD chunk disk1s2) from Core storage using (the data came from your diskutil cs list output)

diskutil cs removeDisk 4AA11193-404F-4A0B-A0BF-8815703F35F1

3. Run Disk Utility, and "Ignore" the "Fix", split it into two parts. The first part HDD1 is 600GB of Free Space, the remainder is 2.4TB of Mac OSX Extended Journaled.

4. Your 3TB HDD will look like EFI (200MB), Free Space (~600GB), MAC OSX (~2.4TB).

5. Run diskutil list.

6. Find out from Step 5, what disk1sN it is (N is what is needed).

7. Add the device from step 6 to CS volume as

diskutil cs addDisk 153ED13B-3675-40D1-9469-2E1A3B4167EC Step6-disk1sN.

8. Install W8.1 on the Free Space (~600GB). This will get split by W8.1 installer into MSR and MSD partitions. If you have issues, please post back here. You can directly use the EFI Boot from the W8.1 DVD. The advantage of the Bootcamp USB is that it will also install Bootcamp drivers automatically.

The adventure continues, with a hang(over)up though. 😉

This is the general syntax of the two commands used.

diskutil cs removeDisk

Usage: diskutil coreStorage removeDisk pvUUID

Remove a physical volume from its CoreStorage logical volume group.

Ownership of the affected disks is required.

Example: diskutil coreStorage removeDisk 11111111-2222-3333-4444-555555555555

diskutil cs addDisk

Usage: diskutil coreStorage addDisk lvgUUID NewMemberDeviceName

Add a new physical volume to a CoreStorage logical volume group.

Ownership of the affected disks is required.

Example: diskutil coreStorage addDisk

11111111-2222-3333-4444-555555555555 disk4s2

here is a fresh

diskutil cs list

CoreStorage logical volume groups (1 found)

+-- Logical Volume Group 153ED13B-3675-40D1-9469-2E1A3B4167EC

=========================================================

Name: OSX-FusionLVG

Status: Online

Size: 2520472952832 B (2.5 TB)

Free Space: 65536 B (65.5 KB)

+-< Physical Volume E5B22231-71E8-49A0-B823-C9CDD51DBB36

| ----------------------------------------------------

| Index: 0

| Disk: disk0s2

| Status: Online

| Size: 120988852224 B (121.0 GB)

+-< Physical Volume 4AA11193-404F-4A0B-A0BF-8815703F35F1

| ----------------------------------------------------

| Index: 1

| Disk: disk1s2

| Status: Online

| Size: 2399484100608 B (2.4 TB)

+-> Logical Volume Family 48FC4D5C-8729-4EB5-A194-0714015C26E5

----------------------------------------------------------

Encryption Status: Unlocked

Encryption Type: None

Conversion Status: NoConversion

Conversion Direction: -none-

Has Encrypted Extents: No

Fully Secure: No

Passphrase Required: No

+-> Logical Volume 2F8B1E82-11CC-4B2F-9AE8-A03854BF4E1E

---------------------------------------------------

Disk: disk2

Status: Online

Size (Total): 2514617630720 B (2.5 TB)

Conversion Progress: -none-

Revertible: No

LV Name: Macintosh HD

Volume Name: Macintosh HD

Content Hint: Apple_HFS

any changes from last weeks advice before i take the plunge? once more thanks for your hand holding

i have kept it below 120gb but i want a backup to be sure

Loner T

Level 9

59,513 points

Oct 27, 2014 6:52 AM in response to Windshadow99

You should backup, but the layout of the disks (especially the 3TB HDD) will change, which means restoring it can be done only using TM and Migration Assistant. TM (or other restore methods) that restore volumes will nullify your current and future work. 😉

Windshadow99 Author

Level 1

34 points

Oct 27, 2014 8:03 AM in response to Loner T

ok yes understood then i jus go ahead with the instructions above i am a bit unclear about

5. Run diskutil list.

6. Find out from Step 5, what disk1sN it is (N is what is needed).

N is a new number that shows up after i do 5 is that right?

and do I need to be in a recovery boot to do all this or is normal Yosemite desktop ok?

Loner T

Level 9

59,513 points

Oct 27, 2014 8:39 AM in response to Windshadow99

Yes, that is correct. N will start at 0. It may be better to be in Recovery Console, so the disks can be manipulated without any issues of locking.

Windshadow99 Author

Level 1

34 points

Oct 27, 2014 8:55 AM in response to Loner T

ok thiss is what i get from Step 2 and i loos like i screwed up some where this from local recovery boot

-bash-3.2# diskutil cs removeDisk 4AA11193-404F-4A0B-A0BF-8815703F35F1

Started CoreStorage operation

newfs_hfs: cannot create filesystem on /dev/rdisk3s2

: Resource busy

Mounting disk

Could not mount disk3s2 with name (null) after erase

Error: -69832: File system formatter failed

Loner T

Level 9

59,513 points

Oct 27, 2014 9:04 AM in response to Windshadow99

The GUIDs should not have changed. The string came from It looks correct. Run diskutil list and see if the disk became a separate slice outside the CS volume. You can also check using diskutil cs list and check if th following entry is still there or not.

+-< Physical Volume 4AA11193-404F-4A0B-A0BF-8815703F35F1

| ----------------------------------------------------

| Index: 1

| Disk: disk1s2

| Status: Online

| Size: 2399484100608 B (2.4 TB)

Windshadow99 Author

Level 1

34 points

Oct 27, 2014 9:17 AM in response to Loner T

seemes to be there should it be after the removedisk?

-bash-3.2# diskutil cs list

CoreStorage logical volume groups (1 found)

+-- Logical Volume Group 153ED13B-3675-40D1-9469-2E1A3B4167EC

=========================================================

Name: OSX-FusionLVG

Status: Online

Size: 2520472952832 B (2.5 TB)

Free Space: 65536 B (65.5 KB)

+-< Physical Volume E5B22231-71E8-49A0-B823-C9CDD51DBB36

| ----------------------------------------------------

| Index: 0

| Disk: disk0s2

| Status: Online

| Size: 120988852224 B (121.0 GB)

+-< Physical Volume 4AA11193-404F-4A0B-A0BF-8815703F35F1

| ----------------------------------------------------

| Index: 1

| Disk: disk3s2

| Status: Online

| Size: 2399484100608 B (2.4 TB)

+-> Logical Volume Family 48FC4D5C-8729-4EB5-A194-0714015C26E5

----------------------------------------------------------

Encryption Status: Unlocked

Encryption Type: None

Conversion Status: NoConversion

Conversion Direction: -none-

Has Encrypted Extents: No

Fully Secure: No

Passphrase Required: No

+-> Logical Volume 2F8B1E82-11CC-4B2F-9AE8-A03854BF4E1E

---------------------------------------------------

Disk: disk5

Status: Online

Size (Total): 2514617630720 B (2.5 TB)

Conversion Progress: -none-

Revertible: No

LV Name: Macintosh HD

Volume Name: Macintosh HD

Content Hint: Apple_HFS

-bash-3.2# diskutil cs

Usage: diskutil [quiet] coreStorage|CS <verb> <options>,

where <verb> is as follows:

list (Show status of CoreStorage volumes)

info[rmation] (Get CoreStorage information by UUID or disk)

convert (Convert a volume into a CoreStorage volume)

revert (Revert a CoreStorage volume to its native type)

create (Create a new CoreStorage logical volume group)

delete (Delete a CoreStorage logical volume group)

rename (Rename a CoreStorage logical volume group)

createVolume (Create a new CoreStorage logical volume)

deleteVolume (Delete a volume from a logical volume group)

encryptVolume (Encrypt a CoreStorage logical volume)

decryptVolume (Decrypt a CoreStorage logical volume)

unlockVolume (Attach/mount a locked CoreStorage logical volume)

changeVolumePassphrase (Change a CoreStorage logical volume's passphrase)

diskutil coreStorage <verb> with no options will provide help on that verb

Windshadow99 Author

Level 1

34 points

Oct 27, 2014 9:22 AM in response to Windshadow99

OOPS

-bash-3.2# diskutil list

/dev/disk0

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *121.3 GB disk0

1: EFI EFI 209.7 MB disk0s1

2: Apple_CoreStorage 121.0 GB disk0s2

3: Apple_Boot Boot OS X 134.2 MB disk0s3

/dev/disk1

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *2.0 TB disk1

1: EFI EFI 209.7 MB disk1s1

2: Apple_HFS CatBoat 2.0 TB disk1s2

/dev/disk2

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *2.0 TB disk2

1: EFI EFI 209.7 MB disk2s1

2: Apple_HFS FishingBoat 2.0 TB disk2s2

/dev/disk3

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *3.0 TB disk3

1: EFI EFI 209.7 MB disk3s1

2: Apple_HFS 2.4 TB disk3s2

3: DE94BBA4-06D1-4D40-A16A-BFD50179D6AC 314.6 MB disk3s4

4: EFI NO NAME 104.9 MB disk3s5

5: Microsoft Reserved 134.2 MB disk3s6

6: Microsoft Basic Data 599.7 GB disk3s7

/dev/disk4

#: TYPE NAME SIZE IDENTIFIER

0: Apple_partition_scheme *1.3 GB disk4

1: Apple_partition_map 30.7 KB disk4s1

2: Apple_HFS OS X Base System 1.3 GB disk4s2

/dev/disk5

#: TYPE NAME SIZE IDENTIFIER

0: Apple_HFS Macintosh HD *2.5 TB disk5

Logical Volume on disk0s2, disk3s2

2F8B1E82-11CC-4B2F-9AE8-A03854BF4E1E

Unencrypted Fusion Drive

/dev/disk6

#: TYPE NAME SIZE IDENTIFIER

0: untitled *5.2 MB disk6

/dev/disk7

#: TYPE NAME SIZE IDENTIFIER

0: untitled *524.3 KB disk7

/dev/disk8

#: TYPE NAME SIZE IDENTIFIER

0: untitled *524.3 KB disk8

/dev/disk9

#: TYPE NAME SIZE IDENTIFIER

0: untitled *524.3 KB disk9

/dev/disk10

#: TYPE NAME SIZE IDENTIFIER

0: untitled *524.3 KB disk10

/dev/disk11

#: TYPE NAME SIZE IDENTIFIER

0: untitled *524.3 KB disk11

/dev/disk12

#: TYPE NAME SIZE IDENTIFIER

0: untitled *6.3 MB disk12

/dev/disk13

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *2.0 TB disk13

1: EFI EFI 209.7 MB disk13s1

2: Microsoft Basic Data Union 500.1 GB disk13s2

3: Apple_HFS Shimmo 499.6 GB disk13s3

4: Apple_Boot Recovery HD 650.0 MB disk13s4

5: Apple_HFS Orange 500.1 GB disk13s5

6: Apple_HFS Newcastle 499.4 GB disk13s6

/dev/disk14

#: TYPE NAME SIZE IDENTIFIER

0: untitled *2.1 MB disk14

/dev/disk15

#: TYPE NAME SIZE IDENTIFIER

0: untitled *1.0 MB disk15

/dev/disk16

#: TYPE NAME SIZE IDENTIFIER

0: untitled *524.3 KB disk16

/dev/disk17

#: TYPE NAME SIZE IDENTIFIER

0: untitled *524.3 KB disk17

/dev/disk18

#: TYPE NAME SIZE IDENTIFIER

0: untitled *1.0 MB disk18

/dev/disk19

#: TYPE NAME SIZE IDENTIFIER

0: untitled *6.3 MB disk19

/dev/disk20

#: TYPE NAME SIZE IDENTIFIER

0: FDisk_partition_scheme *15.6 GB disk20

1: DOS_FAT_32 ABOOTCAMP 15.6 GB disk20s1

/dev/disk21

#: TYPE NAME SIZE IDENTIFIER

0: FDisk_partition_scheme *123.6 GB disk21

1: Windows_FAT_32 CORSAIR 123.6 GB disk21s1

Loner T

Level 9

59,513 points

Oct 27, 2014 9:27 AM in response to Windshadow99

1. I would recommend Command+Opt+R (Internet Recovery) rather than a local Recovery boot (Command+R).

2. If you type diskutil cs removeDisk and press return/enter you will see the syntax. The CS man page is broken.

The goal is to remove disk3s2 from the CS volume, repartition it and add it back, leaving the first 600GB as Free Space for Windows.

/dev/disk5

#: TYPE NAME SIZE IDENTIFIER

0: Apple_HFS Macintosh HD *2.5 TB disk5

Logical Volume on disk0s2, disk3s2

2F8B1E82-11CC-4B2F-9AE8-A03854BF4E1E

Unencrypted Fusion Drive

Windshadow99 Author

Level 1

34 points

Oct 27, 2014 9:26 AM in response to Loner T

does that mean we are starting over from scratch? i was trying tobe on the wagon this week too :-(

Loner T

Level 9

59,513 points

Oct 27, 2014 9:29 AM in response to Windshadow99

Windshadow99 wrote:

does that mean we are starting over from scratch? i was trying tobe on the wagon this week too :-(

No, we are leaving the SSD (121GB intact) and remove the slice of the 3TB disk, change it and add it back again. We should not have to start all over again, unless absolutely necessary.

Windshadow99 Author

Level 1

34 points

Oct 27, 2014 9:40 AM in response to Loner T

ok the here it is from a fresh internet recovery boot

-bash-3.2# diskutil cs removeDisk

Usage: diskutil coreStorage removeDisk pvUUID

Remove a physical volume from its CoreStorage logical volume group.

Ownership of the affected disks is required.

Example: diskutil coreStorage removeDisk 11111111-2222-3333-4444-555555555555

-bash-3.2# diskutil list

/dev/disk0

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *121.3 GB disk0

1: EFI EFI 209.7 MB disk0s1

2: Apple_CoreStorage 121.0 GB disk0s2

3: Apple_Boot Boot OS X 134.2 MB disk0s3

/dev/disk1

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *2.0 TB disk1

1: EFI EFI 209.7 MB disk1s1

2: Apple_HFS FishingBoat 2.0 TB disk1s2

/dev/disk2

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *3.0 TB disk2

1: EFI EFI 209.7 MB disk2s1

2: Apple_HFS 2.4 TB disk2s2

3: DE94BBA4-06D1-4D40-A16A-BFD50179D6AC 314.6 MB disk2s3

4: EFI NO NAME 104.9 MB disk2s4

5: Microsoft Reserved 134.2 MB disk2s5

6: Microsoft Basic Data 599.7 GB disk2s6

/dev/disk3

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *2.0 TB disk3

1: EFI EFI 209.7 MB disk3s1

2: Apple_HFS CatBoat 2.0 TB disk3s2

/dev/disk4

#: TYPE NAME SIZE IDENTIFIER

0: Apple_partition_scheme *1.3 GB disk4

1: Apple_partition_map 30.7 KB disk4s1

2: Apple_HFS OS X Base System 1.3 GB disk4s2

/dev/disk5

#: TYPE NAME SIZE IDENTIFIER

0: untitled *5.2 MB disk5

/dev/disk6

#: TYPE NAME SIZE IDENTIFIER

0: untitled *524.3 KB disk6

/dev/disk7

#: TYPE NAME SIZE IDENTIFIER

0: untitled *524.3 KB disk7

/dev/disk8

#: TYPE NAME SIZE IDENTIFIER

0: untitled *524.3 KB disk8

/dev/disk9

#: TYPE NAME SIZE IDENTIFIER

0: untitled *524.3 KB disk9

/dev/disk10

#: TYPE NAME SIZE IDENTIFIER

0: untitled *524.3 KB disk10

/dev/disk11

#: TYPE NAME SIZE IDENTIFIER

0: untitled *6.3 MB disk11

/dev/disk12

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *2.0 TB disk12

1: EFI EFI 209.7 MB disk12s1

2: Microsoft Basic Data Union 500.1 GB disk12s2

3: Apple_HFS Shimmo 499.6 GB disk12s3

4: Apple_Boot Recovery HD 650.0 MB disk12s4

5: Apple_HFS Orange 500.1 GB disk12s5

6: Apple_HFS Newcastle 499.4 GB disk12s6

/dev/disk13

#: TYPE NAME SIZE IDENTIFIER

0: untitled *2.1 MB disk13

/dev/disk14

#: TYPE NAME SIZE IDENTIFIER

0: untitled *1.0 MB disk14

/dev/disk15

#: TYPE NAME SIZE IDENTIFIER

0: untitled *524.3 KB disk15

/dev/disk16

#: TYPE NAME SIZE IDENTIFIER

0: untitled *524.3 KB disk16

/dev/disk17

#: TYPE NAME SIZE IDENTIFIER

0: untitled *1.0 MB disk17

/dev/disk18

#: TYPE NAME SIZE IDENTIFIER

0: FDisk_partition_scheme *15.6 GB disk18

1: DOS_FAT_32 ABOOTCAMP 15.6 GB disk18s1

/dev/disk19

#: TYPE NAME SIZE IDENTIFIER

0: untitled *6.3 MB disk19

/dev/disk20

#: TYPE NAME SIZE IDENTIFIER

0: FDisk_partition_scheme *123.6 GB disk20

1: Windows_FAT_32 CORSAIR 123.6 GB disk20s1

-bash-3.2# diskutil cs list

CoreStorage logical volume groups (1 found)

+-- Logical Volume Group 153ED13B-3675-40D1-9469-2E1A3B4167EC

=========================================================

Name: OSX-FusionLVG

Status: Offline

Size: 120988852224 B (121.0 GB)

Free Space: -none-

+-< Physical Volume E5B22231-71E8-49A0-B823-C9CDD51DBB36

| ----------------------------------------------------

| Index: 0

| Disk: disk0s2

| Status: Checking

| Size: 120988852224 B (121.0 GB)

+-< Physical Volume 4AA11193-404F-4A0B-A0BF-8815703F35F1

----------------------------------------------------

(No properties)

-bash-3.2#

Loner T

Level 9

59,513 points

Oct 27, 2014 9:48 AM in response to Windshadow99

Fantastic work, W. If you notice the 3TB disk is no longer part of the CS volume as shown by the cs list output.

Please run Disk Utility, and "Ignore" Fix, partition the 3TB disk as 600Gb Free Space in the first partition, and remainder as Mac os extended journaled.

More boot camp problems new 5k imac 3 tera fusion drive