Will not boot in RAID 0

I can't get the Win XP setup to load the drivers from the disk after the formatting stage.
So, I've followed all of the instructions at the beginning of this thread. I boot the Windows cd and hit F6 as required. I'm prompted for the drivers and load both from the floppy. I choose a full format on the drive. After the format, it tells me it can't find the SATA drivers even though I can see it searching the floppy drive. It leaves me no choice but to hit esc to skip the files.
Has anyone else had this problem and found a solution?
MSI K8N Neo2 Platinum Bios 1.4
AMD Athlon 64 3500+ (Socket 939)
OCZ 1GB DDR 3200 (2x512MB) CAS2.5
ATI Radeon All in Wonder 9600 Pro 128MB
2x 34gb wd Raptor
NEC 3500 DVD/CD Rewritable
Antec TruePower 430 Watt PSU (3.3V-28A 5V-36A 12V-26

SUCCESS
All it took was to try a different windows xp cd install diskl...that resolved the issue...very strange like taking a trip in the windows Bill Gates Twilight world
well I guess that chalks up and finally defines what colour of sky Bill lives in...
later and thanx to all who helped me in this regard
take care
Craghael

Similar Messages

Will not boot up on 1st try

Hey everyone,
I am having a strange problem, My computer will not boot up on the 1st try after it has been shut off for 2 hrs or more. Here are my specs and then I will go into more detail. I like to use pictures because some of the terminology escapes my vocabulary.
MSI P6N Diamond LGA 775 NVIDIA nForce 680i SLI ATX Intel Motherboard
Intel Core 2 Duo E6850 Conroe 3.0GHz 4M shared L2 Cache LGA 775 65W Dual-Core Processor
ZALMAN CNPS9700 LED 110mm 2 Ball CPU Cooler
2 X Seagate Barracuda 500GB 7200 RPM SATA 3.0Gb/s Hard Drive In Raid 0
XFX GeForce 8800GT 512MB 256-bit GDDR3 PCI Express 2.0 HDCP Ready SLI Supported Video Card
Kingston HyperX 2GB (2 x 1GB) 240-Pin DDR2 SDRAM DDR2 800 (PC2 6400)
BFG Tech 800W Power Supply>>+3.3V@24A,+5V@30A,+12V1@20A,+12V2@20A,+12V3@20A, +12V4@20A,[email protected],[email protected]
2 X LITE-ON 16X DVD±R DVD Burner
SONY Black 1.44MB 3.5" Internal Floppy Drive
COOLER MASTER Stacker 830 Evolution Black Aluminum ATX Full Tower Computer Case
Logitech Z-5300 Speakers 5.1
Samsung SyncMaster 204B monitor
Logitech G5 mouse
Windows XP home, SP2
Build Date 11/26/2007
Problem:
After being shut off for more than 2 hours my computer will not boot up on the 1st try. It goes to a message that says"Reboot and select proper boot device or insert boot media in selected boot device and press a key". I shut it down using the power button, wait for the hard drives to stop spinning, and then hit the power again and it starts up just fine. It will restart just fine also as many time as I want to restart it, after it has been running in windows. Once it is running, it runs terrific, no problems at all.
If you go right into the bios after sitting for a while you see this in the boot sequence, notice there is no hard drives(Nvidia Stripe)in the boot sequence.
After shutting it down and starting right back up this is what you see in the boot sequence. This pic is from a different time, thats why the boot sequence is different.
Here is a short youtube video (2:10 sec) made to help show the problem. (I called it a Cold boot Storage problem for another thread) just ignore that.
Things I have done to try to solve the problem:
1. Update the bios
2.I have moved the boot sequence around, Foppy1st, or CD 1st, ect. and even disabled the [USB:HP Photosm] in the boot sequence, Hard Drives are 1st now.
3.Replaced the Mobo Battery thinking that it was not remembering the boot sequence
4.Checked that the Hard Drives are connected to the correct plugs (6-7) on the motherboard, and that the raid connector JP1 was shorted out for Raid 0 and the blue indicator light was flashing.
* Just a note in this area. I did set up the Raid 0 with a tech from MSI because I was having an issue with the initial set up, and I did use the Nvidia raid drivers that came with the motherboard. Pchas01 in another thread thought that this could be part of the issue because it is not necessary to load the drivers when you set up the Motherboard in the Raid mode.
F10 and look in the Raid Array
5. Pulled the jumper off of JP1 and it just went to the "Reboot and select proper boot device or insert boot media in selected boot device and press a key" screen much faster, but would never boot up after 5 tries. Put the jumper back in and started up on the 2nd try like the normal problem.
6.Went into the On-Chip ATA devices in the bios and Changed the Raid Mode to an IDE, I cannot F10 and get into the Raid Array now, but I guess that is normal.
Now this is what my boot sequence currently looks like.
That is the point that I am right now. It runs great, games are awesome on it. Its just does not want to start up on the 1st attempt.
Thanks for any help on this
Chris aka Fritzpeed novice builder

Thanks for the reply,
I started with the easy fixes first, changed the sata cables, and tried different power supply connectors. Both tests had same results, still boots up on 2nd try. I did not know how soon the problem would re-occur after it has been shut down, my shortest time so far is 25 minutes.
Quote
Why only one RAID channel is enabled? Array can't be detected in that way...
Well right now, it is not even set up that way, in my #6 problem solving, it was suggested that I turn the Raid Mode off and try [IDE] to see if that made a difference,"because I don't need Raid enabled for the hardware raid". It did not, it only booted to the "Reboot and select proper boot device or insert boot media in selected boot device and press a key" window about 60 seconds faster. It is currently set up in this way.
This is how it looks in my On-Chip ATA Devices
How do I check this?
Quote
Does the problem persist when you use Silicon RAID instead Nvidia RAID?
I am still working on getting the seagate diagnostics to work, I am getting an error message before I can even test them.
I do have another question. Why is my HP Printer showing up in the Hard drive test, and also why is it showing up in my boot sequence, is this normal?
And speaking of boot sequences I got in there again just now and saw 2 [USB:HP Photosm]
Thanks again, still working on testing hard drives.
Chris

Xserve will not boot up, all lights flash rapidly

Just bought a lightly used Intel Xserve. This unit was in a business that failed, and was set up, but never used. Was powered off and unplugged for approximately 18 months. When we tried to plug it up to check it out & configure it, we noticed the following:
System will not post and won't boot
Hard drives do not appear to spin
CD Drive appears to have no power - will not grab disk
All fans do work, and run on high RPM
All lights on back of server and front of server, as well as next to SDRAM slots, and on back of main board flash / flicker (regular quick flashes, no pattern evident). The only light that does NOT come on at all is the light next to the power button.
Anyone heard of a similar condition? Is this server toast?
Thanks,
Rob Hogan

I'm sorry to say I don't have a solution, but I can commiserate.
I have a G5 and two G4's, and so far within a few days / couple of weeks of getting them home and getting them up and running, they seem to fail.
Usually spectacularily.
The G5 operates very much as yours in that power on, fans rev high, and no post or other activity; I don't get any system light status action however other than flashing. I've replaced CPU's and logic board on this.
The single CPU G4's does much the same, but this I've had up and running and then it went down when I upgraded the memory to max (very careful to make sure it was within Apple spec's), and despite swappinbg the original memory back in,nothing.
My latest, a dual core G4, was bought in working order, and I upgraded this from 10.4 to 10.5. Running nicely as a internet gateway. Went away for weekend so put it into sleep mode. Came back, power button on front panel stopped working, and one of the raid slices on the system drive failed.
Tried to repair this and system now no longer boots, but freezes on loading OS (spinning disc stops in mid spin) and it will not boot from installation disc via firewire or internal DVD drive (swapped in a replacement to ensure it works). The installation disc stops at the apple splash screen, but goes no further.
I can, helpfully, get into Open Firmware mode, so something is working on some level. Sadly, I can't seem to find a copy of the Apple Hardware Test for this machine (see my post on this) to check it out.
I can tell you that I'm getting very adept at working with Xserve hardware, if not very effectively.
My working hypothesis on this is that there is some issue with these units being used 27/7x365 for however long, and then being left 'off' for a prolonged period.
Thinking that whilst they are designed to operate reliably as constantly on and working under load, so facet of being 'off' breaks 'something'.
If really pushed to go out on a limb, I'd theorise that under load the electronics/IC's settle into position, but then when switched off things cool down, contract, and causes weaknesses in electrical connections to occur. When next used, these then start to fail, giving a pattern of initial operability followed by delayed failure with a cascade of increasingly servere symptoms until terminal failure is reached.
But that is wild, uneducated, conjecture.
So, no help, but I comiserate.
XD Andy
btw, is anyone has some useful advice for me on where to find the AHT 2.0.1 for Xserve or even just the part number ... ... ...

Will not boot up to log in screen

will not boot up to log in screen when powered up, all I get is a grey screen with apple logo in middle and spinning timer
I have tried resetting SMC
I have tried starting up in Safe Mode (it won't do that either)
I have gotten into disk utility to repair disk
I have tried resetting PRAM
nothing... we are on a network in a school district so my next step is to re-image it but wondering if there is something else I should try first
if not then how do I backup files that are needed before I re-image
thanks, Cindy

Take each of these steps that you haven't already tried. Stop when the problem is resolved.
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 you use a wireless keyboard, trackpad, or mouse, replace or recharge the batteries. The battery level shown in the Bluetooth menu item may not be accurate.
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, or if a firmware password is set, or if the startup volume is a Fusion Drive or 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.

G5 will not boot into OSX - stays at a command-line prompt

My G5 will not boot into OS X. I would appreciate and and all advice. Thanks.
What happened:
I had the G5 running one morning, with the Isight camera on, plugged into the front-console firewire port. I was running EvoCam software.
At about 2 hours into running, the cam stopped broadcasting – I got home to check it out three hours later, and the screen was black, and the fan was louder than I had ever, ever heard it on this box.
I did a hard shut-down with the powerbutton on the Cinema Display monitor.
At reboot, I see a grey screen for approx 5 seconds, with a dark grey apple logo, and then the screen goes to black, with a command-line prompt.
It’s been like that ever since.
I ran the Apple Hardware test, from the internal CD drive, and it shows no errors.
I cannot boot from an OSX installer DVD. It won’t recognize it. It goes straight to the black screen and Command line prompt.
I have re-seated the RAM, as well as the Airport Card. The only other card – which I have not re-seated, it the video card.
I am able to use the machine in Target Mode, so I can extract data from the drives, which is great. Oddly enough, I’m able to use the front-console firewire port to connect to my other Mac in Target mode – with no problems. Also – in Target mode, the fan never goes above the usual quiet self.
I would appreciate any advice one can provide. Thanks!
The machine:
Mac G5 dual 2.0 – First Generation (purchased December 2003)
It’s on it’s 3rd Motherboard – and now it’s fully out of Applecare warrantee.
OSX 10.4.9
4GB Ram
2 internal drives: 160GB + 300GB
Airport Extreme
20” Cinema Display (first generation)
Mac G5 dual 2.0 – First Generation Mac OS X (10.4.9)

Well, Apple Support does have articles on:
Isolating Issues in Mac OS X
http://docs.info.apple.com/article.html?artnum=25392
won't boot or login
http://docs.info.apple.com/article.html?artnum=106464#symp1
And if those don't work, call.
With G4 there is/was
"Fix for a Mac that won't power up
Mirrored Doors G4. When you pressed the power button, the button would light up, but the computer would not turn on. The fans on the power supply wouldn't turn on.
FIX: unplug the machine, pull the clock battery, hit the power button to discharge. Then plug it in without the clock battery. The machine should boot perfectly. Shut down, reinstall the clock battery, and now the system is fully functional. Macosxhints
http://docs.info.apple.com/article.html?artnum=300552
Reseat video? try another video card?
My Step #1 is to always boot into Open Firmware (and do reset-nvram, reset-all, if you can't do that, you are sunk).
Oh, and What do you see in verbose mode on startup?
Mac Pro 2GHz 4GB 10K Raptor 23" Cinema Mac OS X (10.4.9) WD RE RAID Aaxeon FW800 PCIe MDD-G4 APC RS1500 Vista

My 2011 IMac will not boot up past the White apple logo screen with the whirly circle

My 2011 IMac will not boot up past the White apple logo screen with the whirly circle. I have tried various commands but to no avail. does anybody have any advice?

Take each of these steps that you haven't already tried. Stop when the problem is resolved.
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 you use a wireless keyboard, trackpad, or mouse, replace or recharge the batteries. The battery level shown in the Bluetooth menu item may not be accurate.
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, or if a firmware password is set, or if the startup volume is a Fusion Drive or 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.

After down load of Mavericks my macbook pro will not boot up.

Will not boot after many trys of on and off.

Please read this whole message before doing anything.
This procedure is a diagnostic test. It’s unlikely to solve your problem. Don’t be disappointed when you find that nothing has changed after you complete it.
The purpose of the test is to determine whether the problem is caused by third-party software that loads automatically at startup or login, by a peripheral device, by a font conflict, or by corruption of the file system or of certain system caches.
Disconnect all wired peripherals except those needed for the test, and remove all aftermarket expansion cards, if applicable. Start up in safe mode and log in to the account with the problem. You must hold down the shift key twice: once when you boot, and again when you log in.
Note: If FileVault is enabled, or if a firmware password is set, or if the boot volume is a Fusion Drive or a software RAID, you can’t do this. Ask for further instructions.
Safe mode is much slower to boot and run than normal, with limited graphics performance, and some things won’t work at all, including sound output and Wi-Fi on certain models. The next normal boot may also be somewhat slow.
The login screen appears even if you usually login automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
Test while in safe mode. Same problem?
After testing, reboot as usual (not in safe mode) and verify that you still have the problem. Post the results of the test.

Tried to update Mac book pro to maverick now system will not boot

I downloaded the maverick update but something happened during the update and now my Mac book pro will not boot into the os. What should I do?

Please read this whole message before doing anything.
This procedure is a diagnostic test. It’s unlikely to solve your problem. Don’t be disappointed when you find that nothing has changed after you complete it.
The purpose of the test is to determine whether the problem is caused by third-party software that loads automatically at startup or login, by a peripheral device, by a font conflict, or by corruption of the file system or of certain system caches.
Disconnect all wired peripherals except those needed for the test, and remove all aftermarket expansion cards. Boot in safe mode and log in to the account with the problem. Note: If FileVault is enabled on some models, or if a firmware password is set, or if the boot volume is a software RAID, you can’t do this. Ask for further instructions.
Safe mode is much slower to boot and run than normal, with limited graphics performance, and some things won’t work at all, including sound output and Wi-Fi on certain models. The next normal boot may also be somewhat slow.
The login screen appears even if you usually login automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
Test while in safe mode. Same problem? After testing, reboot as usual (i.e., not in safe mode) and verify that you still have the problem. Post the results of the test.

TS140 not booting in RAID

Hi all,
This is my first post as I recently purchased a TS410 to replace a HP N40L.
I have installed 5x 3TB drives and booted up no problem. I have followed the RAID guide but when i change the 'Configure Sata' to RAID, save and reboot the sever will not boot. I get a black screen with no error messages at all. The only way i can get back into the BIOS is if i clear the CMOS.
I have followed the instructions at
https://forums.lenovo.com/t5/ThinkServer-Towers/TS140-RAID-no-ROM-configuration-utility-on-boot/m-p/...
but still no luck, this guide says to use UEFI only and i've also tried Legacy only but still the same problem.
What am i doing wrong?

I'm getting a non-raid disk error at boot on both raid drives. Will not fully boot into ubuntu. Can I disable raid and get in?

I1300 1171-9XU will not boot off battery

I'm having a weird problem with my usually reliable i1300. It will not run off any battery at all. I have 2 fairly new replacement batteries that have worked really well in this laptop. Here are the symptoms.
Seems to draw juice while the unit is off, battery discharge level is down after it's been off a couple of days
Will charge the batteries back up to 100%
Laptop immediately shut off when power is pulled.
Will not boot off the battery at all.
The IBM notebook utility will not refresh the batteries
When the power cable is pulled and you try to start it you hear this faint pulsating clicking noise. The batteries work in another i1300 laptop normally and the notebook utility works fine.
I have some spare parts for the I1300 but I'm not sure what to replace at this moment.
Thanks for any help,
Blank Sheet
Message Edited by blanksheet on 03-13-2008 11:18 AM
Message Edited by blanksheet on 03-13-2008 07:55 PM
Message Edited by blanksheet on 03-13-2008 07:57 PM

Thanks for the reply,
I started with the easy fixes first, changed the sata cables, and tried different power supply connectors. Both tests had same results, still boots up on 2nd try. I did not know how soon the problem would re-occur after it has been shut down, my shortest time so far is 25 minutes.
Quote
Why only one RAID channel is enabled? Array can't be detected in that way...
Well right now, it is not even set up that way, in my #6 problem solving, it was suggested that I turn the Raid Mode off and try [IDE] to see if that made a difference,"because I don't need Raid enabled for the hardware raid". It did not, it only booted to the "Reboot and select proper boot device or insert boot media in selected boot device and press a key" window about 60 seconds faster. It is currently set up in this way.
This is how it looks in my On-Chip ATA Devices
How do I check this?
Quote
Does the problem persist when you use Silicon RAID instead Nvidia RAID?
I am still working on getting the seagate diagnostics to work, I am getting an error message before I can even test them.
I do have another question. Why is my HP Printer showing up in the Hard drive test, and also why is it showing up in my boot sequence, is this normal?
And speaking of boot sequences I got in there again just now and saw 2 [USB:HP Photosm]
Thanks again, still working on testing hard drives.
Chris

Mac will not boot up, white screen with turning gear for hours on end

mac will not boot up, white screen with turning gear for hours on end

Take each of these steps that you haven't already tried. Stop when the problem is resolved.
Step 1
The first step in dealing with a boot failure is to secure your 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 your last backup, you can skip this step.
There are several ways to back up a Mac that is unable to boot. You need an external hard drive to hold the backup data.
a. Boot into 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.”
b. If you have access to a working Mac, and both it and the non-working Mac have FireWire or Thunderbolt ports, boot 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.
c. 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. The easiest way to deal with the problem is to boot from an external drive, or else to use either of the techniques in Steps 1b and 1c 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 boot failure can be resolved by resetting the NVRAM.
Step 4
If you use a wireless keyboard, trackpad, or mouse, replace or recharge the batteries. The battery level shown in the Bluetooth menu item may not be accurate.
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 boot, and remove all aftermarket expansion cards. Use a different keyboard and/or mouse, if those devices are wired. If you can boot 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 booted from an external storage device, make sure that your internal boot volume is selected in the Startup Disk pane of System Preferences.
Boot in safe mode. Note: If FileVault is enabled, or if a firmware password is set, or if the boot volume is a software RAID, you can’t do this. Post for further instructions.
Safe mode is much slower to boot 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 your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
When you boot 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, your boot volume is corrupt and the drive is probably malfunctioning. In that case, go to Step 6.
If you can boot and log in now, empty the Trash, and then open the Finder Info window on your boot 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 reboot as usual (i.e., not in safe mode.)
If the boot 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 your 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 reboot as usual.
Step 9
Reinstall the OS. If your Mac was upgraded from an older version of OS X, you’ll need the Apple ID and password you used to upgrade.
Step 10
Repeat Step 9, but this time erase the boot volume in Disk Utility before installing. The system should automatically reboot into the Setup Assistant. Follow the prompts to transfer your data from a Time Machine or other backup.
Step 11
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 boot 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 12
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.

Yoga Tablet 2 Windows 8 will not boot up, stuck at a flickering screen

I was installing Lenovo's firmware updates from their page for my device and in the middle of installing the BYT Platform Drivers for Windows 8.1, the tablet started went black. Then it went into some kind of flickering screen like it was trying to turn on and off. I left it alone and the next morning it was working fine. But when I came back in the evening, it was completely turned off again. I tried to turn it on, got the Lenovo logo, then it went into flickering on/off again. It still will not boot up. Any suggestions?? Help!

"The drive where Windows is installed is locked. Unlock the drive and try again."
Background:
First encountered on Restore of backup image (ATI-WD) on RAID 0 Two drive [SSD] array
Fixed: Using WINDOWS 7 Installation Disc - Repair Option
Comment:
During many WIN 8/WIN 7 installations on 4 different drives (on my own computer) MULTIBOOT (up to 7 O/S's) with BACKUP/RESTORE operations - WINDOWS 8 Installation Disk Repair has NEVER solved a startup problem
MICROSOFT should be ashamed that a feature that WORKED with WIN 7 was not brought forward to WIN 8 Installation Disk. Those that don't have one, borrow one (Using repair should not infringe any rules)
My Hobby is installing O/S's:
One drive has WIN 8.1 PRO Preview, WIN 8 PRO, WIN 8 Release Preview-64, WIN 8 Release Preview-32, WIN 8 Consumer Preview- 64, WIN 7 - 32, WIN XP - 32 [EasyBCD ver 2.2 essential]
You need to be an enthusiast to install XP with SATA AHCI (Slipstream SP3, load AHCI driver on install)
Happy computing, WIN 8 Great, WIN 8.1 definitely worth having
Additional Note:
With WIN 8 PRO and WIN 8.1 Preview Installation Disks, one is presented with:
Repair Computer/Troubleshoot/Select OS to repair (Forced to repair one O/S at a time)
Result: Diagnosing your PC/Attempting Repairs - Where it hangs with dotty circle, going nowhere... [Requiring switch OFF - no ctrl+alt+del
With the WINDOWS 7 Installation Disk - All partition entries are Recovered (Except XP) in one operation and quickly
Repeat: What are M'soft thinking and doing about this anomaly?

MacBook Air will not boot. Error Message says "Your Computer restarted because of a problem."

MacBook Air will not boot. Error Message says "Your Computer restarted because of a problem."

If you can't start up and log in in the usual way, try in safe mode.
During startup, you’ll see a progress bar, and then the login screen, which appears even if you normally log in automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
Log in as an administrator to carry out these instructions. If you have only one account, you are the administrator.
If you don't see any reports listed, but you know there was a panic, you may have chosen Diagnostic and Usage Messages from the log list. Choose DIAGNOSTIC AND USAGE INFORMATION instead.
Safe mode is slower than normal, and some things won’t work at all.
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 start in safe mode.
If you're able to log in, launch the Console application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad and start typing the name.
In the Console window, select
DIAGNOSTIC AND USAGE INFORMATION ▹ System Diagnostic Reports
(not Diagnostic and Usage Messages) from the log list on the left. If you don't see that list, select
View ▹ Show Log List
from the menu bar.
There is a disclosure triangle to the left of the list item. If the triangle is pointing to the right, click it so that it points down. You'll see a list of reports. A panic report has a name that begins with "Kernel" and ends in ".panic". Select the most recent one. The contents of the report will appear on the right. Use copy and paste to post the entire contents—the text, not a screenshot.
I know the report is long, maybe several hundred lines. Please post all of it anyway.
If you don't see any reports listed, but you know there was a panic, you may have chosen Diagnostic and Usage Messages from the log list. Choose DIAGNOSTIC AND USAGE INFORMATION instead.
In the interest of privacy, I suggest that, before posting, you edit out the “Anonymous UUID,” a long string of letters, numbers, and dashes in the header of the report, if it’s present (it may not be.)
Please don’t post other kinds of diagnostic report.

K9N4 SLI-F Posts But will not boot past F8 Menu.

Rig consists of: K9N4 SLI-F Motherboard
K-Byte - (4) 1 GIG Sticks Ram 667mhz
9600 GT OC (512)
1 Nec DvD Burner
1 HP CD Burner
1 Maxtor 250 GiG PATA Boot Drive
1 Seagate 300 GiG PATA Slave Drive
2 Seagate 120 GIG SATA Drives - not Raided
1 Soundblaster Live Audio Cards w/Boston Acoustics
powered Satellite Spkers and SWfer
1 430 Watt P.S. (NEW)
K9N4 SLI-F Posts But will not boot past F8 Menu; when Safe Mode pressed, will not make it through initial scroll (and last file changes). Does this have anything to do with windows and the three update mess???

Quote from: Bville on 15-March-08, 08:55:37
Yes, This is a New Build, though Windows XP is already on the Hard Drive From a Previous Build. I Had a K8N Neo Platinum Motherboard with ATHLON64 3400. MB caught the hiccups and I changed everything out. So My Hard Drives have to be reloaded but not wiped??
Yes, that is necessary. Also leave only one HDD temporary where you planing to install your OS, when installation is done then attach your other HDD(s).
"So My Hard Drives have to be reloaded but not wiped?"
No need to be wiped, only Windows re-installation.

2009 Mac Pro will not boot up under Windows

I have an Early 2009 Mac Pro system (Mac Pro 4,1) and I've had this system for 3 years already and have been working under OS X with this system ever since I purchased it.
However, when I tried to boot off my Windows disk, something very interesting happens. The Mac Pro WILL NOT boot up off the Windows disk or a known working Windows partition if two monitors are connected. Upon holding down the option key and selecting the Windows partition, I will get a black screen on one monitor (the one connected via Mini Displayport) and the other screen receives no signal and will enter standby and the system is halted. It does not respond to keystrokes, there is no hard drive activity, no measured power increase on the UPS, no apparent network activity, nothing. The only way to exit this scenario (from what I can tell) is to power off the machine, disconnect the display on DVI, power on the machine again, select the Windows partition wait for the system to reach the login window and reconnect the DVI monitor (at which time Windows recognizes it immediately and the system works fine again).
My question to the community is, does anybody know why this is happening and is there a known fix for this? Quite frankly, having to disconnect a monitor just to restart is very tedious and frustrating.
I have two Samsung P2350 monitors attached to an ATI Radeon HD 4870 (512MB, from Apple). One is monitor is connected via directly DVI and the other is using a Mini Displayport to DVI adapter. Both monitors work fine under OS X with no issue. At first, I thought that this may be a driver issue on the Windows side and after installing all the latest updates and drivers the issue is still apparent. From what I can tell, this doesn't seem like a software issue but rather a firmware or EFI issue as this happens before Windows even loads.
If anyone knows of a fix or what to do in this situation, or if you are also having this issue, I would love to hear your input!
Thank you!
For the record, I am running all the latest software builds on the OS X side (10.7.4, not that it would really matter at this point). I have also disconnected all unnecessary equipment in a trial and error scenario but the results are still the same.
The system passes all ASD testing.
The full specification of the computer and all connected equipment are as follows:
2009 Mac Pro (4,1) 8-Core
2x Intel Xeon Nehalem 2.66GHz Quad-Core CPUs
16GB DDR3 ECC 1066MHz RAM (Apple Branded)
Two OWC 120GB SSDs (One for OS X, the other for Windows 7 x64) - These are in place of my optical drives.
4x 2TB WD Black Hard drives for storage.
Two Samsung P2350 Monitors connected via DVI. (One using a Mini Displayport to DVI adapter).

In Windows I am using the latest (12.4) Catalyst Software Suite, 64 bit of course, downloaded directly from AMD's site after installing the drivers from Boot Camp.
As for installing Windows I used an original (not burned) installation media (Disk is in a pristine condition). And yes, Windows is fine, the problem just seems to be getting the system to boot up Windows with that second monitor. However if the "problem monitor" is disconnected the system boots fine 100% of the time and connecting it later after booting the system will still operate properly.
For the sake of arguement I swapped monitor cables and connected the "second" monitor to the mini displayport adapter to verify that it wasn't a cabling issue and I'm still yielding the same issues.
As for GPU testing, I've played games (Crysis, Grand Theft Auto IV, Battlefield 3, etc.) and I've had no issues with the card or stability.
You would think that Apple would try to find a fix for this, especially considering the caliber of this machine.

Will not boot in RAID 0

Similar Messages

Maybe you are looking for