|
Bugzilla – Full Text Bug Listing |
| Summary: | grub install failed after upgrad | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.1 | Reporter: | Lars Müller <lmuelle> |
| Component: | Bootloader | Assignee: | Jiri Srain <jsrain> |
| Status: | RESOLVED INVALID | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Critical | ||
| Priority: | P5 - None | CC: | duwe, forgotten_2Bw2fCSUmf, jreidinger, jsrain |
| Version: | Factory | ||
| Target Milestone: | --- | ||
| Hardware: | i586 | ||
| OS: | openSUSE 11.0 | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
y2logs as created with save_y2logs
Archive of /boot/grub |
||
|
Description
Lars Müller
2008-11-13 20:38:10 UTC
can you please attach your log files? Created attachment 253806 [details]
y2logs as created with save_y2logs
Could you, please, also attach contents of /boot/grub directory? Or, have you indentified which file was missing? should be related to bug 450841 Same error with RC 1. Created attachment 257270 [details]
Archive of /boot/grub
I do not see any reason why GRUB fails to install (maybe except known problem with storing long device paths). Torsten, can you have a look? Where is /dev/sda1 mounted, on / or /boot? lmuelle@gab:~> mount | grep sda1 /dev/sda1 on / type ext2 (rw,acl) Then your initial description is lacking a "/boot". Your Logs are not consistent in that respect. Which one is correct? Please provide a consistent report. Please provide a consistent report. The initial description was a copy and paste from the error shown by YaST. And I don't know which information is missing. /boot is not a separate partition. But according to the log in the initial comment, /etc/grub.conf is configured as if there was a separate /boot partition. Since /etc/grub.conf is not modified during update, it must have been that case before the update. If your /etc/grub.conf was correct before update, installation would have succeeded. Update of bootloader with broken configuration files cannot work (and since there is no bootloader configuration UI during update, they cannot even be fixed to match user's expectation). Strange as this system was initially installed with YaST and updated from 10.1 till the current state. But can you reproduce this? Jiri and I strongly doubt so. There must have been some intervention. I'm not able to reproduce this as this would require to install 10.1 and upgrade to 10.2, ..., 11.1 RC X. I used a lot of beta releases on this system too. Therefore I'm happy as long as this doesn't happen happen to other users. |