Bug 115581 - Update 9.3 -> 10.0 b4+ do not work
Summary: Update 9.3 -> 10.0 b4+ do not work
Status: RESOLVED FIXED
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: Update Problems (show other bugs)
Version: Beta 4 Plus
Hardware: Other All
: P5 - None : Blocker
Target Milestone: ---
Assignee: Michael Andres
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-09-07 12:23 UTC by Karsten Keil
Modified: 2005-09-08 13:52 UTC (History)
2 users (show)

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


Attachments
tar ball of the Y2 log files (305.40 KB, application/octet-stream)
2005-09-07 12:35 UTC, Karsten Keil
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Karsten Keil 2005-09-07 12:23:13 UTC
1. The update overwrite the MBR, the old config was not related to the MBR. 
2. it cannot create a valid init rd -> doesn't boot after update finished. 
 
logs follows.
Comment 1 Karsten Keil 2005-09-07 12:35:03 UTC
Created attachment 49047 [details]
tar ball of the Y2 log files
Comment 2 Karsten Keil 2005-09-07 12:39:24 UTC
The old grub.conf was: 
setup --stage2=/boot/grub/stage2 (hd1,8) (hd1,8) 
quit 
 
during update following grub.conf was created: 
setup --stage2=/boot/grub/stage2 (hd1,8) (hd1,8) 
setup --stage2=/boot/grub/stage2 (hd0) (hd1,8) 
quit 
 
I think, during update grub.conf should be only touch if grub.conf syntax was 
changed, here is no need to add MBR or change bootloader locations. 
 
Comment 3 Karsten Keil 2005-09-07 12:42:19 UTC
Please drop me a short info, if you need some more infos/files. I'll change 
this partion in 30 minutes to test for more update problems. 
 
Comment 4 Martin Vidner 2005-09-08 08:45:28 UTC
(I do not know the code but let's get some info before Jirka arrives.)  
  
> 2. it cannot create a valid init rd -> doesn't boot after update finished.  
  
Karsten, how did you find out that it couldn't create initrd? Did a popup say  
so or was there different evidence?  
Comment 5 Jiri Srain 2005-09-08 12:28:14 UTC
1. The error was even in configuring bootloader in installed system. Fixed in 
SVN, will go to RC2. 
 
2. mkinitrd is being run, but reports some errors. Hannes (see y2logmkinitrd)? 
 
cp: Aufruf von stat für „/lib/klibc/sbin/ata_id“ nicht möglich: Datei oder 
Verzeichnis nicht gefunden 
cp: Aufruf von stat für „/lib/klibc/sbin/scsi_id“ nicht möglich: Datei oder 
Verzeichnis nicht gefunden 
cp: Aufruf von stat für „/lib/klibc/sbin/usb_id“ nicht möglich: Datei oder 
Verzeichnis nicht gefunden 
cp: Aufruf von stat für „/lib/klibc/sbin/vol_id“ nicht möglich: Datei oder 
Verzeichnis nicht gefunden 
cp: Aufruf von stat für „/sbin/path_id“ nicht möglich: Datei oder Verzeichnis 
nicht gefunden 
Shared libs:    ldd: /lib/klibc/sbin/ata_id: Datei oder Verzeichnis nicht 
gefunden 
ldd: /lib/klibc/sbin/scsi_id: Datei oder Verzeichnis nicht gefunden 
ldd: /lib/klibc/sbin/usb_id: Datei oder Verzeichnis nicht gefunden 
ldd: /lib/klibc/sbin/vol_id: Datei oder Verzeichnis nicht gefunden 
ldd: /sbin/path_id: Datei oder Verzeichnis nicht gefunden 
 
Comment 6 Hannes Reinecke 2005-09-08 12:31:15 UTC
You need to update udev also. Preferrably prior to running mkinitrd.
Comment 7 Hannes Reinecke 2005-09-08 12:32:19 UTC
But surely YaST will do this. The snag is that mkinitrd is called during
installation of a new kernel, so you have to make sure that udev and mkinitrd is
updated prior to installing a new kernel.
Comment 8 Jiri Srain 2005-09-08 12:43:07 UTC
Hmm, according to the log (y2logRPM) , udev wasn't updated (the one in the 
list comes from the original installation). Michael, any clue why?  
Comment 9 Michael Andres 2005-09-08 13:30:30 UTC
The installed klibc-devel and udev packages have an empty vendor field. So they
are non-SuSE packages and are per default set to taboo. The list of probabely
problematic packages, available after the packages were calculated, should have
listed them.

Per default foreign packages are not automaticaly replaced.
Comment 10 Karsten Keil 2005-09-08 13:41:10 UTC
Yes, so far I remember I updated udev with some version from STABLE to test 
newer kernels on 9.3. The problem is, that we did not offer a proper udev 
update for 9.3 to support newer kernels, so many people will run into this 
problem. 
 
I 'll retest the update with RC1 and a clean 9.3 version. 
 
Comment 11 Karsten Keil 2005-09-08 13:51:06 UTC
That udev was not updated does not make the complete bug invalid, only the 
second part. 
Comment 12 Jiri Srain 2005-09-08 13:52:51 UTC
Read comment #5.