I managed to make a new initrd with the mkinitrd command but when i rebooted I received the same error as before "Cannot open root device LABEL=/" What am I doing wrong?
Michael -----Original Message----- From: Rick Carroll [mailto:[EMAIL PROTECTED]] Sent: Tuesday, February 18, 2003 9:54 AM To: [EMAIL PROTECTED] Subject: RE: Custom Kernel wont boot Michael, I wish I could tell you exactly why, but all I know is that you need to make a new initrd to support the LABEL=/ thing. That is what's running when you try to mount the ext3 root filesystem. I had this same problem when I first started building kernels, and all the discussion boards, etc. said to change LABEL=/ to LABEL=/dev/sda1 or whatever partition your root fs lives on. I didn't want to accept that because redhat distros work this way, so I kept looking. I finally stumbled across the initrd answer somewhere (on redhat page I think...) HTH, YMMV, FWIW, and whatever else... :) Rick -----Original Message----- From: Mingle, Michael [mailto:[EMAIL PROTECTED]] Sent: Monday, February 17, 2003 4:32 PM To: '[EMAIL PROTECTED]' Subject: RE: Custom Kernel wont boot Ok guys... I'm still having some problems. I have now tried both LILO and GRUB boot managers. I edit the respective config files to point to the new kernel. The installed kernel in Redhat 8.0 uses the option "root=LABEL=/" to define the root fs such as in grub.conf line: kernel /vmlinuz-2.4.18-19.8.0mppe ro root=LABEL=/ After building my new kernel I copied the bzImage file into the /boot partition and then updated the grub.conf file to say the following: kernel /vmlinuz-2.4.20 ro root=LABEL=/ Note: no need for initrd because I compiled ext3 support into the kernel. When I boot the system with the new kernel it comes up with an error 'Cannot open root device "LABEL=/" or 00:00 Please append a correct "root=" boot option Kernel panic: VFS: Unable to mount root on 00:00' If I change the option in the grub.conf to append root=/dev/hda2 then the system will boot fine. Why does it work fine with the RH 8 standard kernel but not with a customized version? Michael -----Original Message----- From: Nick Lindsell [mailto:[EMAIL PROTECTED]] Sent: Monday, February 17, 2003 10:26 AM To: [EMAIL PROTECTED] Subject: RE: Custom Kernel wont boot At 06:58 17/02/2003 -0800, you wrote: >This was the first time I built a custom kernel so I went from the same >configuration that my current installed system used for these options. Say >I didn't want to rely on the make install procedure... How would I rebuild >the initrd properly. This is the process I followed. >make clean >make mrproper >make menuconfig >make >make bzImage >make modules >make modules_install > >copy bzImage from /usr/src/linux/arch/i386/boot to /boot >edit the grub.conf file by copying the previous entries and making a new >entry and changing the vmlinuz kernel pointer to the new bzImage filename. All the above is quite correct although I do "make dep clean && make bzImage modules && make modules_install" as one command. (The && means "continue if last completed successfully") This allows one to go and get coffee, returning to find a built kernel or the reason why the build failed... Then as you do, copy the new kernel to /boot and modify the bootloader accordingly. As I build my root filesystem driver into the kernel I don't need to update initrd - but I have seen it done and the process involves mkinitrd. "man mkinitrd" (sorry ;> ) hih nick@nexnix >What is missing? How do i do the initrd setup? > >-----Original Message----- >From: Nick Lindsell [mailto:[EMAIL PROTECTED]] >Sent: Monday, February 17, 2003 9:46 AM >To: [EMAIL PROTECTED] >Subject: RE: Custom Kernel wont boot > > >At 06:19 17/02/2003 -0800, you wrote: > >I compiled module support for ext3 which is the filesystem I use. I did not > >rebuild initrd with mkinitrd but I thought that the make install did that > >for me. Is this not correct? > >Hmm - not sure if "make install" does rebuild initrd. That's not a standard >feature so unless RedHat tweaked the Makefile then I don't suppose it will. > >Personally I build my kernels with hardwired support for the root >filesystem and whatever >hardware i need (eg scsi raid controller) to access said filesystem. Some >say this is best others not..... YMMV. > > >hih >nick@nexnix > > > >-----Original Message----- > >From: Nick Lindsell [mailto:[EMAIL PROTECTED]] > >Sent: Monday, February 17, 2003 9:18 AM > >To: [EMAIL PROTECTED] > >Subject: Re: Custom Kernel wont boot > > > > > >At 06:00 17/02/2003 -0800, you wrote: > > >I have Red Hat 8 setup with all the kernel-devel packages installed. I > >just > > >downloaded the 2.4.20 kernel and attempted to configure it. After I do > >setup > > >everything I rebooted. I am currently using the Grub boot manager and >when > >I > > >boot it gives me the following error: > > >'Cannot open root device "LABEL=/" or 00:00 > > >Please append a correct "root=" boot option > > >Kernel panic: VFS: > > >Unable to mount root on 00:00' > > > > > >I did a make install to add the line into the grub.conf file but this >error > > >still occurs. Any ideas? > > > >Did you build the relevant root filesystem support into the kernel or make > >it > >as a module and rebuilt initrd? > > > > > >hih > >nick@nexnix > > > > > > >Michael > > > > > > > > > > > >-- > > >redhat-list mailing list > > >unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe > > >https://listman.redhat.com/mailman/listinfo/redhat-list > > > > > > > >-- > >redhat-list mailing list > >unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe > >https://listman.redhat.com/mailman/listinfo/redhat-list > > > > > > > >-- > >redhat-list mailing list > >unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe > >https://listman.redhat.com/mailman/listinfo/redhat-list > > > >-- >redhat-list mailing list >unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe >https://listman.redhat.com/mailman/listinfo/redhat-list > > > >-- >redhat-list mailing list >unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe >https://listman.redhat.com/mailman/listinfo/redhat-list -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
