jamdox Posted September 8, 2012 Share Posted September 8, 2012 Posts I've seen just say "modify this or that using champlist" and things like that. No. Chameleon (voodoo labs installer) is not installing properly. It put *something* in /dev/disk0s1. I have no idea how to get rid of it. Similarly, it's telling me I already have an install on my EFI partition. But this is a fresh re-partitioning, so... did Disk Utility not clean out the EFI partition when I repartitioned? Possibly. I want to NUKE all this {censored}. As in, get rid of it. Sanitize. Glass. Parking lot. Let perish everything that crawleth in the interstices of my partitions! Preferably without wiping my entire install. Please help. Link to comment Share on other sites More sharing options...
segfault Posted September 8, 2012 Share Posted September 8, 2012 2 Link to comment Share on other sites More sharing options...
jamdox Posted September 8, 2012 Author Share Posted September 8, 2012 LOL actually, chameleon wizard was able to install, and the system is booting from the hard drive. :phew: There are still 2 chameleon installs listed, but I can live with it... Thanks, though Link to comment Share on other sites More sharing options...
theconnactic Posted September 8, 2012 Share Posted September 8, 2012 I think unixservice was kind of talking seriously: when you install Windows, it nukes chameleon to write its master boot record. Obviously it won't work on a GUID partition table. Anyway, since you solved it, it doesn't matter anymore. 1 Link to comment Share on other sites More sharing options...
Gringo Vermelho Posted September 9, 2012 Share Posted September 9, 2012 For the record, unless you want to format the drive or you don't need for it to be bootable anymore, the only way to nuke a boot loader is to install another boot loader. did Disk Utility not clean out the EFI partition when I repartitioned? Why would it do that? That would be very bad behavior.. The EFI partition is not touched when repartitioning or resizing other partitions. 1 Link to comment Share on other sites More sharing options...
jamdox Posted September 9, 2012 Author Share Posted September 9, 2012 Yeah... I really dislike the whole "EFI partition" thing. I get that there do exist commands that allow the manipulating of data there, but hidden partitions that won't mount... and it's caused a lot of kooky {censored} when trying to make things work. Link to comment Share on other sites More sharing options...
eep357 Posted September 9, 2012 Share Posted September 9, 2012 Just like an MBR you don't mount and go play around in, just pretend they are not there and if you don't bother them, they won't bother you either and mot people don't even know they exist. There is no need to manipulate any data on them, and there normally is no data on them to manipulate, they are blank. Side note, in regards to you other topic, did you get your jmicron ATA working? 1 Link to comment Share on other sites More sharing options...
jamdox Posted September 10, 2012 Author Share Posted September 10, 2012 OK, I figured out how to do it. I sacrificed my partitions, so DON'T DO THIS UNLESS YOU WANT TO START FROM SCRATCH. Booting into an intall USB stick, go into terminal and type diskutil list This will give a list of the disks in the system. Find your target disk, for example disk0 (existing as /dev/disk0, with partitions /dev/disk0s1, etc). Then type diskutil unmountDisk /dev/disk0 fdisk -i /dev/disk0 and voilà! Your disk has now been successfully nuked YAAAAY!!! To do something similar without nuking the entire drive, there are other options in fdisk, but you'd need to know what you want to do to your boot sectors, and would need to use dd for various tasks, etc, etc. I found some info along these lines when searching on how to install chimera on an efi partition, so there's your hint Link to comment Share on other sites More sharing options...
Recommended Posts