LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Ubuntu (http://www.linuxquestions.org/questions/ubuntu-63/)
-   -   ALERT! /dev/sda7 does not exist. Dropping to shell! (http://www.linuxquestions.org/questions/ubuntu-63/alert-dev-sda7-does-not-exist-dropping-to-shell-573505/)

eye2eye 07-30-2007 04:46 PM

ALERT! /dev/sda7 does not exist. Dropping to shell!
 
hello,

I have a Ubuntu machine and I am trying to install a new kernel (2.6.21.1) and it recompiles and does everything nicely as per http://www.howtoforge.com/kernel_compilation_ubuntu_p2 which is an excellent website, btw. I tried booting to the new kernel but it after a long pause it always comes back with the error:

ALERT! /dev/sda7 does not exist. Dropping to a shell!

But my other kernels are able to recognize this drive and boot no problem so why is this new one giving such a message? Does anyone know? Is there something I am doing wrong concerning the make menuconfig options? I have already compiled 3 other kernels and they all give similar errors. Actually there is one prior message, displayed before the long pause that says:

PCI: Cannot allocate resource region 0 of device 0000:05:06.0.

I am not sure if that is related to the ALERT! error message but I thought I would let you guys know.

Prompt and descriptive help is always appreciated :)

Thanks in advance.

eye2eye

pixellany 07-30-2007 05:12 PM

That looks like the message you might get if the "root=_____" string passed to the kernel was pointing to a non-existent partition.

Check the entries in /boot/grub/menu.lst to be sure that the entry for your new kernel is pointing to the correct partition for mounting the filesystem.

eye2eye 07-31-2007 10:42 AM

I did check the root line in /boot/grub/menu.lst and just to make sure I copied and pasted that line from my working kernels to the new one. Still it was hanging when trying to find the root file system.

Even when I started in recovery mode, it just stalls on the msg "trying to gain access to root file system..." and it just drops down to the that basic shell. Why is not able to read that drive when other kernels have no problem doing it? Could it be a problem with the command 'dpkg' because that is what I used to compile the kernel and make the linux images and initrd disks, althought I am sure if they are the problem.

Does anyone have any suggestions?

eye2eye


All times are GMT -5. The time now is 06:12 PM.