Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
How to recover Bootcamp NTFS Partition?
- Thread starter PerceptorC5
- Start date
- Sort by reaction score
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
So I'm assuming the missing SMFT entry is a major issue?
I don't know enough about NTFS to answer this. An MFT appears to be required and I think there are duplicates in case one is damaged chkdsk can repair it. But it first must find an otherwise valid header for the NTFS volume, and find the primary table structures that NTFS requires. If it doesn't find them, chkdsk presumably pukes.
Ah, amen.
What about my huge list of "NTFS", do you think I should search through those the same way, for a viable NTFS header?
Or do you know this to be something else?
Or is this also a stumper?
At any rate, thanks a lot man, I really appreciate all the help you've provided.
What about my huge list of "NTFS", do you think I should search through those the same way, for a viable NTFS header?
Or do you know this to be something else?
Or is this also a stumper?
At any rate, thanks a lot man, I really appreciate all the help you've provided.
What about my huge list of "NTFS", do you think I should search through those the same way, for a viable NTFS header?
Or do you know this to be something else?
Or is this also a stumper?
No idea. When creating an NTFS file system from scratch on a clean virtual disk, there are only two instances of this NTFS identifying header. I don't know if it's normal for more to be created for some reason as the file system is actually filled, or if so many indicate multiple volumes existed on the hard drive at varying times.
I really dont mean to hijack thread but...
murphychris you are a god! I have been following your posts and support from the appple support forums to here. I have a very similar issue and I am hoping you can help me resolve it:
I have a Macmini running Mac OS x 10.7.5. I was on bootcamp side, running win 7 when suddenly, it just restarted and of course, went right into the mac side as it would by default. I think nothing of it, but when I restart and hold down ALT key, I noticed bootcamp is gone!
I used disk utility and the only discrepancy I notice is a greyed out partion "disk0s2" but not bootcamp but I know its still there, I downloaded data recovery software and Bootcamp does come up as a partition to recover data from.
What do I do?
Your help is greatly appreciated!
murphychris you are a god! I have been following your posts and support from the appple support forums to here. I have a very similar issue and I am hoping you can help me resolve it:
I have a Macmini running Mac OS x 10.7.5. I was on bootcamp side, running win 7 when suddenly, it just restarted and of course, went right into the mac side as it would by default. I think nothing of it, but when I restart and hold down ALT key, I noticed bootcamp is gone!
I used disk utility and the only discrepancy I notice is a greyed out partion "disk0s2" but not bootcamp but I know its still there, I downloaded data recovery software and Bootcamp does come up as a partition to recover data from.
What do I do?
Your help is greatly appreciated!
What do I do?
Code:
sudo gpt -r -vv show disk0
sudo fdisk /dev/disk0Please format with code tags (highlight the pasted text, and then click on the # button in the advanced formatting toolbar).
Will this erase the bootcamp partition?
I have invaluable data on there I am trying to salvage.
They are read only commands. The data is by definition not that valuable if its your only copy.
Code:sudo gpt -r -vv show disk0 sudo fdisk /dev/disk0
Please format with code tags (highlight the pasted text, and then click on the # button in the advanced formatting toolbar).
Here are my results:
"sudo gpt -r -vv show disk0"
Code:
gpt show: disk0: mediasize=320072933376; sectorsize=512; blocks=625142448
gpt show: disk0: Suspicious MBR at sector 0
gpt show: disk0: Bad CRC in GPT table at sector 2
start size index contents
0 1 MBR
1 409639
409640 311492784 3 MBR part 175
311902424 1269544 4 MBR part 171
313171968 311970480
Rabuni-Pujoblss-Mac-mini:~ Rapujols$"sudo fdisk /dev/disk0"
Code:
Disk: /dev/disk0 geometry: 38913/255/63 [625142448 sectors]
Signature: 0xAA55
Starting Ending
#: id cyl hd sec - cyl hd sec [ start - size]
------------------------------------------------------------------------
1: 00 0 0 0 - 0 0 0 [ 0 - 0] unused
2: EE 1023 254 63 - 1023 254 63 [ 1 - 409639] <Unknown ID>
3: AF 1023 254 63 - 1023 254 63 [ 409640 - 311492784] HFS+
4: AB 1023 254 63 - 1023 254 63 [ 311902424 - 1269544] Darwin Boot
Rabuni-Pujoblss-Mac-mini:~ Rapbujols$FYI It is indeed very important data, so please lets be careful here. Thanks.
So the primary GPT table is at least partially corrupt. And the hybrid MBR is malformed. Something clearly tried to modify the first ~3 sectors of the disk, it doesn't look like random corruption.
So you're going to either need to send it off for professional data recovery, or you're going to have to learn how to fix it with gdisk, which is a command line only program. It's the only thing I'd trust to fix this sort of problem. And it is possible to use it in a way that causes total data loss, including the OS X side so you should at least have a backup of your OS X stuff before you start.
Basic steps are to repair the GPT, which gdisk should do automatically by using the backup GPT instead and will later on write out a new primary one, and then create a new hybrid MBR adding partitions 2 3 4 and making partition 4 bootable. All of that is done in memory and doesn't actually write anything to disk yet, you can post the output from the proposed GPT and MBR before you write them to disk if you want me to proof read it first.
It's very important but you don't have a backup? If it's that important, you should just contact a data recovery service to ensure you get your data back.
So you're going to either need to send it off for professional data recovery, or you're going to have to learn how to fix it with gdisk, which is a command line only program. It's the only thing I'd trust to fix this sort of problem. And it is possible to use it in a way that causes total data loss, including the OS X side so you should at least have a backup of your OS X stuff before you start.
Basic steps are to repair the GPT, which gdisk should do automatically by using the backup GPT instead and will later on write out a new primary one, and then create a new hybrid MBR adding partitions 2 3 4 and making partition 4 bootable. All of that is done in memory and doesn't actually write anything to disk yet, you can post the output from the proposed GPT and MBR before you write them to disk if you want me to proof read it first.
FYI It is indeed very important data, so please lets be careful here.
It's very important but you don't have a backup? If it's that important, you should just contact a data recovery service to ensure you get your data back.
This is so bizzare. I was doing nothing that night. I had no virus, no spyware no junk. This is my work computer, not personal.
Ok, so I found gdisk and installed it, can't even find it in applications...
I really could use your help. I will make a donation via paypal once we're done. So far, you're the only person I have come across who specializes in these types of issues.
I would genuinely appreciate it.
Ok, so I found gdisk and installed it, can't even find it in applications...
I really could use your help. I will make a donation via paypal once we're done. So far, you're the only person I have come across who specializes in these types of issues.
I would genuinely appreciate it.
This is so bizzare. I was doing nothing that night. I had no virus, no spyware no junk. This is my work computer, not personal
It's a great reason to use a virtual machine in the future rather than using Boot Camp, which I consider to be risky. But the biggest risk you took is having important information on a computer without a backup.
Ok, so I found gdisk and installed it, can't even find it in applications...
Like I said, gdisk is a command line app. You use it in Terminal like the other two programs I had you use. There is no graphic user interface available. If you're not comfortable with that, and taking the risk of making a mistake and making things worse, then you need to talk to professional disaster recovery experts.
Otherwise, what you need to do in order:
http://www.rodsbooks.com/gdisk/repairing.html
http://www.rodsbooks.com/gdisk/hybrid.html
Again, you're going to add partitions 2 3 4 instead of 1 3 like in the example.
It's a great reason to use a virtual machine in the future rather than using Boot Camp, which I consider to be risky. But the biggest risk you took is having important information on a computer without a backup.
Like I said, gdisk is a command line app. You use it in Terminal like the other two programs I had you use. There is no graphic user interface available. If you're not comfortable with that, and taking the risk of making a mistake and making things worse, then you need to talk to professional disaster recovery experts.
Otherwise, what you need to do in order:
http://www.rodsbooks.com/gdisk/repairing.html
http://www.rodsbooks.com/gdisk/hybrid.html
Again, you're going to add partitions 2 3 4 instead of 1 3 like in the example.
Right off the bat, I'm having some problems just running gdisk.
Rauddni-Pujeeolss-Mac-mini:~ Rapfujols$ gdisk /dev/sdc
GPT fdisk (gdisk) version 0.8.5
Problem opening /dev/sdc for reading! Error is 2.
The specified file does not exist!
Raudfni-Pujdfolss-Mac-mini:~ Rapdfujols$ # gdisk /dev/sdc
Raudfni-Pujoldfss-Mac-mini:~ Rapdfujols$
I don't see a troubleshooting guide on the site. I installed it for everyone on this mac, and then disk specific...
Right off the bat, I'm having some problems just running gdisk.
Do this and report the result:
Code:
sudo gdisk /dev/disk0Do this and report the result:
Code:sudo gdisk /dev/disk0
This is what comes up:
Caution: invalid backup GPT header, but valid main header; regenerating
backup header from main header.
Caution! After loading partitions, the CRC doesn't check out!
Warning! Main and backup partition tables differ! Use the 'c' and 'e' options
on the recovery & transformation menu to examine the two tables.
Warning! One or more CRCs don't match. You should repair the disk!
Partition table scan:
MBR: hybrid
BSD: not present
APM: not present
GPT: damaged
Found valid MBR and corrupt GPT. Which do you want to use? (Using the
GPT MAY permit recovery of GPT data.)
1 - MBR
2 - GPT
3 - Create blank GPT
Your answer:
Caution: invalid backup GPT header, but valid main header; regenerating
backup header from main header.
OK so that's good news. But it means LBA 0 (the MBR) was modified, and somewhere in the last 34 sectors of the disk, where the backup GPT is located, it was modified. That's even less likely random corruption. But it's actually common if there's a resizing attempt of the NTFS volume on the disk as the resize attempt tends to step on the backup GPT.
Your answer:
Input these commands (on the left) followed by enter. Description of what those commands do is on the right.
Code:
2 <enter> choose GPT
r <enter> recovery menu
v <enter> verify disk
o <enter> print the MBR
p <enter> print the GPTPost the results for all of this. Stay in gdisk.
OK so that's good news. But it means LBA 0 (the MBR) was modified, and somewhere in the last 34 sectors of the disk, where the backup GPT is located, it was modified. That's even less likely random corruption. But it's actually common if there's a resizing attempt of the NTFS volume on the disk as the resize attempt tends to step on the backup GPT.
Input these commands (on the left) followed by enter. Description of what those commands do is on the right.
Code:2 <enter> choose GPT r <enter> recovery menu v <enter> verify disk o <enter> print the MBR p <enter> print the GPT
Post the results for all of this. Stay in gdisk.
So that is good? Hopefully you can tell me better news from this...
Code:
Raudfni-Pujodflss-Mac-mini:~ Rapudjols$ sudo gdisk /dev/disk0
Password:
GPT fdisk (gdisk) version 0.8.5
Caution: invalid backup GPT header, but valid main header; regenerating
backup header from main header.
Caution! After loading partitions, the CRC doesn't check out!
Warning! Main and backup partition tables differ! Use the 'c' and 'e' options
on the recovery & transformation menu to examine the two tables.
Warning! One or more CRCs don't match. You should repair the disk!
Partition table scan:
MBR: hybrid
BSD: not present
APM: not present
GPT: damaged
Found valid MBR and corrupt GPT. Which do you want to use? (Using the
GPT MAY permit recovery of GPT data.)
1 - MBR
2 - GPT
3 - Create blank GPT
Your answer: 2
Warning! Secondary partition table overlaps the last partition by
9002440837424676213 blocks!
You will need to delete this partition or resize it in another utility.
Command (? for help): r
Recovery/transformation command (? for help): v
Problem: The CRC for the main partition table is invalid. This table may be
corrupt. Consider loading the backup partition table ('c' on the recovery &
transformation menu). This report may be a false alarm if you've already
corrected other problems.
Caution: The CRC for the backup partition table is invalid. This table may
be corrupt. This program will automatically create a new backup partition
table when you save your partitions.
Problem: partitions 62 and 61 overlap:
Partition 62: 9024114456867150270 to 4785357088958439475
Partition 61: 16177792531902366089 to 9002440838049818627
Problem: partition 61 ends before it begins.
Problem: partition 61 is too big for the disk.
Problem: partition 62 ends before it begins.
Problem: partition 62 is too big for the disk.
Warning! Secondary partition table overlaps the last partition by
9002440837424676213 blocks!
You will need to delete this partition or resize it in another utility.
Caution: Partition 61 doesn't begin on a 8-sector boundary. This may
result in degraded performance on some modern (2009 and later) hard disks.
Caution: Partition 62 doesn't begin on a 8-sector boundary. This may
result in degraded performance on some modern (2009 and later) hard disks.
Consult http://www.ibm.com/developerworks/linux/library/l-4kb-sector-disks/
for information on disk alignment.
Identified 8 problems!
Recovery/transformation command (? for help): o
Disk size is 625142448 sectors (298.1 GiB)
MBR disk identifier: 0xC01E02AA
MBR partitions:
Number Boot Start Sector End Sector Status Code
2 1 409639 primary 0xEE
3 409640 311902423 primary 0xAF
4 311902424 313171967 primary 0xAB
Recovery/transformation command (? for help): p
Disk /dev/disk0: 625142448 sectors, 298.1 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 85E0FC88-16BF-40D9-B83C-28E5411E91BE
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 625142414
Partitions will be aligned on 8-sector boundaries
Total free space is 661 sectors (330.5 KiB)
Number Start (sector) End (sector) Size Code Name
1 40 409639 200.0 MiB EF00 EFI System Partition
2 409640 311902423 148.5 GiB AF00 Customer
3 311902424 313171967 619.9 MiB AB00 Recovery HD
4 313171968 625141759 148.8 GiB 0700 BOOTCAMP
61 16177792531902366089 9002440838049818627 4.9 ZiB FFFF ⶾ糟鮏0狑餀䑱ﾀ歬섾Ｆ塇븀弖ꓧૐ墯픆
62 9024114456867150270 4785357088958439475 6.2 ZiB FFFF 墉晸Ή곑惿拇䷫璈馆菌숏¯靟촓ӝ垬꧹✬
Recovery/transformation command (? for help):Problem: The CRC for the main partition table is invalid.
Caution: The CRC for the backup partition table is invalid.
Not good. Both GPTs are corrupt.
Recovery/transformation command (? for help):
Enter these, followed by enter after each letter, post results. This will print both backup and main GPTs, and see if there's a difference between them, and the MBR.
Code:
c
y
p
e
y
p----------
Could it possibly have to do with the boot disk menu (HOLD DOWN ALT KEY)?
No. The partition tables are hosed, that's the first problem. There may be more but the partition tables need to be repaired first.
Because CDs are also not being picked up. I have tried to boot to the mac os x cd and use disk utility to no avail...
Please stop, you're going to make things worse. Disk Utility does not fix problems with hybrid MBRs, in fact if frequently causes them.
Not good. Both GPTs are corrupt.
Enter these, followed by enter after each letter, post results. This will print both backup and main GPTs, and see if there's a difference between them, and the MBR.
Code:c y p e y p
----------
No. The partition tables are hosed, that's the first problem. There may be more but the partition tables need to be repaired first.
Please stop, you're going to make things worse. Disk Utility does not fix problems with hybrid MBRs, in fact if frequently causes them.
Code:
Recovery/transformation command (? for help): c
Warning! This will probably do weird things if you've converted an MBR to
GPT form and haven't yet saved the GPT! Proceed? (Y/N): y
Caution! After loading partitions, the CRC doesn't check out!
Recovery/transformation command (? for help): p
Disk /dev/disk0: 625142448 sectors, 298.1 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 85E0FC88-16BF-40D9-B83C-28E5411E91BE
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 625142414
Partitions will be aligned on 8-sector boundaries
Total free space is 625142381 sectors (298.1 GiB)
Number Start (sector) End (sector) Size Code Name
1 1762245035278981155 4978843805995936872 1.4 ZiB FFFF ៨菿Ⴤh⌐藖瓀栘誌က恨H栐棨က쒃栐
2 13872511820988159487 462272021473857396 2.2 ZiB FFFF 彙⍞寃쏉譕凬噓뽗က
3 7035772704227161536 27571448056254464 5.0 ZiB FFFF 匘뭖က
4 1473785717573831939 12688327919827615850 4.9 ZiB FFFF 憬က䖍僼ｖ嶉ꠕa蔐瓀蔄痶ﾪᗿ憤က噟ᗿ懴က
5 1153028329402487039 18439450911346029963 7.5 ZiB FFFF က䖋师쏉譕凬坖痿贈ﱅＨ奙痿`蔐瓀樗栂核
6 6985107211248074566 14107911514549587968 3.1 ZiB FFFF 姿삅፴䖋蔘瓀范 咸Ё嶀ᓂ崀◿誘က譕￬ࡵ寨姿
7 1762595326889252616 8502532720475534847 2.9 ZiB FFFF ൴ﾅॵｐＶ박a謐忇嵞ᣂ唀匌譖尵`圐䁨h
8 7498493682491330560 16778199268606371952 4.0 ZiB FFFF 栐䚺က葨h圐�菨菿䃄ꢿh圐�훿삅ᡴ鑨栐䠠က
9 8428071037661074431 18191597813442308617 4.2 ZiB FFFF ᗿ惠က삅ٴ䖋觼ࡅ痿４ၵ痿，ࡵᗿ説က痿诼忓욋孞
10 4906108088471242891 5587568857462079585 302.6 EiB FFFF ㌄䃀৫痿（ꠕ줐ӂ唀凸噑㍗큯삅մ삃㌂
11 18378193649130287874 11823636808535575669 5.2 ZiB FFFF ࣂ㌀퀉삅մ삃㌂藀瓀茐䱸琀贊шƋ僿㌂藀痀
12 16448709242779162451 14409405053842713168 7.1 ZiB FFFF ᣬhП
13 14044756912593823996 8484928316774547430 5.6 ZiB FFFF 怸က荃ӆ尻ဤ멼璍త廨梏耇훨￫櫿樀樀栁쀀
14 2389805702834583 16719743358975220852 7.2 ZiB FFFF �܀�ｓᰕa贐䡷囨棿㿨ကᗿ怴
15 7548090107989458943 16178488307578045454 3.7 ZiB FFFF 囿ᖊ
16 3679441186535790096 17823277000520427775 6.1 ZiB FFFF `弐욋孞싉譕菬೬斃ü 譓`嘐瑗｣ࡵᗿ惤
17 10020509585633574743 5587565761783336005 6.1 ZiB FFFF 惰က幟쎋쥛ￃࡵᗿ惤ကΉ옻蔏ｚ܀嗌噓
18 18398907028598715903 17909502969894699029 7.8 ZiB FFFF （`謐忇孞썝痿（`褐㬆症梞耇䳨￭쳿譕菬წ
19 9897039512659427816 1038087916527287365 4.2 ZiB FFFF 懴က痿跼 夀譙
20 18374803371501552044 4043540941290637333 1.8 ZiB FFFF 폿㖋懄ကʿ标Ϩ
21 6269024710235796226 1153028020828321535 5.8 ZiB FFFF ｐＶ頕a㌐忀埃㶋誼ကﾅ㉵呪ᗿ懌က蕙瓿嘛䃨
22 18389059296806529024 6870620563066478056 3.0 ZiB FFFF ㍙싀譕凬坖疍謈㶋懘က╪ｐ姗蕙瓀㍌櫉븂
23 17549397956699518144 7639103324577137384 3.7 ZiB FFFF 䩵ࣨ跿䡰綍疋㯼瓆個ᗿ惰က㎉ｖ`栐
24 642182482037 18378320349991089033 8.0 ZiB FFFF Ūh
25 6985107210753275419 5819716552387923968 7.5 ZiB FFFF 藼痀棅耇�쳿譕凬坖ᗿ恌က삅䅵Ｓ綉跼ﱵ볨謀
26 8502661940983232651 7847663118247159988 7.7 ZiB FFFF `弐욋쥞嗃嘤㍗움�贁�ꮫꮫꭦ趪�Ѫ䖉壴Ｓ
27 18191727637088437117 1585073929925445005 817.2 EiB FFFF ⡴ᗿ您က㵖·
28 9540902700309634655 1152988340338819210 4.4 ZiB FFFF 菿Ⴤ嗃綃Č卵䖋栈扐က䱨bꌐ誰ကᗿ戀က奙૨
29 609410918493753658 642870687785648961 14.9 EiB FFFF 牴ۆ譭⁅䒍�扳쌫䮍謂胰ﹹ甉耯ｹ甀昩㦃琀茣
30 11918395931198427136 9623347994967665572 7.0 ZiB FFFF aͻ
31 4120076777462732816 2626724482674069644 7.4 ZiB FFFF Ｄ⁵ｓᡵ痿４ၵ痿，ࡵᗿ誈ကƸ
32 10177982053095571552 10182911735092016197 2.2 EiB FFFF 怄က삅♴ｗ綋囼噖ၪ٪痿（`謐ᯞ埶ｆ倕`弐
33 9506126113945534515 3858191206707505388 5.6 ZiB FFFF 觖ﱅ삅萏
34 10225973009435212941 9942960116043478133 7.9 ZiB FFFF 褅䖍僴ժ왞ﺻ彙幛쏉譕룬
35 18378193917469262343 9493644158315920405 4.1 ZiB FFFF 嗃И
36 15961900298853243350 1153034618610384896 1.6 ZiB FFFF 쮄
褀ᡂ警昃䊉茍ࣈ䊉昘襦၂쎃﹅琂訊范504363410523390 3.1 ZiB FFFF ࢨᅴ
38 6837317527801660 13118720744139784272 5.7 ZiB FFFF Ȉ
39 17333038919056387093 13849416490766030847 6.5 ZiB FFFF ｖࡵ狨诿姰㑴橗桀က
40 6946826611573391462 6003310899358928896 7.6 ZiB FFFF ㌂ꏀ誸က蕛瓀赕橑赀ﱍ赑橑觿疉藐磀嘹痿圈
41 359581534983112727 49121845973894598 7.9 ZiB FFFF 綀ӽ䗆ϼ蜏
42 9043300530347688068 9507175277679345913 206.0 EiB FFFF 茧ᇨၴ瑈茅⃨ⅵ䗶ᑵ᧫䗶ۿ綀ǽٴ綀ݶ䪁Đ
43 2083761431308016875 9043241744400860662 3.0 ZiB FFFF ૫綀ѵ䗆ӻ綀ϼ㹴綀Ӹ㡵䗶ჿ㉵䪃Ș좊蠆ൊ좊䊈
44 7356325513604431872 9900671303894107019 1.1 ZiB FFFF 䊈̔ｅ謠ݴ䪁﹅帐䡴䗶䃾⁴䗶ࣿ萏
45 5623997914345468928 4794087297899308917 7.6 ZiB FFFF łძ䶀䊈耇ｍ蠐Ղ䷾痸྅䶶쇿១綀ÿ䪉甘옄ｅ蠁
46 226590580728630263 394610864340074496 74.6 EiB FFFF ̞諈ᤜ嶈胾䪁0茀䗆þﾃ甤옄﹅㈁﹅璀༔
47 10016005582353600257 78894919989261381 3.7 ZiB FFFF 蠆ﱝ媈訉裘ࡂ考ߣܤ嶈裸䖈製ੂ즄ᕴ똏諁﵍
48 15203393172441957337 1750353274294273248 2.2 ZiB FFFF 뎻琐聈ﱽ球耻諒言海ॴꆿ謐訏海覿븐蒡က︤
49 615599474995380363 2465505312112464 7.7 ZiB FFFF 謈р痿謌倈凿崴ೂ唀䖋謈р痿謌倈凿崸ࣂ唀䖋謈
50 18375883345461873644 5211226963050171509 2.3 ZiB FFFF ۇ旐က䛇e䗶Ĉࡴｖ᠕b夐욋嵞ӂ唀
51 5100062696914552519 6757241191758426128 735.9 EiB FFFF 疋蔔痶㌄荞ࡽ甀／Еb謐櫈堖Ɖ䧫綃ᙴ甹爌嘑痿
52 9506126113938431576 7662684585985774828 7.2 ZiB FFFF က쀳懲䗆ÿ嶉웬욫嘐䖋諴똏菰曾み╴ﺃ琦
53 24690665153660172 282329824854023 8.0 ZiB FFFF 譕诬ᑅ삅ݵ垸܀茚 綃
ݴஸȀ謊ࡍ䦋褌㌈巀Ⴢ
54 27281176981434623 12682636829082672400 5.5 ZiB FFFF ٴƋｑࡐ嗃䶋嘈䆍茄ￎチ畎蔋瓉謇樁！᱐욋嵞ӂ
55 306397642303990923 5908529233756190207 2.4 ZiB FFFF 䖋謈рࢋｐࡑ쉝譕￬ၵ䖋謈р痿謌倈凿崌ೂ唀䖋
56 8502774704669461698 18375883345461873424 4.3 ZiB FFFF 쉝
譕诬ࡅ䂋謄倈凿崠ӂ唀䖋謈р痿謌倈凿崤ࣂ唀
57 500176859365390 14005568716497388288 6.1 ZiB FFFF 襦＆�`蔐秀倆ꓨ樀堈痿昈ډᗿ惤က䚉蔈痀㤕ࡅၴ
58 4056050806294272 17044811514712391687 7.4 ZiB FFFF བ킄
59 27263584800101909 13262667654322227984 5.7 ZiB FFFF ܂ｔＷ`蔐瓀謕匇ｐϒ
60 9612373480524778342 3100866380874216914 5.2 ZiB FFFF ﻱ嵟ࣂ謀蔆瓀倐ᗿ愄ကｐＶ`褐茇>삅ੵ܀
61 1126732980515904 2810651412493312 765.8 PiB FFFF 曆綃멵䣨蔀磀园ｗ쐕`蔐磀诡蔎瓉儇ᗿ惼က삅큸
62 5834489789167461763 6974974108773581162 506.5 EiB FFFF 翸謏謎⯃쇇Ӡ䄃弌쏉坨܀厪�ḹㅴ帹縈圡㶋惰ကڋ
63 6199279152729459541 318084318016583051 5.4 ZiB FFFF 蔌痀㌄襇謃ࡃѪ偀珿＄菖ೄ삅䎉謄ࡃ譗섻ˠ䖉
64 1153027831186274047 14051273181536764037 5.6 ZiB FFFF 縈謤ࡍڋjh贱렄ヿᗿ惸က琁䜎縻簈菜嵟ӂ
65 6323273242282821055 6727920446454174696 179.7 EiB FFFF j謐诹్痿茘襦ϔ
66 11884016422709619851 6669082651476885504 5.7 ZiB FFFF 綋贈⑴̧
67 8420470547107807231 6985141893243076375 7.4 ZiB FFFF ｓ᠕b夐幟쀳嵛ӂ唀匌坖ࡪᗿ懌ကᶋ惰က襙ﱅ삅
68 3071569668573692651 11003813573103616 6.7 ZiB FFFF 蔕瓶１Ѷ폿㛿폿ｖ᠕b夐痿（ￓ폿잋幟쥛诃钁
69 8303264926709528833 10017823026330170448 761.4 EiB FFFF 윻ٴࢋｐࡑ玉㭐偳蔏¶
70 608267375465262211 17621267027459404776 7.4 ZiB FFFF `褐蔆痀栊耇የ贀쁃﹦삅ᅸ荦甋昊䖋诸⁍
71 16818694508220484864 8902794376489467907 4.6 ZiB FFFF 藿࿀鞄
72 18398052802509537063 3812306385544163408 1.7 ZiB FFFF 惠က삅ࡵ痿謹痿謈`０ￖﱵ훿幟쥛ࣂ唀坖曆
73 4280117890683764733 1546082146876028170 6.8 ZiB FFFF ཱུ삃茄ӂ蕦痉㏞ᬅ菀삅䖋觴钇
74 14509401949919575891 9445434369856198083 5.8 ZiB FFFF ｐࡵ鋨诿ﱽ佸 ދ䶍儈ｗ낐謀藰磶贫ｐ
75 1584999294787145983 6829299125360550128 2.3 ZiB FFFF ᣬ坓䖍僼痿㌈觛ﱝۨ诿㯸蒌
76 139688309722287373 5011354395728674816 2.1 ZiB FFFF 喍勨Ūh嘀痿僸凿謘廸䖋㬈瓃謆倈凿謈ﱅ쌻ٴࢋｐ
77 9225342423566808512 13566967433617188072 1.9 ZiB FFFF ㊔
78 12274622269184 5011781032077712779 2.2 ZiB FFFF ᗿ惠က삅萏
79 18397446971662007784 7747334578523834838 3.4 ZiB FFFF 觖蔃࿀宄诿Ϩ￫诿ﱅࢋｐࡑᗫ�ٴｓࡐ䶋茈Ӂ
80 18180342317121076325 1135053651740414801 622.4 EiB FFFF 삅萏Ô
81 14160161654326618192 9623347978794723340 6.0 ZiB FFFF 悈က譟廃쏉譕埬曆ᗨ
82 4459933479730 18446739609183938128 8.0 ZiB FFFF 㞨
83 5505741788180973707 13872514015442239589 3.6 ZiB FFFF Ɖ쀳ָ@즀ӂ唀荑ﱥ嘀䖍僼䖋ﾶ疋藼磀荗ࡥ
84 5836478228197822975 596035482027045640 5.7 ZiB FFFF ࡑٴڋｖࡐָ@庀 䆍诸栈
85 18178090657976745984 897905175705990888 518.1 EiB FFFF 痿诖ﱅ幟쥛ࣂᗿ惤က䖉蔌痀梹耇擨찀譕囬
86 10026216224799951702 3190390391136915525 5.0 ZiB FFFF 囆ကᗿ怜က䚋ᯘ廀쉝
譕诬ࡅ譖呰ڋｖѐ욋嵞ӂ唀
87 18178086104045029096 5011100094414652651 2.3 ZiB FFFF 瓀謆倈凿＄ﱵ襑ᱨc０`謐Ɖ삅ੵ܀
88 28327835895009280 1153032350133896976 499.5 EiB FFFF 䎉읨偃
89 15603843012121431377 8470515534596760808 4.9 ZiB FFFF 쎋ၵ㖋惰က훿痿诖忇�᭞寀싉
譕凬坖磨
90 14465987549774678133 9655717567341795307 5.9 ZiB FFFF 쀳삅䢍謄！᱐�쀛 譕菬ၽ嘀㖋惤က兗ﲋᅵ➃茀
91 3591405997923167 6196966820485565269 2.7 ZiB FFFF 䶋茈チ䖍痿謌Ｐ`謐廆 痿，`褐蔆痀
92 4528787463536654 5010772451340451584 2.2 ZiB FFFF
93 8502525035729457152 7354378606834220816 7.5 ZiB FFFF 譕菬წ坓䖍僼痿㌌㏛觿ﱝ퓨$夀襙쌻浴譖ﱵ摴䖍
94 9900698702018773007 233261460422494984 3.8 ZiB FFFF 㬈ﱝ�綋圌ᗿ愀က譞忇쥛ࣂ唀噑⋿
95 920005188793208901 931195945314698637 5.0 EiB FFFF
96 1186134593728685955 16678448472626157311 6.7 ZiB FFFF
97 342939170613692533 6220404922631542016 2.5 ZiB FFFF ⃨姿䎍倠譑请觼㛨璉掃掃χ揨ကᗿ悜
98 596315700890113093 18397213871010267269 7.7 ZiB FFFF 䖋（䚉謔`０ￖၵ훿幟쎋쥛Ⴢ嘀譗跹⁷߇搌က
99 2465506034343696 10215443782977017686 4.4 ZiB FFFF 忿썞譕囬鋨ࡅ琁嘈ᗿ战က譙廆쉝譕菬೬斃ø
100 9046578782315810816 6007366805352164348 6.7 ZiB FFFF 昀㢃甃坊ᗿ懸က襙ﱅ삅㭴ﾅᙴ疍ၙ
101 8502610315707643072 18397222071696123912 4.3 ZiB FFFF ٴࢋｐࡑ䖋藸瓀謆倈凿謈삅ٴࢋｐࡑ䖋藰瓀謆倈凿
102 10039930964740243456 4179115429201740780 5.5 ZiB FFFF 痿，`蔐࿀랄
103 5836478228211987849 3699516570570938116 7.1 ZiB FFFF 䖉觰h䖍褌䖋跼�䗇ﴌ觿ࢋｐ⁑�䖍
104 18397213871010267269 17300013938255005777 7.5 ZiB FFFF ц譓`㬐ࡅ㑴ｐ㏓㧀ࡅ፴痿（Еa倐痿（`茐ࡽ
105 10070996823926071056 10040472502452556865 8.0 ZiB FFFF ﹆䗶Ĉࡴｖ᠕b夐욋嵞ӂ唀茨ࡽ甀）鰕`褐ࡅ
106 18397442271040793088 5768201293281560693 2.5 ZiB FFFF 쥞嗃蕑痀＆鰕`嘐偗綍ｽｙﱵ痿耕a樐僫ᗿ
107 9874232340011059974 1463259900476854398 4.4 ZiB FFFF 痿４ၵ痿圌ჿ幟쉝譕召嶋圈曆弻甐嘒瞋蔈瓶）ѷ
108 10020769222252778768 615586806561443904 3.9 ZiB FFFF 倐ᇿ삅蠏Æ
109 7012128805045146802 17308894659296038912 4.5 ZiB FFFF 됃c０찕a夐삅ቴ䶋茌Ѡ윀쀀c褐ࡈ˫쀳䎉蔈瓀謆倈
110 16719743356032795019 2465508796398820 768.0 EiB FFFF ࡅ琁嘈ᗿ战က譙廆쉝譕诬瑈䡚䵴琎ă
111 16938038617032752904 27430710562286122 682.2 EiB FFFF 地綋嘈ｗ氕a謐ᱎ纉謔！弐㍞巀Ⴢ唀䆋儈ｐࡵ⟨
112 1585008073700308479 1339604863050124 7.3 ZiB FFFF ㌐넏蔊痀坙ᗿ悜ကＳ㥗ᡆ橗０ᑶᗿ慜က㯫表圀
113 1735573976395284744 6728033195135074402 2.2 ZiB FFFF 蔐痀렇䀃耀㳫譖橗处邿e㌐璧謑Ѫ뽙斠က툳ꟳ
114 13258633050049527941 4717306462765097 2.3 ZiB FFFF ݵθ@茈 ڸȀ嶀ᣂ唀䶋脌
115 10022885211371309832 18379624560086419529 3.6 ZiB FFFF 仫烿謈ࡍ䦋（ᡰᆋ勿［ࡰ䶋謈ࡉ烿謘１ђ⣫즃替䢉
116 5011359093550482626 18432814379294348808 5.8 ZiB FFFF 瓀倎Ç揀ကᗿ战က譙廆쉝譕菬ⳬ坖疍贈ﱽ諨贀ѻ
117 6954707913625930064 17549208369436102656 4.6 ZiB FFFF 摴㶋惰က＂〴疉诗у㓿Ｐ诗̻瓾贋ࡵ˨謀
118 2443290794305343500 3731924710955417628 572.3 EiB FFFF 赗譓萕`贐ࡅ
119 6414931641131099779 18053611545166725171 5.0 ZiB FFFF 弐삅ṵᗿ您က삅౾Ｅÿഀ
120 6219841628585066600 15603582927774422527 4.1 ZiB FFFF 攼က噖卖痿（ပ`蔐秀嘍橖匐ᗿ慜က�譗怽a贔
121 30786325602304 20480 8.0 ZiB FFFF @䀀搮瑡a
126 3923213452367957380 3923213452368809292 416.0 MiB FFFF ෘ份ෙ㙲ൊ乾ෙ퍠൶买ෙ퍠ൄ乺ෙ楒档乻ෙ
127 1152939096792891392 1407374917107712 7.5 ZiB FFFF
Recovery/transformation command (? for help): e
Warning! This will probably do weird things if you've converted an MBR to
GPT form and haven't yet saved the GPT! Proceed? (Y/N): y
Caution! After loading partitions, the CRC doesn't check out!
Recovery/transformation command (? for help): p
Disk /dev/disk0: 625142448 sectors, 298.1 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 85E0FC88-16BF-40D9-B83C-28E5411E91BE
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 625142414
Partitions will be aligned on 8-sector boundaries
Total free space is 661 sectors (330.5 KiB)
Number Start (sector) End (sector) Size Code Name
1 40 409639 200.0 MiB EF00 EFI System Partition
2 409640 311902423 148.5 GiB AF00 Customer
3 311902424 313171967 619.9 MiB AB00 Recovery HD
4 313171968 625141759 148.8 GiB 0700 BOOTCAMP
61 16177792531902366089 9002440838049818627 4.9 ZiB FFFF ⶾ糟鮏0狑餀䑱ﾀ歬섾Ｆ塇븀弖ꓧૐ墯픆
62 9024114456867150270 4785357088958439475 6.2 ZiB FFFF 墉晸Ή곑惿拇䷫璈馆菌숏¯靟촓ӝ垬꧹✬
Recovery/transformation command (? for help):@Hubriz70
In my opinion, this is no win. The disk needs to go to professional disk recovery.
The MBR doesn't contain an entry for Windows. That's why it doesn't show up and why it won't boot.
The main GPT does have an entry for for Windows. The fact it's not showing up as Boot Camp in OS X Disk Utiity, or in the Finder makes me think the GPT entry for Windows is wrong. How could it be wrong?
If you try to resize a Windows/Boot Camp volume within Windows, it only changes the size entry in the MBR. This makes the GPT entry wrong. And somehow the MBR entry for Windows is gone.
If the Windows volume was resized, it would step on the GPT backup partition and header, and corrupt it, which it is.
If the GPT is repaired, when written to the drive it will probably overwrite a portion of the Windows volume's file system, corrupting it.
So it's a no win situation without disaster recovery. Any attempt made to fix this disk that's wrong, will exponentially increase the likelihood that data won't be recoverable.
In my opinion, this is no win. The disk needs to go to professional disk recovery.
The MBR doesn't contain an entry for Windows. That's why it doesn't show up and why it won't boot.
The main GPT does have an entry for for Windows. The fact it's not showing up as Boot Camp in OS X Disk Utiity, or in the Finder makes me think the GPT entry for Windows is wrong. How could it be wrong?
If you try to resize a Windows/Boot Camp volume within Windows, it only changes the size entry in the MBR. This makes the GPT entry wrong. And somehow the MBR entry for Windows is gone.
If the Windows volume was resized, it would step on the GPT backup partition and header, and corrupt it, which it is.
If the GPT is repaired, when written to the drive it will probably overwrite a portion of the Windows volume's file system, corrupting it.
So it's a no win situation without disaster recovery. Any attempt made to fix this disk that's wrong, will exponentially increase the likelihood that data won't be recoverable.
Wow. I cant believe this. What would you say caused this? The pc just restarted and that was it.
I already said what I think caused it: an attempt to resize the Windows volume from within Windows. Otherwise it seems way too targeted for me to think this is random, in which case I don't have an idea what could do this.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.