philmcc Posted January 16, 2009 Share Posted January 16, 2009 Hi, I installed Kalyway Tiger to a drive, and it boots perfectly. Months later, I installed Kalyway Leopard to a second drive, and it installed and also boots perfectly (both drives are SATA). I am using the built in Boot selection process offered by the BadAxe2 Bios. When I boot to TIGER, I can see the LEOPARD drive perfectly fine. When I boot to LEOPARD, the TIGER drive is there, however the partitions are non existent, and as a result, I can't access any of the data. Here are my diskutility screencaps from tiger: The next three screen caps are frrom within LEOPARD. Any idea what's going on here? Can leopard simply not recognize a drive formatted MBR as opposed to GUID? Thanks guys, Phil Link to comment Share on other sites More sharing options...
philmcc Posted January 18, 2009 Author Share Posted January 18, 2009 Hi, I installed Kalyway Tiger to a drive, and it boots perfectly. Months later, I installed Kalyway Leopard to a second drive, and it installed and also boots perfectly (both drives are SATA). I am using the built in Boot selection process offered by the BadAxe2 Bios. When I boot to TIGER, I can see the LEOPARD drive perfectly fine. When I boot to LEOPARD, the TIGER drive is there, however the partitions are non existent, and as a result, I can't access any of the data. Here are my diskutility screencaps from tiger: The next three screen caps are frrom within LEOPARD. Any idea what's going on here? Can leopard simply not recognize a drive formatted MBR as opposed to GUID? Thanks guys, Phil bump. Link to comment Share on other sites More sharing options...
Recommended Posts