Find the answer to your Linux question:
Page 1 of 2 1 2 LastLast
Results 1 to 10 of 11
I recently upgraded to Squeeze (2.6.32.5) from Lenny. Problem : GRUB 2 does not boot any kernel I compiled a new kernel, 2.6.32.5, did install_modules. I installed the .deb header ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Just Joined!
    Join Date
    Jun 2012
    Posts
    20

    Booting Squeeze with GRUB 2 - Alert! Dropping to a shell!


    I recently upgraded to Squeeze (2.6.32.5) from Lenny.

    Problem : GRUB 2 does not boot any kernel

    I compiled a new kernel, 2.6.32.5, did install_modules. I installed the .deb header and image files too. All the vmlinuz and initrd files were created at the right places.

    Now, on boot I started getting this error :

    Code:
    Alert ! UUID xxxxxx does not exist! Dropping to a shell.
    So I checked the grub file in /boot and the uuids matched perfectly. Still, as instructed on another forum I modified one line in /etc/default/grub. I uncommented
    Code:
    GRUB_DISABLE_LINUX_UUID = true.
    In /etc/fstab too I commented the line :

    Code:
    UUID=xxxxxxx-yyyyy
    and uncommented the line
    Code:
    /dev/hda1    /
    Still, at boot I get :

    Code:
    Alert! /dev/sda1 does not Exist Dropping to a shell!
    Strange part : fstab denotes hda1, hda2 etc. but /etc/default/grub refers to sda1 and sda5. Is this the cause of the problem ?

    I didn't edit these files too much before getting an opinion from you guys.

  2. #2
    Administrator jayd512's Avatar
    Join Date
    Feb 2008
    Location
    Kentucky
    Posts
    5,025
    I've not run into this problem, but maybe I can help you feel around a bit.
    When you boot, and drop to a shell console, execute:
    Code:
    blkid
    Does the output match your /etc/fstab entries?
    Jay

    New users, read this first.
    New Member FAQ
    Registered Linux User #463940
    I do not respond to private messages asking for Linux help. Please keep it on the public boards.

  3. #3
    Just Joined!
    Join Date
    Jun 2012
    Posts
    20
    Quote Originally Posted by jayd512 View Post
    I've not run into this problem, but maybe I can help you feel around a bit.
    When you boot, and drop to a shell console, execute:
    Code:
    blkid
    Does the output match your /etc/fstab entries?
    OK. blkid on the shell console gives nothing. Just the initramfs prompt comes up.

    But /etc/fstab yields hda1 (not, sda1) as its device. Also, I've commented the line UUID=xxxx yyyy.

    Using a RescueCD to boot, when I execute blkid as root, I get

    Code:
    /dev/sda1 UUID=xxxx yyyyy  Type=ext2
    /dev/sda5 UUID=xxyy yxxxx  Type =swap

  4. $spacer_open
    $spacer_close
  5. #4
    Administrator jayd512's Avatar
    Join Date
    Feb 2008
    Location
    Kentucky
    Posts
    5,025
    Quote Originally Posted by Abhid View Post
    Using a RescueCD to boot, when I execute blkid as root, I get
    Code:
    /dev/sda1 UUID=xxxx yyyyy  Type=ext2
    /dev/sda5 UUID=xxyy yxxxx  Type =swap
    And the output matches your fstab?
    Jay

    New users, read this first.
    New Member FAQ
    Registered Linux User #463940
    I do not respond to private messages asking for Linux help. Please keep it on the public boards.

  6. #5
    Just Joined!
    Join Date
    Jun 2012
    Posts
    20
    Quote Originally Posted by jayd512 View Post
    And the output matches your fstab?
    No it doesn't. The UUIDs do match, but as mentioned, fstab for some reason denotes hda1 instead of sda1

  7. #6
    Administrator jayd512's Avatar
    Join Date
    Feb 2008
    Location
    Kentucky
    Posts
    5,025
    Edit your fstab to match UUID output.
    Reboot.
    And edit to match xda output.
    Jay

    New users, read this first.
    New Member FAQ
    Registered Linux User #463940
    I do not respond to private messages asking for Linux help. Please keep it on the public boards.

  8. #7
    Just Joined!
    Join Date
    Jun 2012
    Posts
    20
    Quote Originally Posted by jayd512 View Post
    Edit your fstab to match UUID output.
    Reboot.
    And edit to match xda output.
    I uncommented the UUID line in fstab (they were already matched), and I changed the hda to sda. After rebooting, the same error appears.

    Some more info if its useful :

    1) This message is also displayed before dropping to the shell :

    Code:
    Mount : Mounting none on /dev failed : No such device
    2)The second kernel option in GRUB has (Recovery mode) in brackets. Why recovery mode ?

  9. #8
    Administrator jayd512's Avatar
    Join Date
    Feb 2008
    Location
    Kentucky
    Posts
    5,025
    Just for clarification, did this all start happening after you compiled and installed a new kernel?
    Was everything working properly before that?
    Jay

    New users, read this first.
    New Member FAQ
    Registered Linux User #463940
    I do not respond to private messages asking for Linux help. Please keep it on the public boards.

  10. #9
    Just Joined!
    Join Date
    Jun 2012
    Posts
    20
    Quote Originally Posted by jayd512 View Post
    Just for clarification, did this all start happening after you compiled and installed a new kernel?
    Was everything working properly before that?
    Yes, I compiled and installed a new kernel, but I did it to fix a broken GRUB2 Master Boot Record.

    Ever since I upgraded from Lenny to Squeeze 2 weeks back, I used to get a GRUB Error 15 on boot. I fixed that, but now the kernel won't load.

    According to another forum post**, some SATA entry in menuconfig must be modified for this error to go.

    Should I compile again ? How do I get the right menuconfig ? (this seems to be the key).

    **linuxquestions.org/questions/linux-kernel-70/alert-dev-sda1-does-not-exist-when-booting-a-new-kernel-643688/
    Last edited by Abhid; 06-18-2012 at 09:05 AM.

  11. #10
    Just Joined!
    Join Date
    Jun 2012
    Posts
    20
    Also, the kernel that I compiled is 2.6.32.5 (if it helps).

Page 1 of 2 1 2 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •