On Mon, Oct 16, 2006 at 11:20:01PM -0400, Daniel Devost wrote: > Hi, > > I have a Dell X300 and I want to dual boot between Sarge and Etch. I > have two drives, /dev/hda that holds Etch (/dev/hda1) and /dev/sda that > holds Sarge (/dev/sda1). Both drives have swap space and grub and fstab > have the correct entries. Grub is installed on the MBR of /dev/hda and > the menu.lst resides in /boot/grub/. > > Etch boots fine but Sarge terminates with: > > pivot_root: No such file or directory > /sbin/init: 432:cannot open dev/console: No such file > Kernel panic - not syncing: Attempted to kill init!
Looks like it can't find the initrd.img file. > /dev/hda is the regular drive of the laptop while /dev/sda is a drive > mounted in the cdrom bay. Once etch is booted, I can mount /dev/sda1 and > read/write to it. > > Not sure what is going on. > > Thanks in advance, > > Daniel Devost > > menu.lst: > > title Debian GNU/Linux, kernel 2.4.27-2-386 > root (hd1,0) > kernel /boot/vmlinuz-2.4.27-2-386 root=/dev/sda1 ro > initrd /boot/initrd.img-2.4.27-2-386 > savedefault > boot > > title Debian GNU/Linux, kernel 2.4.27-2-386 (recovery mode) > root (hd1,0) > kernel /boot/vmlinuz-2.4.27-2-386 root=/dev/sda1 ro single > initrd /boot/initrd.img-2.4.27-2-386 > savedefault > boot > > ### END DEBIAN AUTOMAGIC KERNELS LIST > > # This is a divider, added to separate the menu items below from the Debian > # ones. > title Other operating systems: > root > > > # This entry automatically added by the Debian installer for an existing > # linux installation on /dev/hda1. > title Debian GNU/Linux (testing/unstable) (on /dev/hda1) > root (hd0,0) > kernel /boot/vmlinuz-2.6.15-1-486 root=/dev/hda1 > initrd /boot/initrd.img-2.6.15-1-486 > savedefault > boot > > > # This entry automatically added by the Debian installer for an existing > # linux installation on /dev/hda1. > title Debian GNU/Linux 2.6.16-2-486 (on /dev/hda1) > root (hd0,0) > kernel /boot/vmlinuz-2.6.16-2-486 root=/dev/hda1 > initrd /boot/initrd.img-2.6.16-2-486 > savedefault > boot > > > # This entry automatically added by the Debian installer for an existing > # linux installation on /dev/hda1. > title Debian GNU/Linux (testing/unstable) (on /dev/hda1) > root (hd0,0) > kernel /boot/vmlinuz-2.6.16-2-686 root=/dev/hda1 > initrd /boot/initrd.img-2.6.16-2-686 > savedefault > boot > > > # This entry automatically added by the Debian installer for an existing > # linux installation on /dev/hda1. > title Ok Debian GNU/Linux (testing/unstable) (on /dev/hda1) > root (hd0,0) > kernel /boot/vmlinuz-2.6.17-2-486 root=/dev/hda1 > initrd /boot/initrd.img-2.6.17-2-486 > savedefault > boot What does dpkg-reconfigure linux-image<each-version> do? then What does an update-grub do? That *might* recreate the initrd.img -- Chris. ====== " ... the official version cannot be abandoned because the implication of rejecting it is far too disturbing: that we are subject to a government conspiracy of `X-Files' proportions and insidiousness." Letter to the LA Times Magazine, September 18, 2005. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
