Created zone with defaults won't boot completely (Solaris 10, Update 1)

If I create a zone with defaults, i.e. allowing the zone to inherit the typical package dirs, the resulting zone does not boot completely. When I attach to the zone via zlogin, the zone looks to be in an administrative state. It never boots to a point where one would typically enter in the initial configuration info, e.g. timezone and root password.
However if I create the zone after first removing the inherited dirs, the zone boots to a state where it subsequently can be confiured and fully booted.
Looks as if the SMF facilities are not fully initialized when the zone is configured to inherit its packages. This could be a red herring as I'm a newbie who's moved over from Linux and starting to understand SMF specifically and Solaris in general.
I did not have this problem with Solaris 10. I've just installed Solaris 10 Update 1; the problem seems specific to that installation. I reinstalled and the problem persists.

I snipped the output because there were some errors, which on retrospect seems to have been a silly decision. I repeated the process and captured the missing output:
# zoneadm -z foo install
Preparing to install zone <foo>.
Creating list of files to copy from the global zone.
Copying <5913> files to the zone.
Initializing zone product registry.
Determining zone package initialization order.
Preparing to initialize <942> packages on the zone.
Initialized <942> packages on zone.
Zone <foo> is initialized.
Installation of <1> packages was skipped.
Installation of these packages generated warnings: <SUNWxwfnt
SUNWxwplt SUNWxwcft SUNWjxmft SUNWxwpls SUNWpmowu
SUNWxilrl SUNWolrte SUNWi13rf SUNWi15rf SUNWi2rf SUNWi5rf
SUNWi7rf SUNWi9rf SUNWtxfnt SUNWdoc SUNWi1of SUNWi4rf
SUNWi8rf SUNW1251f SUNWarrf SUNWxwoft SUNWxwxst
SUNWkoi8f SUNWasu SUNWxrpcrt SUNWasac SUNWasdb
SUNWasut>
The file </zone/foo/root/var/sadm/system/logs/install_log> contains a log of the zone installation.The packages are related to App development and X11. I don't see any that might be related to SMF.
The logfile is too large to post at over 37K lines. However there seemed to be a pattern to the package failures. Hopefully these greps highlight the important messages:
# grep "partially failed" /zone/foo/root/var/sadm/system/logs/install_log
Installation of <SUNWxwfnt> on zone <foo> partially failed.
Installation of <SUNWxwplt> on zone <foo> partially failed.
Installation of <SUNWxwcft> on zone <foo> partially failed.
Installation of <SUNWjxmft> on zone <foo> partially failed.
Installation of <SUNWxwpls> on zone <foo> partially failed.
Installation of <SUNWpmowu> on zone <foo> partially failed.
Installation of <SUNWxilrl> on zone <foo> partially failed.
Installation of <SUNWolrte> on zone <foo> partially failed.
Installation of <SUNWi13rf> on zone <foo> partially failed.
Installation of <SUNWi15rf> on zone <foo> partially failed.
Installation of <SUNWi2rf> on zone <foo> partially failed.
Installation of <SUNWi5rf> on zone <foo> partially failed.
Installation of <SUNWi7rf> on zone <foo> partially failed.
Installation of <SUNWi9rf> on zone <foo> partially failed.
Installation of <SUNWtxfnt> on zone <foo> partially failed.
Installation of <SUNWdoc> on zone <foo> partially failed.
Installation of <SUNWi1of> on zone <foo> partially failed.
Installation of <SUNWi4rf> on zone <foo> partially failed.
Installation of <SUNWi8rf> on zone <foo> partially failed.
Installation of <SUNW1251f> on zone <foo> partially failed.
Installation of <SUNWarrf> on zone <foo> partially failed.
Installation of <SUNWxwoft> on zone <foo> partially failed.
Installation of <SUNWxwxst> on zone <foo> partially failed.
Installation of <SUNWkoi8f> on zone <foo> partially failed.
Installation of <SUNWasu> on zone <foo> partially failed.
Installation of <SUNWxrpcrt> on zone <foo> partially failed.
Installation of <SUNWasac> on zone <foo> partially failed.
Installation of <SUNWasdb> on zone <foo> partially failed.
Installation of <SUNWasut> on zone <foo> partially failed.and# grep "not installed" /zone/foo/root/var/sadm/system/logs/install_log
*** package <SPROmrdwf> was not installed:
*** package <SPROdwrfb> was not installed:
*** package <SPROlang> was not installed:
*** package <SPROlangx> was not installed:
*** package <SPROdwrfx> was not installed:
*** package <SPROsbld> was not installed:
*** package <SPROsbldx> was not installed:
*** package <SPROrdbkb> was not installed:
*** package <SPROrdbkx> was not installed:
*** package <SPROcc> was not installed:
*** package <SPROutool> was not installed:
*** package <SPROmrcc> was not installed:
*** package <SPROmrcom> was not installed:
*** package <SPROmr3m> was not installed:
*** package <SPROmrtcv> was not installed:
*** package <SPROm9xs> was not installed:
*** package <SPROsunms> was not installed:
*** package <SPROsmsx> was not installed:
*** package <SPROsmpx> was not installed:
*** package <SPROmrsbe> was not installed:
*** package <SPROsbe> was not installed:
*** package <SPROpnsn> was not installed:
*** package <SPROfd> was not installed:
*** package <SPROupdck> was not installed:
*** package <SPROcpl> was not installed:
*** package <SPROcplx> was not installed:
*** package <SPROcmpl> was not installed:
*** package <SPROtlbn7> was not installed:
*** package <SPROtll7> was not installed:
*** package <SPROtl7x> was not installed:
*** package <SPROtll7x> was not installed:
*** package <SPROscl> was not installed:
*** package <SPROsclx> was not installed:
*** package <SPROmrstd> was not installed:
*** package <SPROmrcpl> was not installed:
*** package <SPROstl4h> was not installed:
*** package <SPROstl4a> was not installed:
*** package <SPROstl4o> was not installed:
*** package <SPROstl4x> was not installed:
*** package <SPROstl4y> was not installed:
*** package <SPROftool> was not installed:
*** package <SPROl90> was not installed:
*** package <SPROl90x> was not installed:
*** package <SPROl90s> was not installed:
*** package <SPROl90sx> was not installed:
*** package <SPROf90> was not installed:
*** package <SPROmrftn> was not installed:
*** package <SPROgc> was not installed:
*** package <SPROlgc> was not installed:
*** package <SPROgcx> was not installed:
*** package <SPROlgcx> was not installed:
*** package <SPROdbx> was not installed:
*** package <SPROdbxx> was not installed:
*** package <SPROjdbx> was not installed:
*** package <SPROjdbxx> was not installed:
*** package <SPROmrdbx> was not installed:
*** package <SPROdemo> was not installed:
*** package <SPROdmake> was not installed:
*** package <SPROmrdmk> was not installed:
*** package <SPROtdemo> was not installed:
*** package <SPROmride> was not installed:
*** package <SPROdbxui> was not installed:
*** package <SPROsvc> was not installed:
*** package <SPROxdplg> was not installed:
*** package <SPROidext> was not installed:
*** package <SPROjnsnb> was not installed:
*** package <SPROjnsrt> was not installed:
*** package <SPROjnsup> was not installed:
*** package <SPROctags> was not installed:
*** package <SUNWnbide> was not installed:
*** package <SUNWnbcpp> was not installed:
*** package <SUJAnbcpp> was not installed:
*** package <SUZHnbcpp> was not installed:
*** package <SUNWexted> was not installed:
*** package <SUJAexted> was not installed:
*** package <SUZHexted> was not installed:
*** package <SPROnbreg> was not installed:
*** package <SPROfdxd> was not installed:
*** package <SPROmrxd> was not installed:
*** package <SPROgvim> was not installed:
*** package <SPROxmbin> was not installed:
*** package <SPROxmshr> was not installed:
*** package <SPROxmsrc> was not installed:
*** package <SPROmrxm> was not installed:
*** package <SPROprfan> was not installed:
*** package <SPROmrpan> was not installed:
*** package <SPROprfax> was not installed:
*** package <SPROprflb> was not installed:
*** package <SPROprflx> was not installed:
*** package <SPROprfgn> was not installed:
*** package <SPROmrpgn> was not installed:
*** package <SPROhtbas> was not installed:
*** package <SPROhttl7> was not installed:
*** package <SPROhtstd> was not installed:
*** package <SPROhtxd> was not installed:
*** package <SPROdwrfs> was not installed:
*** package <SPROrdbks> was not installed:
*** package <SPROctsrc> was not installed:
*** package <SPROplg> was not installed:
*** package <SPROpl> was not installed:
*** package <SPROplx> was not installed:
*** package <SPROpls> was not installed:
*** package <SPROplsx> was not installed:
*** package <SPROmrpl> was not installed:These messages seem to be inline with the general output captured from the zone install itself.
> What does "svcadm list -vc" give you when you started the zone ?
I took that as a typo, instead using "zoneadm?"
# zoneadm list -vc
  ID NAME             STATUS         PATH
   0 global           running        /
   7 foo              running        /zone/fooThe zone is not on its own slice, however "/zone" is mounted as a loopback from /export/zone. I don't think that's a problem since the zone install seems to work if I don't inherit packages. Unless perhaps its a nesting level of lofs's.
FWIW,
# mount |grep zone
/zone on /export/zone read/write/setuid/devices/dev=1540000 on Fri Feb 24 16:10:55 2006
/zone/foo/root/dev on /zone/foo/dev read/write/setuid/devices/zonedevfs/dev=4640007 on Tue Feb 28 13:13:03 2006
/zone/foo/root/lib on /lib read only/setuid/nodevices/nosub/dev=dc0440 on Tue Feb 28 13:13:03 2006
/zone/foo/root/platform on /platform read only/setuid/nodevices/nosub/dev=dc0440 on Tue Feb 28 13:13:03 2006
/zone/foo/root/sbin on /sbin read only/setuid/nodevices/nosub/dev=dc0440 on Tue Feb 28 13:13:03 2006
/zone/foo/root/usr on /usr read only/setuid/nodevices/nosub/dev=dc0440 on Tue Feb 28 13:13:03 2006
/zone/foo/root/proc on proc read/write/setuid/nodevices/zone=foo/dev=4400007 on Tue Feb 28 13:13:06 2006
/zone/foo/root/system/contract on ctfs read/write/setuid/nodevices/zone=foo/dev=43c0008 on Tue Feb 28 13:13:06 2006
/zone/foo/root/etc/svc/volatile on swap read/write/setuid/nodevices/xattr/zone=foo/dev=448000e on Tue Feb 28 13:13:06 2006
/zone/foo/root/etc/mnttab on mnttab read/write/setuid/nodevices/zone=foo/dev=4440008 on Tue Feb 28 13:13:06 2006

Similar Messages

  • Mac won't boot after the latest update. It is loading the update and suddenly shuts down

    My MacBook Pro won't boot after a minor update. The update was all fine and my Mac acted like it used to but when I tried to boot my Mac it just loads the the update then goes back to the Apple logo and then shuts down.
    I hope that someone has got a solution because I do not want to restore my Mac for the 4th time.....

    Hello JonasHallund,
    We've an article that contains information and steps that can help get your MacBook Pro to boot again.
    Troubleshooting: My computer won't turn on
    http://support.apple.com/kb/TS1367
    Cheers,
    Allen

  • Problem with HP Media Centre M7670.UK-a - won't boot after installing an update to Apple Quicktime

    I just installed the latest update to Apple Quicktime (after an update message appeared on the screen). When asked if I wanted to re-boot the PC now, I clicked on Yes.
    Now the computer won't boot. The power light comes on, then the disk drive light flashes for a moment, then nothing else happens and the PC starts to beep. The beeps are repeating, with 2 short beeps and one long beep. What do the beeps mean?
    This question was solved.
    View Solution.

    Then a  clear CMOS would be the next logical troubleshooting step.
    Here is  a link to your motherboard specifications.
    The information on clearing CMOS is at the bottom of the document.
    This is usually the last step before giving up on a motherboard.
    The problem you are facing is motherboard hardware firmware related.
    ****Please click on Accept As Solution if a suggestion solves your problem. It helps others facing the same problem to find a solution easily****
    2015 Microsoft MVP - Windows Experience Consumer

  • My Blackberry torch 9800 won't boot completely

    i have tried several times and have ejecting the battery several times but still not booting completely. it boots to about 99percent and then restarts again and again...

    Try booting in safe mode.
    Remove the battery.
    While holding down the back key, reinsert the battery and continue to hold the back key for another 20 seconds.
    if the device reboots then remove the last application or theme you installed.
    1. Please thank those who help you by clicking the "Like" button at the bottom of the post that helped you.
    2. If your issue has been solved, please resolve it by marking the post "Solution?" which solved it for you!

  • Macbook won't boot after installing Security Update 2008-007 (Intel)

    I installed security update 2008-007 (intel) on my MacBook last night using Software Update, but now my machine won't boot at all. All I get is the gray start-up screen with the dark gray apple, but there's no spinning progress bar or anything. After 5 minutes or so, the machine auto-restarts, but again hangs on the gray start-up screen. It does this over and over again until I shut it off. I tried to boot into safe mode by holding down shift right after the chime, but it still wouldn't boot (again, not even a spinning progress bar). Can anyone please help me? I really don't want to lose my photos/movies, etc. I'll backup everything promptly if I can just get it to boot. Thanks.

    Hi jared-lee, and again, a warm welcome to the forums!
    First for safety, "Try Disk Utility
    1. Insert the Mac OS X Install disc that came with your computer, then restart the computer while holding the C key.
    2. When your computer finishes starting up from the disc, choose Disk Utility from the Installer menu. (In Mac OS X 10.4 or later, you must select your language first.)
    Important: Do not click Continue in the first screen of the Installer. If you do, you must restart from the disc again to access Disk Utility.
    3. Click the First Aid tab.
    4. Click the disclosure triangle to the left of the hard drive icon to display the names of your hard disk volumes and partitions.
    5. Select your Mac OS X volume.
    6. Click Repair. Disk Utility checks and repairs the disk."
    http://docs.info.apple.com/article.html?artnum=106214
    This may or may not fix the problem, but may.
    Do you have another Mac around?

  • HELP: T440s won't boot after unsuccessful memory update

    I have a T440s that came with 4GB RAM. Purchased a G.Skill Ripjaws 8GB DDR3L 1600 SO-DIMM (1.35v, PC3-12800, 11-11-11-28) from Newegg and installed in T440s. I did disable the internal battery from BIOS before installed the memory. However, I found my T440s won't even boot. I then tried the memory chip in two other laptops and found this SO-DIMM is defective so it's on the way back to Newegg.
    Now my big problem is that my T440s won't boot anymore even with original configurations. Push the power button, there is no response from T440s. However, I do observed LEDs blink. When only use battery, then LEDs give one short blink every few seconds. LEDs will give four short blinks every few seconds if I plug in the wall power supply.
    Did I kill my T440s ? Any way that can wake it up or I just need to contact Lenovo for warranty service?
    Any help/suggestion is appreciated. Thanks a lot.
    Jon

    <<It turned out that the defective memory killed the motherboard. >>
    The what now?
    I'd like to know more about that. 

  • Satellite A40-231 won't boot after wrong firmware update

    Hi,
    i own a toshiba satellite a40-231.it won't boot anymore because i have flashed it's dvd-rw drive(sdr-6112) with the wrong firmware and i also made a big mistake making a non-bootable active dos partition,trying to flash the correct firmware.So, my question is: can i boot from usb flash disk?i believe it's the only option i have left, if not network boot.
    Thanks in advance!

    Hi
    As far as I know its not possible to boot from any other devices as from USB FDD / HDD / CD-ROM / LAN
    You could boot from network but if you want to install the OS via LAN you will need an RIS server. But its not very easy to do it without any additional experience. So I think this option is nothing for you.
    It seems the drive is dead or malfunctions and therefore the best idea is to replace the device drive. I know, its hard to hear that but I dont see any other solution

  • IMac won't boot up after latest update. Any suggestions?

    I just updated my software (the latest from apple), then my iMac won't boot again.

    There you go. Your HDD is failing hence its not booting. You need reformat the HDD
    To reformat, same steps: Boot to the install disc > get past the language selection > You will see Welcome to Blah Blah Blah > just hit continue > There should be something there called erase and install
    BUT
    1. if you are absolutely sure that Time machine has BACKED-UP all of your files then proceed above
    2. If not, if you have another mac: connect it via firewire then google Target Disk mode. Basically you want to copy all your files from the damaged machine to the new mac to serve as a backup
    3. if yo dont have another mac: get an external HDD, install Mac os X on it, boot to it then back up your files
    to do this
    a) Plug external HDD
    b) Boot to the CD restart and hold C
    c) Get past language selection and keep hitting continue
    d) when it asks you where you want to install Mac os X > select the external HDD
    e) once its installed. Restart the computer and hold "Option" key. You should now see your external HDD as one of the boot drives. Select that and you'll boot into it
    f) once inside the external HDD OS, you will see the internal HDD(damaged drive)browse/navigate through it and start getting your important files

  • Error with default SSL port (443) on Solaris

    Hi all
    I would like to config default SSL port 443 on Solaris but I found this error. What is the problem?
    I use WebLogic 8.1 sp3
    SSL port : 443
    Unable to create a server socket on Channel Default for port: 443. java.net.BindException: Permission denied Perhaps another process is using port 443
    I dont sure about permission. How can I do?

    Oh I can use root start weblogic and I can use 443 port, but when I use other users. I can't use 443 port

  • Toshiba won't boot after Toshiba BIOS update

    My Satellite P755 would not boot immediately after I did the updates that the Toshiba update software recommended I do.  It still would not boot after going through the entire recovery process.  At this point I'm thinking it must be a hardware failure so I called toshiba.  
    They told me it would be $49.99 for telephone tech support to fix the issue but that would be refunded if it was determined to be a hardware issue.  The tech had me unplug the power, remove the battery and hold the power button down for 30 seconds (apparently this must remove the incorrect bios update or something).  After putting the battery back and plugging back in the recovery process worked and it now boots again.  
    I'm happy this worked but a little frustrated that I paid $49.99 to fix an issue that was not caused by me, it was caused by the Toshiba update software suggesting and installing an incorrect BIOS update, which was confirmed by the technician that I spoke with.  After talking to a rep and a supervisor I was denied a refund.  I've lost time, money, and data over this issue.  
    The tech also told me I should call Toshiba anytime I update software to make sure it will work with my computer, even if it's an update recommended by the Toshiba update software.

    Thanks to the original poster. I bought a laptop and I did the Bio update.  I had an issue on my old laptop and i took out the power supply and that worked.
    Now with this one after the update it would not turn on or do anything. I could not get to the bios or nothing as it was dead for the most part. It would trun on for a few seconds and I panicked as this is a lot of money to spend of a dead computer.
    I have limited income and I was beside myself. I thought after taking the battery out and putting it back it continued to do it that it was dead.  I picked me up and did a search on the web and eventually found this thread.  I did what the oriingal poster did. I think leaving the battery out so it resets is the primary issue. I did both the on button in case. Yeah I know it don't make sense but I did it.
    It is now working. It booted up and I am playing a CD in it. 
    My other laptop basically in direcly was stolen. Well not quite. I loaned it to my son and the car he had it in got impounded. I had my info on it so it could be returned but it was never retruned.  I would like it back as it was realiable but it had the same issue to turn on at one point. Battery taken out fixed it.
    I don't think I am going to do any more bios updates on it.  I hope there is no more of them.  I am not sure if it will shut off and power up right but since it is working now for the last five minutes It is ok. I am playing a CD on it.
    thanks to the poster of this thread.  You save me and my laptop. I love it.
    I did read bad reviews of it as well as good.  It is companies are doing anything to make a profit.  It is why I stand for the resource based economy where planned obsolence will be history.
    HUGS TO YOU GUYS.
    Barb

  • Mac G4 Won't Boot Completely After Restart

    I fired up my Mac G4 and ran software update and installed the 10.4.11 update. When I restarted to complete the install the computer gets hung up -- a blue screen with the gear icon turning and turning. It worked fine before I did the update.
    I've reset the PRAM to no avail. I've tried booting from the 10.4 install disc but that won'w work either?
    Any ideas on how to get this working again?
    Thanks!

    Open the service door and press the PMU reset button from about a second, then see if the computer starts. (Ref: http://support.apple.com/kb/HT1939)
    You can try a safe boot. Press and hold the SHIFT key until you see a message that the computer is starting in safe mode. When you see that message, t=you can let go of the key.
    If this gets you a workable desktop, don't try to use any apps--their extensions are temporarily disabled. Try a normal restart to see if everything works.
    I've found that by repairing permissions before and after doing a softare update, we've avoided update problems in all our OSX Macs.

  • Playbook won't boot - Completely unique problem

    Ok before anyone blasts me for posting before researching I would like to say that I have done my research and this post is my last hope.
    I recently bought a second hand Playbook that was advertised as not working for $20. Me being a BB freak and my Wife and I just having a new baby (so no ex tra $) I said to myself "oh they just don't know what they are doing" well apparently neither do I. 
    This PB was won at a Christmas party this past December and the woman who won it, was never able to get it to turn on.
    Now here's the weird part, this PB does not do what 99% of the other either bricked or drained PB's do. This one shows no signs of life at all if it is not plugged in, I will say here that I am only using the charger that came with the PB and no third party or uniusb's. Once I plug the PB in the red led comes on after about 5 seconds and stays on for exactly 10 minutes. From the hundreds of articles I could find I could not find one that showed the same symptoms.
    Here is what I have tried so far. 
    #1. Just letting it charge for 24 hours
    #2. Several different Stack methods (as a matter of fact, every single method that I came across)
    #3. Trying to get the computer to recognize the PB by hooking up the USB cable, and trying several different ways to get the DM to recognize the PB. No luck, not even for that glimmer of a second like others have reported.
    #4. Removing the back casing, after going online and making sure that there was no longer a warranty, and disconnecting the battery from the mother board for about an hour and then plugging the battery back in and hooking up the charger to see if there were any signs of life. NOTHING
    #5. Disconnecting all of the pin connections from the mother board, then once again after an hour replacing the connections and trying to charge. Nada
    #6. Removing the connections again and placing insulators between the mother board connections and the ribbon connections then placing the display with the batteries in a freezer bag, removing all of the air to stop condensation, then placing it in the freezer for about an hour and a half. Then letting it warm up to room temp and plugging in the charger. Nope
    #7. I saw a post about "jumping" the battery by Knotty Rope. Turns out he has a different version PB than this one because the battery connector is completely different than the one he had. Could not trace the circuit enough to find a valid place to apply a 5V source to trick the PB into thinking it has the proper voltage.
    Now after all of that I finally (don't ask me why I didn't start with this) tested the battery with my VOM and found that the battery only seems to have 0.91Vdc.....
    I know that 0.91V means that the batteries are stone dead and probably have to be replaced and I'm ready to give up.
    Update 1: After charging the battery again for about 12 hours I found that the battery has gone up to 0.98V. I just realized though that with the battery being this low the LED is probably using about 80% of the power being put into the unit, so I have disconnected the ribbon going to the LED indicator and I am going to try and charge it for the rest of the day and see if the battery can get a little more power.
    Update 2: Ok I finally gave up on trying to charge the battery using the USB port and I carefully exposed the main battery connections and found that the batteries actually had 1.7V. After watching a YouTube vid I then cut the end off of an only USB cord, found the + and - power leads and attached an aligator clip to each. I then hooked up the leads after making sure what the polarity was and began to manually charge the battery. I charged the battery up to 3V and then checked it 2 hours later. The battery was still at 3V so I took it up to 3.5V. I thought this was going to be the answer but apparently not. Still has the same symptoms described below and shows no signs of life. I think I'm going to have to call this unit FUBAR and wait until I can afford a new one 
    Update 3: I have tried a few more things to no avail but I figured I'd list them here. Since I charged the battery manually the battery has not discharged by more than .3V. So my problem doesn't seem to be a power issue. I have now tried to use a rapid charger and plugging in the USB cable to see if I could make the computer recognize the PB. That didn't work so I removed the mother board and carefully cleaned and dried it using alcohol and a blow drier. That also didn't work. Apparently I'm the only person to ever have this problem happen and even Blackberry themselves are at a loss as to what could be wrong. So I guess I have a shiny paper weight with a good charger for my 9810 and a new BB USB cable. I can't complain after spending $20 on it but I am really disappointed as I was really hopeful that I would finally be the proud owner of a Playbook.
    Update 4: As a complete "why not" effort I bought a dock charger for $15 and am trying to stack charge with it but after a few days it still hasn't done anything.

    Have you checked the power button on the top. I did see a post where the button was stuck in the down position and the PlayBook would not start. Eventually the poster fiddled with the button using something small until the button popped up again.

  • OSX won't boot completely

    When my MBP boots it stays at the following state:
    The mouse works, the keyboard works, i can change the volume and brightness.
    But it won't continue to the desktop, it should auto-login.
    Before this happend i've shutdown my MBP by holding the powerbutton for 5 seconds.
    Because none of the applications responded and the menubar didn't respond.
    I've tried removing preferences & caches of the user. plist files for the loginitems,desktop & windowserver.
    I've tried repairing the disk, it was ok, I fixed te permissions.

    Reinstalling Mavericks, Lion/Mountain Lion Without Erasing the Drive
    Boot to the Recovery HD: Restart the computer and after the chime press and hold down the COMMAND and R keys until the menu screen appears. Alternatively, restart the computer and after the chime press and hold down the OPTION key until the boot manager screen appears. Select the Recovery HD and click on the downward pointing arrow button.
    Repair the Hard Drive and Permissions: Upon startup select Disk Utility from the main menu. Repair the Hard Drive and Permissions as follows.
    When the recovery menu appears select Disk Utility. After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list.  In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive.  If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the main menu.
    Reinstall Lion/Mountain Lion, Mavericks: Select Reinstall Lion/Mountain Lion, Mavericks and click on the Continue button.
    Note: You will need an active Internet connection. I suggest using Ethernet if possible because it is three times faster than wireless.

  • POST fails on T5140 server.   POST shows errors about "Unable to create files".  Server won't boot

    All,
    Need any help that someone can provide.  Currently I have a T5140 server.   Yesterday it crashed unexpectedly. We were able to reboot the system and it come back up with the service light on.  Service light was indicating a memory DIMM problem.   We powered down the server to replace the memory modules that had service led showing for them.   After powering the system on, it never gets past POST now.  We attached a serial console to the ILOM and watch the post.   POST starts normally. Then we start to see messages about "unable to create files.  Finally POST gets to a point where it looks like it is finishing but hangs.   It hangs at the point where it say that it is initiating run level 3.  But it just sits there and never boots the system.  Any ideas?   Is this a motherboard issue that really cemented itself when the power was removed to the system?  Any help would be greatly appreciated.  We are stuck.
    Thanks.

    I have had this same issue, unfortunately you will need to place a service call for a field tech to come on-site and replace the failty DIMM. The T5140 WILL NOT BOOT if any one or more DIMMs fail to POST.
    The only partial solution is to disable the CPU that is connected to the bad DIMM so the system will successfully boot up in degraded mode. But I would not run the box like that for long.
    You need to call service a.s.a.p.

  • Ibook won't boot completely ! (stops at a blue screen)

    Hi...first time poster here, please be kind. Also, I'm not brilliant by any measure when it to computers.
    Yesterday I was installing updates (now, my ibook was out of use for at least 8 months, so I was bit back logged on updates) and after the second round (a safari update, a java update, and a security update) it said it needed to restart. Ok, easy enough, though apparently not it never booted up again. I get past the grey apple loading screen and to the blue screen that says "loading os x"...the progress bar finishes and then it disappears and all I get is a blue screen with a rotating "busy/working" symbol. A few times I got a black screen with white text asking for my login and password, but it always says it's wrong or it won't even let me type in a password before it freezes and goes on to the blue blank screen again. I did a PRAM cleaning and that ran correctly but did not help. It will not load in safe or verbose mode. Any one have any idea why my ibook is doing this or if there is anyway to fix it ? (also, I'm not sure eaxactly which os X I am running other than it os x 10.4) Help...
    Message was edited by: kurokaze83

    If you can't find the system discs that came with your computer, use fsck (a command-line utility that may be able to verify and repair a disk)
    To use fsck:
    1. Start up your computer in single-user mode to reach the command line.
    2. At the command-line prompt, type /sbin/fsck -fy
    3. Press Return. fsck will go through five "phases" and then return information about your disk's use and fragmentation. Once it finishes, it'll display this message if no issue is found:
    ** The volume (nameofvolume) appears to be OK
    If fsck found issues and has altered, repaired, or fixed anything, it will display this message:
    *** FILE SYSTEM WAS MODIFIED ***
    Important: If this message appears, repeat the fsck command you typed in step 2 until fsck tells you that your volume appears to be OK (first-pass repairs may uncover additional issues, so this is a normal thing to do).
    4. When fsck reports that your volume is OK, type reboot at the prompt and then press Return.

Maybe you are looking for