HFS+ partition error when dual booting vista/leopard

[ulibumpa]

Please help a noob...

 

I managed (geeez they make it hard) to make an extra simple partition in vista for mac os x that I left raw. Installed Kalyway 10.5.2 and formatted into journaled during installation. Apparently it was successful but when rebooting I get the dreaded HFS+ partition error. Now I can't boot into anything except Ubuntu live cd (using it right now). After reading a bit I realise I've made (at least) one big misstake; I never selected custumize during installation and don't know what consequences that might have...

 

I can't boot in safe mode to write all those commands to fix it. When I press F8 nothing happens. The only thing I can get (F2) is the normal boot options (drive, dvd etc)

 

Also how can I check if id=af from ubuntu? When I partitioned I did so with disk manager and there was no option to select anything like that

 

EDIT

Hehe, ok so I found out in ubuntu how to flag my vista partition to boot which I successfully did. The issue with my mac partition remains though. It was labeled "hfs+" which obviously needs to fixed. But how?

 

When I use Diskpart in vista it only gives me one disk with no partitions and with 112GB. In reallity I have (seen in disk manager, disk utility and ubuntu) ~70gb for vista and ~45gb for mac. What is going on?

 

Please advise

[MacNutty]

Boot with your OSX installer disk. After language selection, go to Utilities menu -> Terminal and use following commands:

 

fdisk -e /dev/rdisk0 (replace 0 with your disk no.)

flag 1 (replace 1 with partition no. where OSX is installed)

write

update

quit

 

Once done, reboot. If problem still persist then post.

[ulibumpa]

Boot with your OSX installer disk. After language selection, go to Utilities menu -> Terminal and use following commands:

 

fdisk -e /dev/rdisk0 (replace 0 with your disk no.)

flag 1 (replace 1 with partition no. where OSX is installed)

write

update

quit

 

Once done, reboot. If problem still persist then post.

Thanks.

I've tried all kinds of confusing things but got nowhere. Blue screens with music and information about mac for visually impaired ppl ...Finally I got to the utilities but...

When I get to "update" i'm told:

"device could not be accessed exclusively. A reboot is necessary for changes to take effectt. ok? [n]"

I've tried "quit" (wont save anything) "exit" "y" "ok" and a few more. I can't get it to reboot. I've never really used commands before so please tell me what to do.

 

Also how do I know what to pick from the drivers, kernels etc etc? Would the default choice be ok?

 

Sorry if it all seems very confusing. I am.

[srs5694]

I managed (geeez they make it hard) to make an extra simple partition in vista for mac os x that I left raw. Installed Kalyway 10.5.2 and formatted into journaled during installation. Apparently it was successful but when rebooting I get the dreaded HFS+ partition error. Now I can't boot into anything except Ubuntu live cd (using it right now). After reading a bit I realise I've made (at least) one big misstake; I never selected custumize during installation and don't know what consequences that might have...

 

Chances are you're missing several critical drivers in Mac OS X. You can install them after the fact from an emergency boot, but you'll need to know which ones to install (more on that shortly...).

 

I can't boot in safe mode to write all those commands to fix it. When I press F8 nothing happens. The only thing I can get (F2) is the normal boot options (drive, dvd etc)

 

You can boot the OS X install disc and, when the menu bar appears, locate the option to start the Terminal. You can then use that to type text-mode commands. This is crude and awkward in many ways, but it should enable you to copy files, etc. How to use the Terminal is a big topic in and of itself. Try Googling on "Unix shell" or "MacOS Terminal" for relevant Web sites.

 

Also how can I check if id=af from ubuntu? When I partitioned I did so with disk manager and there was no option to select anything like that

 

At a command prompt, type "fdisk -l /dev/sda" to see the partitions on /dev/sda. You may need to change the device ID to /dev/hda or something else, depending on system hardware details. You must also either type this command as root or precede it with "sudo". For instance:

 

$ sudo fdisk -l /dev/sda
Password:

Disk /dev/sda: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x8e0cb6b5

  Device Boot	  Start		 End	  Blocks   Id  System
/dev/sda1			   1		1247	10016496   27  Unknown
/dev/sda2			1248		6455	41833260	7  HPFS/NTFS
/dev/sda3			6456	   15556	73103782+   5  Extended
/dev/sda4   *	   15557	   19457	31334782+  af  Unknown
/dev/sda5			6456		8203	14040778+   7  HPFS/NTFS
/dev/sda6			8204	   11453	26105593+   b  W95 FAT32
/dev/sda7		   11454	   11645	 1542208+  82  Linux swap / Solaris
/dev/sda8		   11646	   11665	  160618+  83  Linux
/dev/sda9		   11666	   15556	31254426   8e  Linux LVM

 

This example shows that /dev/sda4 is of type 0xAF. Linux's fdisk doesn't recognize this as being Mac OS, so it reports it as "Unknown."

 

Hehe, ok so I found out in ubuntu how to flag my vista partition to boot which I successfully did. The issue with my mac partition remains though. It was labeled "hfs+" which obviously needs to fixed. But how?

 

Partition types can be identified in various ways. The 0xAF code is associated with the partition definition itself, and it can be changed without altering any data stored in the partition -- that is, it's partition metadata, like what's written on a label affixed to in an office filing cabinet drawer. Such a label can be changed without touching the files in the filing cabinet. The "HFS+" label you mention was probably derived by GNU Parted looking into the partition to identify the filesystem, like somebody opening the filing cabinet to see that it contains files of a certain type. The 0xAF label is appropriate for a partition that's formatted as HFS+, and vice-versa. A Mac OS X partition should contain HFS+ data, so this identification is probably correct. The label (0xAF) and actual filesystem data (HFS+) aren't guaranteed to match, though. For some tools, the 0xAF label is important; for others, only the HFS+ data itself is important; and for others, both are important. Chances are it's fine, since you used Apple's Disk Utility during installation to format the partition, and that tool sets the 0xAF code when it formats a partition for HFS+.

 

When I use Diskpart in vista it only gives me one disk with no partitions and with 112GB. In reallity I have (seen in disk manager, disk utility and ubuntu) ~70gb for vista and ~45gb for mac. What is going on?

 

Unfortunately, a lot of modern partitioning tools hide certain details from users; they may show only partitions that are relevant for the host OS, hide certain types of partitions, or omit certain types of partition data. You're probably just running into that issue. Linux fdisk, OS X fdisk, and some other tools show the relevant low-level data. GNU Parted and OS X's Disk Utility hide at least some things. I'm less familiar with Diskpart in Windows.

 

Also how do I know what to pick from the drivers, kernels etc etc? Would the default choice be ok?

 

You need to research your hardware and then research what drivers you need to go with it. If you can get Windows to boot, download CPU-Z. This will give you a report on your hardware. Pay attention to the main chipset (called the "northbridge" and "southbridge," or sometimes abbreviated "NB" and "SB"). The video chipset, Ethernet chipset, and perhaps others can also be important, but the main motherboard chipset is the most important to get the system to boot. Once you know what chipset you've got, Google or search the Mac forums to find out what driver you need to get it working. You'll need to download those drivers and manually install them in OS X using the Terminal. (Chances are you'll only need one driver, for the motherboard chipset's disk subsystem, to get the computer to boot, but others may be required to get Ethernet working, to get the video display working optimally, etc.) Alternatively, you can re-install OS X from scratch and select the appropriate drivers when you do so. In fact, that may be the easier method, although you'll still need to research your hardware before you do that.

 

Be aware that there are multiple drivers for most hardware devices -- there are multiple versions in a single line for some drivers, and sometimes two or more people have released drivers for the same driver. Sometimes one driver works but another one fails on any given hardware. You'll just need to experiment to find what works. Doing so can be tedious and time-consuming. Be prepared to invest several hours in such experiments. (You might get lucky and find something that works right away, but you shouldn't count on it.)

 

The kernel can also be an issue, particularly if you're using an AMD-based system. On an Intel-based system, you may be able to get by with the standard Apple kernel (often called the "vanilla" kernel). Various third-party kernels fix problems that are common on some Hackintoshes, including enabling the system to work on AMD CPUs.

[ulibumpa]

Thanks heaps Rod!

 

I've gone back to vista and got rid of the other partition and mac and the whole thing.

 

I'm doing my homework checking out what I got and what drivers I'll need atm. Thanks for the link

 

I'' be back but hopefully knowing what I'm getting myself into before jumping into the deep end

 

You gotta start somewhere...