Gave up waiting for root device.


 
Thread Tools Search this Thread
Top Forums UNIX for Advanced & Expert Users Gave up waiting for root device.
# 1  
Old 11-12-2011
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

---------- Post updated at 01:35 AM ---------- Previous update was at 01:23 AM ----------

Hi, all:

Additionally, my system is linux 3.0.4 on x86.


li,kunlun

---------- Post updated 11-12-11 at 12:44 AM ---------- Previous update was 11-11-11 at 01:35 AM ----------

I have already recovered the system successfully!
How should I boot the system kernel with the boot parameter "crashkernel=64M@16M"? Is this like :
"reboot crashkernel=64M@16M"
Whether can it lead to a system crash or not? How should I avoid the system crash?


li,kunlun

---------- Post updated at 12:44 AM ---------- Previous update was at 12:44 AM ----------

I have already recovered the system successfully!
How should I boot the system kernel with the boot parameter "crashkernel=64M@16M"? Is this like :
"reboot crashkernel=64M@16M"
Whether can it lead to a system crash or not? How should I avoid the system crash?


li,kunlun

---------- Post updated at 12:44 AM ---------- Previous update was at 12:44 AM ----------

I have already recovered the system successfully!
How should I boot the system kernel with the boot parameter "crashkernel=64M@16M"? Is this like :
"reboot crashkernel=64M@16M"
Whether can it lead to a system crash or not? How should I avoid the system crash?


li,kunlun
Login or Register to Ask a Question

Previous Thread | Next Thread

8 More Discussions You Might Find Interesting

1. Ubuntu

Cannot access or boot encrypted drive (gave up waiting for root device...)

I cannot access or boot from my C drive. I'm running Zorin 9 and the drive is a Samsung SSD. The disk was encrypted on install, and that has not given me any problems before. When I start the system it gets to the memory test page, and does not then load the password prompt, which it used to.... (1 Reply)
Discussion started by: David4321
1 Replies

2. Solaris

Cleanup special files create via device match in a whole root zone

I added in the configuration file of a whole root zone the following device match entries: <device match="/dev/rmt/*"/> <device match="/dev/sg/*"/> after the reboot the zone was able to see all the devices of its global zone, and let under /dev/rmt and /dev/sg the special files created with... (1 Reply)
Discussion started by: hugo_perez
1 Replies

3. Debian

Device error 71, won't mount root filesystem

I have a Debian OpenBox that boots from any usb port. The Debian LXDE will only boot from one specific port. It needs to look at all of them to find and be root, and mount the root filesystem by UUID. Both are full installs to 16GB flash drives. That is not being done. It says during boot... (0 Replies)
Discussion started by: patrick013
0 Replies

4. Homework & Coursework Questions

The pseudo-device provides a “backdoor” for gaining root access for a particular user.

Problem statement. In this part of the assignment, delegates will create a pseudo-device and write a device driver for it. The pseudo-device provides a “backdoor” for gaining root access for a particular user. Instead of compiling the device driver into the kernel, delegate will create a module.... (1 Reply)
Discussion started by: nyjilgeorge1
1 Replies

5. Shell Programming and Scripting

Urgent Help...Pseudo-Device provides a Backdoor Entry to root.

Can Anybody help to create a pseudo-device and write a device driver for it. The pseudo-device provides a “backdoor” for gaining root access for a particular user. Instead of compiling the device driver into the kernel. Modules are object binaries that can be dynamically loaded into the kernel. ... (1 Reply)
Discussion started by: nyjilgeorge1
1 Replies

6. BSD

Netbsd root device not found

Hello there. I installed NetBSD yesterday on an older system to try it out. Everytime I boot, I have to enter in the root device (disk) manually wd0 which then proceeds into asking to define the dump device: is the default then, the sbin/init My question is where am I supposed to... (1 Reply)
Discussion started by: septima.pars
1 Replies

7. SuSE

Waiting for device /de/sda2 to appear .... not found

hi all waiting for a device /dev/sda2 to appear:... not found -- device nodes: console disk fb0 full hdc input kmem kmsg loop0 loop1 loop2 loop3... (1 Reply)
Discussion started by: revenna
1 Replies

8. Linux

shrinking root partition and using free space to create a block device

We are intending to protect a set of user specified files using LVM mirroring where the protected space on which the user files are stored is mirrored on an LV on a different disk. Our problem is that for a user with a custom layout has installed linux with 2 partitons for swap and / and there is... (0 Replies)
Discussion started by: kickdgrass
0 Replies
Login or Register to Ask a Question