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)

Similar Messages

  • Won't boot after kernel upgrade

    I installed Arch and attempted to upgrade the kernel. I had to remove these pkgs because the depended on previous kernel:
    ipw3945
    madwifi
    ndiswrapper
    rt2500
    tiacx
    After kernel upgrade, won't boot:
    Root device '....' doesn't exist, attempting to create it.
    ERROR: Failed to parse block device name for  '....'
    ERROR: unable to create/detect root device '.......'
    Dropping to recovery shell...
    This is the final error messages after making the following attempts to correct the problem:
    Added rootfstype=ext3 to kernel line.
    Added rootdelay=8 (then 20) t6o kernel line.
    Replaced UUID moniker with /dev/sda1 (SATA drive).
    Checked /dev/ in recovery shell, no HD's listed.
    Checked /etc/mkinitcpio.conf and it has sata listed under HOOKS.
    Bill

    userlander wrote:did you try the fallback kernel?
    Yes, same result as with the upgraded kernel.

  • [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)

  • Mac mini won't boot after RAM upgrade.

    Tried installing new RAM in my Mac Mini, 512MB stock to 2GB of Crucial. Followed the directions to a T, grounded myself the whole time.
    Things I've tried so far:
    1. Resetting the PRAM, no luck.
    2. Holding option at start-up, shows no icon.
    3. Holding shift, no luck.
    4. Holding X, nothing.
    How do I get it to accept a CD if it won't boot?

    Welcome to Apple Discussions!
    You clearly have a problem, but you don't describe exactly what that is other than that your mini won't boot after the upgrade. What happens when it starts up? Does it attempt to start and hang up on the grey or blue screens, or does it start beeping at you almost immediately after you try and start it up, and also flash the power light?
    If the former, then you may have dislodged a connector while working inside the system, in which case opening it up and checking that everything is firmly connected would be the first thing to do. If the latter, then the beeping/light flashing is the system telling you it has failed the power-on self test and the pattern of beeps/lights indicates why. In your case likely the system can't find workable memory. In that instance, opening the system and ensuring that the RAM is firmly and fully seated would be a good step, and if the mini continues to fail, then replacing the new RAM with the original to test that the system will then start.
    It is not likely that anything had damaged your MacOS install in the process of upgrading, thus normally no reason to need to boot to CD as a result of a RAM issue.

  • [SOLVED] can't boot after kernel upgrade

    I'm on 3.5.4-1-ARCH, then I upgrade to linux-3.5.6-1 and reboot. The result is a message that cant load "autofs4" module. And a "uname -r" says me: 3.5.4-1-ARCH instead of 3.5.6!!
    I've tried to run depmod after the upgrade with de same result.
    Last edited by siot (2012-10-09 20:11:23)

    It sounds as if the new kernel did not find its way to your boot partition.  This could have been because the boot partition was not mounted when you did the upgrade (in which case the file is in the /boot mount point of your root partition) or that you are not booting from the partition you are expecting (Do you, per chance, have two boot partitions?)
    Regardless, boot from an install media and fix it from the command line.  if the files are in /boot of the root partition rather then one the boot partition, mount both volumes and just move the files.  If there are multiple boot partitions, move the files to the correct partition.  Once you reboot, fix the /etc/fstab to point to the correct boot partition.

  • 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.

  • AP350 won't boot after IOS upgrade

    I have an AP350 and after I upgraded the IOS to 12.2.15-JA it won't boot. In monitor mode it tells me there are no bootable images available. I see the new image there. I was having issues with the authentication on this box. This was the reason to upgrade the box to begin with. Now I have more problems here. If anyone can help please I could use it. The old directory where 12.2.13-JA1 was in is not there and the new image is not in a directory either if that helps.

    Please read the attachment. It shows you how to recover IOS from bootstrap. Specifically, please go to "Using the MODE button" in "Reloading the Access Point Image"
    As a side note, you cannot use HTTP interface to upgrade IOS software starting 12.2(15)JA. Below is from release notes:
    TFTP Required to Upgrade 1200 Series Access Points to this Release
    Software upgrades fail when you use the web-browser interface to install Cisco IOS Release 12.2(15)JA on 1200 series access points. The image size exceeds the access point's 4-MB restriction for software upgrades. Use TFTP to upgrade your 1200 series access point to this release. For complete instructions on using TFTP to upgrade access point software, see the "Working with Software Images" section on page 20-18 in the Cisco IOS Software Configuration Guide for Cisco Aironet Access Points.

  • Satellite A200 PSAEOE won't boot after memory upgrade

    Hi, I am first time here.
    I have bought a Toshiba A200 PSAE0E-03J02JDR with 2 GB ram memory. I bought a pair of Corsair ram (2*2GB VS2GSDS667D2). After I installed the memory the computer won't boot. I have intel 945 chipset, which is capable of 4 gb (manual page1-2). The bios version is 1.8 from 2007.
    Can anyone help me, please.
    Message was edited by: ovidiu marian

    Hi
    The A200 series supports different chipsets;
    Intel 945PM
    Intel 945GM
    Intel 943GML
    As far as I know your notebook supports the *Intel 943GML* chipset and this chipset supports max 2GB RAM.
    Take a look in your notebooks user manual *Page 18.*
    Summery: 4GB RAM are not possible and therefore your notebook does not boot up.

  • GE60 2OC won't boot after RAM upgrade...

    Hi forum
    I just upgraded my laptop ge60 2oc 014ne, with two 8 GB corsair value select sticks.
    Now my machine won't boot. I hit the button, the power light turns on, then the harddrive indicator lights for a while... And then it just stands there... Nothing shows on the screen..
    Any help? Please..
    Cheers

    Quote from: NexumxRaptoR on 07-November-13, 23:58:36
    another thing is that you can't put in more RAM than the notebook came shipped with right?
    If it originally had 8GB over 2 slots you can't put in more than 8GB in the entire notebook right? (I thought I read something about that somewhere....)
    Nope. Not true.
    In most cases it's restricted by 1 of 3 things....either the CPU, the IMC (Integrated Memory Controller) or the BIOS.
    MSI is pretty good about NOT restricting it via the BIOS in some way.
    Usually it ends up being the IMC that restricts it, either via a maximum memory (say 32 GB) or via a maximum amount of memory per module (say 8GB).
    Either way, the GE60 I believe should support up to 16GB of memory. I think it should come with 2 memory sockets. You need to ensure that they are 1.35V compatible given the fact that you have a Haswell system.
    http://www.msi.com/product/nb/GE60-2OC.html#specification
    Confirms that it has 2 memory sockets, and supports up to 16 GB of memory, so 2 x 8GB sticks.

  • IMac won't boot after ram upgrade

    For some reason, my iMac late 2013 3.4Ghz quad core i5 won't boot with new ram modules added.  New ram is exact same specs as original that came with the iMac.  I've tested the new ones on their own in the iMac, and the system boots up fine.  Same goes with just using the original ram.  But when I put all 4 together, the iMac doesn't boot up.  Not even the chime.
    Combinations I've tried are:
    1-Old
    2-New
    3-Old
    4-New
    No boot
    1-New
    2-Old
    3-New
    4-Old
    No boot
    1-New
    2-Old
    3-New
    4-empty
    No boot
    1-Old
    2-New
    3-Old
    4-empty
    No boot
    1-New
    2-Old
    3-Old
    4-New
    No boot
    1-Old
    2-New
    3-New
    4-Old
    No boot
    The only combinations that work are:
    1-New
    2-empty
    3-New
    4-empty
    Boot good
    1-Old
    2-empty
    3-Old
    4-empty
    Boot good
    I just got off the phone with Apple, and they are saying all modules have to be the same size. ie. all 4GB or all 8GB. Can't mix and match sizes. Which is strange, because I've never heard of this. My Mac Pro has different speed ram modules, with different sizes in it. As long as I install ram in pairs, it runs like a charm. I've even heard the new iMacs don't have to have ram installed in pairs.
    I'm wondering if slot 2 and 4 are maybe damaged? I haven't tried using just slot 2 and 4. To my understanding, you have to use 1 and 3 first. Can anyone confirm this?
    Also, I've read a couple of people had to wait 30 seconds for the chime when they installed new ram in their iMacs.  I didn't wait 30 sec to see if it would boot.  Never heard of any Mac taking 30 sec to just chime in. lol  Has anyone else experienced this?  Is there a fix?  Tx.

    CLICKY CLICK---> iMac: How to remove or install memory
    Or
    Apple>About This Mac>More Info>Memory:  Double click "Memory Install Instructions" at the bottom right of window.
    my iMac late 2013 3.4Ghz quad core i5
    Conflicting info.  Your system profile shows: Mac Pro, Mac OS X (10.6.8).  Please update/correct.

  • Brand new iMac 27 2011 won't boot after Lion upgrade

    Got a brand new iMac 27 2011 yesterday and did an update to 10.6.8 first before installing OSX Lion over it...
    After restarting it just shows then the "prohibitive icon" on screen and shuts down after few seconds...
    It won't even boot from an USB stick with the OSX Lion image on it...
    Recovery partition works but can't do a reinstall from there....
    So going back to 10.6.8 now...

    Just so you know I purchased brand new imac in July and did the same upgrade as you. I just installed Lion but did not have any issues. Only one concern overall though, it slowed down my new imac a bit. Not sure if there are settings or not but Leopard was faster than this. AppStore, iTunes are eating lot of memory and CPU util goes up.

  • [SOLVED] Arch won't boot after install - "GRUB" on black screen

    I've installed arch on my 1000H from usb stick using zeneee kernel as described in wiki. Right after install everything was fine - wireless and ethernet were working normally, so i've done reboot.
    Now it shows me black screen with "GRUB" text (sic! not "grub>", no error messages) on it. keyboard is not working.
    I've tried reinstalling completely again - with full repartitioning of HDD and this time without installing eee kernel - just stock kernel26. Everithing went ok, i've checked grub settings and partitions - ok, but after reboot - again "GRUB" and non-working keyboard.
    I'm completely out of ideas.
    EDIT: turns out i misplaced GRUB or something. reinstalled placing GRUB on /dev/sda. works fine now.
    Last edited by glas01 (2008-11-29 12:46:15)

    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 after switching to ext4

    Hi,
    Yesteday I converted my partition to ext4 sucesfully, and I managed to boot once after that, but when I tried to reboot, GRUB2 would say:
    error: invalid magic number
    while trying to load the kernel. I already chrooted from my Ubuntu partition and tried to fix by reinstalling kernel and fsck'ing, but no luck. ideas? I can't even boot from fallback :S

    Ok, here's my grub.cfg
    # Config file for GRUB2 - The GNU GRand Unified Bootloader
    # /boot/grub/grub.cfg
    # DEVICE NAME CONVERSIONS
    # Linux Grub
    # /dev/fd0 (fd0)
    # /dev/sda (hd0)
    # /dev/sdb2 (hd1,2)
    # /dev/sda3 (hd0,3)
    # Timeout for menu
    set timeout=5
    # Set default boot entry as Entry 0
    set default=0
    #Colors
    set menu_color_normal=light-blue/black
    set menu_color_highlight=light-cyan/blue
    #modules insert
    insmod linux
    # (0) Arch Linux
    menuentry "Arch Linux" {
    set root=(hd0,5)
    linux /boot/vmlinuz26 root=/dev/sda5 rootfstype=ext4 ro quiet
    initrd /boot/kernel26.img
    # (1) Arch Linux recovery
    menuentry "Arch Linux Fallback" {
    set root=(hd0,5)
    linux /boot/vmlinuz26 root=/dev/sda5 ro quiet
    initrd /boot/kernel26-fallback.img
    menuentry "Kubuntu 8.10, kernel 2.6.27-7-generic" {
    set root=(hd1,5)
    linux /boot/vmlinuz-2.6.28-4-generic root=/dev/sdb5 ro quiet splash
    initrd /boot/initrd.img-2.6.28-4-generic
    menuentry "Kubuntu 8.10, kernel 2.6.27-7-generic (recovery)" {
    set root=(hd1,5)
    linux /boot/vmlinuz-2.6.28-4-generic root=/dev/hda1 ro single
    initrd /boot/initrd.img-2.6.28-4-generic
    ## (1) Windows
    #menuentry "Windows" {
    #set root=(hd0,3)
    #chainloader +1
    BTW, if I change "linux" command for "multiboot", I get this:
    alloc magic is broken at 0x19710
    Any ideas on what may be causing this? Perhaps changing to GRUB-legacy would help?

  • [SOLVED] Gnome 3 won't start after kernel upgrade

    I have upgraded to kernel 3.0, and now I am getting the following error when I try to start gdm:
    ** (gdm-binary:936): WARNING **: Failed to acquire org.gnome.DisplayManager
    ** (gdm0binary:936): WARNING **: Could not acquire name: bailing out
    Can anybody explain what the deal is?
    Last edited by spiritwalker (2011-08-17 16:50:44)

    theseus, thank you for the reply. I thought you can only start gnome using some kind of display manager. If I understood you correctly, I did 'telinit 5' and then 'startx' with the folowing results:
    INIT: Switching to runlevel: 5
    INIT: cannot execute "/usr/bin/xdm" <---- This line repeats 10 times
    INIT: ID "x" respawning too fast: disabled for 5 minutes
    But when I did 'who -r' I got this:
    run-level 5 2011-08-16 02:26 last = 4
    So I tried to start X wich resulted in the following:
    http://i.imgur.com/yydcd.png
    http://i.imgur.com/RNapr.png
    http://i.imgur.com/NnFaM.png
    Also, arch is installed in a virtual box, so I didn't install any video drivers like nvidia.
    Thanks
    Moderator edit:
    spiritwalker, please do not post pictures of this large size: https://wiki.archlinux.org/index.php/Fo … s_and_Code
    In this specific case you could have made use the log files in /var/log and posted the relevant info in [ code ] tags.
    Besides, this way you will get used to work with logs, which is mandatory in Arch, imo.
    Last edited by bernarcher (2011-08-17 13:33:28)

  • Powerbook won't boot after Leopard upgrade.

    I'll get the apple logo and spinning gear, then blue (kernal panic) screen, and that's as far as it will go.
    I thought I recalled a problem with the Unsanity application enhancers, so I started the PB up in target disk mode and removed the one .ape...that didn't help...now I need help.
    I've searched around here but cannot locate a similar discussion.
    thanks

    Hi Limnos...My profile says 10.4.11 since I have not gotten 10.5 to install yet. Never before had 10.5 on this PB. I was attempting to upgrade to Leopard from the retail install disc, but after the process concluded normally, the restart hung with a blue screen kernal panic.
    I attempted safe boot and it would not do that either. I attempted to restart off the install DVD again, and it would not do that either. It would only boot into target disk mode. I have not tried anything else today, yet. Waiting for some advise from here, before I spin my wheels any more.

Maybe you are looking for