titaniumdecoy
December 30th, 2008, 04:47 PM
I have compiled and attempted to install a custom 2.6.28 kernel. The problem I am having is that when I try to boot using the new kernel I get this message:
Begin: Waiting for root file system... ...
[ 3.359063] scsi_id used greatest stack depth: 6188 bytes left
Done.
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/778cb529-8914-451a-97ee-fb2d8ae404ae does not exist. Dropping to a shell!
BusyBox v1.10.2 (Ubuntu 1:1.10.2-1ubuntu6) built-in shell (ash)
Enter 'help' for a list of built-in commands.
(initramfs) _
For some reason the kernel is unable to locate my ext3 file system.
I have installed the modules via make modules followed by make modules_install.
The relevant snippet from my /boot/grub/menu.lst file is below:
# CURRENT WORKING UBUNTU KERNEL
title Ubuntu 8.10, kernel 2.6.27-9-generic
uuid 778cb529-8914-451a-97ee-fb2d8ae404ae
kernel /boot/vmlinuz-2.6.27-9-generic root=UUID=778cb529-8914-451a-97ee-fb2d8ae404ae ro quiet splash
initrd /boot/initrd.img-2.6.27-9-generic
quiet
# MY CUSTOM KERNEL
title kernel 2.6.28
uuid 778cb529-8914-451a-97ee-fb2d8ae404ae
kernel /boot/vmlinuz-2.6.28 root=UUID=778cb529-8914-451a-97ee-fb2d8ae404ae
initrd /boot/initrd-2.6.28.img
quiet
I created the initrd-2.6.28.img file via the command mkinitramfs -o initrd-2.6.28.img 2.6.28.
I cannot figure out why the new kernel cannot locate the file system since it is using the same UUID as the working kernel. Please help!
EDIT: Sometimes it complains that /lib/modules/2.6.28/modules.dep does not exist. This file does exist. I assume the kernel is unable to access the disk.
Begin: Waiting for root file system... ...
[ 3.359063] scsi_id used greatest stack depth: 6188 bytes left
Done.
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/778cb529-8914-451a-97ee-fb2d8ae404ae does not exist. Dropping to a shell!
BusyBox v1.10.2 (Ubuntu 1:1.10.2-1ubuntu6) built-in shell (ash)
Enter 'help' for a list of built-in commands.
(initramfs) _
For some reason the kernel is unable to locate my ext3 file system.
I have installed the modules via make modules followed by make modules_install.
The relevant snippet from my /boot/grub/menu.lst file is below:
# CURRENT WORKING UBUNTU KERNEL
title Ubuntu 8.10, kernel 2.6.27-9-generic
uuid 778cb529-8914-451a-97ee-fb2d8ae404ae
kernel /boot/vmlinuz-2.6.27-9-generic root=UUID=778cb529-8914-451a-97ee-fb2d8ae404ae ro quiet splash
initrd /boot/initrd.img-2.6.27-9-generic
quiet
# MY CUSTOM KERNEL
title kernel 2.6.28
uuid 778cb529-8914-451a-97ee-fb2d8ae404ae
kernel /boot/vmlinuz-2.6.28 root=UUID=778cb529-8914-451a-97ee-fb2d8ae404ae
initrd /boot/initrd-2.6.28.img
quiet
I created the initrd-2.6.28.img file via the command mkinitramfs -o initrd-2.6.28.img 2.6.28.
I cannot figure out why the new kernel cannot locate the file system since it is using the same UUID as the working kernel. Please help!
EDIT: Sometimes it complains that /lib/modules/2.6.28/modules.dep does not exist. This file does exist. I assume the kernel is unable to access the disk.