Bug 116698

Summary:	unbootable rc2
Product:	[openSUSE] SUSE LINUX 10.0	Reporter:	Dirk Mueller <dmueller>
Component:	Update Problems	Assignee:	Torsten Duwe <duwe>
Status:	RESOLVED WORKSFORME	QA Contact:	Klaus Kämpf <kkaempf>
Severity:	Normal
Priority:	P5 - None	CC:	duwe, jsrain, lnussel
Version:	RC 2
Target Milestone:	---
Hardware:	Other
OS:	All
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	y2logRPM.gz y2log.gz

Description Dirk Mueller 2005-09-13 07:16:39 UTC

after updating from rc1 to rc2 via y2pmsh / update / solve / commit I had an 
unbootable system. apparently grub-install wasn't run, I got a grub stage 2 
loading error.  
 
probably this has something to do with the non-mbr -> mbr switch, not sure. 
its oldboy.suse.de

Comment 1 Klaus Kämpf 2005-09-13 07:26:53 UTC

Please attach logs.  
  
Updating via y2pmsh is not officially supported. However, it should work  
nonetheless. Downgrading to 'normal'

Comment 2 Klaus Kämpf 2005-09-13 07:27:37 UTC

Ludwig, does y2pmsh write logs somewhere ?

Comment 3 Dirk Mueller 2005-09-13 07:32:01 UTC

Created attachment 49725 [details]
y2logRPM.gz

Comment 4 Dirk Mueller 2005-09-13 07:32:22 UTC

Created attachment 49726 [details]
y2log.gz

Comment 5 Ludwig Nussel 2005-09-13 14:02:06 UTC

y2pmsh just updates rpm packages so I'd expect the same to happen if you just 
rpm -U --force grub.rpm. Therefore I'd say it's a grub bug. The grub package 
does something with the stage2 file in it's post install script.

Comment 6 Jiri Srain 2005-09-26 11:02:42 UTC

Torsten, how does the GRUB package handle update of itself? It should not 
break booting of the system IMHO...

Comment 7 Torsten Duwe 2005-09-26 11:12:57 UTC

%post 
[...] 
[ -e /etc/grub.conf ] && /usr/sbin/grub --batch < /etc/grub.conf 
 
So whatever was written in grub.conf. The whole %post script has proven very 
robust so far. Shall I close as invalid (Dirk, I second your assumption that 
non-MBR back to evil MBR install is not handled properly), or reassign to yast 
people? 
 
Or have rpm %post semantics changed once more :-/