Arch Linux

tompouceuh

Member

Registered: 2006-03-22

Posts: 30

after kernel upgrade, wont boot, but not as the others...

Hi, I upgraded my kernel, rebooted, Got the error that I was supposed to have.

So I edited my menu.lst like this:

#  /dev/hda3   /dev/discs/disc0/part3   (hd0,2)

title  Arch Linux
root   (hd0,2)
kernel /boot/vmlinuz26 root=/dev/hda3 ro devfs=nomount

And now I got the same error:
VFS: Cannot open root device "hda3" or unknown-block(0,0)
Please append a correct "root=" boot option
Kernel panic - not syncing: VFS:

I looked over all these kind of threads, and found nothing!

Because It is supposed to work well now that I edited my menu.lst, but It still dont work, I tried many things... but without chances...

Thanks for your help!

---

tompouceuh dot info

stingray

Member

From: Lima, Peru SA

Registered: 2006-03-24

Posts: 188

Re: after kernel upgrade, wont boot, but not as the others...

Note: I'm new to Linux and Arch, so...

Here is what I have in my /boot/grub/menu.lst

title  Arch Linux
root   (hd0,0)
kernel /vmlinuz26 root=/dev/hda3 ro apm=power-off
initrd /initrd26.img

This is all guess work, but you might try changing "root (hd0,2)" to "root (hd0,0)"  (my root is on hda3, but my boot in on hda1)
I also have that "initrd /initrd26.img" after the kernel line?

Anyway, just a guess?

tyme

Member

From: PA

Registered: 2003-06-12

Posts: 139

Website

Re: after kernel upgrade, wont boot, but not as the others...

try this:

title Arch Linux
root (hd0,2)
kernel /boot/vmlinuz26 root=/dev/hda3 ro devfs=nomount
initrd /boot/initrd26.img

not having the initrd line is probably where your problem lies.

---

Generic Geek Unit

Gullible Jones

Member

Registered: 2004-12-29

Posts: 4,863

Re: after kernel upgrade, wont boot, but not as the others...

Yes, that is probably your problem... While we're at it, devfs=nomount is not necessary with a 2.6 kernel.

Sander

Member

Registered: 2006-02-26

Posts: 138

Re: after kernel upgrade, wont boot, but not as the others...

This is all guess work, but you might try changing "root (hd0,2)" to "root (hd0,0)"  (my root is on hda3, but my boot in on hda1)

That probably wouldn't do much good, since apparently (hd0,2) worked for him before

afaik it's definately the missing initrd.

---

You like cheese? You like peas? You'll love cheezy peas!