mitch_de Posted September 1, 2010 Share Posted September 1, 2010 I have 2 HDs and i can only boot from my first HD direct. If i boot direct from second HD (F12 at boottime + select 2. HD) it didnt boot. But if i boot from HD1 and select there Win7 or OSX at HD2 it boots from there ?! For a very long time i didnt had that problem anymore (remembering 10.4.7.. OSX86 install voodoo ) Now i used new (trunk 459) chameleon RC5 on that second HD and problems started. What me makes ???? is, that if i compare diskutil and fdisk partition infos i am lost. Both HDs are MBR . i$ diskutil list /dev/disk0 #: TYPE NAME SIZE IDENTIFIER 0: FDisk_partition_scheme *500.1 GB disk0 1: Apple_HFS OSX_Snow_Leopard 88.4 GB disk0s1 2: Apple_HFS DTP_VIDEO_1 104.7 GB disk0s2 3: Apple_HFS TEMP_1 91.7 GB disk0s3 4: Apple_HFS PROMRAMMEX_1 67.1 GB disk0s5 5: Apple_HFS OSX_Snow_BACKUP_1 50.8 GB disk0s6 6: Apple_HFS WIN_SW_TEMP_1 97.4 GB disk0s7 /dev/disk1 #: TYPE NAME SIZE IDENTIFIER (Second HD, cant boot direct, only from HD1 + selecting WIN or OS X part 0: FDisk_partition_scheme *320.1 GB disk1 1: Windows_NTFS 41.9 GB disk1s1 2: Apple_HFS OSX_2 83.9 GB disk1s5 3: Apple_HFS Timemachine2 125.8 GB disk1s6 4: Apple_HFS TEMP2 68.4 GB disk1s7 So far so good. But also interesting that the disk1s numbers are not "in a row" numbers 2,3,4 are missing : 1,5,6,7 are the part names. But when i use fdisk to look after the MBR part table they look different, some partitions are not listed! # fdisk -e /dev/rdisk0 fdisk: 1> p Disk: /dev/rdisk0 geometry: 60801/255/63 [976773168 sectors] Offset: 0 Signature: 0xAA55 Starting Ending #: id cyl hd sec - cyl hd sec [ start - size] ------------------------------------------------------------------------ *1: AF 0 1 1 - 1023 254 63 [ 63 - 172633888] HFS+ 2: AF 1023 254 63 - 1023 254 63 [ 172633986 - 204554576] HFS+ 3: AF 1023 254 63 - 1023 254 63 [ 377188623 - 179018024] HFS+ 4: 05 1023 254 63 - 1023 254 63 [ 556206647 - 420566521] Extended DOS fdisk: 1> Partition 5+6 are not listed, but all works as itt should on HD 1 Now problematic HD2 (only bootable from HD1) # fdisk -e /dev/rdisk1 fdisk: 1> p Disk: /dev/rdisk1 geometry: 38913/255/63 [625142448 sectors] Offset: 0 Signature: 0xAA55 Starting Ending #: id cyl hd sec - cyl hd sec [ start - size] ------------------------------------------------------------------------ *1: 07 1023 254 63 - 1023 254 63 [ 2048 - 81920000] NTFS 2: 05 1023 254 63 - 1023 254 63 [ 81922048 - 543199232] Extended DOS 3: 00 0 0 0 - 0 0 0 [ 0 - 0] unused 4: 00 0 0 0 - 0 0 0 [ 0 - 0] unused fdisk: 1> Has 4 partitions (in real! OS X mounts them/usable) , but only listed 2 ?! Also the now flagged active part 1 had to be set actove manual by fdisk command. chameleon pkg hasnt set it active (flagged). Is FDISK wrong ? Or is that normal and only some not correct .pgk install didnt really installed+setup bootloader for that second HD. Has someone ideas ? Perhaps info about how using that few dd / fdisk commands to install bootloader complete again by commands and not the script(within packadge). Screenshoot (HD1 is first, HD2 second, untiletled is Win7 NTFS Part) Link to comment Share on other sites More sharing options...
blackosx Posted September 1, 2010 Share Posted September 1, 2010 Hi mtich Sorry for the quick post but I have to go out though I'll be back in a few hours. But for reference, I have only done my setups with a GPT formatted disk and I always install Chameleon manually. Here's a post I worked on a while back which might help throw some light on what I know. From there, Dr. Hurt's Chameleon RC5 pre8 installer was born which worked well. But I tested with iFabio's latest installer package from here and it worked just fine. Okay. I'm back. Did you use the latest installer package? if so, can you install the latest Chameleon files manually, does it work? Link to comment Share on other sites More sharing options...
oldnapalm Posted September 1, 2010 Share Posted September 1, 2010 Hi Mitch, looks like your HFS partitions on disk1 are extended, maybe that's the problem (they should be primary?) 2: Apple_HFS OSX_2 83.9 GB disk1s5 3: Apple_HFS Timemachine2 125.8 GB disk1s6 4: Apple_HFS TEMP2 68.4 GB disk1s7 *1: 07 1023 254 63 - 1023 254 63 [ 2048 - 81920000] NTFS 2: 05 1023 254 63 - 1023 254 63 [ 81922048 - 543199232] Extended DOS Link to comment Share on other sites More sharing options...
mitch_de Posted September 1, 2010 Author Share Posted September 1, 2010 Funny that WIN7 using Acronis Tools shows all Partitions. Maybe fdisk cant list real such disks >=4 partitions. I now uses an other .pkg installer (V 467) and got direct boot from HD2 / Win7 . I dont think its the bootloader itself, its the scripts used in the .pkg installers which may didnt work in all MBR situations. Link to comment Share on other sites More sharing options...
oldnapalm Posted September 1, 2010 Share Posted September 1, 2010 Has any installer worked in this situation? If you install manually it works? Using boot0 or boot0hfs? Link to comment Share on other sites More sharing options...
mitch_de Posted September 3, 2010 Author Share Posted September 3, 2010 I now booted again in WIndows7 and started to work with the paragon Part Manager 10 - it also can handle Apple HFS+ !! I first removed the extended (logical) HFS+ partitions and added again new HFS+ partitions, but now primary type. I think that will fix that problem i only can boot windows7 and not OS X , because that partition was not an primary one. Paragon Part Manager 2010 is really great!!! The there partitioned and formated HFS+ partitions were mounted in OS X , are also journaled and ready to use without any OS X diskurility. Link to comment Share on other sites More sharing options...
mitch_de Posted September 4, 2010 Author Share Posted September 4, 2010 SOLVED: Removing the logical partitions and creating new primary part solved the boot problem. I now also can boot into OS X, before only Win7 (was already primary part) worked. Now also fdisk show all partitions and not only the first. bash-3.2# fdisk -e /dev/rdisk0 Enter 'help' for information fdisk: 1> p Disk: /dev/rdisk0 geometry: 38913/255/63 [625142448 sectors] Offset: 0 Signature: 0xAA55 Starting Ending #: id cyl hd sec - cyl hd sec [ start - size] ------------------------------------------------------------------------ 1: 07 0 32 33 - 1023 254 63 [ 2048 - 81920000] NTFS *2: AF 1023 254 63 - 1023 254 63 [ 81931500 - 143364060] HFS+ 3: AF 1023 254 63 - 1023 254 63 [ 225295560 - 266245245] HFS+ 4: AF 1023 254 63 - 1023 254 63 [ 491540805 - 133596540] HFS+ fdisk: 1> before (same partitin count, but 3 were logical): *1: 07 1023 254 63 - 1023 254 63 [ 2048 - 81920000] NTFS 2: 05 1023 254 63 - 1023 254 63 [ 81922048 - 543199232] Extended DOS 3: 00 0 0 0 - 0 0 0 [ 0 - 0] unused 4: 00 0 0 0 - 0 0 0 [ 0 - 0] unused So fdisk cant handle logcial (extened) partitions right nor can boot from ist. Link to comment Share on other sites More sharing options...
Recommended Posts