|
Bugzilla – Full Text Bug Listing |
| Summary: | grub menu.lst entry for existing install does not include initrd | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | Will Stephenson <wstephenson> |
| Component: | Installation | Assignee: | Jiri Srain <jsrain> |
| Status: | RESOLVED FIXED | QA Contact: | Klaus Kämpf <kkaempf> |
| Severity: | Major | ||
| Priority: | P5 - None | CC: | gchristensen, jpeterse77, martin |
| Version: | Beta 1 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
YaST2 logs
YaST2 log file, starting after the main installation |
||
|
Description
Will Stephenson
2005-08-11 08:47:04 UTC
Please, attach the YaST logs. I had a similar problem, just that in my case the "initrd" line was not missing but contained only the word "initrd", nothing else. Created attachment 45969 [details]
YaST2 logs
Jiri, please have a look. Done in SVN, please, test with Beta3. *** Bug 106135 has been marked as a duplicate of this bug. *** I've installed RC2 because I've a similar problem with RC1. This problem can be reported within this bug report or maybe within #105660. The main aspect is another existing Linux that should be booted via bootloader. Rebooting and choosing another Linux leads to a kernel panic due to missing initrd entry. What I've done to reproduce my observation: I've done a new installation with standard selection - for partitioning I've used /dev/hda8 - the selection of the partition is rather arbitrary. Next follows the fdisk output for that disk: Disk /dev/hda: 60.0 GB, 60011642880 bytes 16 heads, 63 sectors/track, 116280 cylinders Units = cylinders of 1008 * 512 = 516096 bytes Device Boot Start End Blocks Id System /dev/hda1 1 17240 8688928+ 7 HPFS/NTFS /dev/hda2 * 17241 116280 49916160 f W95 Ext'd (LBA) /dev/hda5 17241 19321 1048792+ 82 Linux swap / Solaris /dev/hda6 19322 40127 10486192+ 83 Linux /dev/hda7 40128 56772 8389048+ 83 Linux /dev/hda8 56773 73417 8389048+ 83 Linux /dev/hda9 73418 90062 8389048+ 83 Linux /dev/hda10 90063 116280 13213840+ 83 Linux The main installation works and the menu.lst file seems to be correct. Booting another Linux works as expected. Then I edit the names via YaST within bootloader configuration using the YaST text interface. This leads to a different menu.lst file with the consequence that booting of another Linux is no longer possible. After diffing the menu.lst files the difference is obvious: ---8<--- 1c1 < # Modified by YaST2. Last modification on Di Sep 13 18:53:29 UTC 2005 --- > # Modified by YaST2. Last modification on Di Sep 13 21:26:23 CEST 2005 15c15,16 < title Linux (/dev/hda7) --- > > title SUSE LINUX 9.1 17d17 < initrd (hd0,6)/boot/initrd 20c20,21 < title SUSE LINUX 9.3 (/dev/hda9) --- > > title SUSE LINUX 9.3 22d22 < initrd (hd0,8)/boot/initrd ---8<--- Created attachment 49830 [details]
YaST2 log file, starting after the main installation
This only happens during a manual change via YaST. The automatically generated config was correct. Jiri, please investigate and let's think about an Online Update. If there is need for the complete logs, I've saved info about the basic
installation and the post bootloader configuration:
/var/log/YaST2/y2log*
/boot/grub/*
This has been seen on two different systems and reproduced on a T41p.
*** Bug 118531 has been marked as a duplicate of this bug. *** I successfully reproduced Joerg's problem. Ok for 10.0 - please submit with one of the other bugs in this area. Yes, will submit together and with 1 patchinfo with bug 119428. Already done in SVN. released |