On Thursday 08 April 2004 17:11, Jerome Lyles wrote:
On Thursday 08 April 2004 05:01 am, S.R.Glasoe wrote:
On Wednesday 07 April 2004 18:08, Jerome Lyles wrote: snip
From BackupEdge │┌───────────────────────────────────────────────────────────────────── ── ── ───┐│ ││Create Node: dvd0 OS: Linux version 2.4.21-199-a GRUB: Enabled ││ ││Temp Device: /dev/loop0 System: Cosmos3 ││ ││Format: Yes Verify: Yes Kernel: (hd1,1)/boot/vmlinuz (Linux) ││ ││Kernel '(hd1,1)/boot/vmlinuz' does not exist! ││Technology/ │└───────────────────────────────────────────────────────────────────── ── ── ───
As root check /boot/menu.lst to see where you kernel is actually loaded from. (hd1,1) means the second hard drive and the second partition on it is your / root and boot partition. Guessing that your main hard drive (hd0,0) may be closer to reality? /boot/menu.lst will show you what BackupEdge should be seeing.
Stan
Hi Stan, I don't have a menu.lst file:
# cat /boot/menu.lst cat: /boot/menu.lst: No such file or directory. Is there another way to see where my kernel is actually loaded from?
I think the (hd1,1) is correct: /etc/fstab: /dev/hdb2 / reiserfs defaults 1 1 Thanks, Jerome
Oops. That should be /boot/grub/menu.lst, sorry. Your fstab looks like your root is on (hd1,1). Do you have a separate /boot partition listed in fstab such as /dev/hdb1 or /dev/hdb3? IF you do then that's where BackupEdge should be looking. IF you have a /boot directory in / then I'm out of ideas for now. Stan