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?

Similar Messages

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

Can not boot from a RAID 5 volume

Dear Friends,
I have a Mac Pro (3 GHZ) with RAID that will not boot off of a RAID 5 volume. Here's the details:
The unit has 4 768 GB drives that I have made into one RAID 5 set. After that I broke it down into 2 two volumes one for OS (200 GB) and one for storage (the balance of the RAID). After that I copied a known good image to the OS volume.
The Start-up disk utility on the DVD sees the OS but when I boot it sits for a long time and eventually gives me what Apple calls the prohibited icon; a circle with a line-through it like Ghostbusters.
The patron table is good, and I have done this on another Mac Pro. I have tried to rebuild the RAID a few times with no luck. Ideas would be appreciated. Thanks!

My guess is that the Mac OS X system is damaged. You may need to use the Sysytem CD to perform an archive and install.
For those interested in bootable RAID cards on the Mac Pro, the Areca is the only non-Apple solution that I have found with this capability. You can read more about it here:
http://www.amug.org/amug-web/html/amug/reviews/articles/areca/1221x/
Have fun!

Sata Raid with spare drive not booting?

Hi Peeps,
Been reading throught this forum and founds loads of good tips already, however, I still can't find the answer to my problem.
Just setup 2 new Maxtor (250gb) drives as Raid 0, made them bootable and installed Windows XP SP2. All works fine and dandy. I have tried to install my 3rd Maxtor 250gb drive as a spare on port 3 or 4 but it won't boot saying something about the drive config.
I have disabled Sata 3 & 4 in the bios, changed the boot order (Raid first, Channel 3 last) but no joy.
What the hell am I doing wrong or is it not possible to do?
BTW: If I change the boot order so the single Sata drive is first, it will boot into my drive but not able to see the raid disks!!
Thanks for any help you can give
Tigger
Spec:
AMD Athlon 64 +4000GHz
MSI K8N Neo4 Platinum (Socket 939)
2 x 1gb Ebuyer RAM
3 x 250GB Maxtor Diamondmax 10 (Sata 150)
48x DVDRW
48x DVD
550wat PSU
256MB Radeon 850XT Pro,
Bios 0.3a (Latest)
Samsung 19" Syncmaster 930BF

Tigger I haven't seen anyone post this issue on a non-SLI Neo4. Is the spare disk setup as a spanning drive(JBOD)? See my posts here in might fix your problem:
https://forum-en.msi.com/index.php?topic=98437.0
Loopy, I don't know much about the Neo Plat regular, you could try the above also, but I'm not sure you have the same problem as Tigger.

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

Upgrading to maverick not booting

Hi,
I have a mac pro 4.1 and I am trying to upgrade to maverick, it is nor working,
I have a drive with a maverick osx working already on another mac 4.1 with an Atti,
I tried this drive on my other mac pro with an Nvidia quadro 4000 and it does not boot the wheel stays spining,
I have tried cloning my hard drive and upgrading from 10.8.2 (this is woring on my mac) to 10.8.3 combo
the same thing happens the wheel stays spining after rebooting and it does not start
I have no Pci cards on my mac,
I have tried with 1Gb Ram , with 2 Gb Ram , with 4 GB Ram nothing is wortking
any help?
thanks
Ariana

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.

P45 Platinum will not boot Server 2008 with 2x2GB...

I was working through the night last night to get my new rig built and installed with the new SP2 of Server 2008 and was having problems that seem to point to the mobo not liking the optimized settings for my 2x2GB. Hopefully my signature has all the system specs necessary - but do ask if I've left anything out.
What I did:
- Built system with minimal HW:
CPU & cooler, PSU, 2x2GB (slots 1 & 3), GeForce 8600, 2x250GB SATA2 HDs (ports 7 & 8 for JMicron) , 1xSATA2 DVD-RW
- Got POST and configured BIOS:
Load optimized defaults, reset time.
- Added Rest of HW, got POST and configured RAID:
- Integrated Peripherals - RAID Mode: RAID
- Integrated Peripherals - On-Chip ATA Devices - RAID Mode: IDE
- Save & Exit
- CTRL-J: Built 2x250GB JMicron RAID
- Boot to Server 2008 install DVD
- Loaded RAID driver and installed to RAID
- Installation continued (at a wonderfully fast pace), until it hung about 90% through
- Tried re-installing several times, trying things like reconfiguring RAID, using different drivers, etc.
- Then I removed the 2nd RAM in DIMM 3, and re-install completed without a hitch.
- Booted from RAID, configured Server 2008.
- Installed drivers for Intel P45 Chipset, GeForce 8600, Ethernet, and Audio
- Retried having 2 x 2GB in DIMM 1 & 3, and reboot hung during Server 2008 loading bar
- Tried DIMM in 2 & 4 with same results. Again, system POSTs with no problem, seeing all 4GB. But OS hangs on load.
- Ran MemTest on each RAM separately, with no problems after an hour each.
- Put the 1 RAM back in DIMM 1 and used LiveUpdate to successfully Flash BIOS from v1.2 to v1.6
- Reconfigured BIOS (optimized defaults and JMicron RAID)
- Rebooted to Server 2008 successfully with only 1 RAM in DIMM 1
- Tried DIMM in 1 & 3 and 2 & 4, and again hung on OS load.
- With only 1 RAM installed, the OS flies. I did lots of application and utility experimentation to ensure all was functional and stable. Even Defraged the RAID, so I'm pretty sure no HDD problem.
Based on all the forum posts I've read, I'm not sure about why it POSTS but doesn't load the OS, but I bet it has something to do with the mobo being unstable with the default settings for this RAM. Seems too bad as I tried to pick a decent RAM for future OC potential.
Out of fairness, I should point out that I have not yet tried blowing away the OS and reinstalling with my only other option - XP Pro SP3 - and seeing how that fairs. My guess is that it too will be unstable.
Fortunately, I'm still having fun tinkering - so no real frustration to speak of. But any advice on what to do next would be much appreciated...

Finally, in response to RemusM's request, here's the CPU-Z info for Memory, SPD and CPU using the Optimized Default BIOS settings and 1x2GB in DIMM 1:
Then, I spent a late night last night browsing the forums and searching the web. I found a dude with the same mobo, memory and an E8400. He was having similar problems and listed some recommended BIOS Cell settings. I put in my 2x2GB, removed the HW OC FSB jumpers on the mobo and entered the following settings into BIOS Cell and gave it a try:
Multi-Step OC Booster: Mode1
DOT Control: Disabled
Intel EIST: Enabled
Intel C-STATE Tech: Disabled
Adjust CPU FSB Freq: 400
Advancd DRAM Config: (all Auto)
Enhance Settings: Auto
NB Drive Configure: Auto
FSB/DRAM Ratio: 1:1.00 (1333:667)
Clock Gen Tuner: (all Auto)
Adj PCI Freq: Default
Auto Disable DRAM/PCI Freq: Enabled
CPU Voltage - ICH Voltage: (all Auto)
Spread Spectrum: Disabled
Not only did now my system now boot successfully into the OS for the first time with 2x2GB installed, but it seemed stable through my OS config and application installs. What's more, for the cost of taking the DRAM down to 800MHz, I now had the CPU at 3.8GHz!
Here's the new CPU-Z results:
What's next:
- I need to further test stability by downloading and running some decent benchmarks of some type
- I'd love to get some advice on how I could further tune the above settings for increased stability and even better performance, as the memory and CPU seem capable of more if the mobo is...
Thank you for the input and attention so far. Please keep it coming...

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.

New system does not boot properly

I just set up a new system with:
a MS-6728 Neo2 FIS2R Mobo,
1gb Geil PC-3500 RAM (2x512),
2.6C proc.
2 Maxtor 120gb IDE drives RAID 0 with the onboard promise controller.
Lite-On DVD burner
ATI radeon 9800 video card
Enermax 300 watt power supply with:
3.3v - 28amp
5v - 30amp
12v 22amp
170watt total 3.3/5 combined
My problem is that my system NEVER boots up normally. It always freezes in the bios startup. The D-bracket stops at almost every possible combination of led's, which according to the manual the problems were: Testing RTC, Initialize Video interface, Testing memory, Initializing floppy controller, Memory detection, Decompressing bios to ram, possibly more. Sometimes I also just get beeping, either a continuous beep or 8 beeps. A few times it would display the bios startup screen, but halfway down would be gibberish characters and would be locked up. When I then turn the computer off then on again, the bios is reset at least somewhat(i know because I usually disable the full screen image on startup) and says memory timings are too tight, and I have the choice to enter bios or hit any key to automatically fix things. If I hit any key it will boot up ok. However when I restart/turn off the computer, the next time it again does not boot. I tried upping the ram voltages from 2.5-2.9v, and that seems to stay that way in the bios, even when it resets itself. Everything else is set to auto/slow. If I try to manually adjust the memory timings, even to the slowest possible settings, it does not boot, and I must turn it on/off a few times till the bios resets again, with the boot process stopping at one of the possiblilitys mentioned above. Using the info tab on speedfan, I got the memory info, and it displayed the voltage at 2.5v, not sure what that means but it is strange.
What I have already attempted:
I sent back the ram and got a new set, which hasn't changed anything. The first time the other ram failed memtest, this time it passed(for about 2 hrs). So I don't think its the ram.
I borrowed an antec truepower 430w powersupply, which had no effect.
I went back to bios version 1.3 from 1.9, which also seems to have no effect.
I was hoping to overclock the system a bit and enable performance mode etc etc, but now I'll be happy to just not have to go through a song and dance everytime I restart the computer. This is only the second computer I have built from scratch, and the first with raid, but that seemed to all go ok. Please help me diagnose the problem!

I too am having problems with my system.
865PE Neo2-FIS2R
2 Maxtor 120GB S-ATA drives, RAID 0, Promise
2 512MB Geil Ultra CL2-3-3-6
HP CD-RW
What IDE settings are you using?
E.g...Native? P-ATA Only...all of those settings
For me...sometimes XP will install and boot...but eventually system is unstable and XP crashes and corrupts itself...Event Manager errors different each time
Someone mentioned problems with Maxtor and AMI BIOS...anything I should keep in mind?
Sorry about all the different questions. I'm sure exactly where my problem lies. MSI thinks it may be my memory AND/OR on-board IDE controller since I can't get the on-board Intel RAID setup to consistently "see" and setup my RAID drives...even when it has worked...XP doesn't like the Intel configured RAID drives. Also tried just one S-ATA drive through on-board Intel and Promise. Next I will try a plain old IDE Hard Drive...no S-ATA...and make sure my memory passes memtest86+ testing.
Any other gems you can offer for this config??? Thanks.

HT4790 My Mac OS Lion 10.7 FileVaulted HD does not boot, prohibitory sign, stop sign appears some minutes after boot starts. Disk Utility repair shows four error messages: Unable to bootstrap transaction group 2517: inconsistent crosscheck (the same with

My Mac OS Lion 10.7 FileVaulted HD does not boot, prohibitory sign, stop sign appears some minutes after boot starts. Disk Utility repair shows four error messages:
Unable to bootstrap transaction group 2517: inconsistent crosscheck
No valid commit checkpoint found
The volume xxxxxxxxxxxxxx(here it shows physical volume number) was found corrupt and can not be repaired.
Problems were encountered during repair of the partition map
Error: Storage system verify or repair failed.
(the same with 2518, 2519 and 2520 transaction group)
I suppose it is serious bug in Mac OS Lion managing FileVault and wonder what the help could be?

Most likely culprit is your Lacie drives which are notorious for flaky power supplies which cause just the sort of erratic behaviour that you describe. Have had similar issues myself. Lacie has been good about replacing my power converter-- twice. If you have seven of them, good luck finding the bad one or more. Like I said, the behaviour is erratic. Sometimes it'll work sometimes not. I can't comment on Samsung drives because I've never used them and have never heard anything about them. Same with Softraid. Why not just use Disk Utility. Sounds like you're ready for an external hardware raid. This will be much faster, much more reliable, and may even be cheaper than seven firewire drives. Check out G Tech, and Maxx Digital for starters.
Best of luck
Terry

TS140 not booting in RAID

Similar Messages

Maybe you are looking for