|
Bugzilla – Full Text Bug Listing |
| Summary: | Used yast to switch from bigsmp to default kernel resulted in corrupted menu.lst | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 10.3 | Reporter: | Forgotten User 9WJQF5tTlz <forgotten_9WJQF5tTlz> |
| Component: | YaST2 | Assignee: | Jozef Uhliarik <juhliarik> |
| Status: | RESOLVED FEATURE | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | jplack, stefan.fent |
| Version: | Beta 1 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Beta-Customer | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
Yast generated backup of menu.lst, named menu.lst.old
Yast generated menu.lst with lost entries and missing kernel parameters. Repaired menu.lst complete /var/log/YaST2 broken menu.lst device.map grub.conf old menu.lst |
||
|
Description
Forgotten User 9WJQF5tTlz
2007-08-12 14:43:36 UTC
Could you add menu.lst - and also the backup, please? Created attachment 157055 [details]
Yast generated backup of menu.lst, named menu.lst.old
Created attachment 157056 [details]
Yast generated menu.lst with lost entries and missing kernel parameters.
Notice that the default menu selection is 2, not 0 as it was originally. The first kernel entry is missing the kernel parameters.
Created attachment 157057 [details]
Repaired menu.lst
This one is the manually repaired menu.lst. I've set default to 0, and restored the kernel parameters. Added the entry of SLED10 and its fail safe mode.
Will take care. Have the same on my laptop. I tested it with beta2. logs will be attched Created attachment 159693 [details]
complete /var/log/YaST2
Created attachment 159694 [details]
broken menu.lst
Created attachment 159696 [details]
device.map
Created attachment 159698 [details]
grub.conf
Created attachment 159700 [details]
old menu.lst
But the problem seems to be that there is no kernel installed at all. And even if I try to switch back to the bigsmp - no kernel is installed. Bootloader behaves as expected, reassigning Another Kernel.ycp (probably) issue, might be FaTE #159006 related The only complete log comes from Marco (comment #9). According to this log: 2007-08-26 22:42:12 <0> e103(8616) [zypp] ExternalProgram.cc(start_program):172 Executing '/bin/mount' '-t' 'nfs' '-o' 'ro,nolock,soft,timeo=10' '10.10.0.100:/dist/install/SLP/openSUSE-10.3-Build936-DVD/i386/DVD1' '/var/adm/mount/AP_0x00000001' 2007-08-26 22:42:12 <0> e103(8616) [zypp] ExternalProgram.cc(start_program):283 pid 8823 launched 2007-08-26 22:42:13 <0> e103(8616) [zypp] Mount.cc(mount):98 stdout: mount.nfs: No such device 2007-08-26 22:42:13 <0> e103(8616) [zypp] ExternalProgram.cc(checkStatus):330 pid 8823 exited with status 32 2007-08-26 22:42:13 <0> e103(8616) [zypp] Mount.cc(Status):251 exit code: 32 2007-08-26 22:42:13 <2> e103(8616) [zypp] Mount.cc(mount):144 mount 10.10.0.100:/dist/install/SLP/openSUSE-10.3-Build936-DVD/i386/DVD1 /var/adm/mount/AP_0x00000001: Mounting media failed Looks like some problem accessing the server with the repository. Marco, can you check it? I just tested it here in our local environment, and the kernel switch succeeded. Just installed from scratch and didn't had the problem this time. If you want then I can try another installation and rip out the network cable. IMHO it should not delete the kernel if there is no connection to the source. OK, since it works now, decreasing the severity. The reason why the old kernel was removed is that YaST first deleted the old kernel and afterwards downloaded new one. The network connection is not the only thing that can break - the package may be missing on the media, its signature may be wrong, etc. It is not possible to download everything first and then start the transaction (since some users do not have enough free disk space). Passing to Olaf to try to find a way to preserve the kernel parameters in case of kernel removal followed by kernel installation. However, this is definitly not a blocker. No ressources assigned here right now, will address problem later reevaluate for SLE11 assign to yast2-bootloader maintainer there exist fate request #302245. it solves problem with lost args for kernel params. |