Boot drive detection issue [solved]

Hi,
I upgraded my Arch install yesterday (pacman -Syu). The last one was four weeks ago. Among the packages updated were the stock kernel 2.6.17 and mkinitcpio, so the update generated another image /boot/kernel26.img.
Now I am having random errors while booting. One out of two (yes, 50%) boots ends with kernel panic while identifying the root fs type after initramfs and modules have been loaded. Something like "Can't find device dev(0,0)".
The apparent reason is that sometimes the boot partition is identified as hda2, sometimes as hde2. Because I have the kernel option root=/dev/hda2, boot is successful when boot partition is identified as hda2, and fails with the above message when it is identified as hde2.
My particular hardware is a Abit Be-6 motherboard (quite old) which has two ide ports and two other ide ports controlled by a Highpoint HPT366 controller (which support DMA 66). My HD is connected to one of those.
I suspect that the drive detection relies on some kind of information sent by the bios and that this information is sometimes sorted in one order, sometimes in another one, i.e. sometimes the ide ports first, sometimes the hpt366 ports first.
For information, the install cd-rom would see my drive as hde (always, not 50%) and until yesterday, the boot process would see it as hda (again, always, not 50%).
So now the questions for you, talented forum participants, are:
1/ I would like to understand how disk and partition letters/numbers are allocated: why hde2 and not hda2? Can I force the naming to hda2, whatever the Bios says (for example based on a HD ID or a IDE port ID)?
2/ I read the mkinitcpio wiki. From what I understand, I can configure what modules will be loaded at boot time for detecting my boot drive, either at image generation time, or at boot time with a kernel parameter. Would blacklisting ide modules and leave only hpt366 module help? Conversely, assuming I plug my HD in an IDE port, would blacklisting hpt366 module help?
Help will be much appreciated.

Michel F wrote:The only thing is that I guess I have now to include /etc/mkinitcpio.conf in the NoUpgrade list in pacman.conf to avoid surprises when it upgrades.
The /etc/mkinitcpio.conf file is marked as "backup" in the mkinitcpio package. Therefore, if the default configuration changes, it will be extracted as /etc/mkinitcpio.conf.pacnew and your own configuration won't be touched.

Similar Messages

T43 dvd drive playback issues [SOLVED]

I have recently picked up a t43, and am having some downright bizarre issues with the DVD drive. The t43 has ide drives, but uses a sata-bridge from what I can tell - this essentially means that both IDE drives are seen as scsi. My hard disk is sda and my dvd-rw drive is sr0. The drive seems to work ok for playing music CDs and for playing unencrypted DVDs, but as soon as a DVD with CSS is in the drive, it starts going batshit, and fills dmesg with I/O errors. I've tried Arch, Edgy Eft, and Frugalware -current -- all suffer from the same problem. I have a fully updated Arch install on it now, FWIW. Running kaffeine or mplayer or dvdbackup from the command line fills the console with "failure to crack" messages. I have yet to see how it behaves when burning discs, but cdrecord -scanbus doesn't find a usable drive, so my guess is it may not be pretty.
However, I have only been able to find a single discussion about this issue, and that was on the Gentoo forums. There was no remedy found, though some folks thought it was region related, and others thought it was related to dbus versions. I've swapped the drive out, and the issue remains, so I really don't think it has anything to do with the drive.
Can anyone out there with a t43 or later thinkpad actually view encrypted dvds on it?

As I suspected, it wouldn't burn anything - after a certain amount of dicking around, I discovered that it's expecting to see an sg* device in /dev as a burner which isn't being created by default. I created a symlink from /dev/sr0 to /dev/sg0, and cdrecord can now see the device - for some reason it didn't like being told dev=/dev/sr0 though. As far as I can tell at this point the burner does/will work, or at the very least I've burned a single copy of tpowa's base iso and booted from it fine. I still have no idea wtf is going on with reading - nearly every account I've seen online says that "everything just works" after about 2.6.15 - I've seen about 5 different libata module options, and none of them have changed anything (as far as I can tell) other than I get a nice stream of errors on boot with a couple of them.
This is just a personal observation, but it would be really helpful if people had their blogs and wiki's setup to log dates of entries. Thinkwiki is great, but it's very hard to tell if what you're reading there is from yesterday or two years ago. Also, if you're writing a how-to guide, please don't gloss over what "just works" about something that has been known to not work once it is fixed, and don't say "it all worked OOTB" if you haven't even tested it. A personal gripe there, I guess, but I get a little annoyed when I rely on community reports that "it all just works now," spend $1k+ on a lappy, and discover that it does not, in fact, all "just work" now.
I'll keep banging on this, though, and I'll post more specific error messages later on.

SATA / PATA Drive Detection Issues

I have my SATA hard disk on the primary (0) SATA channel and my DVD-RW on the primary PATA channel. This has worked fine since I've had this set up, but I've recently run into some trouble with it.
I hooked up a PATA hard drive in place of the DVD-RW to pull some data off it. When I tried to boot, it only detected the new drive and couldn't boot from it (Win 2000 blue screen). It didn't even see the original hard drive.
I messed around with the various modes under "On-chip IDE Configuration" and no matter what I do I cannot get it to detect 2 devices at once. There doesn't seem to be any consistency to the results it produces.
I have updated to the latest BIOS (2.2).
Firstly, why can you select SATA / PATA Only, and then keep the other enabled? What is the best setting for my two drives? I originally had it set to PATA Only and keep SATA enabled I think (on advice from people on this board).
If i'm not using RAID, I can disable "Onboard Promise IDE" right?
All help greatly appreciated.
Many thanks in advance.

The most likely reasons for the SATA to not be detected in the Standard Cmos in the order I would check them:
1. Data and power cables firmly connected(remove and re-attach to be sure).
2. Bios>>Integrated Peripherals>>On Chip IDE Config:
- SATA Keep enabled-Yes
- Configured as Raid- NO (Yes removes it from the Standard CMOS Features)
3. Drive no good
Make sure you have other IDE HDD's removed till you get this working again.
And yes, if you have nothing attached to Serial3&4, IDE3 you can set the Promise controller to Disabled.
Edit:
Oops, I didn't see the last post. Glad you got it!

USB/mount drive detection issue (using AIR 2)

I'm creating a drive mount listener in Flash Builder. For the most part, it works well. Lately, I have had a problem actually getting the event of a drive being mounted.
    var s:StorageVolumeInfo=StorageVolumeInfo.storageVolumeInfo;
     s.addEventListener(StorageVolumeChangeEvent.STORAGE_VOLUME_MOUNT,USBM ounted);
Then the handling method:
    private function USBMounted(e:StorageVolumeChangeEvent):void
        Alert.show("Drive Unmounted");
        printDirectory(e.rootDirectory);
My two questions:
- Has anyone ever used this method to read all drives being mounted (CD, SD card, etc)?
- Is there any way to get this to work using a USB hub?
Thanks

> You can write on "usb" because the right are : drwxrwxrwx
They appear only when I use 'sudo mount -o rw,noauto,async,user,umask=1000' instead of plain 'sudo mount /dev/sdb1 /mnt/usb2'.
I use vfat for that USB stick, so maybe that's why it works for me. The first two listings in your first post show the drives in different order, but of course the mountpoints show that the offending drive is ext2 not vfat, my bad.
Edit: This is how my ext3 USB stick behaves like:
[karol@black test]$ sudo mount /dev/sdb1 /mnt/usb
[karol@black test]$ mount | grep sdb1
/dev/sdb1 on /mnt/usb type ext3 (rw)
[karol@black test]$ ls -l /mnt
total 8
drwxr-xr-x 2 karol users 4096 07-03 01:08 usb
drwxr-xr-x 2 root root 4096 2009-09-14 usb2
This time /mnt/usb is an ext3. As you can see, there's no root, I (karol) an the owner, so I can rw to my heart's content. Maybe you should change the ownership - 'chown' (man chown if you're not familiar w/ that command).
Last edited by karol (2010-07-02 23:05:52)

USB Drive detection issues

Hello,
I have been using a 16 GB Sandisk Cruzer Fit thumbdrive for the past year. I tried to access it this morning and it has no files on it. I checked properties and it says 0 out of 0 GB available. I tried the drive in another computer with success. I am able to access a 1 GB thumbdrive on this computer...What's the problem? What other information do I need to supply?

I also can't perform a system restore. Any suggestions?

Mac Version of PS6 Will Not Launch if Scratch Disk is Not Set to Boot Drive

Mac OS 10.8.2. PS6 will not launch unless the boot drive is set as the number one option for the scratch disk. Even if I choose another internal drive and set it as the number one option for PS6 it will not launch. Is there any kind of work around for this? My boot drive is only a 120GB SSD so I don't want to use it as the main scratch disk.

Curt good idea but no go. This is a fresh install of PSCS6. I ran the Apple Disk Utility three times and Disk Warrior on the boot drive. If I leave the Scratch Disk set to the boot drive no issues, only if I change the order of the scratch disk or if I do not have the boot drive selected as a possible option for the scratch disk.
Where is the 'ignor ownership' option found? I did a 'Get Info' and I don't see it in that window.

Error biohd-2 boot path testing no drive detected

Hi, I have an error massage on boot path testing and says no drive detected. The error code is BIOHD-2. My dard drive and everthying is OK but somehow unable to boot. please help.

Hello ayaansharif:
These links might help you http://www.windowserrorhelps.com/biohd-2-error-fix-error-code-biohd-2-by-yourself-now , http://answers.yahoo.com/question/index?qid=20091109134242AAVBaGy, http://www.touchsmartdevzone.com/forum/thread/969/Error-Code-BIOHD-2/ ,http://forums.techguy.org/hardware/948483-solved-hp-desktop-selecting-proper.html Based on these answers it looks like they replaced the hard drive. Check your warranty status your computer maybe still under warranty. You can go to your computer's HP web page and click on manual go down your computers parts list and find what hard drive it uses then go to HP's computers parts ordering page and order one. If under warranty just contact HP Direct Support and they will ship you a new hard drive. They are not to difficult to install. Just time consumming removing the little screws. You may need to order a set of recovery disk from HP as well. Because HP's recovery disk include the operating system disks. Please click on Kudos if this resolves your issue. Thank you frrw.

Boot Camp / Windows 8.1 64-bit / Driver compatibility issues

Hi everyone,
I have been struggling to install Windows 8.1 Pro 64-bit version through Boot Camp on my MacBook Air 13 inch mid-2012 for a few days and I have finally decided to give up and write this thread to see if anyone has encountered the same problems as I have and if they've found a solution.
What I've tried so far:
1. First attempt
     a. Download the ISO from Microsoft (We are a Microsoft Partner and have access to internal use licences of Windows 8.1).
     b. Use the Boot Camp utility to create a bootable USB drive, download the latest Boot Camp drivers and partition my SSD drive.
          Issue: Upon rebooting, I got the "No bootable device found" error message. I still tried to boot on the USB drive, which I was able to, but           when installing Windows, I was unable to format the partition created by the Boot Camp utility as it contained a "MBR partition table"           instead of a GPT.
2. Second attempt
     a. I searched the Internet about the error message about the MBR partition table.
     b. The solution I found was to format the partition created by the Boot Camp utility as "Free space".
     c. I was then able to start Windows installation by formatting the partition I wanted to allot it to through the Windows installation process.
          Issue: The installation went smoothly until my computer rebooted the first time and the "Peripherals preparation" step (sorry about the           approximate translation, I'm used to the French version of it) got stuck at 10% and was brutally followed by a black screen. Forcing the           computer to restart would show the Windows logo and go straight back to the black screen situation...
3. Third attempt
     a. I decided to create a bootable Windows installation USB drive using UNetBootin utility and creating a "Free space" partition through Disk      Utility on which to install Windows.
     b. I then booted on the USB Drive and was able to install Windows properly.
     c. I donwloaded the set of Boot Camp drivers through Apple's wesbsite corresponding to my MacBook Air model.
          Issue: Somehow, the graphics driver installed by Boot Camp made my system crash as I got a black screen when it tried to install. Even           without doing anything and having Windows try to install the right driver by itself, I got a black screen and an unusable installation of           Windows 8.1.
What am I missing here? Why isn't the Boot Camp utility working when it should be so easy? Is there a compatibility issue of my graphics driver (Intel HD Graphics 4000) with Windows running under Boot Camp?
Thanks in advance for your help. I'm in desperate need of a solution as I don't want to go back to using virtualisation softwares such as Parallels Desktop, VMWare, etc. though they work just fine...
Best regards,
Alex

1. Your MBA does not support EFI/Free Space method.
2. You need to ensure that your USB is a USB2 device.
3. The MBR should be checked, because there are known cases where BCA fails to create the MBR.

IPhoto 11 Migration Issue: Unique Circumstance (Boot Drive Crash)

Hello good folk,
I have a migration issue with iPhoto 11 due to a boot drive crash.
The issue: I have imported my library database file and all of my 25,000 photos into a clean install of iPhoto 11. All of the events are imported, but all of the photos appear in the very first event. All of the other events are populated with the correct number of photos, but none of the actual photos have been linked.
I know all about holding down option-click and option-command-click to rebuild libraries, directories, etc., as I have read about in multiple posts. But many tries haven't gotten me to success.
Any suggestions? What am I doing wrong?
Here are the specifics of the chain of events, in case it helps [sorry for all the details, but it might help]:
1. Was running iPhoto 09 in 10.5.8, my boot drive bit the dust.
2. I was able to save most of my data from the drive. Due to corrupt files, I was forced to back up unconventionally: instead of saving the entire library, which I could not do, I unpacked the iPhoto library and, from the Originals folder, I copied over entire year folders (2002, 2003, etc.) onto a non-boot drive. This worked.
3. I then installed the new boot HD and installed 10.6.X.
4. I installed fresh copy of iPhoto 11 and updated the software.
5. In iPhoto 11, I threw away the database and replaced with the recovered database from the old boot drive.
6. I copied all of the year photo folders (from the "Originals" folder on the manual backup disk) wholesale into the "Masters" folder of the new iPhoto 11 install.
7. [I could not use Migration Assistant to do this because Migration Assistant, for some reason, will not migrate from a non-boot drive that's installed internally on my Mac Pro.]
8. I option-command-clicked open iPhoto and selected:
-- Repair iPhoto Library Database
-- Rebuild small thumbnails
-- Rebuild all thumbnails
-- Examine/repair permissions.
9. I did this twice. The first time, the events from the database installed correctly, but the photos did not show up. The second time, after a very long time rebuilding the thumbnails, all 25,000 photos showed up, but in the very first event. All of the other events remain blank.
10. I then did an option-click, and chose to open the main library. I did that, but nothing changed.
11. Perhaps interestingly, when I option-click, it says that my manual backup from my internal drive -- where I did my emergency backup -- remains as the "default." The main iPhoto library is not the default.
12. That's where I am now. I really don't want to have to install manually without the data, when all of the events imported fine, and all of the photos are there, but in the wrong event.
Sorry for the long-windedness. Any suggestions are much appreciated!
John

I have imported my library database file and all of my 25,000 photos into a clean install of iPhoto 11. All of the events are imported, but all of the photos appear in the very first event. All of the other events are populated with the correct number of photos, but none of the actual photos have been linked.
You can not "Import" an old iPhoto library into another iPhoto library - it is not the way it works - if your old iPhoto library is available you simply place it in the pictures folder and launch iPhoto - no importing involved
you can not piece together an iPhoto library - which is why having a backup up is critical to avoid lost data
If your iPhoto library is not available as a single entity then you will have to start over and create a new library and import the photos into it losing all edits, metadata changes, etc
And if the future remember to always backup soon and often -it is the only way to avoid data loss due to failures - hardware, software and/or human
LN

Mac OS X Mountain Lion Boot Drive Issues

Dear Apple Users,
This is my first post here on the Apple Support Communities, so kindly forgive me if I'm repeating a previously asked question.
I'd like to create a Mac OS X Mountain Lion USB Boot Drive and of course I already have it installed on my MBP.
My question is whether I need to buy the App from the App Store if I already have it installed on my MBP[in order to create the USB Boot Drive, I need .dmg ]? On App Store, price tag is still appearing, that's why I'm asking.
Thanks in advance for all your help

If you purchased OS X Mountain Lion to upgrade your computer, open App Store > Purchases, and download OS X Mountain Lion. When the download finishes, use Lion Diskmaker to create a bootable Mountain Lion drive > http://liondiskmaker.com
If your Mac came with OS X Mountain Lion, you may not be able to make a bootable Mountain Lion drive until Apple launches a OS X update. That's because your Mac may be using a special OS X version that you can't get from the App Store, so you can only download it starting in OS X Recovery, and you won't be able to create an external drive with Mountain Lion

Hard Drive detects imminent failure

Please can anyone help. i have a compaq 6735s lap top which is about months ols. Today when i switch on I have a black screen with the following message: 1720-SMART hard drive detects imminent failure.
What should i do now

Hi,
How many months?
The error message might or might not be true. It is worth your time to go ahead and back up all of your data to an external hard disk
Boot into Windows and go to Device manager look at the disk drive device click on the + to expand the category and post the model number (the complete alphanumeric string next to the icon) here in your thread. There is a possibility that your hard drive requires a firmware update. I will do a bit of research to see if that is indeed the issue.
There are some Maxtor drives that have had to have the update done to correct the SMART reporting feature which caused an error message virtually identical to the one you are getting.
regards,
erico.
****Please click on Accept As Solution if a suggestion solves your problem. It helps others facing the same problem to find a solution easily****
2015 Microsoft MVP - Windows Experience Consumer

DV7 - Error 03F0 - No Boot Device Detected - Passes both Memory and HDD Test

Hi there,
My DV7 will not boot up at all. When powered on, I see the HP loading screen briefly, then into "dos type" font saying "No Boot Device Detected - Error 03F0"
I have run both the memory test and hard drive test from the diagnostic menu and both come back ok.
A little more history on the Device/Problem;
2 months ago it was shutting itself off due to overheating - After a good cleaning, the temps cooled down enough that it was no longer shutting off.
I am currently in India, plugging directly into outlets (230v power) using an adapter. 10 days ago there was a small spark at the outlet leaving a very small spot on one of the prongs of the adapter. There was no power flicker, and it wasn't a surge, just almost like a bad connection sparking. This "spark" seemed to have killed my charger immediately. I used the battery until nearly dead, purchased a new charger, but when I returned and tried the new charger, it would not charge, nor power on. When plugged in, at this point, the power/charging light on the side was lit, but not on the front. I used a pin to open the CD drive, and the front light lit up, but it still would not power on.
I took it to a repair shop here in India, and they managed to get it so it would power on (not sure how), but that has only brought me to where I'm at right now with the Error. They said "It worked, and then we tested again and it didn't work and now it no work".
My current BIOS edition is F.46.
Essentially I'm wondering if I'm screwed - and if I'm not, then what can I do to trouble shoot/fix it?
P.S. Finding parts in India that are specific to my computer will be near impossible with the technology differences. Also, dealing with local techs is extremely difficult so I'll need to know
P.S.S. I just tried to power it on again to double check the accuracy of my post and it will not power on, nor can I get the CD drive open again....

Is the unit still in warranty?
Based on the description of the behavior, it does sound a hardware issue beyond the hard drive.
Was the AC adapter that was purchased an HP adapter? I know you said it is difficult to get the right parts in your area, but I want to confirm if it is an HP adapter or aftermarket.
↙-----------How do I give Kudos?| How do I mark a post as Solved? ----------------↓

Front row in Lion 10.7 issue (-70012) and video_ts not playing issue -solved

Hi all,
thought I just post my solution to the front row issues in 10.7. I looked for a solution for days, and when I found it, I thought it would make other peoples live easier if I combine everything in one post.
I actually had a couple of issues:
PROBLEM:
first front row stopped playing VIDEO_TS files in 10.6.
the second issue occurred when I thought upgrading to 10.7 would solve the issue; Front row still couldn't play the VIDEO_TS, because FRONT ROW was gone...
SYMPTOMS:
both issues always showed the same symptoms:
when a dvd-back folder was selected, front row would show a black screen, and then, caused by my frantic pushing the ESC button, front row would give me the dvd player not valid -70012 error.
CAUSE:
so what happened? I chose to buy my MBP 17" with the smallest HDD (yep sorry, was cheap-s-ing). Then later that year, I decided to buy the HDD caddy and switch my internal superdrive for a SSD. I ended up placing the original HDD in the hdd caddy, which I then put in the Superdrive's slot, and I placed the SSD in the slot where the original HDD was residing first. I now had a MBP 17" late 2011, with vertex3 SSD. I forgot, I also put in 16 GB, replacing the 8 GB.
So, when I back-upped all my favorite DVDs as VIDEO_TS files, (no I did not download dvds through usenet), grabbed the popcorn, and started Front Row, the disappointment began. No VIDEO_TS file would play, always the same -70012 error message. So after a lot of internet research I stumbled upon a guy who said: yeah, you have to upgrade to 10.7. After the upgrade my FRONT ROW was gone.
SOLUTIONS:
In 10.6:
As Apple's DVD player is always looking for the internal dvd player as a prerequisite to start, Front Row, which uses Apple's DVD player as video player, will throw up the -70012 error. 'Cause it finds the HDD in the HDD Caddy instead of the SuperDrive. So in 10.6 (and in 10.7 also) you can use the following solution:
(I got this solution partial from http://reviews.cnet.com/8301-13727_7-20070591-263.html)
1: modify the DVDPlayback framework that the DVD Player uses so that it will recognize external drive as a valid DVD playback device. (The HDD Caddy came with an external casing for the SuperDrive)
2: download a hex editor (I used Hexedit 220 from http://hexedit.sourceforge.net/ )
3: Go to the folder /System/Library/Frameworks/ and back up the file "DVDPlayback.framework."
4: Open Hexedit_220 and use it to open the following file:/System/Library/Frameworks/DVDPlayback.framework/Versions/A/DVDPlayback.
5: Using the editor's find&replace through COMMAND-F, replace "Internal" with the text "External" and save the file. Note that Hexedit also saves a backup automatically.
6: Close the file once saved, and then run a permissions fix on the boot drive using Disk Utility. Then restart the system and you should now be able to play DVDs off the external drive using DVD Player. That is, If you use an external dvd player (which I don't use).
7: I inserted a very small USB stick in the MBP with no data on it, and Front Row and Apple DVD Player accepted this. I could now play my backupped DVDs.
ofcourse, I still wanted to upgrade to 10.7, so here's the solution to 10.7
10.7:
upgrading was a simple click with the mouse, worked like a charm, Office still worked, and some minor updates installed through software.
Front Row however, gone...
I used the steps outlined in http://osxdaily.com/2011/07/21/front-row-for-mac-os-x-lion/ to get Front Row back:
- first get the package from Madhatter: Download the free package installer by MacHatter
- install, or customize the install
- all done.
Then I used the steps from step 3 through 7 outlined above in solution 10.6.
Catch:
So I did not find a solution to fooling the DVD Player / Front Row with the USB stick. So everytime I watch VIDEO_TS in Front Row the USB stick must be inserted. But, the good news, I can still use my remote control for something.
Hope I helped some guys out there with this solution.
Regards,
Johnno

The issue has previously hit Apple TV owners. I think people came to the conclusion that it was a HDMI handshake problem. Basically the process where the device and TV greet each other, make up some rules about communicationg and what their secret key is and so on.
I haven't tried this yet, but my local service center says that basically I can do one of two things:
- Downgrade to 10.7 and then download the 10.7.1 update from Apples website. To do this without having a Mac OS X Lion disc, you can hold down CMD + R when the computer boots to be able to access the recovery partition on newer Macs that come without the OS disc.
or..
- Put something in between the computer and TV. For example, if you're using an amplifier as a part of your home theather set up, this will probably work. The service guy said he has his Mini connected to the amplifier, which in turn is connected to speakers and a projector. The inverted colors still appear, but only once per night (i.e. after the first problem is reset by resetting the link then it's fine).
For now, I'll do my little dance of changing the source on the TV from HDMI 1 to HDMI 2 and then back again to reset the link... But, I'll probably try downgrading in a few days.

Primary hard drive upgrade issues

All this great software has finally taken its toll on the 80Gb of hard drive space that this computer came with (Just for the record, I use the primary drive for the OS and applications only -- I store all of my data on other drives).
So, I need to upgrade the primary hard drive so I can install even more software and do even more amazing things . I'm going to upgrade my primary drive to a 120gb.
I've got Carbon Copy Cloner, but it hasn't solved a couple of issues:
First off, when I make the dupe, it doesn't maintain the original disk's Tech Tool Pro eDrive partition -- I need this on my new drive just in case. Now, you'll say "Why don't you just uninstall Tech Tool Pro and then re-install it when you set up your new drive?" Well, that's because Micromat tracks how many installs you make with any particular activation code, and I'd have to purchase another license to do another install -- and I really don't want to have to lay out $$ when there's really no clear reason.
Secondly, the CCC'd dupe doesn't play well with Classic. (Yeah, I'm a hold-out who still has a couple of OS9 oldies-but-goodies that I won't give up). The CCC'd dupe drive doesn't contain the OS9 drivers that I need to be able to successfully run Classic.
So, my overall question is this -- how do I properly set up my new 120gb drive and then properly transfer a complete image of my old 80gb drive onto it so I maintain all my functionality and all my software applications, but wind up with more space to play?
Thanks!

I solved my own problem! Here's how we did it:
First, we booted up using the Tech Tool Pro disk and removed the eDrive partition from the original boot drive.
Next, we took the new target drive (we went with a 250gb rather than a 120 -- more is always better, no?) and formatted it using Disk Utility from the OSX Panther install disk. This allowed us to put in the OS9 drivers on the disk (didn't find the option for this with Tiger's DU).
Then we used CCC to clone the old drive over. Then I did a little bit of physical re-arranging so that the new drive was in the master spot on the primary IDE chain in the box.
Finally, we booted up again using the TTP disk and had TTP create a new eDrive on the 250gb disk.
After all that, everything works just fine! No problems running apps in Classic, and no need to re-install TTP and spend more money on another license!

Switching boot drive to new internal drive??

I just got a new 150 gb internal drive installed and I've been trying to install the restore software to use it for the new boot drive instead of my old 80 gb. Disk Utility will recognize it but the install software process just shows the old drive. I've tried several times, starting up with the restore disk. Disk Utility will not format it either, all options remain greyed out. The new drive is a ST3160811AS, the profiler says SMART status is Not Supported if that is relevant.
power mac g5 Mac OS X (10.4.8) 1.5 ram, dual 1.8,

That's odd...the link doesn't work but I can do a search and access the popst from there...so I copied and pasted the text from the post
"Some of you might know that Seagate 7200.9 series SATA drives have had a problem when installed inside a PowerMac G5 because the G5s are not compatible with the Spread Spectrum Clocking (SSC) feature on those drives.
Apparently, Seagate has been paying close attention to this problem, because they have recently begun shipping some of these drives with SSC disabled.
The clue to whether a 7200.9 drive has SSC disabled is in the part number. If the part number has a suffix that is NOT -301, the drive has SSC disabled, which means that you can install it in a G5 without first installing it in a PC and running Seagate's MS-DOS utility to disable the feature.
For example a 400GB drive with SSC disabled would be ST3400633AS-303.
In case you don't know, SSC is a feature intended to reduce electronic emissions (EMI) in large multi-drive installations. These drives meet EMI standards for a single drive without SSC enabled.
FYI. FWIW."
Do a search on 7200.9, SSC and you'll see several threads which may help you solve the problem....I'm afraid it sounds like the old SSC issue.

Boot drive detection issue [solved]

Similar Messages

Maybe you are looking for