|
Bugzilla – Full Text Bug Listing |
| Summary: | Update (from beta2) to RC1 didn't boot | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | Michael Matz <matz> |
| Component: | YaST2 | Assignee: | Jiri Srain <jsrain> |
| Status: | RESOLVED FIXED | QA Contact: | Klaus Kämpf <kkaempf> |
| Severity: | Blocker | ||
| Priority: | P5 - None | ||
| Version: | RC 1 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | Yast logfiles | ||
|
Description
Michael Matz
2005-09-08 18:07:30 UTC
Created attachment 49254 [details]
Yast logfiles
Let's assign it to Jiri who seems to deal with such kind of problems. 2) and 3) are direct results of 1) Ad 1) The device map has not been transfered correctly from the perl-Bootloader library to YaST. Unfortunatelly, I can't get from the logs why. Do you - by chance - have the original device map backed-up? I feel it could be caused by something void inside the file... I forgot that the originel device.map file is kept as /boot/grub/device.map.old (unless you ran YaST again after the unsuccessful update). So hope it won't be problem to get it. I tested the update Beta4->RC1 (I don't have any older image in Prague). The update was done without any problem, the device map was read correctly. So, I have no clue what could have caused this problem... Jiri, unfortunately device.map.old is empty on Michas box. I just checked it to keep things moving...: -rw------- 1 root root 0 2005-09-08 20:31 device.map.old I am logged there in, but thanks anyway. It may have two reasons: 1. device.map was empty before update (bug is INVALID) 2. Michael ran YaST again (we dont' know anything) I talked to AJ, I will workaround this bug (if empty device map is read from disk, it is automatically proposed). This is safe not to break anything. AFAIK Michael didn't ran YaST again, but he should know for sure ;) Then the bug could be marked as invalid. But as YaST reconstructs during update a lot of configuration options anyway, I find it good idea to check for empty device map. Another issue is that we don't know how the device map got empty... I did not run Yast again, after fixing. When I first logged in to the rescue system to fix grub, the device.map.old was already empty. It was the first I looked into because I hoped that it would contain a saved copy of the old working one. But it didn't. I also looked at the timestamps of that file, in order to see, if it was even touched by the install process, and indeed it was: -rw-r--r-- 1 root root 30 2005-09-08 20:47 /boot/grub/device.map -rw------- 1 root root 0 2005-09-08 20:31 /boot/grub/device.map.old 20:31 was about the time I installed the machine. So Yast did write and empty device.map.old. I of course don't know anymore if the original device.map _before_ update was empty. And that also can't be reconstructed anymore :( It was because when you got the fail during upadte, you tried it once more. So, "mv device.map device.map.old" was done twice. I forgot abuot it, sorry. The workaroudn I will submit in a moment will make sure that there won't be ampty map written during update. I see, thanks. Workaround submitted. As I can't learn what was in original device.map, this is the only fix I'm able to provide, therefore closing as FIXED. |