|
Bugzilla – Full Text Bug Listing |
| Summary: | Update 9.3 -> 10.0 b4+ do not work | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | Karsten Keil <karsten.keil> |
| Component: | Update Problems | Assignee: | Michael Andres <ma> |
| Status: | RESOLVED FIXED | QA Contact: | Klaus Kämpf <kkaempf> |
| Severity: | Blocker | ||
| Priority: | P5 - None | CC: | jsrain, mvidner |
| Version: | Beta 4 Plus | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| Found By: | Development | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | tar ball of the Y2 log files | ||
|
Description
Karsten Keil
2005-09-07 12:23:13 UTC
Created attachment 49047 [details]
tar ball of the Y2 log files
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. 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. (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?
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 You need to update udev also. Preferrably prior to running mkinitrd. 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. Hmm, according to the log (y2logRPM) , udev wasn't updated (the one in the list comes from the original installation). Michael, any clue why? 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. 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. That udev was not updated does not make the complete bug invalid, only the second part. Read comment #5. |