Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

After installing Mavericks Windows won't start

C

cool-dude

macrumors newbie
Original poster
Jun 21, 2012
11
0
Hello folks,
So yesterday I upgraded from ML to Mavericks and I think it messed up my windows 7 partition :|
after I boot from the windows partition right when the windows logo appears the startup fails and reboots then goes to windows repair, I tried to do a startup repair it didn't work. And i'm not the only one with that issue, A lot are complaining. So help me folks!
 
Had you done any partitioning since you installed Windows in Bootcamp?
How many partitions were present when you upgraded to Mavericks?

If you open a terminal inside OSX and run
sudo fdisk /dev/rdisk0
what is the output please?
 
I've experienced similar issues with Mavericks and Boot Camp. In my case, Windows 8/8.1 would freeze at the boot screen. The only way around it was to reformat and revert back to Mountain Lion.

If you come across a solution, please post it here.
 
MBR missing

cool-dude said:
Hello folks,
So yesterday I upgraded from ML to Mavericks and I think it messed up my windows 7 partition :|
after I boot from the windows partition right when the windows logo appears the startup fails and reboots then goes to windows repair, I tried to do a startup repair it didn't work. And i'm not the only one with that issue, A lot are complaining. So help me folks!
Click to expand...

I had the same problem when I upgraded from SL to Mavericks (and then reverted to SL from a backup). I traced it to a missing MBR because of too many partitions.... Rebuilding the MBR in an old BootCamp installation proved too onerous, (and my Windows backup drive is "dead") so I let it go. I was hoping somebody would come up with a simple solution here.
 
Sorry for my late reply ,,
I had 2 partitions when I upgraded to Mavericks.
And the issue appears to be that Mavericks corrupted the windows local disk, So every time I start windows I get an error in a blue screen saying UNMOUNTABLE_BOOT_VOLUME
and I tried to use some commands in the cmd like chkdsk, fixboot, fixmbr
none worked :(

And here is the output for sudo fdisk /dev/rdisk0
Code: 
 Disk: /dev/rdisk0	geometry: 121601/255/63 [1953525168 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 - 1063692264] HFS+        
 3: AB 1023 254  63 - 1023 254  63 [1064101904 -    1269536] Darwin Boot 
*4: 07 1023 254  63 - 1023 254  63 [1065371648 -  490233856] HPFS/QNX/AUX
 
Last edited:
And here is the output of : sudo gpt -r -vv show /dev/rdisk0

Code: 
 gpt show: /dev/rdisk0: mediasize=1000204886016; sectorsize=512; blocks=1953525168
gpt show: /dev/rdisk0: Suspicious MBR at sector 0
gpt show: /dev/rdisk0: Pri GPT at sector 1
gpt show: /dev/rdisk0: Sec GPT at sector 1953525167
       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  1063692264      2  GPT part - 48465300-0000-11AA-AA11-00306543ECAC
  1064101904     1269536      3  GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC
  1065371440         208         
  1065371648   490233856      4  GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7
  1555605504   397919631         
  1953525135          32         Sec GPT table
  1953525167           1         Sec GPT header
 
Surely if you are seeing a Windows entry in the boot menu and when selecting that entry it gets to the Windows logo and spinning dots then any failure to boot from that point must be a Windows problem rather than anything else?
That would be my thoughts on the matter.
In any event your partition structure and partition tables (both MBR and GPT) look ok to me.
 
Quackers said:
Surely if you are seeing a Windows entry in the boot menu and when selecting that entry it gets to the Windows logo and spinning dots then any failure to boot from that point must be a Windows problem rather than anything else?
That would be my thoughts on the matter.
In any event your partition structure and partition tables (both MBR and GPT) look ok to me.
Click to expand...

I see what you are saying, Though I'm 100% sure that just before I install mavericks windows was running properly and after the install finished I booted to windows and the issue occurred.

And the weird part is that I can view my windows partition right from my mac.
But windows is not able to mount it thinking it's corrupted :|
 
I appreciate what you are saying and it seems suspiciously coincidental.

Have you run a chkdsk on the Windows partition? If so, were any errors reported/fixed? If so, did you re-run chkdsk until no errors were reported?
 
Quackers said:
I appreciate what you are saying and it seems suspiciously coincidental.

Have you run a chkdsk on the Windows partition? If so, were any errors reported/fixed? If so, did you re-run chkdsk until no errors were reported?
Click to expand...

I tried to run CHKDSK but windows couldn't do it saying that the disk is in RAW format and CHKDSK is not available for RAW formats, But actually my format is NTFS but windows thinks it's RAW because it's corrupted.
 
cool-dude said:
I tried to run CHKDSK but windows couldn't do it saying that the disk is in RAW format and CHKDSK is not available for RAW formats, But actually my format is NTFS but windows thinks it's RAW because it's corrupted.
Click to expand...

Wow, that seems an odd state of affairs. Obviously it can't recognise a NTFS file system. That's not good at all and I fear it's all lost.

It's possible that testdisk may be able to recover the lost partition but it would need to be worth the effort for you to go through that process. It is free though :)

http://www.cgsecurity.org/wiki/TestDisk_Step_By_Step
 
Quackers said:
Wow, that seems an odd state of affairs. Obviously it can't recognise a NTFS file system. That's not good at all and I fear it's all lost.

It's possible that testdisk may be able to recover the lost partition but it would need to be worth the effort for you to go through that process. It is free though :)

http://www.cgsecurity.org/wiki/TestDisk_Step_By_Step
Click to expand...

Great!, Thanks a lot for your help. I'll try ASAP
 
Quackers said:
Good luck with it if you go down that route.
Click to expand...

Yup, It was a demanding route and I haven't succeeded :|

However, I'm only left with reinstalling windows and I did not want to do that because I have games in my program files folder that I can't use if I just copy them and put them back after Installing windows again.

I really appreciated your help though, Thanks a lot.
 
cool-dude said:
Yup, It was a demanding route and I haven't succeeded :|

However, I'm only left with reinstalling windows and I did not want to do that because I have games in my program files folder that I can't use if I just copy them and put them back after Installing windows again.

I really appreciated your help though, Thanks a lot.
Click to expand...
Hmm I don't know what's happened exactly but something has roasted your Windows file system :confused:
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back