Find the answer to your Linux question:
Results 1 to 5 of 5
Yestoday, in order to analysis the core dump information which is a result of my bugged device driver, I configurate and make the kernel according to "Documentation/kdump/kdump.txt" in linux source ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Just Joined!
    Join Date
    Nov 2011
    Posts
    28

    Gave up waiting for root device.


    Yestoday, in order to analysis the core dump information which is a result of my bugged device driver, I configurate and make the kernel according to "Documentation/kdump/kdump.txt" in linux source code and today, I reboot the system with "crashkernel=64M/16M". The system cannot boot now and display the following information:

    Gave up waiting for root device. Common problems:
    -Boot args (cat /proc/cmdline)
    -Check rootdelay= (did the system wait long enough?)
    -Check root= (did the system wait for the right device?)
    -Missing modules (cat /proc/modules; ls /dev)
    Alert! /dev/disk/by-uuid/99339357-923a-4cfb-a288-6336c7499359 does not exist. Dorpping to a shell!

    BusyBox v1.13.3 (ubuntu 1:1.13.3-1ubuntu11) built-in shell (ash)
    Enter 'help' for a list of built-in commands.

    (initramfs)


    What should I do to boot the system?
    What do these information mean?

    thanks!
    li,kunlun

  2. #2
    Just Joined!
    Join Date
    Nov 2011
    Posts
    28
    Quote Originally Posted by liklstar View Post
    Yestoday, in order to analysis the core dump information which is a result of my bugged device driver, I configurate and make the kernel according to "Documentation/kdump/kdump.txt" in linux source code and today, I reboot the system with "crashkernel=64M/16M". The system cannot boot now and display the following information:

    Gave up waiting for root device. Common problems:
    -Boot args (cat /proc/cmdline)
    -Check rootdelay= (did the system wait long enough?)
    -Check root= (did the system wait for the right device?)
    -Missing modules (cat /proc/modules; ls /dev)
    Alert! /dev/disk/by-uuid/99339357-923a-4cfb-a288-6336c7499359 does not exist. Dorpping to a shell!

    BusyBox v1.13.3 (ubuntu 1:1.13.3-1ubuntu11) built-in shell (ash)
    Enter 'help' for a list of built-in commands.

    (initramfs)


    What should I do to boot the system?
    What do these information mean?

    thanks!
    li,kunlun


    My system is linux 3.0.4 on x86.

    li,kunlun

  3. #3
    Trusted Penguin
    Join Date
    May 2011
    Posts
    4,353
    Can you interrupt the boot loader (grub?) and modify the kernel parameters manually? In grub, you just hit 'a' I think, then you can just remove the crashkernel part, in order to revert to your previous boot configuration.

    Edit: and shouldn't it be '@' not '/' in the crashkernel parameters?
    Last edited by atreyu; 11-11-2011 at 02:55 PM. Reason: and another thing

  4. #4
    Just Joined!
    Join Date
    Nov 2011
    Posts
    28
    Dear atreyu:

    Thanks!

    I have already recovered the boot loader(grub) and now, an other problem appears that the system cannot boot automatically, only can it boot by manually input the grub commands such as "root (hd0,0)", "kernel /boot/vmlinuz-3.0.4 ro root=/dev/sda1", and so on.

    How can I repare it?

    li,kunlun

  5. #5
    Trusted Penguin
    Join Date
    May 2011
    Posts
    4,353
    once you manually boot into the system, try:
    Code:
    grub-install /dev/sda

Posting Permissions

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