Jump to content

Wowzer42

Members
  • Content count

    23
  • Joined

  • Last visited

About Wowzer42

  • Rank
    InsanelyMac Protégé
  1. I am still using this setup, but I just upgraded to 10.6.8 and lost my sound. I've just applied the ALC889 and will restart to see if it works again. EDIT: I've reapplied the v3 hack and it works just fine again.
  2. How did you build this beast? I have a spare sawtooth and a gigabyte micro-ATX board that I'd like to give it a try.
  3. I have a USB drive with OSX installer---I'd prefer to have a good drive that would permit me to chose which drive I want to boot off of. But given how the 1TB drive performs well, it's not a big, big deal for me...but I would like to have the ability to select the hard drive that I want booted in software over the ROM BIOS...is there a way to do this? My reason for wanting a 2TB drive is that OSX naturally defaults to using the single drive for my photos and home movies (for which I use iPhoto and iMovie). Overall, I've found that hard drives seem to do better with 1 single partition---otherwise, when I try to upgrade, I'd have to include both 1 TB partitions (I know it's not a lot of work, but as someone who has managed to formate a 2 partition drive and forgot about the second partition, it is to fool proof myself).
  4. I actually have a single 2 TB partition. I can boot from that 2 TB partition if I use the bootloader from one of my 1 TB drives. I tried to search the thread, but couldn't find the post describing the size limitation... ;-(
  5. Ugh. That really puts a damper on my storage hopes. I have two 1 TB and one 2 TB internal drives. I have one 1TB external and a redundant twin 1 TB array. I was hoping to migrate to the 2 TB and using the 1 TB for my movies and photos. Now I have to figure out a new config. Why is there a 1 TB limit? Is it Apple's issue or the hack issue? Just curious.
  6. Does anyone have trouble with booting using V3 and a 2 TB HD? I have made several 1 TB drives that can boot, but when I try to boot from my 2 TB Seagate (formatted the same way as the other drives), I get the boot- testing error after "Verifying DMI Pool Data": boot0: GPT boot0: testing boot0: testing boot0: done boot1: error Does the V3 installer have a limitation of less than 2 TB? The only thing substantially different between the Hard drives is that the 2TB volume's name is 2 words and the other drives are 1 word. I have swapped the SATA cables and BIOS such that the drives that worked off of SATA 1 are now booting off of the 2 TB drive (SATA 5). I've confirmed that the 1TB volumes can boot successfully...but the 2TB drive cannot. I've deleted /Extras in the 2TB volume and re-installed Stella V3 a couple of times...all without fixing the problem. If I run the bootloader from one of the 1TB drives, it will permit me to switch to the 2 TB drive at the 'Press Any Key to Change Boot Drive' screen in 10.6.4. If I use the 1 TB to boot, I can successfully launch 10.6.4. Is there something that I'm missing? I've pasted the drive info below in case it helps: These 2 drives boot just fine: ST31000520AS: Capacity: 1 TB (1,000,204,886,016 bytes) Model: ST31000520AS Revision: CC32 Serial Number: 5VX07J00 Native Command Queuing: Yes Queue Depth: 32 Removable Media: Yes Detachable Drive: No BSD Name: disk2 Rotational Rate: 5900 Medium Type: Rotational Partition Map Type: GPT (GUID Partition Table) S.M.A.R.T. status: Verified Volumes: Andoria: Capacity: 999.86 GB (999,860,912,128 bytes) Available: 180.85 GB (180,849,647,616 bytes) Writable: Yes File System: Journaled HFS+ BSD Name: disk2s2 Mount Point: /Volumes/Andoria SAMSUNG HD103UI: Capacity: 1 TB (1,000,204,886,016 bytes) Model: SAMSUNG HD103UI Revision: 1AA01111 Serial Number: S1PGJ1DQ504801 Native Command Queuing: Yes Queue Depth: 32 Removable Media: Yes Detachable Drive: No BSD Name: disk0 Medium Type: Rotational Partition Map Type: GPT (GUID Partition Table) S.M.A.R.T. status: Verified Volumes: DS9: Capacity: 999.86 GB (999,860,912,128 bytes) Available: 172.77 GB (172,773,404,672 bytes) Writable: Yes File System: Journaled HFS+ BSD Name: disk0s2 Mount Point: /Volumes/DS9 This drive is the problematic one: ST32000542AS: Capacity: 2 TB (2,000,398,934,016 bytes) Model: ST32000542AS Revision: CC34 Serial Number: 5XW0N6L8 Native Command Queuing: Yes Queue Depth: 32 Removable Media: Yes Detachable Drive: No BSD Name: disk1 Rotational Rate: 5900 Medium Type: Rotational Partition Map Type: GPT (GUID Partition Table) S.M.A.R.T. status: Verified Volumes: Terra Prime: Capacity: 2 TB (2,000,054,960,128 bytes) Available: 1.18 TB (1,181,112,303,616 bytes) Writable: Yes File System: Journaled HFS+ BSD Name: disk1s2 Mount Point: /
  7. No mistake---and definitely no apologies needed. I knew going in that the kext could have caused my OS to quit booting...but I had forgotten that my second internal HD was being used by Time Machine for a back-up. However, I didn't have the SL master with Stella's V3 on a USB drive anymore. I also forgot my external HD was recently switched over to a video storage instead of a bootable OS. Thus, with 3 TB drives, only 1 was bootable. When it went down, I did boot into single user mode. I removed the .kext but the still refused to boot. BTW- how do you remove the .mkext cache? Thanks
  8. Man what a fun time it was (miserable, but fun). Wouldn't you know it? I forgot to make a back-up of my system disk and am currently waiting for another HD to come so that I can create a second boot disk. Well...I had to remaster SL onto my usb drive and reinstall lifehacker's extensions. Brought me to the installation window where I was able to choose Restore via Time Machine. Dialed it back 1 hour and voila! Well, at least the OS was able to boot. I had to reapply the StellaV3 extensions again, but it is back up and running. Fun, fun, fun...a little miserable, but fun.
  9. Oh man...what a mistake this was. Since posting at around 8pm, I've done nothing short of pulling my hair out. The system hung on the reboot. I tried single user mode to remove the /Extra/Extensions and kext files, but the system wouldn't boot. It gets stuck on the sound kext. I tried to remove /System/Extensions/Extensions.kext and mkext and that didnt' work. I'm remastering the SL DVD as we speak because I used my original usb drive (which I used to boot OSX) for something else. What a disaster...but at least my files are all there (and backed up if I have to nuke the whole drive). Needless to say, don't try installing the hot swappable kext...it'll make you miserable (at least it made me miserable).
  10. Scorcho, I read the website, and it appears that my build has the jmicron kext already. In my apple system profiler, I see the Jmicron JMB36x AHCI. Does the 'x' make any difference? Also, I've downloaded the kext, but am having trouble---when I install them and rebuild the kext with vchad's utility, I get a statement that the kext was installed improperly. Ahhh...nevermind. I re-read the instructions and it says to place the kext into /Extra/Extensions and not /System/Library/Extensions my bad...going to see if this works....it didn't work immediately. Going to restart and see if it works.
  11. Scorcho, I read the website, and it appears that my build has the jmicron kext already. In my apple system profiler, I see the Jmicron JMB36x AHCI. Does the 'x' make any difference? Also, I've downloaded the kext, but am having trouble---when I install them and rebuild the kext with vchad's utility, I get a statement that the kext was installed improperly. Ahhh...nevermind. I re-read the instructions and it says to place the kext into /Extra/Extensions and not /System/Library/Extensions my bad...going to see if this works....it didn't work immediately. Going to restart and see if it works.
  12. Scorcho, Thanks for the link. I'll give it a go when I get back to my machine.
  13. MacTech84 (SBMac), you hit the nail on the head. It is not hot swappable...i.e. I had to restart with the drive power on before it was recognized. Now the problem is that if I have the external eSATA device on at the boot stage, the machine hangs on the verifying DMI... stage. I believe this has to do with the order of boot in the SATA bios. I can't, however, figure out how to change it. The trick is to not have the external enclosure powered on until AFTER the boot screen shows up (i.e. before the point where you select your boot drive via OSX). Does this also mean that external eSATA devices can boot OSX? That would be sweet.
  14. I've checked my hardware and a SATA cable is inserted into the eSATA interface of my case. The SATA cable is plugged into one of the orange/yellow motherboard SATA slots. IIRC, the purple slots were not good to use. However, when I plug in the eSATA cable and turn on my external enclosure, I do not see my HD mount. In my Apple System profiler, I do not see an eSATA interface---what should I see? I've embedded a picture of what I see below:
  15. Does anyone know if the eSATA interface works with this rig? I have a box with eSATA ports, but am not sure if the motherboard has connectors/support for eSATA. Thanks.
×