Bug 444809 - grub install failed after upgrad
Summary: grub install failed after upgrad
Status: RESOLVED INVALID
Alias: None
Product: openSUSE 11.1
Classification: openSUSE
Component: Bootloader (show other bugs)
Version: Factory
Hardware: i586 openSUSE 11.0
: P5 - None : Critical (vote)
Target Milestone: ---
Assignee: Jiri Srain
QA Contact: Jiri Srain
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-11-13 20:38 UTC by Lars Müller
Modified: 2008-12-03 13:48 UTC (History)
4 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
y2logs as created with save_y2logs (1.06 MB, application/x-gzip)
2008-11-20 10:26 UTC, Lars Müller
Details
Archive of /boot/grub (277.78 KB, application/x-bzip2)
2008-12-02 14:11 UTC, Lars Müller
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Lars Müller 2008-11-13 20:38:10 UTC
Upgraded the system from 11.0 to 11.1 Beta 5 with the Network Install method (http://en.opensuse.org/Network_Install).  After the failed kernel install (see bug #444804) YaST displayed a grub error message:


    GNU GRUB  version 0.97  (640K lower / 3072K upper memory)

 [ Minimal BASH-like line editing is supported.  For the first word, TAB
   lists possible command completions.  Anywhere else TAB lists the possible
   completions of a device/filename. ]
grub> root (hd0,0)
 Filesystem type is ext2fs, partition type 0x83
grub> install --stage2=/boot/grub/stage2 /grub/stage1 d (hd0) /grub/stage2 0x8000 (hd0,0)/grub/menu.lst

Error 15: File not found
grub> quit
Comment 1 Stephan Kulow 2008-11-20 09:57:02 UTC
can you please attach your log files?
Comment 2 Lars Müller 2008-11-20 10:26:51 UTC
Created attachment 253806 [details]
y2logs as created with save_y2logs
Comment 3 Jiri Srain 2008-11-20 14:09:48 UTC
Could you, please, also attach contents of /boot/grub directory? Or, have you indentified which file was missing?
Comment 4 Josef Reidinger 2008-12-02 13:18:28 UTC
should be related to bug 450841
Comment 5 Lars Müller 2008-12-02 14:08:43 UTC
Same error with RC 1.
Comment 6 Lars Müller 2008-12-02 14:11:34 UTC
Created attachment 257270 [details]
Archive of /boot/grub
Comment 7 Jiri Srain 2008-12-02 14:56:35 UTC
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?
Comment 8 Torsten Duwe 2008-12-02 15:42:58 UTC
Where is /dev/sda1 mounted, on / or /boot?
Comment 9 Lars Müller 2008-12-02 17:13:25 UTC
lmuelle@gab:~> mount | grep sda1
/dev/sda1 on / type ext2 (rw,acl)
Comment 10 Torsten Duwe 2008-12-02 17:23:48 UTC
Then your initial description is lacking a "/boot".
Your Logs are not consistent in that respect.
Which one is correct?
Comment 11 Torsten Duwe 2008-12-02 17:24:49 UTC
Please provide a consistent report.
Comment 12 Torsten Duwe 2008-12-02 17:25:04 UTC
Please provide a consistent report.
Comment 13 Lars Müller 2008-12-02 17:38:50 UTC
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.
Comment 14 Jiri Srain 2008-12-03 09:14:48 UTC
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).
Comment 15 Lars Müller 2008-12-03 12:31:35 UTC
Strange as this system was initially installed with YaST and updated from 10.1 till the current state.
Comment 16 Torsten Duwe 2008-12-03 13:21:52 UTC
But can you reproduce this?
Jiri and I strongly doubt so. There must have been some intervention.
Comment 17 Lars Müller 2008-12-03 13:48:56 UTC
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.