Windows 7 partition (bootcamp) missing after Yosemite update
Hi, I just recently updated my OS to Yosemite and now my windows partition is missing. I saw LonerT was helping others with a similar problem and was hoping if I could get some help as well since I am very bad with computers.
As for the command outputs:
Last login: Sun Jan 4 16:50:25 on console
Jamess-MacBook-Pro:~ jamesrhee$ diskutil list
/dev/disk0
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *500.3 GB disk0
1: EFI EFI 209.7 MB disk0s1
2: Apple_CoreStorage 350.0 GB disk0s2
3: Apple_Boot Recovery HD 650.0 MB disk0s3
4: Microsoft Basic Data 70.4 GB disk0s4
/dev/disk1
#: TYPE NAME SIZE IDENTIFIER
0: Apple_HFS Macintosh HD *349.6 GB disk1
Logical Volume on disk0s2
A2DFE5A5-01F0-44A6-B5DB-E47A17372B23
Unencrypted
Jamess-MacBook-Pro:~ jamesrhee$ diskutil cs list
CoreStorage logical volume groups (1 found)
|
+-- Logical Volume Group 8CD970FC-C3B9-49C1-8C04-AB6A87B90D43
=========================================================
Name: Macintosh HD
Status: Online
Size: 349999996928 B (350.0 GB)
Free Space: 18882560 B (18.9 MB)
|
+-< Physical Volume 14E3361B-B8FC-4FE4-8112-DBA81BDBD154
| ----------------------------------------------------
| Index: 0
| Disk: disk0s2
| Status: Online
| Size: 349999996928 B (350.0 GB)
|
+-> Logical Volume Family 81BEBCE6-658C-4E20-93B8-4F89FC3591C9
Encryption Status: Unlocked
Encryption Type: None
Conversion Status: NoConversion
Conversion Direction: -none-
Has Encrypted Extents: No
Fully Secure: No
Passphrase Required: No
|
+-> Logical Volume A2DFE5A5-01F0-44A6-B5DB-E47A17372B23
Disk: disk1
Status: Online
Size (Total): 349628792832 B (349.6 GB)
Conversion Progress: -none-
Revertible: Yes (no decryption required)
LV Name: Macintosh HD
Volume Name: Macintosh HD
Content Hint: Apple_HFS
Jamess-MacBook-Pro:~ jamesrhee$ sudo gpt -vv -r show /dev/disk0
WARNING: Improper use of the sudo command could lead to data loss
or the deletion of important system files. Please double-check your
typing when using sudo. Type "man sudo" for more information.
To proceed, enter your password, or type Ctrl-C to abort.
Password:
gpt show: /dev/disk0: mediasize=500277790720; sectorsize=512; blocks=977105060
gpt show: /dev/disk0: Suspicious MBR at sector 0
gpt show: /dev/disk0: Pri GPT at sector 1
gpt show: /dev/disk0: Sec GPT at sector 977105059
start size index contents
0 1 MBR
1 1 Pri GPT header
2 32 Pri GPT table
34 6
40 409600 1 GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
409640 683593744 2 GPT part - 53746F72-6167-11AA-AA11-00306543ECAC
684003384 1269536 3 GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC
685272920 154298536
839571456 137533440 4 GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7
977104896 131
977105027 32 Sec GPT table
977105059 1 Sec GPT header
Jamess-MacBook-Pro:~ jamesrhee$ sudo fdisk /dev/disk0
Disk: /dev/disk0 geometry: 60821/255/63 [977105060 sectors]
Signature: 0xAA55
Starting Ending
#: id cyl hd sec - cyl hd sec [ start - size]
1: EE 1023 254 63 - 1023 254 63 [ 1 - 409639] <Unknown ID>
2: AC 1023 254 63 - 1023 254 63 [ 409640 - 683593744] <Unknown ID>
3: AB 1023 254 63 - 1023 254 63 [ 684003384 - 1269536] Darwin Boot
4: 0C 1023 254 63 - 1023 254 63 [ 839571456 - 137533440] Win95 FAT32L
Jamess-MacBook-Pro:~ jamesrhee$ sudo dd if=/dev/rdisk0s4 count=1 2>/dev/null | hexdump -C
Password:
00000000 22 46 69 6c 74 65 72 73 22 0a 7b 0a 09 22 66 61 |"Filters".{.."fa|
00000010 76 6f 72 69 74 65 73 22 0a 09 7b 0a 09 7d 0a 09 |vorites"..{..}..|
00000020 22 68 69 73 74 6f 72 79 22 0a 09 7b 0a 09 09 22 |"history"..{..."|
00000030 31 22 0a 09 09 7b 0a 09 09 09 22 6e 61 6d 65 22 |1"...{...."name"|
00000040 09 09 22 32 30 38 2e 37 38 2e 31 36 35 2e 32 31 |.."208.78.165.21|
00000050 38 3a 32 37 30 35 39 22 0a 09 09 09 22 61 64 64 |8:27059"...."add|
00000060 72 65 73 73 22 09 09 22 32 30 38 2e 37 38 2e 31 |ress".."208.78.1|
00000070 36 35 2e 32 31 38 3a 32 37 30 35 39 22 0a 09 09 |65.218:27059"...|
00000080 09 22 4c 61 73 74 50 6c 61 79 65 64 22 09 09 22 |."LastPlayed".."|
00000090 31 33 39 30 35 33 36 35 34 32 22 0a 09 09 09 22 |1390536542"...."|
000000a0 61 70 70 69 64 22 09 09 22 30 22 0a 09 09 09 22 |appid".."0"...."|
000000b0 61 63 63 6f 75 6e 74 69 64 22 09 09 22 30 22 0a |accountid".."0".|
000000c0 09 09 7d 0a 09 09 22 32 22 0a 09 09 7b 0a 09 09 |..}..."2"...{...|
000000d0 09 22 6e 61 6d 65 22 09 09 22 32 30 38 2e 37 38 |."name".."208.78|
000000e0 2e 31 36 35 2e 32 31 36 3a 32 37 30 34 31 22 0a |.165.216:27041".|
000000f0 09 09 09 22 61 64 64 72 65 73 73 22 09 09 22 32 |..."address".."2|
00000100 30 38 2e 37 38 2e 31 36 35 2e 32 31 36 3a 32 37 |08.78.165.216:27|
00000110 30 34 31 22 0a 09 09 09 22 4c 61 73 74 50 6c 61 |041"...."LastPla|
00000120 79 65 64 22 09 09 22 31 33 39 30 35 33 39 30 32 |yed".."139053902|
00000130 34 22 0a 09 09 09 22 61 70 70 69 64 22 09 09 22 |4"...."appid".."|
00000140 30 22 0a 09 09 09 22 61 63 63 6f 75 6e 74 69 64 |0"...."accountid|
00000150 22 09 09 22 30 22 0a 09 09 7d 0a 09 09 22 33 22 |".."0"...}..."3"|
00000160 0a 09 09 7b 0a 09 09 09 22 6e 61 6d 65 22 09 09 |...{...."name"..|
00000170 22 32 30 38 2e 37 38 2e 31 36 35 2e 36 33 3a 32 |"208.78.165.63:2|
00000180 37 30 32 32 22 0a 09 09 09 22 61 64 64 72 65 73 |7022"...."addres|
00000190 73 22 09 09 22 32 30 38 2e 37 38 2e 31 36 35 2e |s".."208.78.165.|
000001a0 36 33 3a 32 37 30 32 32 22 0a 09 09 09 22 4c 61 |63:27022"...."La|
000001b0 73 74 50 6c 61 79 65 64 22 09 09 22 31 33 39 30 |stPlayed".."1390|
000001c0 37 32 35 37 30 36 22 0a 09 09 09 22 61 70 70 69 |725706"...."appi|
000001d0 64 22 09 09 22 30 22 0a 09 09 09 22 61 63 63 6f |d".."0"...."acco|
000001e0 75 6e 74 69 64 22 09 09 22 30 22 0a 09 09 7d 0a |untid".."0"...}.|
000001f0 09 09 22 34 22 0a 09 09 7b 0a 09 09 09 22 6e 61 |.."4"...{...."na|
00000200
Jamess-MacBook-Pro:~ jamesrhee$
I tried running deeper search via testdisk but I came across about 20 different MS data and thought I must've done something wrong. Thanks in advance!
Twenty entries may seem overwhelming, but checking each one using P - List Files should be fairly quick and painless. Most partitions will be damaged anyway.
Similar Messages
-
Bootcamp disk0s4 after Yosemite update (fdisk and testdisk info)
Hello everyone and Loner T,
I've been following the threads where similar issues were reported. I downloaded Testdisk and GPT disk. And I've been trying to follow the directions as best I could on my own to provide you with the information needed for support. I have a 40 GB Windows 7 Bootcamp partition on a 200 GB Macbook Pro Early 2008 HDD. Before the Yosemite upgrade, I have successfully added another 10 GB to the windows partition by shrinking the Mac OS partition. After the upgrade, the bootcamp was not visible as a bootable partition to be selected after restart and displayed as disk0s4 in Disk Utility. In addition, the 10 GB are now displayed as unallocated space. I have since downgraded to Mavericks 10.9.5 since Yosemite keeps on lagging on my maschine. I hope you can help me too recover the data stuck under Windows. Thank you for your kind assistance.
1. I have run the following commands in terminal with the specified output:
diskutil list
diskutil cs list
sudo gpt -vv -r show /dev/disk0
sudo fdisk /dev/disk0
Last login: Mon Dec 15 22:00:47 on console
Robert-4:~ RGl$ diskutil list
/dev/disk0
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *200.0 GB disk0
1: EFI EFI 209.7 MB disk0s1
2: Apple_HFS Star Cluster 149.2 GB disk0s2
3: Apple_Boot Recovery HD 650.0 MB disk0s3
4: Microsoft Basic Data 40.0 GB disk0s4
Robert-4:~ RGl$ diskutil cs list
No CoreStorage logical volume groups found
Robert-4:~ RGl$ sudo gpt -vv -r show /dev/disk0
Password:
gpt show: /dev/disk0: mediasize=200049647616; sectorsize=512; blocks=390721968
gpt show: /dev/disk0: Suspicious MBR at sector 0
gpt show: /dev/disk0: Pri GPT at sector 1
gpt show: /dev/disk0: Sec GPT at sector 390721967
start size index contents
0 1 MBR
1 1 Pri GPT header
2 32 Pri GPT table
34 6
40 409600 1 GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
409640 291386712 2 GPT part - 48465300-0000-11AA-AA11-00306543ECAC
291796352 1269536 3 GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC
293065888 19532640
312598528 78123008 4 GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7
390721536 399
390721935 32 Sec GPT table
390721967 1 Sec GPT header
Robert-4:~ RGl$ sudo fdisk /dev/disk0
Disk: /dev/disk0 geometry: 24321/255/63 [390721968 sectors]
Signature: 0xAA55
Starting Ending
#: id cyl hd sec - cyl hd sec [ start - size]
1: EE 0 0 2 - 1023 254 63 [ 1 - 312598527] <Unknown ID>
*2: 07 1023 254 63 - 1023 254 63 [ 312598528 - 78123008] HPFS/QNX/AUX
3: 00 0 0 0 - 0 0 0 [ 0 - 0] unused
4: 00 0 0 0 - 0 0 0 [ 0 - 0] unused
2. I have followed the instructions in Bootcamp win8.1 autorepair fail after yosemite upgrade post to perform a deep search in Testdisk.
After analyzing the EFI GPT partition map, Testdisk returns:
Disk /dev/disk0 - 200 GB / 186 GiB - 390721968 sectors (RO)
Current partition structure:
Partition Start End Size in sectors
1 P EFI System 40 409639 409600 [EFI System Partition]
2 P Mac HFS 409640 291796351 291386712 [Star Cluster]
3 P Mac Boot 291796352 293065887 1269536 [Recovery HD]
No FAT, NTFS, ext2, JFS, Reiser, cramfs or XFS marker
4 P MS Data 312598528 390721535 78123008 [BOOTCAMP]
QuickSearch returns:
Disk /dev/disk0 - 200 GB / 186 GiB - 390721968 sectors (RO)
The harddisk (200 GB / 186 GiB) seems too small! (< 250 GB / 232 GiB)
Check the harddisk size: HD jumpers settings, BIOS detection...
The following partitions can't be recovered:
Partition Start End Size in sectors
> MS Data 390721535 488376311 97654777
Mac HFS 390721924 391991459 1269536
Continue on MS Data returns:
Disk /dev/disk0 - 200 GB / 186 GiB - 390721968 sectors (RO)
Partition Start End Size in sectors
>P EFI System 40 409639 409600 [EFI]
D Mac HFS 409640 291796351 291386712
D MS Data 195411976 293066752 97654777
D Mac HFS 291796352 293065887 1269536
D MS Data 293066752 390721528 97654777
D MS Data 293066759 390721535 97654777
D Mac HFS 389452392 390721927 1269536The first entry you posted is the correct one. Glad to see you found it. I have this table to make sure no existing partitions are lost.
GPT 3 Start
GPT 3 Size
GPT 3 End
NTFS Start
Sector Offset
NTFS Size
NTFS End
291796352
1269536
293065888
293066752
864
97654777
390721528
The 'Sector Offset' being positive is good. A negative value means you lose GPT#3. The NTFS size is roughly 48GB which is good.
You need to use the following steps. If you see any error messages during the following steps, please stop and post back here with the error message. The following steps have values from your Testdisk output (and you can verify) in Steps 7 and 8.
Rebuild GPT4 using start/end offsets
Sudo gdisk /dev/rdisk0
P (print the full list of parts)
D (delete)
4 (part 4)
N (new part)
4 (part 4)
293066752 - Start offset in bytes (start point for Bootcamp part)
+97654777 (Size offset as opposed to End offset)
0700 (Windows part type)
P (print list of all parts just to see what changes will be made)
W (Write the new GPT)
Y (Yes! really write the new GPT)
This will delete and re-write the GPT partition info for /dev/disk0s4.
Rebuild MBR to match the new GPT information thus resetting the Hybrid MBR. Use defaults for other questions (like partition codes).
Sudo gdisk /dev/disk0
P (Print list of parts)
R (Recover)
H (chooses Hybrid)
Partitions numbers to be hybridized: 2 3 4
Y (Good for GRUB question)
N (part 2 boot flag)
N (part 3 boot flag)
Y (part 4 boot flag make NTFS bootable partition)
W (Write the new MBR)
Y (Yes! write the new MBR)
Reboot
Test 1 - Does Bootcamp Volume show up in Finder?
Test 2 - Can you see files in Bootcamp Volume?
Test 3 - Can you select Bootcamp in System Preferences -> Startup Disk?
Test 4 - If Test 3 is successful, select Bootcamp and Click Restart
If you see a hanging underline cursor at the top left on a black screen, and it does not proceed further, you may need Windows Startup Repair or a tool called EasyBCD. -
Windows 7 partition got corrupted after yosemite upgrade
Loner T please help. I can't believe Apple would do this to me. After Yosemite upgrade, windows 7 keeps booting into setup or recovery.
Salmans-MBP-2:~ salman$ diskutil list
/dev/disk0
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *600.1 GB disk0
1: EFI EFI 209.7 MB disk0s1
2: Apple_HFS OS X 199.5 GB disk0s2
3: Apple_Boot Recovery HD 650.0 MB disk0s3
4: Microsoft Basic Data Windows 7 300.0 GB disk0s4
5: Microsoft Basic Data 99.8 GB disk0s5
Salmans-MBP-2:~ salman$ diskutil cs list
No CoreStorage logical volume groups found
Salmans-MBP-2:~ salman$ sudo gpt -vv -r show /dev/disk0
Password:
gpt show: /dev/disk0: mediasize=600127266816; sectorsize=512; blocks=1172123568
gpt show: /dev/disk0: Suspicious MBR at sector 0
gpt show: /dev/disk0: Pri GPT at sector 1
gpt show: /dev/disk0: Sec GPT at sector 1172123567
start size index contents
0 1 MBR
1 1 Pri GPT header
2 32 Pri GPT table
34 6
40 409600 1 GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
409640 389617848 2 GPT part - 48465300-0000-11AA-AA11-00306543ECAC
390027488 1269536 3 GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC
391297024 585936896 4 GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7
977233920 194887680 5 GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7
1172121600 1935
1172123535 32 Sec GPT table
1172123567 1 Sec GPT header
Salmans-MBP-2:~ salman$ sudo fdisk /dev/disk0
Disk: /dev/disk0 geometry: 72961/255/63 [1172123568 sectors]
Signature: 0xAA55
Starting Ending
#: id cyl hd sec - cyl hd sec [ start - size]
1: EE 1023 254 63 - 1023 254 63 [ 1 - 409639] <Unknown ID>
2: AF 1023 254 63 - 1023 254 63 [ 409640 - 389617848] HFS+
3: AB 1023 254 63 - 1023 254 63 [ 390027488 - 1269536] Darwin Boot
*4: 07 1023 254 63 - 1023 254 63 [ 391297024 - 585936896] HPFS/QNX/AUX
Salmans-MBP-2:~ salman$
Salmans-MBP-2:~ salman$
Salmans-MBP-2:~ salman$
Salmans-MBP-2:~ salman$ çsudo dd if=/dev/rdisk0s4 count=1 2>/dev/null | hexdump -C
Password:
00000000 eb 52 90 4e 54 46 53 20 20 20 20 00 02 08 00 00 |.R.NTFS .....|
00000010 00 00 00 00 00 f8 00 00 3f 00 ff 00 00 b8 52 17 |........?.....R.|
00000020 00 00 00 00 80 00 80 00 ff 5f 8a 2e 00 00 00 00 |........._......|
00000030 00 00 0c 00 00 00 00 00 02 00 00 00 00 00 00 00 |................|
00000040 f6 00 00 00 01 00 00 00 e0 4f 34 ba 5b 34 ba c0 |.........O4.[4..|
00000050 00 00 00 00 fa 33 c0 8e d0 bc 00 7c fb 68 c0 07 |.....3.....|.h..|
00000060 1f 1e 68 66 00 cb 88 16 0e 00 66 81 3e 03 00 4e |..hf......f.>..N|
00000070 54 46 53 75 15 b4 41 bb aa 55 cd 13 72 0c 81 fb |TFSu..A..U..r...|
00000080 55 aa 75 06 f7 c1 01 00 75 03 e9 dd 00 1e 83 ec |U.u.....u.......|
00000090 18 68 1a 00 b4 48 8a 16 0e 00 8b f4 16 1f cd 13 |.h...H..........|
000000a0 9f 83 c4 18 9e 58 1f 72 e1 3b 06 0b 00 75 db a3 |.....X.r.;...u..|
000000b0 0f 00 c1 2e 0f 00 04 1e 5a 33 db b9 00 20 2b c8 |........Z3... +.|
000000c0 66 ff 06 11 00 03 16 0f 00 8e c2 ff 06 16 00 e8 |f...............|
000000d0 4b 00 2b c8 77 ef b8 00 bb cd 1a 66 23 c0 75 2d |K.+.w......f#.u-|
000000e0 66 81 fb 54 43 50 41 75 24 81 f9 02 01 72 1e 16 |f..TCPAu$....r..|
000000f0 68 07 bb 16 68 70 0e 16 68 09 00 66 53 66 53 66 |h...hp..h..fSfSf|
00000100 55 16 16 16 68 b8 01 66 61 0e 07 cd 1a 33 c0 bf |U...h..fa....3..|
00000110 28 10 b9 d8 0f fc f3 aa e9 5f 01 90 90 66 60 1e |(........_...f`.|
00000120 06 66 a1 11 00 66 03 06 1c 00 1e 66 68 00 00 00 |.f...f.....fh...|
00000130 00 66 50 06 53 68 01 00 68 10 00 b4 42 8a 16 0e |.fP.Sh..h...B...|
00000140 00 16 1f 8b f4 cd 13 66 59 5b 5a 66 59 66 59 1f |.......fY[ZfYfY.|
00000150 0f 82 16 00 66 ff 06 11 00 03 16 0f 00 8e c2 ff |....f...........|
00000160 0e 16 00 75 bc 07 1f 66 61 c3 a0 f8 01 e8 09 00 |...u...fa.......|
00000170 a0 fb 01 e8 03 00 f4 eb fd b4 01 8b f0 ac 3c 00 |..............<.|
00000180 74 09 b4 0e bb 07 00 cd 10 eb f2 c3 0d 0a 41 20 |t.............A |
00000190 64 69 73 6b 20 72 65 61 64 20 65 72 72 6f 72 20 |disk read error |
000001a0 6f 63 63 75 72 72 65 64 00 0d 0a 42 4f 4f 54 4d |occurred...BOOTM|
000001b0 47 52 20 69 73 20 6d 69 73 73 69 6e 67 00 0d 0a |GR is missing...|
000001c0 42 4f 4f 54 4d 47 52 20 69 73 20 63 6f 6d 70 72 |BOOTMGR is compr|
000001d0 65 73 73 65 64 00 0d 0a 50 72 65 73 73 20 43 74 |essed...Press Ct|
000001e0 72 6c 2b 41 6c 74 2b 44 65 6c 20 74 6f 20 72 65 |rl+Alt+Del to re|
000001f0 73 74 61 72 74 0d 0a 00 8c a9 be d6 00 00 55 aa |start.........U.|
00000200
sudo dd if=/dev/rdisk0s5 count=1 2>/dev/null | hexdump -C
00000000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
00000200
Thx. -
Bootcamp missing after Yosemite upgrade
So I had OS-X Mavericks installed and a Windows 7 Bootcamp partition. Now I've installed OS-X Yosemite and I’ve run into a problem. Here are the steps I took:
First, I resized partitions manually using Disk Utility to even up the space a bit.
Installed Yosemite
Now, I can boot into Bootcamp just fine, and I can boot into OS-X fine. But I can no longer see my Bootcamp drive in OS-X and I can’t access it via Parallels.
Looking at previous similar problems on the forums here, I ran a couple of sudo commands for more info:
[REDACTED} sudo gpt -r -vv show disk0
WARNING: Improper use of the sudo command could lead to data loss
or the deletion of important system files. Please double-check your
typing when using sudo. Type "man sudo" for more information.
To proceed, enter your password, or type Ctrl-C to abort.
Password:
gpt show: disk0: mediasize=750156374016; sectorsize=512; blocks=1465149168
gpt show: disk0: Suspicious MBR at sector 0
gpt show: disk0: Pri GPT at sector 1
gpt show: disk0: Sec GPT at sector 1465149167
start size index contents
0 1 MBR
1 1 Pri GPT header
2 32 Pri GPT table
34 6
40 409600 1 GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
409640 927734368 2 GPT part - 48465300-0000-11AA-AA11-00306543ECAC
928144008 1269544 3 GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC
929413552 1616
929415168 242765824 4
1172180992 292966400 4 GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7
1465147392 1743
1465149135 32 Sec GPT table
1465149167 1 Sec GPT header
[REDACTED] sudo fdisk /dev/disk0
Disk: /dev/disk0 geometry: 91201/255/63 [1465149168 sectors]
Signature: 0xAA55
Starting Ending
#: id cyl hd sec - cyl hd sec [ start - size]
1: EE 0 0 2 - 25 127 14 [ 1 - 409639] <Unknown ID>
2: AF 25 127 15 - 1023 254 63 [ 409640 - 927734368] HFS+
3: AB 1023 254 63 - 1023 254 63 [ 928144008 - 1269544] Darwin Boot
*4: 07 1023 254 63 - 1023 254 63 [ 929415168 - 535732224] HPFS/QNX/AUX
============
DIsk0s4 shows up in Disk Utility, but shows as the old size (150GB) not as it’s new size (closer to 275GB).
I think I see the problem here, but I’m not yet enough of an OS-X ninja to know for sure… any help would be appreciated.
Thx!Nothing? Nobody? Well, at least I'm seeing a lot of other posts about Yosemite/bootcamp issues, so I know it's not just me. It just ***** to have to take time off work to rebuild my Windows side so I can actually... well, work.
- Mal -
about a month ago, Mavericks had an automatic update. I have a Windows 7 partition bootcamped on my macbook pro. Before the update, everything was fine. Now, when I attempt to start Windows partition, as soon as I touch the keyboard or mouse the screen goes black and I can't go any further. I have tried to re-load the bootcamp drivers and try again. It does the same thing. Any help would be great.
i sue windows 7 and my orignal macintosh formated and get online same window
-
Usb port not working after yosemite update please help
ive got an early 2011 macbook pro i5. and one of my usb stopped working. if i reset my computer it works for a while and then stops again. all these after yosemite update please i really need help on this.. and also when ever im in the middle of something it keeps crashing and saying these things below after i booting back up. ive tried several things, didnt work, tried repairing disk permissions. please anybody with any idea help me!
Anonymous UUID:
CCC4DCA9-48E9-4692-250B-488588FCC69E
Sun Nov 9 17:58:17 2014
*** Panic Report ***
panic(cpu 0 caller 0xffffff802a005eb2): "Possible memory corruption: pmap_pv_remove(0xffffff803b8db998,0x7fff7360f000,0x6d654, 0x6d654d64, 0xffffff8031663cc4, 0xfffffeb38ae0f078): null pv_list!"@/SourceCache/xnu/xnu-2782.1.97/osfmk/i386/pmap_internal.h:768
Backtrace (CPU 0), Frame : Return Address
0xffffff8031663b80 : 0xffffff8029f3a811
0xffffff8031663c00 : 0xffffff802a005eb2
0xffffff8031663cf0 : 0xffffff802a0065e5
0xffffff8031663d50 : 0xffffff8029fb6b4a
0xffffff8031663e60 : 0xffffff8029facd2c
0xffffff8031663e90 : 0xffffff8029f5c747
0xffffff8031663ed0 : 0xffffff802a3c45ff
0xffffff8031663f40 : 0xffffff802a3c425c
0xffffff8031663f50 : 0xffffff802a44dcb2
0xffffff8031663fb0 : 0xffffff802a03ac46
BSD process name corresponding to current thread: suhelperd
Mac OS version:
14A389
Kernel version:
Darwin Kernel Version 14.0.0: Fri Sep 19 00:26:44 PDT 2014; root:xnu-2782.1.97~2/RELEASE_X86_64
Kernel UUID: 89E10306-BC78-3A3B-955C-7C4922577E61
Kernel slide:
0x0000000029c00000
Kernel text base: 0xffffff8029e00000
__HIB text base: 0xffffff8029d00000
System model name: MacBookPro8,1 (Mac-94245B3640C91C81)
System uptime in nanoseconds: 7052072843826
last loaded kext at 6483411185500: com.huawei.driver.HuaweiDataCardActivateDriver 1.0.12 (addr 0xffffff7fac6ba000, size 16384)
last unloaded kext at 6604174049015: com.apple.driver.AppleUSBCDC 4.2.2b5 (addr 0xffffff7fac717000, size 16384)
loaded kexts:
com.huawei.driver.cdc_ncm 2.7.2f16
com.huawei.driver.dc_net 1.0.2
com.huawei.driver.cdc_acm 2.6.2f17
com.huawei.driver.cdc_usb_bus 1.0.3
com.huawei.driver.HuaweiDataCardDriver 4.25.45
com.apple.driver.AppleHWSensor 1.9.5d0
com.apple.driver.AudioAUUC 1.70
com.apple.driver.AGPM 100.14.37
com.apple.filesystems.autofs 3.0
com.apple.iokit.IOBluetoothSerialManager 4.3.0f10
com.apple.driver.AppleOSXWatchdog 1
com.apple.driver.AppleMikeyHIDDriver 124
com.apple.driver.AppleHDA 266.5
com.apple.driver.AppleMikeyDriver 266.5
com.apple.driver.AppleSMCLMU 2.0.4d1
com.apple.driver.ApplePolicyControl 3.7.21
com.apple.driver.AppleLPC 1.7.3
com.apple.driver.AppleUpstreamUserClient 3.6.1
com.apple.iokit.IOUserEthernet 1.0.1
com.apple.Dont_Steal_Mac_OS_X 7.0.0
com.apple.driver.AppleHWAccess 1
com.apple.driver.AppleHV 1
com.apple.driver.ACPI_SMC_PlatformPlugin 1.0.0
com.apple.driver.AppleIntelHD3000Graphics 10.0.0
com.apple.driver.AppleIntelSNBGraphicsFB 10.0.0
com.apple.driver.AppleBacklight 170.4.12
com.apple.driver.AppleMCCSControl 1.2.10
com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport 4.3.0f10
com.apple.driver.AppleSMCPDRC 1.0.0
com.apple.driver.AppleThunderboltIP 2.0.2
com.apple.driver.SMCMotionSensor 3.0.4d1
com.apple.driver.AppleUSBTCButtons 240.2
com.apple.driver.AppleUSBTCKeyboard 240.2
com.apple.driver.AppleIRController 327.5
com.apple.AppleFSCompression.AppleFSCompressionTypeDataless 1.0.0d1
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0d1
com.apple.BootCache 35
com.apple.iokit.SCSITaskUserClient 3.7.0
com.apple.driver.XsanFilter 404
com.apple.iokit.IOAHCIBlockStorage 2.6.5
com.apple.driver.AppleUSBHub 705.4.1
com.apple.iokit.AppleBCM5701Ethernet 10.1.2b3
com.apple.driver.AppleFWOHCI 5.5.2
com.apple.driver.AppleSDXC 1.6.5
com.apple.driver.AirPort.Brcm4331 800.20.24
com.apple.driver.AppleAHCIPort 3.0.7
com.apple.driver.AppleUSBEHCI 705.4.14
com.apple.driver.AppleSmartBatteryManager 161.0.0
com.apple.driver.AppleRTC 2.0
com.apple.driver.AppleACPIButtons 3.1
com.apple.driver.AppleHPET 1.8
com.apple.driver.AppleSMBIOS 2.1
com.apple.driver.AppleACPIEC 3.1
com.apple.driver.AppleAPIC 1.7
com.apple.driver.AppleIntelCPUPowerManagementClient 218.0.0
com.apple.nke.applicationfirewall 161
com.apple.security.quarantine 3
com.apple.security.TMSafetyNet 8
com.apple.driver.AppleIntelCPUPowerManagement 218.0.0
com.apple.iokit.IOSCSIBlockCommandsDevice 3.7.0
com.apple.iokit.IOUSBMassStorageClass 3.7.0
com.apple.AppleGraphicsDeviceControl 3.7.21
com.apple.kext.triggers 1.0
com.apple.iokit.IOSerialFamily 11
com.apple.driver.DspFuncLib 266.5
com.apple.kext.OSvKernDSPLib 1.15
com.apple.iokit.IOAudioFamily 200.6
com.apple.vecLib.kext 1.2.0
com.apple.driver.AppleHDAController 266.5
com.apple.iokit.IOHDAFamily 266.5
com.apple.iokit.IOFireWireIP 2.2.6
com.apple.driver.AppleSMBusPCI 1.0.12d1
com.apple.iokit.IOSurface 97
com.apple.driver.IOPlatformPluginLegacy 1.0.0
com.apple.driver.AppleGraphicsControl 3.7.21
com.apple.driver.AppleBacklightExpert 1.1.0
com.apple.iokit.IONDRVSupport 2.4.1
com.apple.driver.AppleSMBusController 1.0.13d1
com.apple.iokit.IOGraphicsFamily 2.4.1
com.apple.iokit.IOBluetoothHostControllerUSBTransport 4.3.0f10
com.apple.iokit.IOBluetoothFamily 4.3.0f10
com.apple.driver.IOPlatformPluginFamily 5.8.0d49
com.apple.iokit.IOUSBUserClient 705.4.0
com.apple.driver.AppleSMC 3.1.9
com.apple.driver.AppleUSBMultitouch 245.2
com.apple.iokit.IOUSBHIDDriver 705.4.0
com.apple.driver.AppleUSBMergeNub 705.4.0
com.apple.driver.AppleUSBComposite 705.4.9
com.apple.iokit.IOSCSIMultimediaCommandsDevice 3.7.0
com.apple.iokit.IOBDStorageFamily 1.7
com.apple.iokit.IODVDStorageFamily 1.7.1
com.apple.iokit.IOCDStorageFamily 1.7.1
com.apple.iokit.IOAHCISerialATAPI 2.6.1
com.apple.iokit.IOSCSIArchitectureModelFamily 3.7.0
com.apple.driver.AppleThunderboltNHI 3.1.7
com.apple.iokit.IOThunderboltFamily 4.2.1
com.apple.iokit.IOEthernetAVBController 1.0.3b3
com.apple.iokit.IOFireWireFamily 4.5.6
com.apple.iokit.IO80211Family 700.52
com.apple.driver.mDNSOffloadUserClient 1.0.1b8
com.apple.iokit.IONetworkingFamily 3.2
com.apple.iokit.IOAHCIFamily 2.7.0
com.apple.iokit.IOUSBFamily 705.4.14
com.apple.driver.AppleEFINVRAM 2.0
com.apple.driver.AppleEFIRuntime 2.0
com.apple.iokit.IOHIDFamily 2.0.0
com.apple.iokit.IOSMBusFamily 1.1
com.apple.security.sandbox 300.0
com.apple.kext.AppleMatch 1.0.0d1
com.apple.driver.AppleKeyStore 2
com.apple.driver.AppleMobileFileIntegrity 1.0.5
com.apple.driver.AppleCredentialManager 1.0
com.apple.driver.DiskImages 389.1
com.apple.iokit.IOStorageFamily 2.0
com.apple.iokit.IOReportFamily 31
com.apple.driver.AppleFDEKeyStore 28.30
com.apple.driver.AppleACPIPlatform 3.1
com.apple.iokit.IOPCIFamily 2.9
com.apple.iokit.IOACPIFamily 1.4
com.apple.kec.corecrypto 1.0
com.apple.kec.Libm 1
com.apple.kec.pthread 1
Model: MacBookPro8,1, BootROM MBP81.0047.B04, 2 processors, Intel Core i5, 2.3 GHz, 4 GB, SMC 1.68f96
Graphics: Intel HD Graphics 3000, Intel HD Graphics 3000, Built-In, 384 MB
Memory Module: BANK 0/DIMM0, 2 GB, DDR3, 1333 MHz, 0x80CE, 0x4D34373142353737334448302D4348392020
Memory Module: BANK 1/DIMM0, 2 GB, DDR3, 1333 MHz, 0x80CE, 0x4D34373142353737334448302D4348392020
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0xD6), Broadcom BCM43xx 1.0 (5.106.98.100.24)
Bluetooth: Version 4.3.0f10 14890, 3 services, 19 devices, 2 incoming serial ports
Serial ATA Device: ST9320325ASG, 320.07 GB
Serial ATA Device: HL-DT-ST DVDRW GS31N
USB Device: Hub
USB Device: HUAWEI Mobile
USB Device: IR Receiver
USB Device: FaceTime HD Camera (Built-in)
USB Device: Hub
USB Device: BRCM2070 Hub
USB Device: Bluetooth USB Host Controller
USB Device: Apple Internal Keyboard / Trackpad
Thunderbolt Bus: MacBook Pro, 20080d.0I have the same problem when I updated to OS X 10.10 I lost both my USB ports as far as they will not recognize anything that I plug into them. The power part of the USB seams to work since it will recharge my Striiv Touch but nothing shows up when you connect anything to the ports.
I have tried a number of things from rebooting, trying other usb devices that work on other systems with no problems but will not work on my Macbook Pro.
Any Help out there?
Hardware Information: ℹ️
MacBook Pro (Retina, 15-inch, Late 2013) (Verified)
MacBook Pro - model: MacBookPro11,3
1 2.3 GHz Intel Core i7 CPU: 4-core
16 GB RAM Not upgradeable
BANK 0/DIMM0
8 GB DDR3 1600 MHz ok
BANK 1/DIMM0
8 GB DDR3 1600 MHz ok
Bluetooth: Good - Handoff/Airdrop2 supported
Wireless: en0: 802.11 a/b/g/n/ac
System Software: ℹ️
OS X 10.10.1 (14B25) - Uptime: 1:43:41
USB Information: ℹ️
Apple Internal Memory Card Reader
Apple Inc. BRCM20702 Hub
Apple Inc. Bluetooth USB Host Controller
Apple Inc. Apple Internal Keyboard / Trackpad -
macbook pro - iPhoto keep prompting to update after Yosemite update. Error message when trying to update -This update is not available for this Apple ID either because it was bought by a different user or the item was refunded or cancelled.
I only have 1 apple ID and the same was used to set up this early 2011 macbook pro and iPhoto app. I don't want to loose out on any photos. I tried logging out of app store and back in but no luck. PLEEAASEE HELPP!!!
This problem has been reported by quite a few forum members, who skipped the update to iPhoto 9.5.1 while running Mavericks. In that case try to purchase iPhoto again instead of updating.
After making your backup try the following:
Uninstall iPhoto by deleting it from the applications folder, but do not empty the Trash.
Launch the App Store, click the "Store" menu, and sign in with your AppleID.
Open the main page of the App Store and search for iPhoto.
If iPhoto is listed as "Free", click the "Free" button to buy it with your current AppleID.
If it is not showing as free, there is no help but contacting the App Store Support, as Niel pointed out: http://www.apple.com/support/mac/app-store/contact/ -
My early 2008 Macbook Pro is suffering from black screen after Yosemite update
My early 2008 Macbook Pro is suffering from black screen after Yosemite update. It ran beta 5 great but failed on restart after beta 6 install. There is no cursor but I can hear the HDD spooling up. I have tried booting in safe mode, PRAM reset and SMC reset but nothing works. After the first 5 days of every now and then trying to start it, it started fine. I used the machine all day with no problems, it had rolled back the install and was back on beta 5. I decided to try the update again, the same thing happened and it has stayed black for over a week now. It wont work with a monitor either. Help!
Hello Adam,
I would try instead of installing the beta software, to install the official build of OS X Yosemite from the Mac App Store to see if that gets you passed the no video issue when updating the beta software.
How to install OS X Yosemite on your Mac
http://support.apple.com/en-us/HT6412
Regards,
-Norm G. -
Mac mail CRASHING after Yosemite update 10.10.3
Are you KIDDING APPLE?
mac mail CRASHING after Yosemite update 10.10.3
The program is completely unusable and crashed after update.
Computer is less than 1 month old and can't run a basic mail program
I REALLY HOPE APPLE FIXES THIS BUG ASAP
Without fix I will return the computerTrue,
I also have AppleCare, but unfortunately, after calling them they can't determine what is creating the problem either.
Other forums have shown other troubleshooting steps which didn't solve my problem, but may help others:
Mail app keeps crashing after Yosemite update
Mail crashing after upgrading to 10.10.3
Lets cross our fingers that 10.10.4 will be out shortly to fix this -
Lacie Rugged external drive will not show up after Yosemite update.
Lacie Rugged external drive will not show up after Yosemite update. It show up in disc utility I can't access it.
I have the exact same issue. Have you had any luck with a solution?
-
I have an original version of Photoshop CS3. I run Windows 7 32 bit. After an update of the operat
I have an original version of Photoshop CS3. I run Windows 7 32 bit. After an update of the operating system by MS, my Photoshop refused to work, whereas before the MS update, the software worked perfectly. Please help. Ernst
Dear Sir,
I have an original version of Photoshop CS3. I run Windows 7 (32 bit) on my PC. After a recent (±2 months ago) update/upgrade by Microsoft of Windows 7 (32 bit) on my PC, I lost all functionality of the Photoshop software despite the fact that I have been running Photoshop CS3 on Windows 7 for the past 2 years without any problems. I uninstalled the software from my PC and tried to re-install it again. It would not re-install. After I press the software “setup” function to install the software, a window appears and a blue band runs across it, but then everything disappears from the screen again without leaving any message as to why the software would not install.
I have been informed by Adobe Helpdesk that Photoshop CS3 does not run on the Windows 7 OS. Due to previous experience that Photoshop CS3 had in fact run on my PC on Windows 7, I find it totally strange that I could not install the software again.
In fact the, same version of Photoshop CS3 is currently running without any problems on my laptop under Windows 7 (64 bit).
Please help if you can.
Kind regards,
Ernst Odendaal -
After yosemite update I'm unable to type in word
After Yosemite update I am now unable to type in any of my word documents. Any suggestions?
Sorry for hijacking your post -
I have had an issue with my Lumia 820 too after installing the Amber update.
The phone once updated displayed " restarting " and from that point on has failed to go beyond the screen that displays the Nokia logo.
Spoken to Customer care guys and tried hard resetting the device but to no avail.
Unfortunately for me i haven't made a back up of the data i have on the phone and I have extremely important business contacts and other relevant info that I can't afford to lose, hope I am provided with a solution. -
Bootcamp won't load after Yosemite Update
So after trouble with Yosemite freezing in which i was able to fix, i tried to boot back into Windows on my bootcamp drive.
When i went into Startup Disk, i selected the Bootcamp Drive i had windows installed on. All i got was a black screen and then saw the message that the boot device could not be found. I restarted the computer and held down option to see the boot drives on that, but only drives that showed up was my OS X partition and Restore option. So my partition for windows was not found on boot.
I see a lot of people posting about losing their bootcamp partition or saying it was renamed, i don't know if this is the same issue. Is there any way to fix this or will i have to reinstall windows?Here is the output for the following commands
Sudo gpt -vv -r show /dev/disk0
sudo fdisk /dev/disk0
diskutil list
diskutil cs list -
Missing bootcamp win7 after Yosemite crash
I am having a similar issue as these guys:
https://discussions.apple.com/thread/6627170
https://discussions.apple.com/thread/6621798?start=30&tstart=0
My problem started after Yosemite crashed and rebooted. Here is the output of the terminal commands:
sudo gpt -vv -r show /dev/disk0
gpt show: /dev/disk0: mediasize=251000193024; sectorsize=512; blocks=490234752
gpt show: /dev/disk0: Suspicious MBR at sector 0
gpt show: /dev/disk0: Pri GPT at sector 1
gpt show: /dev/disk0: Sec GPT at sector 490234751
start size index contents
0 1 MBR
1 1 Pri GPT header
2 32 Pri GPT table
34 6
40 409600 1 GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
409640 82880688 2 GPT part - 48465300-0000-11AA-AA11-00306543ECAC
83290328 1269544 3 GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC
84559872 405673984 4 GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7
490233856 863
490234719 32 Sec GPT table
490234751 1 Sec GPT header
sudo fdisk /dev/disk0
Disk: /dev/disk0 geometry: 30515/255/63 [490234752 sectors]
Signature: 0xAA55
Starting Ending
#: id cyl hd sec - cyl hd sec [ start - size]
1: EE 0 0 2 - 25 127 14 [ 1 - 409639] <Unknown ID>
2: AF 25 127 15 - 1023 254 63 [ 409640 - 82880688] HFS+
3: AB 1023 254 63 - 1023 254 63 [ 83290328 - 1269544] Darwin Boot
*4: 07 1023 254 63 - 1023 254 63 [ 84559872 - 405673984] HPFS/QNX/AUX
sudo dd if=/dev/rdisk0s4 count=1 2>/dev/null | hexdump -C
00000000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
00000200Ok, that took a while but resulted in nothing. I'll run a deep search over night. Here is the output:
TestDisk 7.0-WIP, Data Recovery Utility, October 2014
Christophe GRENIER <[email protected]>
http://www.cgsecurity.org
Disk /dev/disk0 - 251 GB / 233 GiB - 490234752 sectors (RO)
The harddisk (251 GB / 233 GiB) seems too small! (< 813 GB / 757 GiB)
Check the harddisk size: HD jumpers settings, BIOS detection...
The following partitions can't be recovered:
Partition Start End Size in sectors
> MS Data 102559704 508233687 405673984
Mac HFS 354985583 1588930160 1233944578
MS Data 490233855 895907838 405673984
...and when I clicked continue:
TestDisk 7.0-WIP, Data Recovery Utility, October 2014
Christophe GRENIER <[email protected]>
http://www.cgsecurity.org
Disk /dev/disk0 - 251 GB / 233 GiB - 490234752 sectors (RO)
Partition Start End Size in sectors
P EFI System 40 409639 409600 [EFI]
P Mac HFS 409640 83290327 82880688
P Mac HFS 83290328 84559871 1269544
>D MS Data 84559872 490233855 405673984
D MS Data 84682627 84688800 6174
D MS Data 84688800 84694973 6174 [Boot]
D MS Data 85599456 85602335 2880 [EFISECTOR]
D MS Data 88317315 88323488 6174
D MS Data 88323488 88329661 6174 [Boot]
D MS Data 88323507 88329680 6174
D MS Data 88329680 88335853 6174 [Boot]
D MS Data 88329699 88335872 6174
Structure: Ok. Use Up/Down Arrow keys to select partition.
Use Left/Right Arrow keys to CHANGE partition characteristics:
P=Primary D=Deleted
Keys A: add partition, L: load backup, T: change type, P: list files,
Enter: to continue
NTFS found using backup sector, blocksize=4096, 207 GB / 193 GiB
When I listed the files for the first one, I got junk:
TestDisk 7.0-WIP, Data Recovery Utility, October 2014
Christophe GRENIER <[email protected]>
http://www.cgsecurity.org
MS Data 84559872 490233855 405673984
Directory /
dr-xr-xr-x 0 0 0 26-Oct-2014 00:48 .
>dr-xr-xr-x 0 0 0 26-Oct-2014 00:48 ..
dr-xr-xr-x 0 0 0 24-Jan-2012 15:26 $Recycle.Bin
-r--r--r-- 0 0 8 26-Oct-2014 00:48 ..:^EC0B21842-99B8-46E2-A991
-r--r--r-- 0 0 8 26-Oct-2014 00:48 .:^EC0B21842-99B8-46E2-A991-
-r--r--r-- 0 0 6148 14-Apr-2014 11:46 .DS_Store
-r--r--r-- 0 0 310 15-Oct-2014 16:03 .apdisk -
Macbook air does not boot after yosemite update
After latest Yosemite update my Mac book Air is not finishing to reboot, all I see is the white apple on the black screen and the progress bar whch loads slowly and kind of get stuck half the way to the end, and it stays there forever.
I forced to restart with the start hardware key and it does the same. any idea what went wrong and or what can I do next?
thanksTake each of these steps that you haven't already tried. Stop when the problem is resolved.
To restart an unresponsive computer, press and hold the power button for a few seconds until the power shuts off, then release, wait a few more seconds, and press it again briefly.
Step 1
The first step in dealing with a startup failure is to secure the data. If you want to preserve the contents of the startup drive, and you don't already have at least one current backup, you must try to back up now, before you do anything else. It may or may not be possible. If you don't care about the data that has changed since the last backup, you can skip this step.
There are several ways to back up a Mac that is unable to start. You need an external hard drive to hold the backup data.
a. Start up from the Recovery partition, or from a local Time Machine backup volume (option key at startup.) When the OS X Utilities screen appears, launch Disk Utility and follow the instructions in this support article, under “Instructions for backing up to an external hard disk via Disk Utility.” The article refers to starting up from a DVD, but the procedure in Recovery mode is the same. You don't need a DVD if you're running OS X 10.7 or later.
b. If Step 1a fails because of disk errors, and no other Mac is available, then you may be able to salvage some of your files by copying them in the Finder. If you already have an external drive with OS X installed, start up from it. Otherwise, if you have Internet access, follow the instructions on this page to prepare the external drive and install OS X on it. You'll use the Recovery installer, rather than downloading it from the App Store.
c. If you have access to a working Mac, and both it and the non-working Mac have FireWire or Thunderbolt ports, start the non-working Mac in target disk mode. Use the working Mac to copy the data to another drive. This technique won't work with USB, Ethernet, Wi-Fi, or Bluetooth.
d. If the internal drive of the non-working Mac is user-replaceable, remove it and mount it in an external enclosure or drive dock. Use another Mac to copy the data.
Step 2
If the startup process stops at a blank gray screen with no Apple logo or spinning "daisy wheel," then the startup volume may be full. If you had previously seen warnings of low disk space, this is almost certainly the case. You might be able to start up in safe mode even though you can't start up normally. Otherwise, start up from an external drive, or else use the technique in Step 1b, 1c, or 1d to mount the internal drive and delete some files. According to Apple documentation, you need at least 9 GB of available space on the startup volume (as shown in the Finder Info window) for normal operation.
Step 3
Sometimes a startup failure can be resolved by resetting the NVRAM.
Step 4
If a desktop Mac hangs at a plain gray screen with a movable cursor, the keyboard may not be recognized. Press and hold the button on the side of an Apple wireless keyboard to make it discoverable. If need be, replace or recharge the batteries. If you're using a USB keyboard connected to a hub, connect it to a built-in port.
Step 5
If there's a built-in optical drive, a disc may be stuck in it. Follow these instructions to eject it.
Step 6
Press and hold the power button until the power shuts off. Disconnect all wired peripherals except those needed to start up, and remove all aftermarket expansion cards. Use a different keyboard and/or mouse, if those devices are wired. If you can start up now, one of the devices you disconnected, or a combination of them, is causing the problem. Finding out which one is a process of elimination.
Step 7
If you've started from an external storage device, make sure that the internal startup volume is selected in the Startup Disk pane of System Preferences.
Start up in safe mode. Note: If FileVault is enabled in OS X 10.9 or earlier, or if a firmware password is set, or if the startup volume is a software RAID, you can’t do this. Post for further instructions.
Safe mode is much slower to start and run than normal, and some things won’t work at all, including wireless networking on certain Macs.
The login screen appears even if you usually log in automatically. You must know the login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
When you start up in safe mode, it's normal to see a dark gray progress bar on a light gray background. If the progress bar gets stuck for more than a few minutes, or if the system shuts down automatically while the progress bar is displayed, the startup volume is corrupt and the drive is probably malfunctioning. In that case, go to Step 11. If you ever have another problem with the drive, replace it immediately.
If you can start and log in in safe mode, empty the Trash, and then open the Finder Info window on the startup volume ("Macintosh HD," unless you gave it a different name.) Check that you have at least 9 GB of available space, as shown in the window. If you don't, copy as many files as necessary to another volume (not another folder on the same volume) and delete the originals. Deletion isn't complete until you empty the Trash again. Do this until the available space is more than 9 GB. Then restart as usual (i.e., not in safe mode.)
If the startup process hangs again, the problem is likely caused by a third-party system modification that you installed. Post for further instructions.
Step 8
Launch Disk Utility in Recovery mode (see Step 1.) Select the startup volume, then run Repair Disk. If any problems are found, repeat until clear. If Disk Utility reports that the volume can't be repaired, the drive has malfunctioned and should be replaced. You might choose to tolerate one such malfunction in the life of the drive. In that case, erase the volume and restore from a backup. If the same thing ever happens again, replace the drive immediately.
This is one of the rare situations in which you should also run Repair Permissions, ignoring the false warnings it may produce. Look for the line "Permissions repair complete" at the end of the output. Then restart as usual.
Step 9
If the startup device is an aftermarket SSD, it may need a firmware update and/or a forced "garbage collection." Instructions for doing this with a Crucial-branded SSD were posted here. Some of those instructions may apply to other brands of SSD, but you should check with the vendor's tech support.
Step 10
Reinstall the OS. If the Mac was upgraded from an older version of OS X, you’ll need the Apple ID and password you used to upgrade.
Step 11
Do as in Step 9, but this time erase the startup volume in Disk Utility before installing. The system should automatically restart into the Setup Assistant. Follow the prompts to transfer the data from a Time Machine or other backup.
Step 12
This step applies only to models that have a logic-board ("PRAM") battery: all Mac Pro's and some others (not current models.) Both desktop and portable Macs used to have such a battery. The logic-board battery, if there is one, is separate from the main battery of a portable. A dead logic-board battery can cause a startup failure. Typically the failure will be preceded by loss of the settings for the startup disk and system clock. See the user manual for replacement instructions. You may have to take the machine to a service provider to have the battery replaced.
Step 13
If you get this far, you're probably dealing with a hardware fault. Make a "Genius" appointment at an Apple Store, or go to another authorized service provider.
Maybe you are looking for
-
"column ambigously defined" error
ORA-00918: column ambigously defined 00918.00000 - "column ambigously defined" *Cause: *Action Vendor code 918 I've gotten this error on a few of the queries I've ran in SQL Developer 1.5 and tried to export to xls, but when I run and try to exp
-
Changes made in existing positions
Hi, I have made changes in po13 for the existing positions (ex: Developer Trainee - ABAP). Earlier it was "Developer Trainee". The changes were displaying in the master data but while generating reports in easy access (Employee List) the changes that
-
Only Bridge CS 5 will open with PS CS 6
I installed PS CS 6 without first deleting PS CS 5 first. I was told I did not need to. Anyway now only Bridge CS 5 will open with PS CS 6, not Bridge CS 6. Bridge CS 6 is loaded. I can access Bridge CS 6 through the Mini Bridge which doesn't work w
-
Analytical using FULL outer join
Hi, Please execute the below script and check the output for the given select query the output gives rnum alias value as null which should not be the case. I am just wondering what is wrong in this case CREATE TABLE A ID INTEGER, RD INTEGER, SD DATE
-
"Complete" instead of "Delete" from calendar
It would be great to be able to take a reminder of the active standby screen on my phone without deleting the appointment from my calendar. I would like to have a record of the appointment in the phone and on OVI even though I have already completed