Contribute
Register

Windows 7 not in Chimera - limitation of Chimera or not?

Status
Not open for further replies.
RehabMan said:
In OS X Terminal, run diskutil list:

Code: 
diskutil list

Post the output here.
Click to expand...


Code: 
Family-Room:~ laminar$ diskutil list
/dev/disk0
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *3.0 TB     disk0
   1:                        EFI                         209.7 MB   disk0s1
   2:                  Apple_HFS Delorean4               1.0 TB     disk0s2
   3:                  Apple_HFS HOTSPACHO               2.0 TB     disk0s3
/dev/disk1
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *1.0 TB     disk1
   1:                        EFI                         209.7 MB   disk1s1
   2:                  Apple_HFS OS X ML Test            20.0 GB    disk1s2
   3:                  Apple_HFS Mountain Lion           775.0 GB   disk1s3
   4:       Microsoft Basic Data                         49.5 GB    disk1s4
Family-Room:~ mikael$

RehabMan said:
Check your /Extra/org.chameleon.Boot.plist for a Hide Partition as well...
Click to expand...

Code: 
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>EthernetBuiltIn</key>
	<string>Yes</string>
	<key>GenerateCStates</key>
	<string>Yes</string>
	<key>GeneratePStates</key>
	<string>Yes</string>
	<key>GraphicsEnabler</key>
	<string>Yes</string>
	<key>Instant Menu</key>
	<string>Yes</string>
	<key>Kernel</key>
	<string>mach_kernel</string>
	<key>Kernel Flags</key>
	<string>darkwake=0</string>
	<key>Legacy Logo</key>
	<string>Yes</string>
	<key>Theme</key>
	<string>Blackosx_Default_II</string>
	<key>UseKernelCache</key>
	<string>Yes</string>
</dict>
</plist>

RehabMan said:
Maybe also boot Windows to show what your partition setup looks like in diskmgmt.msc ??
Click to expand...

Since installing Chimera on my ML partition, I can no longer boot into Windows. Would I boot from a Windows installer and run a startup repair?
 
Laminar said:
Since installing Chimera on my ML partition, I can no longer boot into Windows. Would I boot from a Windows installer and run a startup repair?
Click to expand...

Before you do that (replace boot record for Windows), let's try to get more information on your partitions. In terminal:

Code: 
sudo fdisk /dev/rdisk0
sudo fdisk /dev/rdisk1
 
Code: 
Family-Room:~ laminar$ sudo fdisk /dev/rdisk0
Password:
Disk: /dev/rdisk0	geometry: 45600/255/63 [732566645 sectors]
Sector size: 4096 bytes
Signature: 0xAA55
         Starting       Ending
 #: id  cyl  hd sec -  cyl  hd sec [     start -       size]
------------------------------------------------------------------------
 1: EE 1023 254  63 - 1023 254  63 [         1 -  732566644] <Unknown ID>
 2: 00    0   0   0 -    0   0   0 [         0 -          0] unused      
 3: 00    0   0   0 -    0   0   0 [         0 -          0] unused      
 4: 00    0   0   0 -    0   0   0 [         0 -          0] unused

Code: 
Family-Room:~ laminar$ sudo fdisk /dev/rdisk1
Disk: /dev/rdisk1	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 -   39062504] HFS+        
 3: AF 1023 254  63 - 1023 254  63 [  39734288 - 1513671872] HFS+        
*4: 0B 1023 254  63 - 1023 254  63 [1856804864 -   96718848] Win95 FAT-32
 
Laminar said:
Code: 
Family-Room:~ laminar$ sudo fdisk /dev/rdisk1
Disk: /dev/rdisk1	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 -   39062504] HFS+        
 3: AF 1023 254  63 - 1023 254  63 [  39734288 - 1513671872] HFS+        
*4: 0B 1023 254  63 - 1023 254  63 [1856804864 -   96718848] Win95 FAT-32
Click to expand...

The type of partition 4 is wrong. It should be type 07, but it is type 0B. Are you sure you formatted as NTFS in gparted? When you run gptsync on that disk (after formatting NTFS in gparted) in Linux what does it show as it makes its changes?
 
I didn't use gparted when I did this install last year, I let the Windows installer format its own partition. I meant to record what gptsync said when it made its changes but closed out of the window before I remembered.
 
Laminar said:
I didn't use gparted when I did this install last year, I let the Windows installer format its own partition. I meant to record what gptsync said when it made its changes but closed out of the window before I remembered.
Click to expand...

Unless you're pretty good at fixing/verifying this kind of thing in Linux gdisk, you're probably going to end up re-installing your Windows install to have it working. Linux gdisk is a very powerful partitioning utility that can deal both with GPT/MBR as well as hybrids, and you could probably use the tools in it to fix the type of that partition in both the MBR and GPT tables. I've never done it, so I can't give you a step-by-step, but that tool definitely has that kind of advanced capability.

You could also re-install the Windows boot record to that disk and do what you were doing before. Windows Recovery might be able to do that, but I find often it doesn't work, and it is just easier to do it manually with bootsect.exe at the command line (use diskpart.exe, list vol, at the command line to determine the correct volume letter of your Windows install).

You would do something like:
- boot Windows install disk
- when the first screen comes up hit Shift+F10
- type diskpart
- type list vol
- type exit
(Now you have the drive letter of the Windows partition)
- type:
bootsect /nt60 /mbr /force [drive-letter-of-windows-partition]

If you choose to re-install Windows and try to get it working, it is probably a good idea to use gparted to do the formatting (followed by gptsync), as I do in my multi-boot guide (see my blog, link in signature).
 
Thanks for the help!
 
Followup question - how do I get back into Windows? The Windows 7 DVD can't find any Windows installations, and the standard FixMbr, FixBoot, and Rebuildwhatever commands don't work.

I installed Chimera onto a USB stick from the latest Multibeast and booted from that stick. It found my test partition on hd1,1, my ML partition on hd1,2, and actually listed "GPT Unknown" on hd1,4, which is my Win7 partition. The first two boot fine, if I try and boot the Windows partition, the spinning cursor freezes and nothing happens.
 
Laminar said:
Followup question - how do I get back into Windows? The Windows 7 DVD can't find any Windows installations, and the standard FixMbr, FixBoot, and Rebuildwhatever commands don't work.

I installed Chimera onto a USB stick from the latest Multibeast and booted from that stick. It found my test partition on hd1,1, my ML partition on hd1,2, and actually listed "GPT Unknown" on hd1,4, which is my Win7 partition. The first two boot fine, if I try and boot the Windows partition, the spinning cursor freezes and nothing happens.
Click to expand...

Doesn't sound good. You might have to re-install.
 
I booted into a Parted Magic Live CD and I can still see all of my files on that partition.
 
Status
Not open for further replies.
Copyright © 2010 - 2024 tonymacx86 LLC
Back
Top