Problem to boot on a 2 TB disk or to upgrade from 10.6.1 to 10.6.4

Hello
Having upgraded for all those years for 10.1 to 10.6, I have decided to build a new system on a brand new 2 TB disk
So I have partition the disk and install Snow Leopard.
Using this new system, at the beginning, everything was OK,
Now it refuse to boot on that disk
I have *repaired disk and permission, re-install Snow leopard* !!! no way
It is trying to boot on that disk then after a while it is booting on my old system disk
Look that the problem comes with the upgrade from 10.6.1. to 10.6.4
Any idea ?
Best
Cyril

Cyril Blanc wrote:
So I upgrade from 10 to 10.1, to 10.2 ...... to 10.6 and at last to 10.6.4
Earlier, you wrote
Using this new system, at the beginning, everything was OK,
Now it refuse to boot on that disk
Among the things that still aren't clear is when this disk started refusing to boot. IOW, did it work OK with one upgrade but stop after another of them, or do you mean something else?
Please keep in mind that what may be clear to you won't be to others unless you provide all the relevant info, & that just repeating what you have already said probably won't improve things much if at all. Put another way, our ability to help you depends almost entirely on the info you provide. If you provide very little, you can expect very little help. If you take the time to explain the situation fully, including anything that would not be obvious to anyone watching you do whatever you do, you will get much better results.

Similar Messages

Iq506 problem wont boot, i need a recovery disks please

I have a prob with my touchsmart iq506 it wont boot and i think i need recovery disks, i tried ordering but it appears no longer available, can anyone help? pls

Hi
As you mentioned disc was not available i was able to find a link for you.
http://www.ebay.com/itm/HP-TouchSmart-IQ506-Driver-Recovery-Disc-CD-DVD-/230849382523
Let us know how it goes!
"I work for HP."
****Click the (purple thumbs up icon in the lower right corner of a post) to say thanks****
****Please mark Accept As Solution if it solves your problem****
Regards
Manjunath

Old disk-loading iMac upgrade from 8.6 to 9.2.2?

Hello everyone,
I have an ancient Bondi Blue iMac (disk-loading) with OS 8.6. I would like to upgrade it to Mac OS 9. I can buy OS 9 from Fastmac.com for $30, but they are sold out of the OS 9.0 CD.
My question is: can I buy the 9.2.2 CD full install instead? Could I upgrade directly from 8.6? Here's the site: http://store.fastmac.com/productinfo.php?productsid=101
Thanks!
matt

*There are no universal full installer OS 9.2.2 CDs.* You will need to purchase either a univeral full installer OS 9.1 or OS 9.2.1 CD. Then you can go to Apple's Download site & download the OS 9.2.2 upgrade for free.
You can get the above mentioned CDs from:
(I have not checked these links in awhile. Hope most still work)
Make sure you check out all of the following links as prices vary for the OS 9.x cds.
Ask the vendors the color of the CD lable. All universal full install CDs are white w/an orange/golden 9.x on it.
http://store.yahoo.com/hardcoremac/index.html(RECOMMENDED BY APPLE)
http://welovemacs.com/apsyso.html
http://www.applerescue.com
Do NOT buy a gray installation CD - those are not universal installers but model-specific [NO matter what the seller says about them!] OEM-versions have caused problems in the past when used on other computer models.

Disk Space Required - Upgrade from 11.5.9 to 12

Just wondering, roughly, aside from the database, how much disk space should I require for a basic upgrade of Oracle Fins - release 11.5.9 to release 12?
Is release 12 just like 11i was - meaning, it installed all the apps, even though you used just a few?
Thanks.

You can post on http://forums.oracle.com/forums/forum.jspa?forumID=40
--Shiv

Not enough disk space to upgrade from Aperture Library

My Aperture library is about 140 GBs (I've also got an iPhoto library, which is about 40 GBs, and I don't know for sure if all the stuff in there is in my Aperture library.) I've got about 23 GBs free, and when I try to upgrade, Photos tells me it needs an additional estimated 29 GBs. What options do I have at this point? I'm wondering if this would work:
- Copy Aperture Library to an external drive.
- Delete the library from the internal drive (scary. Yes I have backups, but still scary).
- Open Photos, and point it to the library on the external drive.
Would that create a Photos library on my internal drive with all the contents of the external library? I'm worried that it would reference all the files on the external, and then I would always have to have the external drive connected to use Photos.

Okay, that's not an option. Does it need this 29 GBs just temporarily for the upgrade process? I was under the impression that the new Photos library simply references everything in the Aperture/iPhoto library, so shouldn't take up more space than what you had before. So I'm wondering if I delete some things to free up the 29 GBs, if I can run the upgrade, and then put the things back that I deleted. But if it really wants 29 GBs permanently, I'm in trouble.

Upgrade from 10.4.11 to 10.5.6 - problem with installer

This is doubtless an old problem with maybe with a new twist. I am upgrading from OSX 10.4.11 to OSX 10.5.6. I crossed my fingers hoping all would go well but can't even get the machine to restart and to mount the Installer on the desktop. Hence, evolving from a Tiger to Leopard hasn't been a success.
No matter what I try the machine goes to a grey OS screen with gobblygook on screen and stops. Investigation leads me to understand the gobblygook is a kernel panic, also featuring a Multilanguage screen. I have tried the normal restart procedure with the installer, holding C key down with restart and setting up the CD as the install disk for the restart, all to no avail.
When I eject the install DVD I can recommence using my machine without any apparent ill-effect.
An action plan and suggestions would be welcome.

Leopard requires at least a Mac with an 867MHz or faster PowerPC G4 processor -- see the Minimum System Requirements section of Mac OS X v10.5.6 Leopard - Apple Store (U.S.) or just look on the retail box packaging.
According to your profile info, your Mac is an "iMac DV," apparently a 400 MHz PowerPC G3 model. Since that isn't even close to meeting the minimum system requirements for Leopard, & the installer disc itself runs a version of Leopard as well as installing it, it is no surprise that you get a kernel panic when trying to startup from the disc.
IOW, your G3 Mac cannot run any version of OS X beyond Tiger.

My Imac fails when I try to upgrade from Snow Leopard 10.6.8. I have to boot up from disk. Does anyone know how to overcome this problem?

My iMac fails when I try to upgrade from Snow Leopard 10.6.8. I have to boot up from disk. Does anyone know how to overcome this problem?   I need to upgrade in order to install latest software.

It would be lovely to know what your talking about. Upgrading from Snow Leopard does not involve discs.
Upgrading to Lion
If your computer does not meet the requirements to install Mavericks, it may still meet the requirements to install Lion.
You can purchase Lion at the Online Apple Store. The cost is $19.99 (as it was before) plus tax. It's a download. You will get an email containing a redemption code that you then use at the Mac App Store to download Lion. Save a copy of that installer to your Downloads folder because the installer deletes itself at the end of the installation.
     Lion System Requirements
       1. Mac computer with an Intel Core 2 Duo, Core i3, Core i5, Core i7,
           or Xeon processor
       2. 2GB of memory
       3. OS X v10.6.6 or later (v10.6.8 recommended)
       4. 7GB of available space
       5. Some features require an Apple ID; terms apply.
Upgrading to Mountain Lion
To upgrade to Mountain Lion you must have Snow Leopard 10.6.8 or Lion installed. Purchase a redemption code at the Online Apple Store: OS X Mountain Lion. Mountain Lion is $19.99 plus tax. Use the code to redeem a download of Mountain Lion from the App Store. The file is quite large, over 4 GBs, so allow some time to download. It would be preferable to use Ethernet because it is nearly four times faster than wireless.
     OS X Mountain Lion - System Requirements
       Macs that can be upgraded to OS X Mountain Lion
         1. iMac (Mid 2007 or newer) - Model Identifier 7,1 or later.
         2. MacBook (Late 2008 Aluminum, or Early 2009 or newer) - Model
             Identifier 5,1 or later.
         3. MacBook Pro (Mid/Late 2007 or newer) - Model Identifier 3,1 or later.
         4. MacBook Air (Late 2008 or newer) - Model Identifier 2,1 or later.
         5. Mac mini (Early 2009 or newer) - Model Identifier 3,1 or later.
         6. Mac Pro (Early 2008 or newer) - Model Identifier 3,1 or later.
         7. Xserve (Early 2009) - Model Identifier 3,1 or later.
To find the model identifier open System Profiler in the Utilities folder. It's displayed in the panel on the right.
     Are my applications compatible?
         See App Compatibility Table - RoaringApps.
Upgrading to Yosemite
You can upgrade to Yosemite from Lion or directly from Snow Leopard. Yosemite can be downloaded from the Mac App Store for FREE.
Upgrading to Yosemite
To upgrade to Yosemite you must have Snow Leopard 10.6.8 or Lion installed. Download Yosemite from the App Store. Sign in using your Apple ID. Yosemite is free. The file is quite large, over 5 GBs, so allow some time to download. It would be preferable to use Ethernet because it is nearly four times faster than wireless.
    OS X Mavericks/Yosemite- System Requirements
    Macs that can be upgraded to OS X Yosemite
         1. iMac (Mid 2007 or newer) - Model Identifier 7,1 or later
         2. MacBook (Late 2008 Aluminum, or Early 2009 or newer) - Model Identifier 5,1 or later
         3. MacBook Pro (Mid/Late 2007 or newer) - Model Identifier 3,1 or later
         4. MacBook Air (Late 2008 or newer) - Model Identifier 2,1 or later
         5. Mac mini (Early 2009 or newer) - Model Identifier 3,1 or later
         6. Mac Pro (Early 2008 or newer) - Model Identifier 3,1 or later
         7. Xserve (Early 2009) - Model Identifier 3,1 or later
To find the model identifier open System Profiler in the Utilities folder. It's displayed in the panel on the right.
     Are my applications compatible?
         See App Compatibility Table - RoaringApps.

P35Neo2 FIR and problem with booting

So I have problem with booting my compie. Compie try to boot to the part of start windows, after that in case of switch into graphicis mobo going down and restarting (WinXP SP3). I think, that problem is not in PSU, cos i have 800W XILENCE (+3,3V 28A, +5V 32A, 4x+12V 20A, -12V 0,5A, 5VSB 3A), Board P35 Neo2 FIR, E7200 proc, bios 1.9 (updated). I have 5 disk and use raid function in bios. Graphic Radeon HD3650, Memory Zeppelin 4x1GB KIT 800Mhz.
I start with change of PSU from 550W to 800W but it didnt work, previus PSU had (+3,3V 30A, +5V 32A, 2x+12V 18A, -12V 0,8A, 5VSB 3A),
i try change memory, but no efect.
After update bios there was standard warning about bad cheksum, after resave Bios settings it was gone, and compie boot after that.
Any idea?
Thanks

So my problem is solved...but my feeling of this is not good...
I updated BIOS from 1.9 to 1.10, reset Bios settings, after restart i pressed F2 for load standart settings and i changed in Bios only that i am using RAID and disable disket and it works...i boot my compie into windows without any problem...
So i try change another things in Bios and my compie hangs in continous resets without booting into windows...no BSOD only restart and restart...
After reseting Bios settings and again Load to Default it works...and run windows...
There was only one new thing ... screen flick for the second with new screen about checking NVRAM ....this screen was not visible before (and maybe this is the problem), cos if i change something in BIOS about clocking and power management and other ones, this screen is by booting missing...and compie not run in Windows...
Next thing what i see, that in CPU multiplication dont work multiplication 9,5 and proc used frequency 2400 (9x) (it is E7200 on 2533)
i hope that this bios 1.10 fixed my problems...and my opinion is that P35 Neo 2 FIR is not ideal board for E7200 proc...so i m looking for another proc...and maybe another board...

Macbook w/ whole slew of problems...Won't Start Up, Disk Utility Can't Repair Disk, Horizontal Lines on Screen, Etc.

I purchased my Macbook in the summer of 2011 and before it went berserk it was running Mavericks. 3 years later, it's finally seemed to have run its course.
It won't start up normally and it won't start up on safe boot. Attempting to use disk utility to repair the disk only gives me the message: "Disk utility can't repair this disk. Back up as many of your files as possible." There are also horizontal lines across the start screen (before it inevitably shuts down) and the screen looks very faintly purple-ish/off-colored.
This actually didn't come out of the blue. On Monday, my macbook suddenly froze, went white, and beeped three beeps repeatedly. I restarted it and backed up all my important work files and set up an appointment at the genius bar for Friday once work ended. It remained buggy during this process with the beeps returning an occasionally a blue screen popping up.
Unfortunately, there wasn't enough space to back up my important photos and by the time I returned on the next day with an external hard drive to store them on, my macbook would no longer turn on.
Is there anything I can do to bring my macbook back to life? Ideally I'd like for it to last one more year before I graduate college. Is it still salvageable, and if so, is it worth salvaging?

I hate to spread gloom, but that computer has serious problems. The only people who can diagnose the problem(s) are technicians. I would take it back to the Apple store for further testing.
Barry

IMac will not boot with OS9 or OS8 Disk

Hello,
I have a bit of a problem. I am trying to upgrade a friends iMac to 10.3.9. He had 10.2.xx on it. This is a slot loading blue G3. I went to do the upgrade from the 10.3 disks and it told me I needed a firmware upgrade. I got that tried to run it, but was told OS 9 is not on the system. No problem, I thought I could install that without incident. I put in my factory CD and all I got was a flashing folder and after a short delay, it booted into OSX. I then went to the prefs and told it to startup from the disk. Restarted. Short delay and then the flashing icon came up. So I decided to boot from Disk Warrior and format the drive. Rebooted with OS 9 disk and problem persisted. I tried the usual stuff, PRAM, took apart set SMU. No luck. Saw on a forum, that my battery could be low or dead. I purchased a new one set PRAM and the same thing happened. I am all out of ideas and am hoping one of you out there has had this happen to them and found a solution.
Thanks
Quadra

Are you sure that Mac OS 9 CD is bootable. There are some similar looking discs (white with a big orange 9) that are for "upgrading" and cannot be used to boot. It should say something like "full installation" on it if it is bootable. If it's a disc that came with Macs, not the retail disc, it usually needs to be the one that came with model.
Also, depending on the specific iMac G3 slot-loader you have, it may not boot it if the iMac originally came with a later version of Mac OS 9. For example, if the original OS was Mac OS 9.0.4, an installation disc with 9.0 will probably not work (because it is earlier). However, a 9.1 installation disc will work.

Problems with Boot Camp - PLEASE HELP!

I'm having problems with Boot Camp. Here's what's happening. I ran Boot Camp Assistant, partitioning a 32GB BOOTCAMP drive. I insert my copy of XP and start the installation. My MBP restarts and boots into the Windows Setup. I let it run through the initial actions. I press ENTER to proceed, F8 to accept the license agreement, then when I get to the part where I should be able to select the Partition 3 BOOTCAMP drive (as it says in the Apple Boot Camp Manual) there is only a Partition 1 Unknown drive. It is the only drive to choose from and its a C: drive. I can't figure out why after I run boot camp the partitioned drive doesn't appear as an option in the windows installation. Please help!!!
Message was edited by: CarlConti08

Boot into Leo, start Disk Utility and you should see two partitions, your Leo partition and a Fat32 partition of 32GB at the end of the drive.
If not, boot camp didn't create it for some reason. If it is there then check it with DU and make sure its OK.
While your in there give it a name so you can easily identify it in your windows installer.
If there is no partition, create one using Disk Utility at the END if the drive. make sure you create it as a msdos (Fat32) partition and give it a name. The name cannot be more than 11 characters must be comprised of numbers and/or letters (no special characters).
Verify it before exiting DU.
Put in windows install disk, reboot - hold option key after the chime until you see the boot screen - select windows CD to begin install.
Don't forget to install Leo windows drivers after installing windows.
Kj

My MacBook Pro won't go beyond a white screen, after I pushed the restart button. How can I get it to a login? I have routinely backed it up, but don't know how to bring that up, nor if I have a boot file on that external disk. Help!

My MacBook Pro won't go beyond a white screen, after I pushed the restart button. How can I get it to a login? I have routinely backed it up, but don't know how to bring that up, nor if I have a boot file on that external disk. Help!

Take each of these steps that you haven't already tried. Stop when the problem is resolved.
To restart an unresponsive computer, press and hold the power button for a few seconds until the power shuts off, then release, wait a few more seconds, and press it again briefly.
Step 1
The first step in dealing with a startup failure is to secure the data. If you want to preserve the contents of the startup drive, and you don't already have at least one current backup, you must try to back up now, before you do anything else. It may or may not be possible. If you don't care about the data that has changed since the last backup, you can skip this step.
There are several ways to back up a Mac that is unable to start. You need an external hard drive to hold the backup data.
a. Start up from the Recovery partition, or from a local Time Machine backup volume (option key at startup.) When the OS X Utilities screen appears, launch Disk Utility and follow the instructions in this support article, under “Instructions for backing up to an external hard disk via Disk Utility.” The article refers to starting up from a DVD, but the procedure in Recovery mode is the same. You don't need a DVD if you're running OS X 10.7 or later.
b. If Step 1a fails because of disk errors, and no other Mac is available, then you may be able to salvage some of your files by copying them in the Finder. If you already have an external drive with OS X installed, start up from it. Otherwise, if you have Internet access, follow the instructions on this page to prepare the external drive and install OS X on it. You'll use the Recovery installer, rather than downloading it from the App Store.
c. If you have access to a working Mac, and both it and the non-working Mac have FireWire or Thunderbolt ports, start the non-working Mac in target disk mode. Use the working Mac to copy the data to another drive. This technique won't work with USB, Ethernet, Wi-Fi, or Bluetooth.
d. If the internal drive of the non-working Mac is user-replaceable, remove it and mount it in an external enclosure or drive dock. Use another Mac to copy the data.
Step 2
If the startup process stops at a blank gray screen with no Apple logo or spinning "daisy wheel," then the startup volume may be full. If you had previously seen warnings of low disk space, this is almost certainly the case. You might be able to start up in safe mode even though you can't start up normally. Otherwise, start up from an external drive, or else use the technique in Step 1b, 1c, or 1d to mount the internal drive and delete some files. According to Apple documentation, you need at least 9 GB of available space on the startup volume (as shown in the Finder Info window) for normal operation.
Step 3
Sometimes a startup failure can be resolved by resetting the NVRAM.
Step 4
If a desktop Mac hangs at a plain gray screen with a movable cursor, the keyboard may not be recognized. Press and hold the button on the side of an Apple wireless keyboard to make it discoverable. If need be, replace or recharge the batteries. If you're using a USB keyboard connected to a hub, connect it to a built-in port.
Step 5
If there's a built-in optical drive, a disc may be stuck in it. Follow these instructions to eject it.
Step 6
Press and hold the power button until the power shuts off. Disconnect all wired peripherals except those needed to start up, and remove all aftermarket expansion cards. Use a different keyboard and/or mouse, if those devices are wired. If you can start up now, one of the devices you disconnected, or a combination of them, is causing the problem. Finding out which one is a process of elimination.
Step 7
If you've started from an external storage device, make sure that the internal startup volume is selected in the Startup Disk pane of System Preferences.
Start up in safe mode. Note: If FileVault is enabled in OS X 10.9 or earlier, or if a firmware password is set, or if the startup volume is a software RAID, you can’t do this. Post for further instructions.
Safe mode is much slower to start and run than normal, and some things won’t work at all, including wireless networking on certain Macs.
The login screen appears even if you usually log in automatically. You must know the login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
When you start up in safe mode, it's normal to see a dark gray progress bar on a light gray background. If the progress bar gets stuck for more than a few minutes, or if the system shuts down automatically while the progress bar is displayed, the startup volume is corrupt and the drive is probably malfunctioning. In that case, go to Step 11. If you ever have another problem with the drive, replace it immediately.
If you can start and log in in safe mode, empty the Trash, and then open the Finder Info window on the startup volume ("Macintosh HD," unless you gave it a different name.) Check that you have at least 9 GB of available space, as shown in the window. If you don't, copy as many files as necessary to another volume (not another folder on the same volume) and delete the originals. Deletion isn't complete until you empty the Trash again. Do this until the available space is more than 9 GB. Then restart as usual (i.e., not in safe mode.)
If the startup process hangs again, the problem is likely caused by a third-party system modification that you installed. Post for further instructions.
Step 8
Launch Disk Utility in Recovery mode (see Step 1.) Select the startup volume, then run Repair Disk. If any problems are found, repeat until clear. If Disk Utility reports that the volume can't be repaired, the drive has malfunctioned and should be replaced. You might choose to tolerate one such malfunction in the life of the drive. In that case, erase the volume and restore from a backup. If the same thing ever happens again, replace the drive immediately.
This is one of the rare situations in which you should also run Repair Permissions, ignoring the false warnings it may produce. Look for the line "Permissions repair complete" at the end of the output. Then restart as usual.
Step 9
If the startup device is an aftermarket SSD, it may need a firmware update and/or a forced "garbage collection." Instructions for doing this with a Crucial-branded SSD were posted here. Some of those instructions may apply to other brands of SSD, but you should check with the vendor's tech support.
Step 10
Reinstall the OS. If the Mac was upgraded from an older version of OS X, you’ll need the Apple ID and password you used to upgrade.
Step 11
Do as in Step 9, but this time erase the startup volume in Disk Utility before installing. The system should automatically restart into the Setup Assistant. Follow the prompts to transfer the data from a Time Machine or other backup.
Step 12
This step applies only to models that have a logic-board ("PRAM") battery: all Mac Pro's and some others (not current models.) Both desktop and portable Macs used to have such a battery. The logic-board battery, if there is one, is separate from the main battery of a portable. A dead logic-board battery can cause a startup failure. Typically the failure will be preceded by loss of the settings for the startup disk and system clock. See the user manual for replacement instructions. You may have to take the machine to a service provider to have the battery replaced.
Step 13
If you get this far, you're probably dealing with a hardware fault. Make a "Genius" appointment at an Apple Store, or go to another authorized service provider.

IMac freezes and problems subsequently booting

For a few days now my imac has frozen; I don't know if it's only happening after waking from sleep but that's when it's been noticed.
e.g.
This morning I woke it from sleep and the cursur could be moved but nothing responded. the time was showing as sometime the previous night. the only thing that caused a response was to press and hold the power button to turn off.
Having done that, turning on again only gets as far as a grey-blue screen.
I can only get it to boot by reseting the PRAM when turning on.
I've searched the discussions here and found similar things but nothing that fits.
Any suggestions on what might be wrong and how to fix it?
(I'm running Tiger and everything is up-to-date. I've also repaired disc (no problems) and repaired permissions).
Dan

thanks for the sugguestions... although I don't like the sound (or the cost) of a new logic board!
I am running 10.4.11 (my profile was just out of date - I've updated it).
Since posting I've done a few more things...
- a hardware test from install disk (no problems)
- disk repair and permissions from install disk (no problems)
- run APPLEJACK (no problems)
- I'm saving a reinstall for a real last resort for now...
I've also seen that the machine has always been freezing within 2 hours on logging on normally - either when waking from sleep or in use.
Last night I logged on with SAFE BOOT and left it. A few hours later I woke it from sleep - no problem. This morning I woke it from sleep - no problem.
Perhaps I've not done this enough times but it does look as though SAFE Mode is fine whereas normal node is not.
Have you any sugguestions on where this info should lead me?

Hi I just updated from Snow Leopard to Mountain Lion. I write DVD's using Final Cut Pro, creating a DVD that plays HD and Standard Definition on one disk. My problem is when I used load the disk on my G5 it would ask if you want High Definition or Standar

Hi I just updated from Snow Leopard to Mountain Lion.
I write DVD's using Final Cut Pro, creating a DVD that plays HD and Standard Definition on one disk.
My problem is when I used load the disk on my G5 it would ask if you want High Definition or Standard Definition, now it just defaults to Standard Definition.(I'm using Apple's DVD Player)
Can I fix this problem?

Addendum: I read on a post here (http://forums.macrumors.com/showthread.php?t=420169) about removing some kext files in order to trick OSX into thinking that there were no FireWire ports.
I followed the instructions and removed from /System/Library/Extensions/ the following files:
IOFireWireSerialBusProtocolTransport.kext
IOFireWireAVC.kext
IOFireWireFamily.kext
IOFireWireIP.kext
IOFireWireSBP2.kext
I restarted and BAM...Snow Leopard booted crazy fast and the mouse and keyboard worked instantly.
The System Profiler says "No FireWire ports were found."
So this tells me that the FW port is probably the culprit and is messing up the installation.
So how do I hack the Mountain Lion installer and tell it to ignore the FW port, which is obviously quite dead? Or is there something I can do to the Base system that is similar?

DISK BOOT FAILURE: PLEASE INSERT SYSTEM DISK....

Hi
I have exhausted two full days on the following problem so I would greatly appreciate some help. The problem I am experiencing is that the disk will not boot on its own. I receive the "DISK BOOT FAILURE: PLEASE INSERT SYSTEM DISK...." error when starting up. I have run chkdsk, i have run Western Digital Diagnostics for Dos (quick test) and no problems come up with the drive. I have also jumpered pins 5 and 6 to force the drive to run at SATA-I speeds. Now here's the curious part: The disk boots up and functions absolutely perfectly IF and ONLY IF, the bios is set to boot from my IDE drive. Now on the IDE drive I have a boot.ini file set up to allow me to boot the SATA drive instead. Using this work around (i.e. boot from IDE, select SATA drive from boot menu) the drive seems to work just fine. However if i change the bios back to boot from the SATA drive (and therefore use its own boot.ini) I receive the error again and the boot will not continue.
Here is my set up:
MSI K8T Neo2-F v2.0 motherboard (with latest BIOS).
Athlon 64 X2 4200+ dual core CPU
1024GB DDR 400 RAM
1 Western Digital 120GB IDE HD running on primary master.
1 Pioneer DVD-108 DVD-RW running on secondary master.
1 Western Digital 250GB (WD2500KS) running on SATA1.
Nividia GeForce 6800 running on AGP.
M-Audio Audiophile 2496 PCI
Sound Blaster Audigy 2 ZS PCI
Originally the system was as above without the new WD2500KS drive. I then bought the new SATA drive and installed windows to it with the intention of clearing windows from the original IDE and making it a storage drive. The above workaround is how I completed installation of Windows XP and installed my other programs, otherwise when rebooting during installation the disk would fail again.
Another issue is that Windows will NOT designate the SATA as drive C. When disconnecting the IDE, the SATA will become "c:" but as soon as the IDE is plugged back in, it immediately claims "c:" again and the SATA becomes "d:". This is ascertained from running the Recovery Console and using 'map' for example. It is important that I get this to "c:" as I have programs which appear to look for files by an absolute path and will not find them on "d:".
I have also tried to 'fixmbr' and this is the only time I have seen any curious message. Using the workaround the disk works fine. But when I tried to 'fixmbr', the system warned that the disk had a non-standard boot record (or something to that effect). But in any case, boot seems fine so long as we're not booting it directly.
Finally, I should confirm that the BIOS is set to run the SATA in IDE mode and not SATA (although as a sanity check I have run it in RAID and the result is the same).
I have no idea at this stage whether the problem lies with the SATA drive or the motherboard. I have sent a copy of this to WD "for further troubleshooting", and am posting a copy here for any advice on the mobo side of things.
Many thanks

Thank you for your reply. You are right, I've just resolved the problem today and discovered that this was the case.
To close the topic and leave advice for anyone else facing similar difficulties I will sum up the progress since the initial post.
Having tried absolutely everything else, I thought "what happens if i make this sata c:?" so I decided to edit the registry and force a drive letter change to ensure that my SATA was "c:". After having done this the SATA for the first time successfully booted to the boot menu! However when loading up into Windows it kept hanging. So next I thought all I need to do is a repair install now, I disconnected the IDE to leave the SATA only and attempted this. Unfortunatley the repair install also kept hanging. The Microsoft support page detailing how to force the drive letter change does warn that doing so can mess everything up unless the problem occurred in some specific circumstances.
So a new install was in order. I hooked up the IDE again and booted from it, backed up all my files to the IDE, and then disconnected it again. Then booted from a Western Digital diagnostics disk and zero filled the SATA - this was more for my own sanity so as not to worry about dodgy MBR's and what not. Then booted from WINXP CD and formatted and reinstalled fresh.
Install was successful.
Hooked up IDE externally to dump back my backed up files. Then deleted the IDE's partition and formatted it. Powered down, connected the IDE internally again - booted from SATA successfully (now on c:)... the IDE was no longer recognised as a "system" disk in Disk Manager, so I gave it a drive letter and hey presto we're business again!! One SATA system disk on drive c: and one IDE storage drive!
SHORT VERSION: If you are adding an SATA drive to an IDE set up, and want the SATA to be your OS disk, unhook all the IDE's first... if the target drive is not in isolation when installing Windows, all kinds of problems can ensue which are very difficult to correct after the install.

Problem to boot on a 2 TB disk or to upgrade from 10.6.1 to 10.6.4

Similar Messages

Maybe you are looking for