Problem with early 2011 MacBook Pro. Circle with line

Question

Level 1

0 points

Problem with early 2011 MacBook Pro. Circle with line

Im having trouble starting my MacBook Pro. I've been trying to troubleshoot the issue myself but am having no luck. When I turn on my laptop, it tells me to put in my password, then it tries to start up but changes to a circle with a line through it. I googled those symptoms and tried following some guides to reboot. Nothing seemed to work. I entered recover mode by restarting comp and holding command r. I attempted to reinstall mavericks so that I could restore using timemachine that I backed up a few days ago onto an external harddrive. When I goto reinstall mavericks, it only recognizes a partition that I made in my harddrive the other day. I suspect the issue I'm having is around this partition. When I launch disk utility the partition that I need to reinstall mavericks is not mounted and I'm not sure how to mount it. The other partition should be empty, I was trying to delete the partitons because I no longer needed them. (I originally wanted to dual boot ubuntu on mac but decided to just use a virtual box.) does anyone have any ideas about what I can do? If you need more info il try my best to help. Thanks

Posted on Jan 25, 2014 8:44 AM

Reply

Answer 1

Melophage

Level 5

7,213 points

Jan 25, 2014 11:09 AM in response to Nriz

Nriz,

reboot into Recovery mode and from the Utilities menu on the menu bar, select Terminal. Within the Terminal window give it the following commands, one per line, pressing the Return key after each command:

diskutil list

diskutil cs list

mount

Please include in your reply the full output from these commands.

Reply

Answer 2

Nriz Author

Level 1

0 points

Jan 25, 2014 11:23 AM in response to Melophage

-bash-3.2# diskutil list

/dev/disk0

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *500.1 GB disk0

1: EFI EFI 209.7 MB disk0s1

2: FFFFFFFF-FFFF-FFFF-FFFF-FFFFFFFFFFFF 457.5 GB disk0s2

3: Apple_HFS Recovery HD 650.0 MB disk0s3

4: Linux Swap 1.1 GB disk0s4

5: Linux Swap 1.2 GB disk0s5

6: Apple_HFS disk0s7 38.2 GB disk0s6

/dev/disk1

#: TYPE NAME SIZE IDENTIFIER

0: Apple_partition_scheme *1.3 GB disk1

1: Apple_partition_map 30.7 KB disk1s1

2: Apple_HFS OS X Base System 1.3 GB disk1s2

/dev/disk2

#: TYPE NAME SIZE IDENTIFIER

0: untitled *524.3 KB disk2

/dev/disk3

#: TYPE NAME SIZE IDENTIFIER

0: untitled *524.3 KB disk3

/dev/disk4

#: TYPE NAME SIZE IDENTIFIER

0: untitled *524.3 KB disk4

/dev/disk5

#: TYPE NAME SIZE IDENTIFIER

0: untitled *524.3 KB disk5

/dev/disk6

#: TYPE NAME SIZE IDENTIFIER

0: untitled *524.3 KB disk6

/dev/disk7

#: TYPE NAME SIZE IDENTIFIER

0: untitled *6.3 MB disk7

/dev/disk8

#: TYPE NAME SIZE IDENTIFIER

0: untitled *2.1 MB disk8

/dev/disk9

#: TYPE NAME SIZE IDENTIFIER

0: untitled *1.0 MB 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 *1.0 MB disk12

-bash-3.2# diskutil cs list

No CoreStorage logical volume groups found

-bash-3.2# mount

/dev/disk1s2 on / (hfs, local, read-only)

devfs on /dev (devfs, local, nobrowse)

/dev/disk2 on /Volumes (hfs, local, union, nobrowse)

/dev/disk3 on /private/var/tmp (hfs, local, union, nobrowse)

/dev/disk4 on /private/var/run (hfs, local, union, nobrowse)

/dev/disk5 on /System/Installation (hfs, local, union, nobrowse)

/dev/disk6 on /private/var/db (hfs, local, union, nobrowse)

/dev/disk7 on /private/var/folders (hfs, local, union, nobrowse)

/dev/disk8 on /private/var/root/Library (hfs, local, union, nobrowse)

/dev/disk9 on /Library/ColorSync/Profiles/Displays (hfs, local, union, nobrowse)

/dev/disk10 on /Library/Preferences (hfs, local, union, nobrowse)

/dev/disk11 on /Library/Preferences/SystemConfiguration (hfs, local, union, nobrowse)

/dev/disk12 on /Library/Keychains (hfs, local, union, nobrowse)

/dev/disk0s6 on /Volumes/disk0s7 (hfs, local, journaled)

/dev/disk0s3 on /Volumes/Image Volume (hfs, local, read-only, journaled)

-bash-3.2#

Reply

Answer 3

Nriz Author

Level 1

0 points

Jan 25, 2014 11:30 AM in response to Nriz

disk0s2 is the main portion of the partition that I mentioned in my OP. I partitioned off 40gb for ubuntu and thats disk0s6. disk os4 and 5 are supposed to be part of the 40gb partitioned off, but in order to install ubuntu I had to label them as linux swap.

When I tried to install mavericks again, it would only let me choose disk 0s6.

Disk 0s2 is grey, which I think means un-mounted, in disk utility.

Reply

Answer 4

Melophage

Level 5

7,213 points

Jan 25, 2014 11:45 AM in response to Nriz

Nriz,

is everything that you need in your Time Machine backup, or do you need to preserve anything that’s currently on the internal disk? As you can see by looking at the disk0s2 entry, it no longer recognizes disk0s2 as having an Apple_HFS partition type.

Reply

Answer 5

Nriz Author

Level 1

0 points

Jan 25, 2014 11:52 AM in response to Melophage

Is it possible to give it an apple hfs partition? I'm not positive but I think I downloaded a dogecoin wallet after I backed up to the external hd. So I might lose around 3000 doge if I can't recover the wallet. There's nothing else besides the wallet that I would need though. And if that can't be recovered it's not the end of the world for me.

Reply

Answer 6

Melophage

Level 5

7,213 points

Jan 25, 2014 12:09 PM in response to Nriz

Nriz,

it’s possible, but not guaranteed — the filesystem in that partition might be corrupted. For the first step, go back into Recovery mode’s Terminal, and give it the following command:

gpt show disk0

Again, please include its full output in your reply.

Reply

Answer 7

Nriz Author

Level 1

0 points

Jan 25, 2014 12:45 PM in response to Melophage

-bash-3.2# gpt show disk0

start size index contents

0 1 PMBR

1 1 Pri GPT header

2 32 Pri GPT table

34 6

40 409600 1 GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B

409640 893637936 2 GPT part - FFFFFFFF-FFFF-FFFF-FFFF-FFFFFFFFFFFF

894047576 1269536 3 GPT part - 48465300-0000-11AA-AA11-00306543ECAC

895317112 904

895318016 2117632 4 GPT part - 0657FD6D-A4AB-43C4-84E5-0933C84B4F4F

897435648 2062336

899497984 2318336 5 GPT part - 0657FD6D-A4AB-43C4-84E5-0933C84B4F4F

901816320 74694664 6 GPT part - 48465300-0000-11AA-AA11-00306543ECAC

976510984 262151

976773135 32 Sec GPT table

976773167 1 Sec GPT header

-bash-3.2#

Thank you for helping me by the way, you're kind of awesome.

Reply

Answer 8

Melophage

Level 5

7,213 points

Jan 25, 2014 1:35 PM in response to Nriz

Nriz,

since it’s the partition at index 2 that will be changed, its parameters will be the ones which will be used in the commands below. The partition will be deleted from the partition table, then added again with the right partition type; the partition’s contents will not be affected by these two commands. I’d recommend copying and pasting here, since a typo in these commands will not help things:

gpt remove -b 409640 -s 893637936 -t FFFFFFFF-FFFF-FFFF-FFFF-FFFFFFFFFFFF disk0
gpt add -b 409640 -s 893637936 -t 48465300-0000-11AA-AA11-00306543ECAC disk0

(If the forum software wraps these commands, note that each gpt command line should be provided on a single line, and the UUIDs should not have spaces separating their constitutent parts.)

After these commands have been run, do the following commands to ensure that everything looks OK, partition-wise:

gpt show disk0

diskutil list

Please include their full output in your reply.

You’re welcome — I’m glad that I can lend a hand.

Reply

Answer 9

Nriz Author

Level 1

0 points

Jan 25, 2014 4:43 PM in response to Melophage

-bash-3.2# gpt remove -b 409640 -s 893637936 -t FFFFFFFF-FFFF-FFFF-FFFF-FFFFFFFFFFFF disk0

gpt remove: unable to open device 'disk0': Resource busy

-bash-3.2# gpt add -b 409640 -s 893637936 -t 48465300-0000-11AA-AA11-00306543ECAC disk0

gpt add: unable to open device 'disk0': Resource busy

-bash-3.2# gpt show disk0

start size index contents

0 1 PMBR

1 1 Pri GPT header

2 32 Pri GPT table

34 6

40 409600 1 GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B

409640 893637936 2 GPT part - FFFFFFFF-FFFF-FFFF-FFFF-FFFFFFFFFFFF

894047576 1269536 3 GPT part - 48465300-0000-11AA-AA11-00306543ECAC

895317112 904

895318016 2117632 4 GPT part - 0657FD6D-A4AB-43C4-84E5-0933C84B4F4F

897435648 2062336

899497984 2318336 5 GPT part - 0657FD6D-A4AB-43C4-84E5-0933C84B4F4F

901816320 74694664 6 GPT part - 48465300-0000-11AA-AA11-00306543ECAC

976510984 262151

976773135 32 Sec GPT table

976773167 1 Sec GPT header

-bash-3.2# diskutil list

/dev/disk0

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *500.1 GB disk0

1: EFI EFI 209.7 MB disk0s1

2: FFFFFFFF-FFFF-FFFF-FFFF-FFFFFFFFFFFF 457.5 GB disk0s2

3: Apple_HFS Recovery HD 650.0 MB disk0s3

4: Linux Swap 1.1 GB disk0s4

5: Linux Swap 1.2 GB disk0s5

6: Apple_HFS disk0s7 38.2 GB disk0s6

/dev/disk1

#: TYPE NAME SIZE IDENTIFIER

0: Apple_partition_scheme *1.3 GB disk1

1: Apple_partition_map 30.7 KB disk1s1

2: Apple_HFS OS X Base System 1.3 GB disk1s2

/dev/disk2

#: TYPE NAME SIZE IDENTIFIER

0: untitled *524.3 KB disk2

/dev/disk3

#: TYPE NAME SIZE IDENTIFIER

0: untitled *524.3 KB disk3

/dev/disk4

#: TYPE NAME SIZE IDENTIFIER

0: untitled *524.3 KB disk4

/dev/disk5

#: TYPE NAME SIZE IDENTIFIER

0: untitled *524.3 KB disk5

/dev/disk6

#: TYPE NAME SIZE IDENTIFIER

0: untitled *524.3 KB disk6

/dev/disk7

#: TYPE NAME SIZE IDENTIFIER

0: untitled *6.3 MB disk7

/dev/disk8

#: TYPE NAME SIZE IDENTIFIER

0: untitled *2.1 MB disk8

/dev/disk9

#: TYPE NAME SIZE IDENTIFIER

0: untitled *1.0 MB 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 *1.0 MB disk12

-bash-3.2#

Reply

Answer 10

Melophage

Level 5

7,213 points

Jan 25, 2014 6:45 PM in response to Nriz

Nriz,

it didn’t show disk0s2 as being mounted before, so I’m surprised that the gpt commands returned with the “resource busy” error. Try doing the following command before repeating the gpt remove and gpt add commands:

umount -A

Do the gpt commands still return the “resource busy” error?

Reply

Answer 11

Nriz Author

Level 1

0 points

Jan 26, 2014 5:50 AM in response to Melophage

Still getting the resource busy error:

-bash-3.2# umount -A

umount(/Volumes/Image Volume): Resource busy -- try 'diskutil unmount'

umount(/private/var/root/Library): Resource busy -- try 'diskutil unmount'

umount(/private/var/folders): Resource busy -- try 'diskutil unmount'

umount(/private/var/db): Resource busy -- try 'diskutil unmount'

umount(/private/var/run): Resource busy -- try 'diskutil unmount'

umount(/private/var/tmp): Resource busy -- try 'diskutil unmount'

umount(/Volumes): Resource busy -- try 'diskutil unmount'

umount(/dev): Resource busy -- try 'diskutil unmount'

-bash-3.2# gpt remove -b 409640 -s 893637936 -t FFFFFFFF-FFFF-FFFF-FFFF-FFFFFFFFFFFF disk0

gpt remove: unable to open device 'disk0': Resource busy

-bash-3.2# gpt add -b 409640 -s 893637936 -t 48465300-0000-11AA-AA11-00306543ECAC disk0

gpt add: unable to open device 'disk0': Resource busy

-bash-3.2#

Should I go ahead and try the diskutil unmount command?

Reply

Answer 12

Melophage

Level 5

7,213 points

Jan 26, 2014 2:01 PM in response to Nriz

Nriz,

yes, go ahead and try it on each of them above — it can’t hurt.

Reply

Answer 13

Nriz Author

Level 1

0 points

Jan 26, 2014 2:38 PM in response to Melophage

Sorry, when you say try it each above, what would that look like. Would I just type 'diskutil unmount' and hit enter? or would I have to say

'diskutil unmount umount(/Volumes/Image Volume)'

then

'diskutil unmount umount(/private/var/root/Library)'

and so on?

Or should it look different? Sorry I'm somewhat of a novice in Terminal

Reply

Answer 14

Melophage

Level 5

7,213 points

Jan 26, 2014 3:35 PM in response to Nriz

Nriz,

command-line programs often have documentation that can be accessed via the man command, e.g. man diskutil can be used to find the parameters for the diskutil command. In this case, something like

diskutil unmount '/Volumes/Image Volume'

should work. (Names with spaces in them need to be surrounded by quotes so that their parts aren’t interpreted as being separate parameters.)

Reply

Answer 15

Nriz Author

Level 1

0 points

Jan 26, 2014 4:41 PM in response to Melophage

-bash-3.2# diskutil unmount '/Volumes/Image Volume'

Volume Recovery HD on disk0s3 failed to unmount

-bash-3.2# diskutil unmount 'private/var/root/Library/'

Unmount failed for private/var/root/Library/

I tried the others and I received "Unmount failed for ____"

Reply