|
Bugzilla – Full Text Bug Listing |
| Summary: | YaST doesn't list partition to upgrade | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 10.3 | Reporter: | Christian Boltz <suse-beta> |
| Component: | Update Problems | Assignee: | Thomas Fehr <fehr> |
| Status: | RESOLVED INVALID | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | aj |
| Version: | Beta 2 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
y2logs
for comparison: y2logs when booted with brokenmodules=ata_piix |
||
Created attachment 156961 [details]
for comparison: y2logs when booted with brokenmodules=ata_piix
The name of your disk changed from hda in 10.2 to sda in 10.3. This is normally detected and handled automatically by hwinfo and YaST2 by analyzing the content of /var/lib/hardware in the system to update. For reasons unknown to me, it seems there is no directory /var/lib on your root filesystem, therefore it is not possible to handle and update with changed disk names properly. Do you have any idea why you have no /var/lib directory in your root filesystem in /dev/hda5? Ah, my famous disk layout ;-) # ls -l /var # (date and owner removed) lrwxrwxrwx account -> ../home/var/account/ lrwxrwxrwx adm -> ../home/var/adm/ lrwxrwxrwx agentx -> run/agentx/ lrwxrwxrwx cache -> ../home/var/cache/ lrwxrwxrwx cvs -> ../home/var/cvs/ lrwxrwxrwx games -> ../home/var/games/ lrwxrwxrwx lib -> ../home/var/lib/ drwxrwxr-t lock/ drwxr-xr-x log/ lrwxrwxrwx mail -> spool/mail/ lrwxrwxrwx opt -> ../home/var/opt/ drwxr-xr-x run/ lrwxrwxrwx spool -> ../home/var/spool/ lrwxrwxrwx tmp -> ../home/var/tmp/ lrwxrwxrwx X11R6 -> ../home/var/X11R6/ lrwxrwxrwx yp -> ../home/var/yp/ /var/lib is a symlink to /home/var/lib, and /home is an encrypted partition. (Needless to say that YaST couldn't mount this partition because of bug 258222, however it usually doesn't even try in that early stage.) Oh, I think now I see where this issue could come from: - when the harddisk is recognized as hda, YaST at least knows that the symlink points to an existing partition found in /etc/cryptotab - when the harddisk is recognized as sda, YaST still searches for the encrypted partition as "hda6" (see bug 258222) which does not exist (it's "sda6" now) I think this bug is related to bug 258222, maybe even a strange duplicate. However I still wonder: If the partition is recognized as openSUSE 10.2, it should also be listed by default... Your disk layout is not supported. YaST2 is not able to update as system with such a layout. Please do not report any more bugs encountered during update on such a system. Huh? I'm using this disk layout since several releases, and never had problems with it. Maybe it doesn't match your "supported disk layouts" checklist, but the upgrade always works well ;-) Anyway, I expect this bug to be fixed with bug 258222 and will retest in beta2. It will break as soon as disk names change (as is the case between 10.2 and 10.3). Your expectation is wrong, this will not be fixed with bug 258222. So your retest with beta#2 makes not much sense, you can make this work by either manually changing your /etc/fstab to use sda instead of hda before update or by providing /var/lib/hardware into your root filesystem. reopening as recommended of AJ ;-)
first, YaST really didn't like my disk layout, causing lots of errors:
- /etc/fstab was not converted
-> nothing except / could be mounted
- /etc/cryptotab was not converted
-> my encrypted partition could not be mounted
- /boot/grub/device.map was not converted
second: YaST detects the partition as "openSUSE 10.2" when activating "show all partitions", so it should also list in the default view.
third: If YaST really needs data from an encrypted partition or directory (like /var/lib/hardware), it should ask for the password of encrypted partitions earlier.
forth: the encrypted partition was mounted after choosing the partition to update (and editing cryptotab), so the symlink got valid. (Yes, I use relative symlinks.) I don't see why it couldn't read /var/lib/hardware then.
fifth: if you really declare this as unsupported, there should at least be an error message ("can't access /var/lib/hardware on partition /dev/sdaX") - this would avoid lots of problems later.
y2logs: http://www.cboltz.de/tmp/y2logs-103b2.tar.bz2 - too large for bugzilla
If you use an encrypted /var, you have an unsupported system and update will not work. Thats it. |
Created attachment 156960 [details] y2logs I just tried to upgrade from 10.2 to 10.3b1. After choosing "upgrade" in YaST, the "choose partition" dialog was empty. After activating "show all partitions", my 10.2 system was listed - recogniced correctly as "openSUSE 10.2, i386". I could even continue the upgrade (at least until I hit another bug ;-) so the partition should be valid. The y2logs are attached to this report. (harddisk = sda) Another thing that might be relevant: In the next attemp, I booted with broken_modules=ata_piix to enforce hda as harddisk name. This time, the 10.2 partition _was_ listed as available for upgrade.