While no error message was presented to me or reported to Console, I assume that the GUID partition table was the reason for the volumes not appearing in the list. I read through the documentation for DW and one of the requirements for being able to repair a drive is "a valid partition map". (I've never run it from the CD, since I have 9+ partitions in the G5 and I boot to another one to run it). I tried this and my G5 was booted into 10.4.7 and I was running DiskWarrior 3.0.3 from the hard drive. That's just it: I believe DiskWarrior is actually examining the partition map. As long as Disk Warrior calls on OSX to dismount and mount the volume it's working on, and doesn't try to read the partition map itself, it should work." The newer OSX should know how to mount a partition on an Intel Mac with the GUID Partition Table. "Though this is not for the original problem, it might work if you install Disk Warrior on the Power PC's OSX disk and run it under OSX, instead of from its CD. As long as Disk Warrior calls on OSX to dismount and mount the volume it's working on, and doesn't try to read the partition map itself, it should work. Though this is not for the original problem, it might work if you install Disk Warrior on the Power PC's OSX disk and run it under OSX, instead of from its CD. Use "GUID Partition Table" type partition map,ĭiskWarrior won't list the volumes on these disks as That, as far as I know, DiskWarrior only recognizesĭisks that have an "Apple Partition Map" type The opposite of what you were trying to do, but Iįigure I'd mention it anyway). Volumes from the Intel Mac won't appear in the list PowerPC Mac and run DiskWarrior from there, the Second, if you start an Intel-based Mac up inįireWire Target Disk-mode, and connect it to a Since, by default, Intel-based Macs use "GUID Partition Table" type partition map, DiskWarrior won't list the volumes on these disks as ones which it can repair.ĭual 2.7GHz PowerPC G5 w/ 2.5 GB RAM 17" MacBook Pro w/ 2 GB RAM - Mac OS X (10.4.8) The reason for that is that, as far as I know, DiskWarrior only recognizes disks that have an "Apple Partition Map" type partition map. (This actually sounds like the opposite of what you were trying to do, but I figure I'd mention it anyway). Second, if you start an Intel-based Mac up in FireWire Target Disk-mode, and connect it to a PowerPC Mac and run DiskWarrior from there, the volumes from the Intel Mac won't appear in the list of volumes in DiskWarrior. Since DiskWarrior is a PowerPC-only application, the kernel extension can't be loaded). (Since the kernel on an Intel-based Mac is an Intel process, and a kernel extension works by plugging into the kernel, for an Intel Mac to be able to load a kernel extension, that extension has to be a universal binary. You'll have a couple of limitations with DiskWarrior and Intel-based Macs.įirst, since DiskWarrior uses a kernel extension (.kext), it can't run properly on Intel-based Macs.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |