Hello,
I recomplied my kernel 2.4.20 but when tried to boot with new kernel image, grub gives an error-
" cannot open root device / please append a correct root=boot option"
any suggessions ?
my /etc/grub.conf is -
default=0 timeout=10 splashimage=(hd0,0)/grub/splash.xpm.gz title Red Hat Linux (2.4.20-8) root (hd0,0) kernel /vmlinuz-2.4.20-8 ro root=LABEL=/ initrd /initrd-2.4.20-8.img
title Red Hat Linux NEW (2.4.20-8) root (hd0,0) kernel /newbzimage ro root=LABEL=/ initrd /initrd-2.4.20-8.img
--------------------------------- Do you Yahoo!? Win a $20,000 Career Makeover at Yahoo! HotJobs
Evening Pramila,
--- pramila prami_22@yahoo.com wrote:
Hello, " cannot open root device / please append a correct root=boot option"
[snip]
Mention root=/dev/hdxx and it should boot appropriately. Where hdxx is the hard disk with the partition in particular to boot.
Many a time the initrd when created by users doesn't contain the needed modules. I suggest you compile the modules needed to mount the File system as static module into the kernel too.
Trevor
any suggessions ?
my /etc/grub.conf is -
===== ( >- -< ) /~\ __ Scaling FLOSS in the __ /~\ | ) / Enterprise : trevor.w@pvision.biz \ (/ | |_|_ \ Call Now: 9820349221 / _|_| ____________________________________/
__________________________________ Do you Yahoo!? Win a $20,000 Career Makeover at Yahoo! HotJobs http://hotjobs.sweepstakes.yahoo.com/careermakeover
try using the following at an entry in yout grub.conf file.
title Red Hat Linux NEW (2.4.20-8) root (hd0,0) kernel /newbzimage ro root=/dev/hdXX initrd /initrd-2.4.20-8.img
hdXX is your root partition (eg. hda1, hda5, etc etc)
worked for me, hope it does for you.
vivek
________________________________________________________________________ Yahoo! India Matrimony: Find your partner online. http://yahoo.shaadi.com/india-matrimony/
looks like this is a path related issue.
Use a rescue CD if available, mount your partitions, chroot and edit the grub.conf file to set the correct location
pramila wrote:
Hello,
I recomplied my kernel 2.4.20 but when tried to boot with new kernel image, grub gives an error-
" cannot open root device / please append a correct root=boot option"
any suggessions ?
my /etc/grub.conf is -
default=0 timeout=10 splashimage=(hd0,0)/grub/splash.xpm.gz title Red Hat Linux (2.4.20-8) root (hd0,0) kernel /vmlinuz-2.4.20-8 ro root=LABEL=/ initrd /initrd-2.4.20-8.img
title Red Hat Linux NEW (2.4.20-8) root (hd0,0) kernel /newbzimage ro root=LABEL=/ initrd /initrd-2.4.20-8.img
Do you Yahoo!? Win a $20,000 Career Makeover at Yahoo! HotJobs
thanks 4 help,
/dev/sda1 worked actually mkinitrd but now i am getting error Kernel panic: no init found. Try passing init= option to kernel. whats this ? tried google but cant find solution
Santhosh Joseph santhosh@ezrs.com wrote: looks like this is a path related issue.
Use a rescue CD if available, mount your partitions, chroot and edit the grub.conf file to set the correct location
pramila wrote:
Hello,
I recomplied my kernel 2.4.20 but when tried to boot with new kernel image, grub gives an error-
" cannot open root device / please append a correct root=boot option"
any suggessions ?
my /etc/grub.conf is -
default=0 timeout=10 splashimage=(hd0,0)/grub/splash.xpm.gz title Red Hat Linux (2.4.20-8) root (hd0,0) kernel /vmlinuz-2.4.20-8 ro root=LABEL=/ initrd /initrd-2.4.20-8.img
title Red Hat Linux NEW (2.4.20-8) root (hd0,0) kernel /newbzimage ro root=LABEL=/ initrd /initrd-2.4.20-8.img
Do you Yahoo!? Win a $20,000 Career Makeover at Yahoo! HotJobs
Hi Pramila, Trevor mentioned in his reply to your original post that you have to compile all required modules directly into the kernel. Now what has happened here is that the kernel doesn't know how to read your file systems, and hence cannot find init. This is because support for file systems have been compiled as modules. What you have to do is the compile ext2, ext3 and if required vfat & ntfs directly into the kernel. That will solve your immediate problem. Also when you recompile, directly compile support for your Display Adapter, Sound Adapter, NIC, etc etc, into the kernel. This will avoid a lot of headache later. cheerio vivek
________________________________________________________________________ Yahoo! India Matrimony: Find your partner online. http://yahoo.shaadi.com/india-matrimony/
i hv already compiled ext3 in kernel i.e Ext3 journalling file system suport in File System option
still getting same error
Vivek J Patankar vj714151-ilugbom@yahoo.com wrote: Hi Pramila, Trevor mentioned in his reply to your original post that you have to compile all required modules directly into the kernel. Now what has happened here is that the kernel doesn't know how to read your file systems, and hence cannot find init. This is because support for file systems have been compiled as modules. What you have to do is the compile ext2, ext3 and if required vfat & ntfs directly into the kernel. That will solve your immediate problem. Also when you recompile, directly compile support for your Display Adapter, Sound Adapter, NIC, etc etc, into the kernel. This will avoid a lot of headache later. cheerio vivek
________________________________________________________________________ Yahoo! India Matrimony: Find your partner online. http://yahoo.shaadi.com/india-matrimony/