From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4b) Gecko/20030410 Description of problem: This has happened before, but I dismissed it earlier as an unrelated problem and a problem w/ my own configuration. However, after installing the latest kernel release from RHN (kernel-2.4.20-13.9) for my i686, when trying to boot this kernel using grub, I get the following kernel panic: VFS: Cannot open root device "LABEL=/" or 00:00 Please append a correct "root=" boot option Kernel panic : VFS: Unable to mount root fs on 00:00 Because this has happened before, I know that the grub.conf in my seperate /boot partition was written wrong by the installation rpm downloaded from RHN. Either the file was corrupted a second time, or the rpm was built wrong. Then again, it could be the RPM program itself. Either way it's very important. I am posting a copy of my bad grub.conf file, and I will upload the corrected one at a later time. Version-Release number of selected component (if applicable): rpm-4.2-0.69, up2date-3.1.23-1 How reproducible: Always Steps to Reproduce: 1.Download and install the latest kernel update from RHN using up2date 2.Reboot the computer, and use GRUB to boot RH w/ recently installed kernel 3. Actual Results: Receiver Kernel panic: VFS: Cannot open root device "LABEL=/" or 00:00 Please append a correct "root=" boot option Kernel panic : VFS: Unable to mount root fs on 00:00 Expected Results: Boot properly Additional info: Workaround is possible just by fixing the grub.conf file, but I feel that this could discourage any inexperienced person trying to learn linux from pursuing it farther. This problem really needs to be alleviated.
Created attachment 91939 [details] Bad GRUB config file generated by up2date (or rpm)
Created attachment 91940 [details] Corrected GRUB Config Changes to the file, have been commented.
Download the latest kernel from RH (2.4.20-18.9). When rpm installed, it made the same error as usual, mixing up the LABEL=/ option and the root= option. This is a fairly reoccuring and important but, and I am not sure why I am not getting a response.
Created attachment 92275 [details] Bad GRUB file generated after 2.4.20-18.0 update The error is consistent and needs to be fixed.
Why is this being assigned now? It's been over two years.
Development Management has reviewed and declined this request. You may appeal this decision by reopening this request.