Solaric boot up problem after poweroff

Hi Everybody,
I have a solaris 10 8/07 installation on X86. I have problem regarding boot up after power off. Its not booting in multiuser mode and hangs up at the blue screen. Could we do something in the single user mode to rectify the problem, because its possible to boot in single user mode?
Thanks.

Please include your full model number when posting problems on the forums. It can be found on the bottom of your laptop.
If it's now working perfectly, then I wouldn't worry about it if I were you. However, I can say that it's best to do a system recovery with the exact media designed for your notebook and then upgrade if you wish.
- Peter

Similar Messages

Boot up problems after latest Security Update

I just arrived home after a three day vacation, and I booted up my Power Mac G4 running Tiger 10.4.11. Software Update immediately notified me of a Security Update, which I okayed. After restart, my screen showed the grey Apple logo for a bit, then went right to a grey circle with a slash through it. I restarted the machine with my Tiger Install disk and ran Disk Utility, and then ran through the Repair Disk Permissions and Repair Disk utilities, with no abnormalities noted. It'll boot into OS 9 just fine, but when I restart while hold down the Option key for Startup Disk select, then select the Mac OS X disk (I have two hard drives on my machine), it shows me the Circle/Slash icon again as before. What gives? everything was working fine until this blasted Security Update (I believe it was the 2008-004 update).
I just recently upgraded my Mac OS X volume with a 500GB hard drive and a controller card, as my previous drive failed. Did something get messed up with that setup after this update?

I don't know whether other users would make any difference, as I don't even get to the User Select screen yet- would changing my password really have any effect?
Safe Boot will bring up the Login window if it gets that far.
Not sure if the PW change would help, best to wait on that 'till after all else fails.
PS. I only use Software Update to see what is needed, then get them for real via...
http://www.apple.com/support/downloads/
That way I can wait a week or so, check the forums for potential problems, and get Permissions & such in order before installing.

Windows XP/Solaris 10/laptop - Problem after to install recomended patches

Hi,
I have a Toshiba laptop with a HDD 40GB. Tow partitions: 20GB for Windows XP and 20GB for Solaris 10 3/05.
1.- Windows was installes first, later with a boot linux CD I use fdisk to resize the disk and create a new partition to install Solaris 10.
2. I installed Solaris 10 perfectly and I worked for more than 1 year this way.
3.- When I turn on the laptop a menu show me and let me choose from where to boot, Windows XP or Solaris.
4.- Now, I got the Solaris 10 Recomended bundle of patches from EIS-DVD (may302006) and I decide to update Solaris 10. I loged into Solaris 10 and in Single user applied the recomended bundle of patches. It become with the new boot loader GRUB and this just let me start Solaris.
5.- format sees the disk with 20GB for solaris and from fdisk utility I could see the Windows XP partition and the Solaris 10 partition as Active.
6.- I setted the Windows partition (1) as Active and reboot the system.
7.- Now I cannot get anything. The laptop turn on and no display is show, nothing.
Someone of you can helpme with this?
Thank you for comments and experience.
spersant

Well, I found a doc #73412 where teach how to enable Windows XP partition with boot loader GRUB.
But my problem is my laptop don't start because the active partition defined with fdisk from Solaris, doesn't have the Master Boot Record and don't show anything on the screen. I am trying to get access through the function keys, but I cannot.
Any suggestion??
spersant

Boot up problems after power spike

Hi all:
My MSI computer was running along fine until last Sunday. On a clear day, a power surge came threw and my computer was in the middle of backing up to a usb remote hard drive.
Now, the computer only will boot if I disconnect the hard drive and then reconnect it. If I don't do this, the bios hangs and never reaches the windows load process. The hard drive makes a repetitive "eee" sound as well.
Hard Drive damaged or crashing? Why does it work when I disconnect the hard drive and reconnect it?
Any suggestions?
Thanks in advance,
Civitas

You run Vista? And it is the USB hard disk that makes a fuzz, right?
However, I think there might be something else the matter with your system. If it was a power surge it would hit more than an external USB thing.
Pull power plug out. Disconnect external things, mostly at the rear of the case of course, but also the USB disk. Hit the power button a couple of times. Then clear CMOS. Reattach things and power up again.

A lot of problems after installing Windows XP using Boot Camp on a Mac Book

I have been having a lot of problems after installing Windows XP Home Edition (2002).
For one, after installing Windows using Boot Camp with Mac OS X 10.5.1, I opened Windows on my Mac Book, inserted the Mac OS X Disk 1 as in the instructions and got the message: +"This package requires a newer version of the Windows installer. Do you want to update the version of the Windows Installer on your system?"+ When I clicked Yes (I had NO idea what it meant at the time), I got the message: "The required resource 'UPDATE' is missing" and the Installer quit.
How do I fix this problem?
Another problem I have is that there is no sound on the Windows XP, yet it works perfectly on Mac OS X. Is there any way to fix this problem?
A third problem I have is that I can't wirelessly connect to the internet using Window XP, yet I can on Mac OS X. I have no idea on how to fix this, and it's really messing with me. D:<
D: There are way too many problems, and I have a feeling there will be a lot more later on. Help....
~Twilight

---I'm moving this topic to the Boot Camp forums.
-Twilight

Mac Pro Boot Problems After 10.6.2 Update

After installing the latest version of snow leopard I am now having boot problems on my mac pro.
Symptoms;
-Screen resolution is incorrect at apple splash screen.
-Takes a lot longer than usual to boot.
-Once booted the blue tooth magic mouse isn't imediately reckonised, takes a while to find that.
-Once the mouse is finally reckonised it can move around but can't click on anything or bring up the dock. Tried a wired mouse, had the same problem.
-The keyboard is also not appearing to do anything, none of the shortcuts or quick keys work..
Had exactly the same problem after 3 restarts but on the 4th after leaving it for a good 20-30minutes it setled down and everything was working okay. However this is a recurring problem as I had the same thing yesterday...
I have a my 10.5.8 system backed up on an external so I am running from that at the moment. Don't want to go back to snowy til these problems are solved.
Any help will be greatly appreciated!
Martin

Try Safe Mode (It will take more time to startup in Safe Mode because it runs a directory check.)
Let us know.
-mj

CMOS/Boot Problems after BIOS Update

I just used Live Update (two weeks ago) to update to all the latest utilities, drivers and BIOS on the following computer:
MSI 865PE Neo2-FIS2R
Pentium 4 2.4ghz / 800mhz / HT
512mb PC3200 (1 DIMM)
ATI Radeon 9600 128mb 8xAGP
Two WD 120GB/7200RPM ATA Harddrives - mirrored
FSP350-60PN Power Supply
Pinnacle PCTV PCI Card
Windows XP Pro - fully updated
The boot up screen now identifies BIOS as A6728 IMS V2.2 051904.
Since the update, the computer does not allow the operating systyem to shut it down - and the boot up process has been problematic (to say the least).
After the BIOS update, I set the BIOS settings to "performance defaults" - and everything seemed fine for awhile.
But then the boot up problems started - and I was once confronted with the message that "dram timing was too tight".
I reverted the bois settings to "default" - to no avail. The problems are continuing - and I am getting somewhat fearful that the system will not boot at all pretty soon.
After about 20 power on/off cycles where I got nothing but a blank screen, the system is now booted to a screen that is telling me that the CMOS settings are incorrect - and I have the options to run setup or load defaults and continue.
I know that I want to run setup, but what do I do to get this to stop happening?
Tahnks,
Bob99

As is usual, at least one mistake is made when building a PC. Rather than getting name-brand memory, in a moment of weakness, I ordered the generic stuff:
http://www.mwave.com/mwave/viewspec.hmx?scriteria=BA08583
I looked for documentation on RAM voltage, and found the MSI information on the MOBO product page:
Due to the High Performance Memory design, motherboards or system configurations may or may not operate smoothly at the JEDEC (Joint Electron Device Engineering Council) standard settings (BIOS Default on the motherboard) such as DDR voltage, memory speeds and memory timing. Please confirm and adjust your memory setting in the BIOS accordingly for better system stability.
Example: Kingston HyperX DDR500 PC4000 operates at 2.65V, 3-4-4-8, CL=3.
For more information about specification of high performance memory modules, please check with your Memory Manufactures for more details.
I also saw a couple of articles that said to be "very careful" with this setting as you can fry your memory. But I haven't found anything to help me learn about what the settings mean - or where I should start (2.65?).
Should I call Mwave and as them for the specs?
BTW - The computer is my son's - and he is moving back to college. I was giving it a tune up (driver's, etc.) - and noticed the ATI issue. Since I won't see it for 9-10 months and who knows what he will want to add to it, I thought it would be a good idea. I am a previous user of ASUS and my experience with them is that it takes about a year of BIOS updates to actually stabilize all the features.
Thanks for your help...
Bob

Boot up problems into Vista via Bootcamp after changing monitor (to Formac)

Doesn't seem to be general hardware support subsection for Bootcamp forum, I guess this seems like next best place
I am running Windows Vista Business 32 bit via bootcamp on Leopard 10.5.1 on a Mac Pro with 3Gb RAM and with the two systems installed on separate 250Mb hard drives. My GPU is an ATI 1900 512Mb card
Up until now I have used an LG 1920P 19" LCD monitor with this setup, which has been recognised perfectly well by both Leopard and Vista.
I purchased a Formac Gallery 1900 19" LCD in the January sales and now have that connected as main monitor. This works fine with Leopard however Vista has issues. Starting up with the alt key option, I get the MacOS/Windows disk choices come up as usual and select 'Windows' to get Vista, but then the screen goes black and into 'sleep' mode (pulsing front light). After a little time and some disk activity, the computer reboots itself into Leopard. Next time I do start Windows successfully it reports an unsuccessful startup last time.
I tried booting into Vista with the old LG monitor then hot-swapping DVI cables with the Formac, and the Formac is then driven perfectly well in Vista as a plug and play monitor (same as for the LG)
However if I connect both monitors, I can boot into Vista on the new Formac monitor (even if the LG is actually unplugged from the power socket but just connected to the DVI).
I'm very puzzled by this, quite enjoying dual monitors, but I'd still like to be able to boot to Vista using just the single Formac monitor alone. As it seems to be a 'boot-time' problem I suspect the problem may lie with Bootcamp. I tried installing the ATI Catalyst Control Centre in Vista and configuring displays there but it did not help.
Does anyone have any advice please ?

Bad cable? using same port on the X1900?
Display preferences on a SAFE BOOT and make sure that Vista knows about the new monitor? It can have trouble forgetting one and learning about the new monitor, which is "main" and which is "extended desktop" mode.
There have been problems with displays. Might want to look in the Mac Pro: Displays discussion, and bring it up there with other Mac Pro owners.

Solaris 8 installation problem on Dell PowerEdge 500SC

Hi,
I am having TWO PROBLEMS installing Solaris 8 on Dell PowerEdge 500SC.
This hardware spec is:
Pentium-III at 1GHz
256MB 133MHz ECC SDRAM
20GB 7200RPM ATA100 EIDE hard drive (on integrated ATA-100 controller)
48X EIDE CD-ROM drive (on integrated ATA-100 controller)
Motherboard: unknown
more details: http://www.dell.com/us/en/esg/topics/esg_pedge_sc_towermain_servers_3_pedge_500sc.htm
FIRST PROBLEM is the following message was shown at the hardware probe.
WARNING: ACPI Tables not in Reclaim Memory
Warning: Resource Conflict - both devices are added
NON-ACPI device: PNP0C01
Port: C00-C01, C06-C08, C14, C50-C52, C6C-C6F,
CD6-CD7
F50-F57
ACPI device: PNP0C01
Port 814-85B, 580-58F, C00-CD7, F50-F58
At this time, I was using "Solaris 8 (Intel Platform Edition) 10/01" released version.
I am not sure what this means, but it was RESOLVED with using newer "x86 DCA boot diskette (Patch-ID# 110930-05)".
But, the SECOND REAL PROBLEM is another one. It just happens booting the kernel after the hardware probe. I get the following messages about 2 minutes later, after beginning to load kernel.
WARNING:/pci@0,0/pci-ide@1/ata@1 (ata1): timeout: abort request, target=0 lun=0
WARNING:/pci@0,0/pci-ide@1/ata@1 (ata1): timeout: about device, target=0 lun=0
WARNING:/pci@0,0/pci-ide@1/ata@1 (ata1): timeout: reset target, target=0 lun=0
WARNING:/pci@0,0/pci-ide@1/ata@1 (ata1): timeout: reset bus, target=0 lun=0
After another 1 or 2 minutes I get more error and the system reboots.
Please give me any suggestion or advice!
Thanks.
Kazuyoshi

I've been having the exact same problems on a PowerEdge 500SC. I have managed to get Solaris up and running on the machine, however. I booted the DCA from the floppy disk and installed from the CD-ROM. When the DCA is ready to scan for devices I use the "Specific Scan" option to tell it to look for specific devices. I tell it to scan for all devices in the listing and in doing so the DCA finds ISA-based IDE controllers. After it provides a listing of the devices it found I use the "Device Tasks" option and the "View/Edit Devices" menu item then delete the Bus Mastering IDE controller device. Once the screen comes up to ask for a boot device, the drives will show up as on the ISA controllers.
I have to go through this process every time I boot the machine but I am able to make the system run at least.
I haven't figured out the ACPI problem, yet.
Regards,
Doug

Fresh install of solaris 10 x86 hangs after 'Configuring devices'

Hi All,
I just received a new SuperMicro server with an LSI MegaRAID SAS 9261-8i controller. While trying to install Solaris 10 it hangs after "Configuring devices". I checked the LSI page and Solaris 10 is supported according to them. Any ideas how to proceed?
Fairly new to Solaris on x86 hardware.
The system has a Xeon X5690 processor in an Intel Workstation Board S5520SC motherboard. The motherboard documents claim that not disabling usb 2.0 can hang an install. I have disabled the usb 2.0 in the bios but the system still hangs. Booting it with the -kd and -kv options don't give much information.
Any help is appreciated. I might be returning these machines if I can't get this worked out.
Cheers,
Steve
Edited by: 967729 on Oct 25, 2012 3:51 PM

See if you can add the verbose option "-v" to the kernel boot options. I think you can get to the GRUB menu off the Solaris 10 install disk. That should tell you what device is causing the hang, or at least the last device that worked.
Also, can you try Solaris 11 and see if it gets past that point? A few years ago I has a similar issue with Solaris 10 on a Dell server. Solaris 11/OpenSolaris worked fine, though. IIRC I could work around the issue if I disabled the 2nd CPU - Solaris 10 had a problem bringing up the 2nd CPU on that Dell's CPU/MB config.

Solaris boot images fail with bad magic number

hi guys, have had Solaris on boxes for allmost 10 years. I have never installed sol10, and I have a problem
1. I download the zip file, then use winrar to unzip them..
2. burt the image with nero 7
when my SunBlade 1000 comes up I do the Stop-A, and from the Ok promt
I do boot cdrom
this fails with "bad magic number" I have redown loaded it and reburnt it with nero reinstalled
and also changed out the DVD on SunBlade
3 I found a copy of Solaris 8 and the I got back a 'bitch' where is Solaris 9 so, most likely the drive is OK
HELP
Cris Harrison

Hello Cris,
unfortunately I don't understand your last sentence !
I found a copy of Solaris 8 and the I got back a '*****' where is Solaris 9 so, most likely the drive is OK
If this was a Solaris 8 (7/01 or later) DVD that did successfully boot, your DVD drive firmware (assuming that this is the Sun Toshiba SD-M1401) is up-to-date. If the DVD drive has firmware 1007, an update to 1009 is required to boot from DVD. otherwise you won't be able to boot from DVD (boot from CD works and a DVD can be automounted/mounted).
Partial output of probe-scsi
Before update:
Unit 0 Removable Read Only device TOSHIBA DVD-ROM SD-M14011007
After update:
Unit 0 Removable Read Only device TOSHIBA DVD-ROM SD-M14011009
[*Patch 111649-04 - Toshiba DVD 1401 firmware update*|http://sunsolve.sun.com/search/advsearch.do?collection=PATCH&type=collections&queryKey5=111649&toDocument=yes]
when my SunBlade 1000 comes up I do the Stop-A, and from the Ok promt ...
Instead of trying to directly boot, disable auto-boot and retry after a clean power-on.
Break with Stop-A
setenv auto-boot? false
reset-all
boot cdrom
Michael

Wifi problem after.4.3 update on xperia z

Hi all,
After updating my Xperia Z (C6603) to build number 10.4.1.B.0.101 I've been having connection issues with every Wi-Fi network.
I've checked the forum but I only found problems about people having Wi-Fi issues with their smartwatch, I do not own a smart watch this is just a general networking issues.
Here's the problem in detail:
When having no Wi-Fi switched on while booting the phone the phone will start without any issues, I will receive my 3G/4G signal and I can browse, e-mail, everything.
Once I switch on Wi-Fi it will start connecting to previously stored Wi-Fi access points but will not connect. Eventually it says that there was a problem with connecting, even though this will take several minutes.
I can go into the Wi-Fi settings, select a different Wi-Fi network (if it is in range) and press connect, however the settings app will freeze at that point and eventually I'll get a notification that the settings app has stopped working.
I have found a "work-around": I switch the Wi-Fi to on, power off the phone and power on again. Now the Wi-Fi connection immediately powers on without an issue once the phone has completely booted, it also will connect to the default Wi-Fi connection that is in range. A different issue appears however once I move out of Wi-Fi range, it will no longer pick up my 3G/4G signal. It is also impossible to switch off Wi-Fi or switch Wi-Fi network connections without rebooting the phone.
As I said before this happened to me after updating to version 10.4.1.B.0.101 after having it received through OTA update. I do not have root access on my phone either so this can't be it.
Is there anyone experiencing the same issues? Is this somehow related to the issues people are experiencing with their smart watch connections (as seen in this topic: http://talk.sonymobile.com/t5/Software-Updates/wifi-problem-after-4-3-update-on-xperia-z/td-p/490591...
If there's anyone who is experiencing the same issues, or has found a fix for this I'd gladly hear from you.
Regards,
Danny
Sony Xperia Z
Modelnumber: C6603
Android version: 4.3
Kernal version: 3.4.0-ge09aff8
Build number: 10.4.1.B.0.101

I faced the same problem. So what u did now to connect your 3g or 4g. Did u tried kitkat update? Its works or not?

Another major problem after 10.4.8 update

Hi everyone,
I've never had any major problem with any Mac OS update yet until I had the crazy idea to install the 10.4.8 update last week. I wish I would have never done this. This is also the first time I wish I had Windows since I can't remember such a big screw up with any Windows update I've seen.
But back to the problem, after the installation on my old 12" Powerbook (1.33GHz with an additional 1GB of RAM) the system got really slow. The harddisk was accessed all the time, so after reading some forums people said that Spotlight would run a re-index of the database which made sense to me. So I just let it run over night and the next day the permanent HDD access was gone, but whenever I tried to access a folder it took ages (HDD access again...). So I decided to reboot which took about 20 minutes until the desktop fully showed up and was useable. Again, I had HDD access all the time. After two hours or so it stopped again, but as soon as I clicked on something, for example a folder, it started again. At that point the Powerbook was simply not useable anymore because I couldn't even start a program.
So I start browsing through several forums and many people suggested to re-install the 10.4.8 combo update again. That's what I tried, after a while I could only hear the HDD access running and running. The installer said 29 minutes left and progress bar didn't move any further. I had it running for over a hour like that. I couldn't abort it, I could start no other software, nothing. It still showed 29 minutes and the HDD was accessed all the time.
So I restarted the Powerbook since this obviously wasn't going anywhere. Apple logo came up, the little gear spinning thing as well and of course I could hear the HDD being accessed. After two hours of doing this I aborted and decided to boot into safe mode to install the combo update. Again, same situation. HDD running like crazy and Apple logo, but no login screen coming up.
So I decided to boot from the Install disk and have the disc utility check the HDD... but of course after selecting the language and clicking continue at the screen when the HDD first shows up it starts to access the HDD... I can't select the HDD, I can't even get to the DU, nothing. It's been running like that for hours now. It seems like whenever the HDD is involved in something the accessing starts and just keeps running without any result. The HDD is getting very hot already.
I've never run into such a problem before, so I'm kinda clueless what to do next. I don't mind to reinstall, but I have some files on that HDD that I need (some notes in text files, some emails and so on).
So at this point I can't boot into OS X to access the HDD and I can't use the installer disk to access DU or even reinstall if I wanted to. I don't think the HDD is broken, this only happened after the 10.4.8 update. It just seems that every HDD access takes hours and hours longer than it should.
What options do I have to get my data from the disk? I'll try to install OS X to a new external drive tomorrow (need one with firewire first). If that doesn't help I thought about pulling out the HDD from the Powerbook and hook it up to my MacMini or an iMac.
If anyone has any other suggestion or solved a similar problem before, please let me know.
Best,
Stephan

See my FAQ:
http://www.macmaps.com/WIFI1048.html

Networking problem after a zone is created and installed

Hi all,
I've got a networking problem after a zone was created and installed on a Solaris 10 box. The box was configured with two NICs, one (e1000g0) with a public IP address, the other one (e1000g1) with a private IP address and connected to a local switch. All worked fine so far.
Then I created a local zone with shared networking (e1000g1). The zone has a private IP address which is in the same subnet as e1000g1 on the global zone. After some time, I noticed that I could not access (ssh, ping) the global zone. Then after some time, the global zone became available. The problem happened quite frequently.
Also I observed that: 1) When the global zone was unavailable from outside, it was available (ssh, ping) from another box within the same subnet (e1000g0); 2) If I shutdown e1000g1, the problem was gone.
Any idea what caused this problem?
Many thanks,
Xiaobo

It was a route problem.

Beige G3 boot from **** problem; open firmware issues; bad motherboard?

Dear all,
I'm having huge boot/startup problems with my beige G3 that had been happily running OSX 10.3.9, but for purposes of this discussion we can (mostly) revert to OS 9. Originally, the machine was a G3 @300; was upgraded more than a year ago to a ZIF G4 @500.
To make a long story short, it won't boot from any hard drives, will not boot from any OS X CD, and will only occasionally boot from a 9.x startup CD (whether Apple or Norton Utilities). I think it's an open firmware issue, possibly caused by a bad motherboard (rev. 2).
All this started happening after I used techtool pro, but I think that's coincidence (even though I acknowledge that, for cops and computer users, there are no coincidences.) Also, as discussed below, I'm having the same problems with an HD that wasn't even in the computer when all these things began.
Here are some of the things I've done.
--repeatedly reset PRAM, both with key combinations and removing battery. The only time it will boot from a 9.x CD is after resetting PRAM.
--removed all add-on PCI cards.
--removed additional VRAM
--removed all memory cards and tried replacing one at a time.
--disconnected both existing hard drives and replaced with an older OS 9.x hard drive (approx 60 mb) that I'd used before. Also tried different ribbon cables.
--unplugged floppy drive
--disconnected PCI ATA disk controller that I'd been using for running a large (1.8 gb) hard drive.
--regarding open firmware: readenv usually shows totally normal default AND installed settings. Using reset-all works fine -- at least it makes the machine reboot, but doesn't solve the problem. reset-nvram does NOT work -- says it's an "unknown word."
--using startup keys like holding down the option key, or shift key, or X key or cmd-option plus two others I can't remember, has no effect. Again, after I've tried any kind of reboot, the ONLY way to get the C-key at startup to boot the CD is by resetting the pram (key combination). Otherwise, the usual result of these experiments is a dark screen on startup -- nothing at all (and the LCD monitor tells me "no input.")
--regarding OSX: sometimes (and I emphasize sometimes) I can get the machine to start booting from an OSX 10.2 CD, but it won't complete the process. Sometimes I get a "prohibited" (as in no-parking, no-smoking) icon; sometimes it will start booting (grey screen, OS X Apple icon), then crash (horizontal grey and white jagged bars); sometimes it will show the OS 9 start icon (the tiny smiling Mac SE), but not boot at all.
--when I get the mac successfully booted with an OS 9.x CD (again, this works sometimes, but not always), the old hard drive with two partitions does show on the desktop and can be accessed. Using either disk repair or Norton Utilities shows the 9.2 system partition on the hard drive to be fine. But if I go to the startup disk control panel, confidently set the 9.2 partition as my startup disk, then reboot, there's no change. It won't boot and I'm back at square one.
--even when I do get successfully booted with 9.x, the machine will still occasionally crash for no reason -- ie when I'm moving a Window.
--the only thing I haven't done is slowed down the processor. It's a ZIF G4 bought more than a year ago from XLR8 your Mac. I'm running at the default 500 mhz, and it's never given me any trouble.
So I think it's a bad motherboard or ROM. Thoughts?
Thanks.

The beige Mac is now operating happily again. My original tentative diagnosis remains the same (although still tentative): corrupted PRAM from bad battery, compounded by bad cables that wrote corrupted data to hard drives, and also (possibly) allowing Tech Tool Pro (a utility that I now regard with deep suspicion) to create a "virtual" startup partition.
A few things I've learned along the way that hopefully may be useful:
--remember that the Ex Post Facto utility can be used to help OS X startup, not just installation. This applies to hard drives, emergency CDs, installation CDs, etc. If you can boot into any working hard drive partition (OS 9 or a backup OS 10), then run Ex Post Facto (same program runs on either OS 9 or X -- don't ask me how) and tell it what system you want to start up from. Also, the utility has sometimes told me that the startup extensions on the disc that I wanted to boot up from were bad, and offered to fix them (which works).
--at least on my Mac (beige, v. 2 motherboard), resetting the CUDA button, resetting the PRAM, resetting Open Firmware and "draining" the memory by unplugging the computer and disconnecting the battery for several hours ALL DO DIFFERENT THINGS.
Specifically, if I'm having trouble booting (from a hard drive or a CD), the FIRST thing I do is restart and resetting the PRAM on the fly -- holding down command, option, P and R at startup, and waiting for the chimes (preferably at least 3-4 times).
If I do that and DON'T hear the chimes, that's my cue for my SECOND action -- restarting into open firmware (command, option O and F keys on startup). That should bring up the black text on white background open firmware screen. View other posts or apple support for details, but if you do PRINTENV and see a bunch of weird gibberish after the default/installed lists, you know that it was messed up and you need to clear it through reset nvram and reset all commands. Be aware some of these commands do or do not work depending upon what version of Open Firmware you have.
After I've rebooted with Open Firmware, then on restart I should be able to reset the PRAM on the fly. If that works, then either let the machine run and see what happens, or hold down the C command and see if it will boot from the CD
Usually, if I've fixed everything as above, the machine will boot into whatever version of OS 9 it finds on a hard drive. That's fine with me -- at that point, use Ex Post Facto to reboot into your OS X. (Before I forget: I used the shareware startup CD creator program BootCD to make an emergency boot CD based on OS 10.2.8 (which theoretically will support a beige mac in native fashion) and Disk Warrior, the god of disk repair utilities. Even though the CD should boot just by holding down the C key on startup, it doesn't -- but if I use Ex Post Facto to boot it, no problems (although the process is very slow -- be patient). Then I can fix almost anything using Disk Warrior.)
If none of the above works, then I'll try resetting the CUDA (on my beige minitower, it's a very small black button inconveniently located between a PCI slot and the side of the computer housing). Hold it down for 15 seconds. That should REALLY clear the PRAM. I know this does something different from the previous steps because this is the only action (except the battery disconnect -- next) that clears the date and time from the memory.
If all else fails, I will unplug the computer and disconnect the battery, then push the CUDA button for 15 seconds and let the machine sit overnight.
One final finding -- I thought I'd fixed everything, but both my hard drives suddenly quit working, I discovered that during all this repeated connect/disconnect of things, one of the male pins inside one of the connectors on my Acard ATA PCI card had broken off. Not good. Fortunately, the card had a second connector, which works fine. And I did some extensive shaking of the computer to make sure (I hope) that the broken pin hadn't landed on a circuit board.
All this took more than two weeks, and the advice of this board was much appreciated. Now I'm on to my next adventure -- trying to figure out why a combo Firewire/USB PCI card won't mount an external drive on Firewire, but will on USB. I've tried two cards with same result -- but a Firewire-only card works just fine.)
Regards to all,
Graham

Solaric boot up problem after poweroff

Similar Messages

Maybe you are looking for