Arch won't boot on Virtual Box afted updating

I instaled Arch as guest on Vbox, after updating, it won't boot any more. It prints the message "Loading udev...SCSI subsystem initialized" and then the VM crash and the window is inmediately closed.
I searched on the Vbox forum and others have the same problem.
See: http://forums.virtualbox.org/viewtopic. … 890#p83890
Probably is an issue with Arch, because a clean install from core iso does work, but does not after updating.

What do you mean under updating ? pacman -Syu ? And what packages was installed?
Isn't there any virtualbox log or something ?

Similar Messages

[SOLVED] Arch won't boot after I created a separate /var parition

Arch won't boot after I created a separate /var parition on an existing installation.And let me confess: it was maybe stupid trying to do it on an existing install.
I edited the fstab correctly, copied the files using rsync preserving permissions. Then I kept a backup of /var using tar. Then went on to delete everything under /var, ie /var/*, the /var folder is still there. All this I did from a live CD. After that I booted into my arch linux. Here I get messages about systemd successfully finishing fsck on each of my partitions, then the screen starts blinking. And there is no more output. Pressing Ctrl+Alt+Delete causes systemd to stop its services and reboot.
Having realized I had borked my system, I removed the /var line from fstab and restored /var from the tar file I made earlier. Again I did this from a live cd. Rebooted into my arch system, and again similar issues, namely that after fsck and messages informing a few services had started, the screen keeps blinking.
The live cd I used for reorganizing my partitions was elementary OS freya. They have GParted in there. I also have an arch install iso lying aroung from May 2013. If necessary, I can download the latest version. I am currently typing from a Windows installation I dual boot from.
I don't know how to extract any boot logs as I am locked out of the system. Here is my fstab in any case:
# Filesystem information
# /dev/sda5 LABEL=fs_root
UUID=b9d739cf-fd8c-46dd-a919-bd827dc47c66 / ext4 rw,noatime,data=ordered 0 1
# /dev/sda9 LABEL=fs_var
UUID=ec0f7a49-dccd-43ab-8651-9aa3fdb41cc7 /var ext4 rw,noatime,data=ordered 0 2
# /dev/sda2 LABEL=fs_boot
UUID=0e8ab31a-3bda-4b85-a901-a36f21b1583d /boot ext2 rw,noatime 0 2
# /dev/sda6 LABEL=fs_home
UUID=d9e63c47-274e-447f-ad01-0d97afe0fd34 /home ext4 rw,noatime,data=ordered 0 2
# /dev/sda7 LABEL=fs_swap
UUID=7301227c-e9f3-41b8-9d0f-4cf3c159491c none swap defaults 0 0
# /dev/sda3 LABEL=fs_win
UUID=12B639D1B639B5D7 /fs_win ntfs uid=1000,gid=1000,dmask=027,fmask=137,showexec,nofail,noauto,x-systemd.automount 0 0
# /dev/sda3 LABEL=fs_share
UUID=D272269772268079 /fs_share ntfs uid=1000,gid=1000,dmask=027,fmask=137,showexec,noauto,nofail,x-systemd.automount 0 0
I would greatly appreciate any help.
Last edited by richcocoa (2015-05-03 18:04:44)

Have you moved everything from /var to /new_var (i named it for learning purpose)? You shoud copy content from /var but not on the fly but booting from arch iso cd, and than you shoud mount your / into arch-chroot environement, mount all of your mount points and than copy content from default /var to new /var. The copying should be done with this
cp -rax
and you can add -v switch to verbose output. I have my own /var moved the same way.
The simples way is:
-boot the arch iso cd
-mount all of your mount point (i created here in this step /new_var to move /var to a new place, and this /new_var i put in /etc/fstab as /var later)
-copy /var to /new_var with -rax or -vrax (recursive, archive, this filesystem or verbose, recursive, archive, this filesystem switches)
-umount all of it
-reboot.
Last edited by firekage (2015-05-02 07:49:20)

Arch won't boot, FS not detected, Kernel Panic.

Ok so here is the situation. I have arch linux installed on sda1, which is a sata drive, samsung. Seems lately I been having problems getting arch to boot because it doesn't know what type filesystem my root device has. It goes on and tells me that I can use the kernel parameter rootfstype= to solve the issue, but yet when I try this, it does nothing. I stop getting the error, about unknown FS type, but arch still won't boot. Init fails...
I have tried everything on these forums to fix the problem and not one thing in general has solved the issue. What seems to be most consistent about this problem, is it takes me at least 20 - 30 times of rebooting before it will finally go through and boot. But, even then this is not foolproof. Last night I tried at least 30+ times of rebooting, powering off and still it would not boot.
So after reading the forums some more I found an article somewhat related to my problem and it was suggested that I add my root FS type as a module and then remove the filesystem hook in mkinitcpio.conf. I tried this approach and at the same time downgraded to 2.6.24.2-1 kernel26 so mkinitcpio would generate the new image. Then I rebooted and arch loaded just fine. So then I rebooted and again, unknown fs type on root device error.
So I retraced my steps and tried the same process again, only this time when I rebooted I got same problem. So as it seems, nothing I did to mkinitcpio.conf did anything to alleviate my problem.
As of right now, I managed to get the fallback image to work(but fallback does not load all the time, just this last time I tried it it worked), but I am scared to death to turn off my machine because I know it's not gonna reboot without a lot of hassle.
So can anyone help me diagnose this problem? What can I do to get the kernel to boot and mount the root device with ext3 and pass init on boot up? I am completely lost when it comes to this...
here is my mkinitcpio.conf
# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run. Advanced users may wish to specify all system modules
# in this array. For instance:
# MODULES="piix ide_disk reiserfs"
MODULES="ext3 pata_amd ata_generic sata_nv"
# BINARIES
# This setting includes, into the CPIO image, and additional
# binaries a given user may wish. This is run first, so may
# be used to override the actual binaries used in a given hook.
# (Existing files are NOT overwritten is already added)
# BINARIES are dependancy parsed, so you may safely ignore libraries
BINARIES=""
# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in anyway. This is useful for config files.
# Some users may wish to include modprobe.conf for custom module options,
# like so:
# FILES="/etc/modprobe.conf"
FILES=""
# HOOKS
# This is the most important setting in this file. The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added. Run 'mkinitcpio -H <hook name>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'modload' may be used in place of 'udev', but is not recommended
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
# This setup specifies all modules in the MODULES setting above.
# No raid, lvm2, or encrypted root is needed.
# HOOKS="base"
# This setup will autodetect all modules for your system and should
# work as a sane default
# HOOKS="base udev autodetect pata scsi sata filesystems"
# This is identical to the above, except the old ide subsystem is
# used for IDE devices instead of the new pata subsystem.
# HOOKS="base udev autodetect ide scsi sata filesystems"
# This setup will generate a 'full' image which supports most systems.
# No autodetection is done.
# HOOKS="base udev pata scsi sata usb filesystems"
# This setup assembles an pata raid array with an encrypted root FS.
# Note: See 'mkinitcpio -H raid' for more information on raid devices.
# HOOKS="base udev pata raid encrypt filesystems"
# This setup loads an lvm2 volume group on a usb device.
# HOOKS="base udev usb lvm2 filesystems"
HOOKS="base udev autodetect pata sata"
here is my fallback.conf
# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run. Advanced users may wish to specify all system modules
# in this array. For instance:
# MODULES="piix ide_disk reiserfs"
# BusLogic is added to support VMWARE arch booting in fallback image
MODULES="BusLogic"
# BINARIES
# This setting includes, into the CPIO image, and additional
# binaries a given user may wish. This is run first, so may
# be used to override the actual binaries used in a given hook.
# (Existing files are NOT overwritten is already added)
# BINARIES are dependancy parsed, so you may safely ignore libraries
#BINARIES=""
# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in anyway. This is useful for config files.
# Some users may wish to include modprobe.conf for custom module options,
# like so:
# FILES="/etc/modprobe.conf"
FILES=""
# HOOKS
# This is the most important setting in this file. The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added. Run 'mkinitcpio -H <hook name>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'modload' may be used in place of 'udev', but is not recommended
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
# This setup specifies all modules in the MODULES setting above.
# No raid, lvm, or encrypted root is needed.
# HOOKS="base"
# This setup will autodetect all modules for your system and should
# work as a sane default
# HOOKS="base udev autodetect ide scsi sata filesystems"
# This setup will generate a 'full' image which supports most systems.
# No autodetection is done.
# HOOKS="base udev ide scsi sata usb filesystems"
# This setup assembles an ide raid array with an encrypted root FS.
# Note: See 'mkinitcpio -H raid' for more information on raid devices.
# HOOKS="base udev ide filesystems raid encrypt"
# This setup loads an LVM volume group on a usb device.
# HOOKS="base udev usb filesystems lvm"
HOOKS="base udev ide pata scsi sata usbinput raid filesystems"
modules I need
sudo mkinitcpio -M
Password:
Modules autodetected:
ata_generic
libata
pata_acpi
pata_amd
sata_nv
cdrom
ide-core
amd74xx
generic
forcedeth
sd_mod
sr_mod
usbcore
ehci-hcd
ohci-hcd
jbd
ext3
Last edited by jacko (2008-04-15 19:53:35)

I had a similar issue (I think, can you post the exact error the kernel panics with to check?) and it seemed grub or the kernel had difficulties with finding my root device which was specified as a device node in /dev. The solution for me was to change the root parameter in my kernel line in grub's menu.lst to root=/dev/disk/by-label/<label>, I'm sure UUID and such will work fine too. After doing that I haven't encountered a single such kernel panic. More info about persistent device naming can be found here.

Arch won't boot after rEFInd update

I've followed https://wiki.archlinux.org/index.php/UEFI_Bootloaders as closely as I can, but still can't get Arch to boot. It doesn't even get to the boot loader.
uname -m
x86_64
Partitions:
Device Type Name
/dev/sda1 Linux filesystem root
/dev/sda2 Linux filesystem boot
/dev/sda3 EFI System efi
/dev/sda4 Linux filesystem var
/dev/sda5 Linux filesystem home
lsblk
Name Type Mountpoint
sda disk
sda1 part /
sda2 part /boot
sda3 part /boot/efi
sda4 part /var
sda5 part /home
Directory tree:
/boot/
efi/
EFI/
arch/
initramfs-arch-fallback.img
initramfs-arch.img
refind_linux.conf
vmlinux-arch.efi
refind/
icons/
refind.conf
refind_x64.efi
initramfs-linux-fallback.img
initramfs-linux.img
vmlinuz-linux
/boot/efi/EFI/arch/refind_linux.conf:
"Default boot" "root=PARTUUID=d368616d-a423-4511-88df-f2f645079bab ro rootfstype=ext4 add_efi_memmap system.unit=graphical.target"
"Boot to terminal" "root=PARTUUID=d368616d-a423-4511-88df-f2f645079bab ro rootfstype=ext4 add_efi_memmap system.unit=multi-user.target"
ls -l /dev/disk/by-partuuid/
lrwxrwx 1 root root Jan 30 1:08 d368616d-a423-4511-88df-f2f645079bab -> ../../sda1
efibootmgr -v
BootOrder: 0018, ...
Boot0018* Arch Linux (rEFInd) HD(3,0,0,74930800)File(EFI\refind\refind_x64.efi)
Anything else I'm missing? By the way, I think this is related to the Jan 27. update to refind. Today was the first time I've rebooted my computer since then.
Also - I tried both commenting and uncommenting scan_all_linux_kernels in refind.conf. No dice.
Thank you very much!
EDIT: Some updates...
I was poking around the UEFI shell. The following commands caused my computer to hang (I had to hard-restart):
Shell> fs0:
FS0> ls
I could ls just fine using shell 1.0, but shell 2.0 caused a hang. Then, after the hard restart, more strange behavior:
Shell> bcfg boot add 0 fs0:\EFI\refind\refind_x64.efi "Test"
Error. The file 'fs0:\EFI\refind\refind_x64.efi' did not open.
Also, I can "bcfg boot dump" just fine, but if I want to scroll through the output, I get an error, and it hangs, so I have to hard restart again.
Shell> bcfg boot dump
// bunch of output
Shell> bcfg boot dump -b
// after printing five boot entries...
Press ENTER to continue or 'Q' to break:
ASSERT_EFI_ERROR (Status = Not Ready)
ASSERT c:\dev\edk2top\ShellPkg\Library\UefiShellLib\UefiShellLib.c(3223) : !EFI_ERROR (Status)
Not sure if any of that last but is relevant. Thanks again.
Tried downgrading kernel to 3.6, still won't boot.
Last edited by MitchellSalad (2013-01-30 20:05:10)

MitchellSalad wrote:
Partitions:
Device Type Name
/dev/sda1 Linux filesystem root
/dev/sda2 Linux filesystem boot
/dev/sda3 EFI System efi
/dev/sda4 Linux filesystem var
/dev/sda5 Linux filesystem home
/boot/efi/EFI/arch/refind_linux.conf:
"Default boot" "root=PARTUUID=d368616d-a423-4511-88df-f2f645079bab ro rootfstype=ext4 add_efi_memmap system.unit=graphical.target"
"Boot to terminal" "root=PARTUUID=d368616d-a423-4511-88df-f2f645079bab ro rootfstype=ext4 add_efi_memmap system.unit=multi-user.target"
ls -l /dev/disk/by-partuuid/
lrwxrwx 1 root root Jan 30 1:08 d368616d-a423-4511-88df-f2f645079bab -> ../../sda3
Shouldn't that be sda1? Your root-partition is /dev/sda1.

Intel D2700DC + Arch won't boot without display

I've faced really wierd (to me) problem running Arch as mini webserver on the Intel D2700DC mini-ITX board with Atom D2700 integrated and NM10 Express chipset.
I successfully installed the system, configured network and started sshd to continue setting up other services remotely via ssh console. Then I disconnected the keyboard and display from the case and put it under the table. After that I was quiet surprised that the system was not starting up anymore.
After some investigation I've found that the system is not booting if no display is attached to the DVI port of the motherboard. If I start the system with display disconnected, I can hear one beep that notifies about successful BIOS POST, HDD led blinks 2-3 times, and then just nothing happens. System isn't booting up. If I attach the display right after that - nothing is seen on the screen, and display is immediately falling into sleep mode. Keyboard is still active though, and if I press ctrl+alt+del - the system is restarting, and, if display was just connected, it boots ok then. Also it boots fine from the cold state if the display was attached to the DVI port at the time of powering on.
As I can assume from the timings and HDD led blinking, the boot process stops right after GRUB is loaded. There's nothing in system log, cause it seems that boot hangs just before the kernel is loaded by GRUB. I'm really stuck and don't know how to work around this situation, because if the display was disconnected when system was powered on - then there's no way to see anything on the screen until next reboot, and if the display was connected - then the system boots OK.
One more thing to notice:
There was an old CentOS installation on the HDD, to which I installed Arch Linux. I've tried to boot it once or twice before installing Arch, and, as I could remember, it could boot up without display connected, on the very same hardware. So I suppose it's definitely something in Arch that is preventing the system to boot without the display.
I guess that when no display is connected at boot time, NM10 chipset completely disables onboard video, and because of this we can't see anything on the display until the system is restarted. But this somehow affects Arch, so it can't boot without any video hardware present.
Last edited by rand256 (2012-05-10 10:23:28)

I'm afraid there's no such option, but it looks like arch isn't booting just because no graphics card is detected in the system when display it disabled during powering up.
There is a couple of similar topics about some other linux distros can't boot without video card inserted ([1], [2]) with some recommendations on what to do in such a case.
I've followed them - including enabling serial console in /etc/inittab, setting nomodeset in kernel line in grub's menu.lst, checking for enabled splash-screens... but that didn't help.
Does anyone know what options should be tuned in order to boot Arch without any active graphics card present in the system hardware?

Arch Won't Boot After Kernel Upgrade

I installed Arch on VirtualBox, but after upgrading the Kernel to 2.6.30 it wouldn't boot. It gets to "Loading udev...." and then VirtualBox crashes.

Hello, I'm having this same problem, except I'm not using VirtualBox or VMWare, I have Arch installed to the hard drive. It worked fine after upgrading to 2.6.30, but after upgrading kernel-headers to 2.6.30.1-1, neither Arch NOR Arch-Fallback will boot! I don't even get to Udev or the part where the two arch logos are on top. It just starts up a little bit, then restarts my computer.
I don't even know if my system has been wiped or something, but I doubt that; I think it's just the booting process. I do have a 2009.2 Live CD, but it's an FTP installation. Is there any way to start up my live CD and do a pacman -U for the old kernel version with the cache on my hard drive? How would I do this?
Last edited by Allamgir (2009-07-07 00:32:12)

[SOLVED] Enabled AHCI - Arch won't boot

I have switched the SATA preference to AHCI from IDE in the BIOS. Now Arch refuse to boot with following warning:
ERROR: device '/dev/sda2' not found. Skipping fsck.
ERROR: Unable to find root device '/dev/sda2
[rootfs /]#
I have checked the WIKI and it has a remedy with 'mkinitcpio'; looks outdated. I have also found about adding one moule to initrd with mkinitrd on the www. However, I am not sure and need some guidance regarding this.
By the way, I dual-boot with Ubuntu and it booted just fine after the switch to AHCI.
Thanks.
Last edited by fantab (2013-04-21 22:27:38)

Thanks guys I fixed it from Ubuntu with 'chroot'. I added "ahci" to MODULES in /etc/mkinitcpio.conf and ran mkinitcpio.
I can boot Arch now.
Do I have to re-install the kernel? Do I have to add "ahci" to mkinitcpio.conf at every kernel upgrade and run mkinitcpio? Or am I OK.
Out of curiosity, regarding 'fallback image', how is it "even simpler"? Would love to know, for future reference, any pointers?
Last edited by fantab (2013-04-21 21:39:57)

[SOLVED] Arch will not boot all the way after update

Hey all,
I feel really stupid about this one, but I really need some help.
Today I updated my system and eventually during that session I decided to turn off the computer using "shutdown -h 0". This resulted in an error. I tried simply "reboot", but got the same message. I stupidly did not write down the message and then even more stupidly just held down the power button to turn the computer off thinking that I could boot back in later, get the same message, and deal with it then.
However, when I booted up, I was confronted with a screen telling me that "/dev/sda3" was recovering, the orphaned sectors, and the fact that sda3 is clean. All of it seemed to be expected after an improper shutdown, but it won't boot any further. I tried turning it off and on again a couple times, but it is still stuck on that screen. It doesn't describe the orphans anymore, but it still says it is recovering the journal.
I'm not sure what to do. Any help would be appreciated. I did look for posts concerning the recent update and found this: https://bbs.archlinux.org/viewtopic.php?pid=1370237, but I don't know if I have the same problem.
Last edited by MongooseOfPower (2014-01-14 01:23:43)

Thank you for the reply.
After waiting on that screen for at least 20 minutes, It started displaying systemd[1] errors. If it would be helpful I could type them all out, but they are all just Dependency or Time out fails.
After a while it displayed a welcome to emergency mode greeting and after a couple minutes finally let me give the root password. I straight out tried "journalctl -xb" which responded with:
journalctl: error while loading shared libraries: libcrypt.so.20: cannot open shared object file: No such file of directory
Periodically I am now getting this error:
systemd[1]: Failed to start Trigger Flushing of Journal to Persistent Storage.

G4 450 MP won't boot after 10.4.8 update

My main disk is a 160Go on a PCI IED card (acard)
After Software update did its thing, the computer won't boot on this disk.
It displays the apple logo, then nothing (no spinning thing). There are display artifacts (blanck line on top of screen, sometimes the grey background turns blue)
I tried zapping the PRAM, reinstalling the combo update, removing third partry cards to no available.
I tried plugging the disk on the integrated IDE channel (but I know my computer does not support disk larger than 120 Go)
Any one has an idea ?
G4 450 MP Mac OS X (10.4.7)

I verified and repaired permissions on both disks, updated the new system to 10.4.7 and ran Migration Assitant, which, aside from giving wild estimates of time remaining and not copying the Developer folder, did indeed work magnificently. Not going to bother with cloning back to the original drive.
Gulliver:
1)Umm, yes, I didn't bother repairing permissions before updating to 10.4.8, but the only way to know if that caused the problem is to try updating the new system. I'm not that curious. I think scb is not impressed with repairing permissions.
2)Removing 3 PCI boards and swapping the processor and then putting it all back together everytime there is a system update is not an option. Besides, if it doesn't work with the 3rd party hardware, then I wouldn't want to bother updating anyway. Next time, I'll try updating on another drive first.
Anyway, everything is running well again. Thank you for your help.

Early 2008 Macbook won't boot after 10.7.5 update?

Updated to 10.7.5, when it rebooted to do the install, there was an error message, and now the machine won't boot. Stuck on grey screen with spinning wheel.... reset PRAM, Disk utility says drive is OK... still no luck. ??
Looks like this has hit the news. Any update from Apple? I would take it to the apple store, but there's a mob becuase of the new iPhone, so..... yea.
Apple, please fix this. And bring back Google Maps to IOS while you're at it.

Updated to 10.7.5, when it rebooted to do the install, there was an error message, and now the machine won't boot. Stuck on grey screen with spinning wheel.... reset PRAM, Disk utility says drive is OK... still no luck. ??
Looks like this has hit the news. Any update from Apple? I would take it to the apple store, but there's a mob becuase of the new iPhone, so..... yea.
Apple, please fix this. And bring back Google Maps to IOS while you're at it.

Computer won't boot after installing latest iTunes update

Won't boot after the apple screen. Turns black and disk stops Help! Was running Mavericks.

Hi Neodoc,
Welcome to the Apple Support Communities! I understand that your MacBook Pro will not boot past the Apple logo. There may be a few troubleshooting steps I would recommend for this situation. The following article outlines the steps to perform to get this resolved for you.
Mac OS X: Gray screen appears during startup
http://support.apple.com/kb/ts2570
I hope this helps,
-Joe

Powerbook G4 won't boot after 10.4.10 update

Hi,
Looking for help with the following problem. Last week, I updated my Powerbook G4 to 10.4.10 and since then the system fails to boot. The failure may or may not be linked to the update, but the timing is suspicious.
When I attempt to book the system, it hangs with the spinning daisy wheel at the gray screen with the apple logo. It won't boot from the Tiger install DVD; doesn't seem to get as far as looking for the DVD.
If I boot into single user mode and run fsck -fy, the command reports a number of block count errors when checking the catalog file and then fails while a "disk0s3: I/O error. Invalid key length (4, 20821).
I don't want to lose the data in disk if at all possible and I'd like to know;
(a) can this be repaired using a more powerful disk utility such as DiskWarrior?
(b) is this worth taking to the Genuis Bar for further work?
Thanks.

*Invalid key length* indicates a disk directory problem that should be fixable with DiskWarrior. To boot with the install DVD, pop it in, restart, holding down the C key. If that doesn't boot the machine, leave it in, restart, holding down the OPTION key, and see if it shows up when the Startup Manager finishes loading. If so, click on the DVD icon and click the right-hand arrow. The left=hand arrow will search for bootable disks, which it already did.

BP won't boot up after 2.0 update?

Updated my Balckberry Playbook this afternoon and now it's dead! It won't boot and no lights are showing??? Help!

Hey beepbop,
Can you try to use the steps in the workaround listed in the following link?
http://www.blackberry.com/btsc/KB26748
Hopefully that will help, but if not, I would contact PlayBook Support. You can get their info here:
http://ca.blackberry.com/support/playbook-support/contact.jsp
If you want to thank someone for their comment, do so by clicking the Thumbs Up icon.
If your issue is resolved, don't forget to click the Solution button on the resolution!

My Mac Pro won't boot after installing the latest update

Im running the latest OSX on my mac and recenty did a small updated that i believe contain a few security thing and bug fixs but when restarting the machine after the update it would not boot again after the apple logo has appeard apple script is displayed on the screen contain what i think is boot script failing to run. I have been able to boot the system in safe mode. does anyone have and solution for this as i realy don't want to reinstall the OS
Thanks

The most common cause for "Won't boot after software Update" is Directory Damage that existed before the Update, but was made worse by adding files during the Update.
The most common cure for that Directory Damage problem is to boot in Safe Mode, which takes five minutes to repair the disk, then comes up demanding your username and password, even if you normally auto-login.
Rarely, third-party add-ons are made obsolete by an update. In this case, booting in Safe Mode (with few Apple extensions and NO third-party extensions loaded) works fine, even if normal mode does not work.
Have you tried normal mode again after your Safe Boot?

HP Compaq 6715s won't boot on battery after BIOS update

Hello!
I updated the bios of my HP Compaq 6715s with the latest version F.0E I downloaded from HP support site.
Everything went fine, but now it won't boot on battery alone anymore. It just flashes amber light on power indicator and shuts down. If the charger is connected and later disconnected when it starts loading Windows, everything is fine.
Please help, what should I do?

Hi:
You can try performing a hard reset of the notebook in hopes that it will solve the problem.
Here is the link to the instructions for this procedure.
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&cc=us&objectID=c01684768&prodT...
If that doesn't work, I'm afraid something went kerflooey with your BIOS udpate.
Paul

Arch won't boot on Virtual Box afted updating

Similar Messages

Maybe you are looking for