Fail to boot after thunder storm

Early yesterday morning a sever thunder and lightening storm came through. My iMac was off and attached to a surge protector. today, i went to boot the iMac up and found that it would not boot. I also noticed that my panasonic phone system was not working properly (digitial phones are not functional).
the building was NOT hit by lightening nor can I find any nearby location that was, but we did lose power for several hours while the power company sorted it out.
i brought the iMac to the local Mac store and tech support tere says it is getting power, but fails to continue the boot cycle which they think is either the logic board or video card, but will not know more until tomorrow.
Has anyone ever heard of a "none" lightening strike fried a computer?

It doesn't take a direct lightning strike to fry delicate electronics like a computer or phones. And surge protectors do not provide any protection against lightning whatsoever.
The lightning strike could have been miles away, it would not have to be right at your building. There could even have been a ground strike in your neighborhood that has no physical evidence you could see. And it wouldn't even have to be a ground strike - cloud-to-cloud strikes can generate as much EMP or EMI as a ground strike.
The EMP/EMI induced by lighning could also have come in via your phone line or internet connection, not just the power line. Even the ground line can end up being a conductor.

Similar Messages

Restored 10.6 OS from CD and fails to Boot after Combo upgrade

I have a clean install of Lion on my internal drive and an external clone of the HD from the previous Snow Leopard install. The Clone worked until I updated via the latest auto update. I have App's and other settings to transfer to Lion from this clone so want to get it working so I can ensure all the App's are upgraded to work on Lion or are deleted.
After the external drive failed to boot I reinstalled the system from my Snow Leopard Install CD, not the 24-inch iMac (Mid 2007) restore CD.
I then used Auto updater to install the combo and other updates to 10.6.8 this booted fine until I upgraded Safari 5.1 and Java - the last items that came up on the software updater. Upon restart, the boot failed in the last portion of the boot and at this point the Apple emblem went away and the round circle with diaginoal line apeared.
On starting with the option key down, the clone disk 10.6.8 shows as being available, along with the internal Drive, for booting.
Starting with "command + S" gets through to the last line of the process then states "waiting on Root"
When compaired to a Snow OS that boots OK it is the last line of code before the curser is ready for entering a command.
Can anyone tell me what to look for or how to repair this error so that I can get my data across to Lion. Thanks

Well, in case anyone else has a similar problem I managed to fix the system by the following process:
I reinstalled 10.6.0 from the retail Snow Leopard CD. The drive Booted OK but I needed to be upgraded to 10.6.8 to use the migration tool so I then upgraded using the Software Update utility. Boot failed again at this point and could not be fixed by anything I did.
I then reinstalled 10.6.0 from the CD to try again, but the HD would not boot this time around.
I downloaded CleanApp by Synium Software (http://www.syniumsoftware.com/cleanapp/) on a commendation from the famous eBook, "Take Control of installing Lion" by Joe Kissell of TidBits. I used this from my Lion HD to remove all orphan files, PPC files and Apps, and other junk. Snow Leapard still not Booting after repairs by various disk repair utilities including Apples.
I Booted from my internal HD using Lion and ran SuperDuper to make a new Clone of the failed HD on a second external HD. Took a day and a night to run while I was at work, but the new clone would not boot at this stage so I ran SuperDuper again using the "Smart Update Backup" option. This just adds changed files or missing files to the clone. At the end of this process I had a running Clone that would boot on 10.6.0.
I Booted from the second Clone and used the Software Update utility then to up grade in the two stages the Auto system used to bring my OS up to 10.6.8. This was successful and I had a Bootable Snow Leopard with no old Apps from which to Migrate my data.

Arch fails to boot after installation (BIOS mode)

I finished my Arch installation, following the Beginner's Guide, and once I unmounted the partitions and rebooted, GRUB failed to boot into Arch. I'm not exactly sure what the problem is though. Basically what happens is I power on the machine, the Dell splash screen comes up, GRUB loads, I choose
Arch Linux, with Linux core repo kernel
the kernel and ramdisk attempt to load, then some message about "recovering journal" appears, and then I return back to the Dell splash screen. The same thing happens even if I choose the second option
Arch Linux, with Linux core repo kernel (Fallback initramfs)
However, when I choose to boot Win XP everything boots just fine. My apologies for the quality of the videos and pictures.
Here's a video of what happens:
http://youtu.be/uC96kX6iTjI
I suspect this has to do with this error I got when I generated the "grub.cfg". Although I'm not entirely sure because my understanding is that this error would affect booting Win XP which in fact boots perfectly fine.
Error (and no I'm not using any lvm volumes)
http://imgur.com/qqxpoGG
I believe these are the portions of the "grub.cfg" that load Arch and Win XP. I got these by pressing "e" while on their menu entry in the GRUB bootloader.
Arch (I had to scroll down to see the rest, hence two pictures)
http://imgur.com/79dBw2C
http://imgur.com/qusEfL0
Win XP
http://imgur.com/oLnLlT0
Any idea how I can fix this? Any help is greatly appreciated and please be patient, I know, I'm a noob.
* I'm not sure if this is of any significance but I had a problem very similar to this when trying to get the Arch install to boot via usb (this computer doesn't have CD/DVD drive). I solved it by following this excerpt from the Beginner's Guide.
Troubleshooting boot problems
If you are using an Intel video chipset and the screen goes blank during the boot process, the problem is likely an issue with Kernel Mode Setting. A possible workaround may be achieved by rebooting and pressing
e
over the entry that you are trying to boot (i686 or x86_64). At the end of the string type
nomodeset
and press
Enter
Here's a video of what it looked like:
http://youtu.be/vXRcbU0zdto
The computer specs:
OS: Windows XP Professional 32 bit Version 2002 Service Pack 3
CPU: Intel Pentium 4 @ 3.00 GHz
RAM: 2 GB DDR2
HDD: 80 GB

Hi,
why did you not try adding nomodeset with the regular boot? During the net-install no video drivers will be installed;
you have to install them after reboot after installing xorg. The (video)problem you had with booting from usb is still
present.

Dell Latitude E6520 fails to boot after Windows Updates

Hello,
I have a Dell Latitude E6520 that is not starting up after Windows updates. It installs updates and requests a reboot, after which it blue screens at the splash logo and reboots again. This goes on indefinitely. The only way to repair it is to boot from
a recovery disk and run:
dism /image:D:\ /cleanup-image /revertpendingactions
This is after running dism /image:D:\ /get-packages and noticing that several updates are still in an "Install_Pending" state. These are the kb's that are pending:
kb2982378
kb2978742
kb2977629
kb2976897
kb2973112
kb2972211
There were other updates, but those showed as installed. I would post the WindowsUpdate.Log, but I do not see a button to attach a file and the log is very long. Here is what I think is relevant towards the end of the log:
2014-09-18 10:52:04:214
496 540
AU Install complete for all calls, reboot needed
2014-09-18 10:52:04:216
496 540
AU Successfully wrote event for AU health state:0
2014-09-18 10:52:04:623
496 8a4
AU UpdateDownloadProperties: 0 download(s) are still in progress.
2014-09-18 10:52:04:623
496 8a4
AU Triggering Offline detection (non-interactive)
2014-09-18 10:52:04:623
496 8a4
AU AU setting pending client directive to 'Reboot Pending'
2014-09-18 10:52:04:623
496 8a4
AU Changing existing AU client directive from 'Progress Ux' to 'Reboot Pending', session id = 0x1
2014-09-18 10:52:04:625
496 8a4
AU Successfully wrote event for AU health state:0
2014-09-18 10:52:04:625
496 1668
AU #############
2014-09-18 10:52:04:625
496 1668
AU ## START ## AU: Search for updates
2014-09-18 10:52:04:625
496 1668
AU #########
2014-09-18 10:52:04:626
496 1668
AU <<## SUBMITTED ## AU: Search for updates [CallId = {7C1069F1-2D57-421E-A378-38DE401BF9F1}]
2014-09-18 10:52:04:626
496 166c
Agent *************
2014-09-18 10:52:04:626
496 166c
Agent ** START ** Agent: Finding updates [CallerId = AutomaticUpdates]
2014-09-18 10:52:04:626
496 166c
Agent *********
2014-09-18 10:52:04:626
496 166c
Agent * Online = No; Ignore download priority = No
2014-09-18 10:52:04:626
496 166c
Agent * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0
and DeploymentAction='Uninstallation' and RebootRequired=1"
2014-09-18 10:52:04:626
496 166c
Agent * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
2014-09-18 10:52:04:626
496 166c
Agent * Search Scope = {Machine}
2014-09-18 10:52:05:210
496 166c
Handler Using CBS interface ICbsSession7
2014-09-18 10:52:07:170
496 166c
Handler Using CBS interface ICbsSession7
2014-09-18 10:52:09:475
496 166c
Handler Using CBS interface ICbsSession7
2014-09-18 10:52:09:569
496 166c
Handler Using CBS interface ICbsSession7
2014-09-18 10:52:11:590
496 166c
Handler Using CBS interface ICbsSession7
2014-09-18 10:52:14:999
496 166c
Handler Using CBS interface ICbsSession7
2014-09-18 10:52:16:887
496 166c
Handler Using CBS interface ICbsSession7
2014-09-18 10:52:18:753
496 166c
Handler Using CBS interface ICbsSession7
2014-09-18 10:52:19:623
496 1668
Misc WARNING: IsSessionNonstandardUI: session 65536 is an unknown session type 0; treating it as a standard session
2014-09-18 10:52:20:673
496 166c
Handler Using CBS interface ICbsSession7
2014-09-18 10:52:22:573
496 166c
Handler Using CBS interface ICbsSession7
2014-09-18 10:52:22:773
496 166c
Handler Using CBS interface ICbsSession7
2014-09-18 10:52:24:464
496 166c
Handler Using CBS interface ICbsSession7
2014-09-18 10:52:24:651
496 1668
AU AU received handle event
2014-09-18 10:52:26:366
496 166c
Handler Using CBS interface ICbsSession7
2014-09-18 10:52:27:520
496 1668
Shutdwn user declined update at shutdown
2014-09-18 10:52:27:520
496 1668
AU Successfully wrote event for AU health state:0
2014-09-18 10:52:27:520
496 1668
AU AU initiates service shutdown
2014-09-18 10:52:27:520
496 1668
AU ########### AU: Uninitializing Automatic Updates ###########
2014-09-18 10:52:28:206
496 166c
Agent * WARNING: Exit code = 0x8024000B
2014-09-18 10:52:28:206
496 166c
Agent *********
2014-09-18 10:52:28:206
496 166c
Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates]
2014-09-18 10:52:28:206
496 166c
Agent *************
2014-09-18 10:52:28:206
496 166c
Agent WARNING: WU client failed Searching for update with error 0x8024000b
2014-09-18 10:52:28:253
496 1668
Report REPORT EVENT: {62FF14E3-DDBE-4DDC-BE90-12B98EC74605}
2014-09-18 10:52:04:216-0600 1
193 102
{00000000-0000-0000-0000-000000000000}
0 0 AutomaticUpdates
Success Content Install
Restart Required: To complete the installation of the following updates, the computer must be restarted. Until this computer has been restarted, Windows cannot search for or download new updates: - Security Update for Windows 7 for x64-based Systems
(KB2982378) - Security Update for Microsoft .NET Framework 3.5.1 on Windows 7 and Windows Server 2008 R2 SP1 for x64-based Systems (KB2973112) - Security Update for Windows 7 for x64-based Systems (KB2976897) - Security Update for Windows 7 for x64-based Systems
(KB2918614) - Cumulative Security Update for Internet Explorer 9 for Windows 7 for x64-based Systems (KB2977629) - Security Update for Microsoft .NET Framework 3.5.1 on Windows 7 and Windows Server 2008 R2 SP1 for x64-based Systems (KB2972211) - Security Update
for Microsoft .NET Framework 3.5.1 on Windows 7 and Windows Server 2008 R2 SP1 for x64-based Systems (KB2937610) - Security Update for Microsoft .NET Framework 3.5.1 on Windows 7 and Windows Server 2008 R2 SP1 for x64-based Systems (KB2894844) - Security Update
for Windows 7 for x64-based Systems (KB2978742)
2014-09-18 10:52:28:253
496 1668
Report CWERReporter finishing event handling. (00000000)
2014-09-18 10:52:28:253
496 1668
Report CWERReporter finishing event handling. (00000000)
2014-09-18 10:52:28:425
496 1668
Service *********
2014-09-18 10:52:28:425
496 1668
Service ** END ** Service: Service exit [Exit code = 0x240001]
2014-09-18 10:52:28:425
496 1668
Service *************
Please let me know if there is a better way of attaching the log to this post and thank you in advance for any help.

Hi ChristianBoman,
We could use the OneDrive to upload the log and then paste the shared link here. For more information, please refer to the following article.
http://windows.microsoft.com/en-us/onedrive/share-file-folder
for the update error 0x8024000b, please refer to the following article.
http://windows.microsoft.com/en-us/windows/windows-update-error-8024000b#1TC=windows-7
Please take the following steps:
1. Run the Windows Update Troubleshooter.
2. Click the Start button , type Run in the search box, and then, in the results list, click Run.
3. Copy the following text, and then paste it into the Run text box:
Cmd /c ren %systemroot%\System32\Spupdsvc.exe Spupdsvc.old
4. Click OK.
Best regards,
Fangzhou CHEN
Fangzhou CHEN
TechNet Community Support

G41 Fails to boot after updating BIOS

I hope that somebody has some suggestions, and thank you in advance.
I am helping out a friend who has inherited a 2881-22U. I have managed to successfully upgrade to an 120GB HD and copy the Recovery partition to the drive. (Hey, you use what you can in education). I have gone through the reinstall process successfully several times, and have worked for two weeks with several test WinXP loads so I know that the system works properly.
In checking the support website, of course, I noticed that there was a BIOS update (1XET57WW) and so I did the 1xuj15us.exe non-diskette update. It successfully completed and then rebooted automatically. Windows then failed to load - it hangs during the load process. With trying to boot in Safe Mode & with logging, it would appear that the system hangs after loading drivers\mup.sys (normal configuration) or drivers\agpcpq.sys (safe mode).
If I press the Access IBM button, the recovery partition (IBM Rescue and Recovery) software runs OK, and when if I select "Restore factory contents", it properly completes the format & copy, reboots, does the first automated batch file sequence, reboots and then hangs (at the same place as described above, never getting to SysPrep).
If I put the original 30GB drive back in, it also fails loading Windows XP at the same spot, now that the BIOS has changed.
The system was previously upgraded to 1GB years ago. The system was purchased in January 2005. The hardware diagnostics pass OK.
Thoughts on what's wrong and possible remedies:
Is there some BIOS setting that got changed that I am not understanding?
Is the BIOS update somehow bad (even though the recovery partition software runs OK)?
Was the recovery partition image upgraded as well when the BIOS was updated? If so, what is the specific part number to get the revised image?
Is there some way I can get a BIOS image rollback to an older version?
Thanks for any responses.
Solved!
Go to Solution.

Solved the problem:
Got the 1xuj15ud.exe diskette BIOS update and got it transferred to a USB flash drive (kind of hard to use a diskette when the system does not have a floppy drive).
Did the update. Reset the BIOS settings again. Voilà, Windows starts loading again.
Why I needed to reflash again, I dunno... Didn't have any sort of error message after the first flash. Certainly wasn't resetting the BIOS settings to default - already did that the first time around.

New HP HDD load recovery disks fails to boot after install process on pressing continue

I have Pavilion d7-4165dx notebook. I live out US, though made purchase from US (BestBuy).
- HDD failed after renewing trial period of virus software.
- All diagnostics would not recognize HDD.
- HP support indicated still in warranty, but I am out of country. HP indicated most likely issue was HDD cable.
- Purchase cables and had someone hand carry out of US.
- Installed, still same response.
- Ordered new HDD from HP. Backordered. Finally on inquiring was directed to a US 3rd part rep. He recommended buying directly from outlet, but a higher speed. Did that and then HP replacement HDD arrives. Hand carry both out of US.
- Install faster (slightly smaller) Seagate 500G 7200. Started recovery with recovery disks (5 total that received from BestBuy, but not OEM looking), but is squawked as new HDD is smaller than original WD 640G 5400. Put WD into #1 bay and Seagate into #2.
- Start recovery disk process. Go through entire recovery from factory process and on last disk, it says to not touch while PC boots on and off, etc. Then says press Continue to continue.
- When press continue, simply goes to black screen with "No boot device..."
- Run other options, same message.
- Ran diagnostics. HDD all OK.
- Called HP support. He indicates I need to buy the HP recovery disks. The ones I have (5) are not the right one, that there should only be 3! They are as I received from BestBuy, but look like they were made there when BestBuy sets up the PC.
Any suggestions anyone?
This question was solved.
View Solution.

Sorry, I don't have an answer, but rather a similar issue. I replaced a 320Gb - 5400 rpm drive that failed with a 750Gb - 7200 rpm drive and even though I have the factory restore disks, it won't recognize the hard drive and I too get the "No Boot device" message. Unfortunately, the BIOS is not the best and it won't allow me to see if it actually recognizes the new hdd, which I suspect it doesn't. Either that or I have a bad MB.
Sytem information - HP G71-340US
Processor - 2.20 GHz Intel Core2 Duo Processor T6600
BIOS - InsydeH20 3.5
Recovery manager *appears* to be installing W7 just fine, but it's a no go when it's time to actually boot to it. Is this a mb issue or did I just buy the wrong hd?

Machine fails to boot after setting locale

Hi,
I am trying to set the locale during the jumpstart. In my profile I set
locale en_US.UTF-8and in sysidcfg I set
system_locale=en_US.UTF-8The locale is correctly installed and /etc/default/init looks like
TZ=Europe/Stockholm
CMASK=022
LANG=en_US.UTF-8However when I type locale, I get
# locale
LANG=C
LC_CTYPE="C"
LC_NUMERIC="C"
LC_TIME="C"
LC_COLLATE="C"
LC_MONETARY="C"
LC_MESSAGES="C"
LC_ALL=Using some info from
http://docs.sun.com/app/docs/doc/817-2521/6mi67tj5d?a=view
I changed the /etc/default/init to look like
TZ=Europe/Stockholm
CMASK=022
LANG=en_US.UTF-8
LC_ALL=""
LC_CTYPE=""
LC_NUMERIC=""
LC_TIME=""
LC_COLLATE=""
LC_MONETARY=""
LC_MESSAGES=""However when I reboot my machine, I get the following error from SVC:
Boot device: /pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2/disk@0,0:a File and args:
SunOS Release 5.10 Version Generic_118833-18 64-bit
Copyright 1983-2005 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
libscf.c:2060: scf_pg_get_property() failed with unexpected error 1007. Aborting.
Sep 1 16:26:50 svc.startd[11]: restarting after interruption
libscf.c:2060: scf_pg_get_property() failed with unexpected error 1007. Aborting.
Sep 1 16:26:51 svc.startd[14]: restarting after interruption
libscf.c:2060: scf_pg_get_property() failed with unexpected error 1007. Aborting.
Requesting maintenance mode
(See /lib/svc/share/README for additional information.)
Root password for system maintenance (control-d to bypass):Any ideas?

I booted up the system in failsafe, than he asked me do i want to mount rw the / fs? tap y
then chmod 755 /a/etc/default/init
vi /a/etc/default/init
erase the LC_ALL line, and save, chmod 555 /a/etc/default/init
then reboot
it worked me fine

P67A GD55 Windows fails to boot after flashing

Hi!
Tried to update my bios today using Live Update 5. Everything went according to plan until it was time to reboot after the succesful flashing. It started booting and everything was fine. The windows loading screen appears but then i get a message that something is wrong and it tries to repair it. Of course this fails and i've also tried to do a system repair using a back up.
I'm running windows 8 64-bit.
Got a Intel i7 2600k 3.4ghz cpu.
The old bios was from 2010 something.
I cannot get into the bios either when pressing f8 or del.
Any help is appreciated.

Quote from: xmad on 06-December-12, 07:33:29
7681v1C.zip
>>Use the MSI HQ Forum USB flasher<<
http://www.msi.com/product/mb/P67A-GD55.html#/?div=BIOS
Try to re-flash to 1C, make sure to use the forum flash tool. You will need to install the tool on another computer and use that computer to prepare the flash drive.
Then try to boot from the flash drive.
1 min just in case I am going to attached special archive. Make sure that is your board.
Use option 1 of the forum flash tool and point it at the attached archive. This will flash you ME version as well if needed.
That is my board. Can i use that forum flash tool on a mac? I only have mac computers in my house except for my gaming rig.
Edit. I read in the thread you can only use it on Windows systems. Guess i will have to wait until tomorrow and borrow a Windows computer. Is there a chance the whole Motherboard is garbage now?

Acer aspire 5560g Failing to boot after Firmware update

Hey guys, So i recently upgraded my Aspire 5560g to Windows 8.1. I liked it but it seemed to have lost my drivers in the process (my track pad scrolling didnt work and my Dolby audio origram was gone). I went to for the drivers and decided to start with a firmware upgrade (9545 for hard disk performance). After the computer rebooted, I entered the dreaded Windows 8.1 boot loop. It would say "Your PC ran into problems..." with the bluescreen, then turn off. Then it would attempt the Automatic repair, and fail again, then restart the cycle. I wasn't able to even get into my BIOS until I cleared my CMOS, now at least I can get into BIOS. I created a bootable USB for Windows in hopes I could do a clean install, but even when trying to boot from a USB I get the blue Windows 8 screen, "Your PC ran into problems..."
Is there a way I can undo the firmware update, it seems like the culprit, doesn't it? Any help appreciated. Thanks EDIT: I've read that the Windows boot loop may be caused by outdated drivers. Think this could be the problem after I did the firmware update? How can I install the drivers without being able to boot into Windows? Thanks

Okay, I tried each stick at a time in both slots with the same results. Windows blue screened on both the HDD and the bootable USB. Isn't it too much of a coincidence that it started acting up after the firmware update?
To be clear, it was a firmware update for the BIOS. The page is here for the Aspire 5560G: http://us.acer.com/ac/en/US/content/drivers I am open to more suggestions, I'd really love to get this working again after dropping the $ on Windows 8

Ubuntu 11.10 failed to boot after (un)successful install on Thinkpad X61

Hello,
I installed Ubuntu from a USB drive and now it won't boot. I get the screen from which I can enter BIOS and manually boot from the USB stick but it won't automatically boot from the HDD. if I don't do that, what happens is that once the BIOS screen disappears all I get is a black screen with a blinking cursor in the top left corner. nothing else happens anymore. pressing down any key has no effect.
Shortly before finishing the installation, I get this message: "An attempt to configure apt to install additional packages from the CD failed". it doesn't say that the installation as a whole failed thought...
Your help is appreciated!

Hi red_revenger,
Can you try formatting the usb in fat32 with the windows (or Linux) tool and after that dump again the ISO image to your usb with unetbootin.
If the problem persist, make a test with another distro, or another version of ubuntu.
If after all steps above you can't still start the system, the problem might be elsewhere. Post back the outcome.
abvasili
I'm just a volunteer. I like to help others where I can. Do my ideas work? I hope so. o_O
Who helped you today? Do not forget to thank him.
My hardware: TP x120e 0596-2ru. Windows 7, sp1, 64Bit, English, installed in UEFI mode.

Persistent USB Arch installation fails to boot after first shut down

Hey all,
I've recently installed Arch on a 32-GB USB flash drive (with the help of the wiki, of course). I have some experience installing arch on my computers, so the process went relatively smoothly. As some background info, I AM using UUIDs in both the bootloader and the fstab file, so that shouldn't be a problem.
Anyways, the problem itself: I have arch installed and ready to go, and it boots up fine (the first time). The thing is, after I shut down, if I try to boot the USB drive again, it simply hangs there-- no boot. What's weirder is not only does it not boot, but it also freezes the host computer at that point in the boot cycle. I mean, everything will be frozen up at the startup BIOS/splash whatever screen when the USB key is in, but once I take it out the computer will boot up regularly. It's really strange.
If I reinstall the bootloader on the USB drive then everything works again (that is, until I reboot).
Is the bootloader somehow getting corrupted while shutting down? I have tried using both GRUB and SYSLINUX (not at the same time of course) but they both behave the same.
Any help would be greatly appreciated.
Thank you for your time,
Ushahin

https://wiki.archlinux.org/index.php/Be … nvironment
Here you need to set the right hooks if the root is on a USB drive, if you use RAID, LVM, or if /usr is on a separate partition.
Did you remember to do this?
If not, mount the partition(s) starting with the root partition first, chroot into it, edit that file and re-generate the initramfs. Then reboot with the reboot command, don't forcefully shut it down using the power button or something like that.
It could also be a BIOS issue. Restore its defaults, set "Removable Dev." first, "CD-ROM" second (if you have an optical drive), "Internal Storage" third. Then select the USB stick as the first to boot in the boot priority screen.
Last edited by DSpider (2012-10-12 07:07:30)

Macbook Pro fails to boot after any OS update.

Hi, I've been a PC user all my life so please be patient!
I have a mid 2010 MBP running 10.6.3 with Win7 on a boot camp partition. I have read and followed the instructions regarding boot issues from many sources on these forums but nothing so far has solved my problem.
I can install anything via software update as long as it isnt an OS update. Any OS update installs fine but the MBP will not reboot afterwards; I get an endless spinner. I cant boot into safe mode either, endless spinner again after the progress bar dissappears.
I have verified and repaired the disk in single user mode and via the disk utilities tool after booting into the install DVD, I have repaired permissions I have tried just about every instruction I could find, I have read posts where people are talking about replacing ACPIPPlatform.kext and IOPCIFamily.kext but I'm not sure this applies to me as they seem to be saying to lift those files from 10.6.6 / 10.6.7 and I cant event get to 10.6.4.
Just to be clear, I cannot update to anything above 10.6.3. I have tried combo and single updates for every patch version from 10.6.4 up to 10.6.8 and the MBP will not reboot after any of the OS updates. The only way I can get the machine to boot again is to wipe the Mac partition and re-install 10.6.3. So, am I doomed to be stuck on 10.6.3 forever?
To add insult to injury, of course Windows 7 works perfectly
I have no obvious HD issues, once I reinstall 10.6.3 everything works perfectly.
It did cross my mind that the only thing I haven't tried is to strip the win partition off completely and put the MBP back to pure mac and see if the updates work then but thats a lot of hassle (its a dev machine) so I thought I'd ask if any of you fine people might be able to help me out before I go for the nuclear option.
Thanks.

Put a bootable backup/clone of your 10.6.3 volume onto an ext FWHD using something like Carbon Copy Cloner or SuperDuper!, boot from it, and try updating to 10.l6.8. If that works, then finish updating everything, and reverse the process. If not, then, try the nuclear option. I don't do windoze, so you'll have to figure out to back that stuff up before proceeding.

Solaris 10u6 fails to boot after installation on HP Proliant DL380 G4

Hello,
I have used Solaris 10u5 without issues on the HP DL380 G4. However, when I tried to install update 6 (new installation), it fails to reboot. I starts to boot, then aborts and reboots the system. I added the arguments -av to help get more information. Here's what I was able to capture:
Enter default directory for modules [platform/i86pc/kernel /kernel /usr/kernel]:
module /platform/i86pc/kernel/amd64/unix: text at [0xfffffffffb800000, 0xfffffffffb8d5f0f] data at 0xfffffffffbc00000
module misc/amd64/krtld: text at [0xfffffffffb8d5f10, 0xfffffffffb90a89f] data at 0xfffffffffbc74ce0
module /kernel/amd64/genunix: text at [0xfffffffffb90a8a0, 0xfffffffffbb04f4f] data at 0xfffffffffbc7ee00
Name of system file [etc/system]:
SunOS Release 5.10 Version Generic_137138-09 64-bit
Copyright 1983-2008 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
features: 14dffdf<cpuid,mwait,cx16,sse3,asysc,htt,sse2,sse,sep,pat,cx8,pae,mca,mmx,cmov,pge,mtrr,msr,tsc,lgpg>
mem = 6225476K (0x17bf91000)
root nexus = i86pc
pseudo0 at root
pseudo0 is /pseudo
scsi_vhci0 at root
scsi_vhci0 is /scsi_vhci
isa0 at root
psuedo-device ppm0
ppm0 is /pseudo/ppm@0
npe0 at root: space 0 offset 0
npe0 is /pci@0,0
pcie_pci0 is /pci@0,0/pci8086,3595@2
PCIE-device: pci8086,32a@0,2, pcie_pci3
pcie_pcie3 is /pci@0,0/pci8086,3595@2/pci8086,32a@0,2
NOTICE:
* This device is not bootable! *
* It is either offlined or detached or faulted. *
* Please try to boot from a different device. *
NOTICE:
spa_import_rootpool: error 22
panic[cpu0]/thread=fffffffffbc26ba0: cannot mount root path /pci@0,0/pci8086,3595@2/pci8086,32a@0/pcie11,4091@3/sd@0,0:a /pci@0,0/pci8086
,3595@2/pci8086,32a@0,2/pcie11,4091@3/sd@1,0:a
fffffffffbc49320 genunix:rootconf+114 ()
fffffffffbc49350 genunix:vfs_mountroot+61 ()
I have tried this on two identical machines with the same results. Some other details:
- Booting into failsafe mode works; the system finds and mounts the zfs volumes
- I did a network installation. I rebuilt the miniroot to include the CPQary3 package
- I tried installing with a zpool with two disks as well as only one disk; the result was the same
- I also tried installing without using a ZFS root disk; it also fails
I have googled for this problem but have not found anything like it. I would greatly appreciate any help!
Thanks,
Michael

I finally figured it out. For some reason, the installer does not install the driver package (CPQary3) or include it in the boot archive. The driver is in the fail-safe miniroot, however. So, I booted into fail-safe mode and installed the driver, and now everything works!
I ran into two problems with the installer on this hardware. I'll post details and work-arounds for both in a separate message.

Lenovo E531 failing to boot after it crashed during a Windows 10 update.

Hello guys, A few weeks back I signed up for the Windows 10 insider program and installed the windows 10 ISO without any problems. Of course there were the usual bugs that you get when working with a non-final build of a new OS, but that's not the problem here. A few days ago I received a new update, and after it was done downloading it prompted me to upgrade to the new version, which I complied to. Halfway the installation I suddenly get the " Oops, something went wrong, we're collecting information and rebooting your pc" pop-up screen. The error had something to do with installing a driver. After it rebooted I just stared at a black screen. Since then I'm not able to boot into windows anymore. Bascially what happens is when i boot, i get the usual bios screen and the Lenovo splash screen. But followed by a black screen with absolute no information. Apart from one single '-' .When pressing 'enter' I hear a beep, and the "boot interruption" screen pops up with various options. Like booting into the Bios to change settings, and to temporarily chose a different boot device. Getting into the Bios settings is no problem, and i can change anything (I resetted the settings to default just to be sure, which didnt do anything). But as soon as I try to chose a different boot device, I get the same black screen. So I am not able to boot my windows 10 Preview installation DVD. I even tried booting without the HDD installed, which gave me the same screen again. I did all the diagnostics test from the lenovo diagnostics screen, which all resulted in no problems found. It recognizes the HDD, and the DVD when i get the Bios splash screen. Does anyone have an idea on how to fix this? Thanks so much in advance.

Thanks for the reply. I tried updating the BIOS by running the .exe on a different pc and burn the BIOS the a CD, and even tried a USB.The thing is that when i want to boot from a CD or USB. I never get the option to do so. Always a black screen. I've contacted Lenovo support via phone and they told me that I had to buy a recovery disc from https://www.lenovorecovery.com. Which I did. The person on the telephone even told me that it didnt matter what the boot order was, This recovery disc would instantly boot. After i received these discs and tried to boot from them, it didn't work. Just as every other bootable DVD/USB I tried.See below for a pic from my laptop screen. Now I don't see any other option other than sending it to a repairshop to get the bios chip replaced... Any ideas? Thanks! https://www.dropbox.com/s/sdln9jnysc8vmas/2015-08-10%2013.49.26.jpg?dl=0

IMac fails to boot after restart. Shows folder icon with ?

I have managead to boot up from start up disc previously. I did a hardward scan and it stated my hardware was fine. It is my understanding the folder icon with the "?" means that the iMac can't find the OS. I thought maybe I had a corrupted spot on my HD where the OS is, and tried to re-install, and I wasn't allowed to re-install. Do you think my HD is bad, or maybe I have a virus? I'm ashamed to admit that my anti-virus software had been expired for a bit. I should also mention I am running OSX Tiger. I know, bad Apple geek, but it more than served my needs. This is last ditched effort before I take it in for service.

Highly unlikely it's a virus.
The question mark on startup can mean several things. One the hard drive is failing or failed or your Mac cannot locate a System Folder to boot from.
Try starting up while holding down the Option key. If there's a volume to boot from you'll see the Startup Manager window where you can select the startup disk to restart from.
A flashing question mark appears when you start your Mac
and tried to re-install, and I wasn't allowed to re-install.
Not a good sign.

Fail to boot after thunder storm

Similar Messages

Maybe you are looking for