https://bugzilla.novell.com/show_bug.cgi?id=330705#c1 --- Comment #1 from andreas bittner 2007-10-04 10:28:08 MST --- Created an attachment (id=176380) --> (https://bugzilla.novell.com/attachment.cgi?id=176380) firststep: cleaninstall opensuse 10.2 textmode (from x86 dvd) testcase: cleaninstall of x86 opensuse 10.2 from download dvd media. y2logs after setup is done with all steps. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=330705#c3 --- Comment #3 from andreas bittner 2007-10-04 10:35:38 MST --- so i have attached two files here, y2log directory of another test on my testsystem. thistime i made a quicker and plain textmode installation. installed x86 10.2 from dvd media, selected minimal textmode system for installation. i have created several partitions, first = swap, second = /boot third = / hda4 = extended for the whole rest of the hdd hda5=usr hda6=var and hda7=opt all inside the hda4 extened one. filesystem was ext3 for everything 10.2 installation completed allright. after that, i tried my upgrade of this minimalistic 10.2 system with the opensuse 10.3 x86 dvd download media. everything is still as i have described. the yast/install-module doesnt detect the old 10.2 installation, you have to check show all partitions, to be able to see /dev/hda3 for the old / (root) partition then it asks exactly for two more partitions so that i point /dev/hdaX to /dev/sdaX it only asks for the old /usr and the old /opt partitions to point to the new name. and i suppose, that this is the big mistake. the system upgrades the 10.2 packages to 10.3 ones without any visible problems. it tries to install the bootmanager and so forth, but fails there with grub. end of story. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=330705 Stephan Kulow changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.provo.novell.com |fehr@novell.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=330705#c6 --- Comment #6 from Christian Boltz 2007-10-08 05:37:00 MST --- Mounting /var is a good idea, but you never know if it really works - some people (like me) have interesting disk layouts. (In reply to comment #5 from Thomas Fehr)

From y2log: RootPart.ycp:613 There are only 0 files in /var/lib/hardware/, translation needn't work!

And please, as I already proposed in bug 299667, please let YaST display an error message if it can't find files in /var/lib/hardware like Can't find any files in /var/lib/hardware. This means you'll have to modify /etc/fstab, /etc/cryptotab, /boot/grub/menu.lst and /boot/grub/device.map (or lilo.conf if you use lilo) to switch them to the new /dev/sd* naming scheme. [Retry] [Ignore] (retry should check /var/lib/hardware again, maybe the user mounted the partition manually) Of course, this doesn't solve the problem, but at least the user is aware of it and has a chance to work around it. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=330705#c8 --- Comment #8 from andreas bittner 2007-10-08 07:15:28 MST --- hello there, i dont quite understand the discussion about this bug. how come the upgrade fails if the /var/ is on a separate partition, but only when coming from oldstyle ide names /dev/hdX i did an install on sata-only hardware already with clean opensuse 10.2 using dev/sdX names and still /var/ being on a separate partition. opensuse 10.3 upgrade from this sata-only 10.2 system just works fine. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=330705#c10 Lukas Ocilka changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |locilka@novell.com AssignedTo|locilka@novell.com |aschnell@novell.com --- Comment #10 from Lukas Ocilka 2007-10-09 03:13:20 MST --- update/rootpart.ycp:274 Selected root partition: /dev/sda3 $[`arch:"i386", `arch_valid:false, `fs:`ext3, `fstype:"Linux native", `label:"", `name:"openSUSE 10.2", `valid:false] RootPart.ycp:1157 mount partitions: /dev/sda3 FileSystems.ycp:75 SuggestMPoints init:["/", "/usr", "/var", "/opt", "/boot", "/home", "/srv", "/tmp", "/local", ""] Update.ycp:490 SuSERelease::ReleaseInformation: openSUSE 10.2 Fstab describing /var partition $["file":"/var", "freq":1, "mntops":"acl,user_xattr", "passno":2, "spec":"/dev/hda6", "vfstype":"ext3"] Anyway, mounting the /var partition has been solved by Arvin already (reassigning). It seems we need to clean the code up :( Which means - rewrite. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=330705#c12 --- Comment #12 from Lukas Ocilka 2007-10-09 08:11:43 MST --- A workaround already exists (I'm thinking about writing an article ;) ), * boot the system you want to upgrade * run `yast2 disk` * change mountpoints not to use device names (/dev/hda) but LABEL or device ID, or anything else (but not device name) * reboot to the installation Does it work? Well, maybe changing the mountpoints (/etc/fstab) doesn't work when those devices are already mounted :( but anyway, changing /etc/fstab directly on a system could work. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=330705#c14 --- Comment #14 from andreas bittner 2007-10-09 15:15:59 MST --- Created an attachment (id=177225) --> (https://bugzilla.novell.com/attachment.cgi?id=177225) 10.2 to 10.3 upgrade scenario with manually edition fstab lines as advised: 10.2 to 10.3 upgrade scenario with manually edition fstab lines from old pata-style /dev/hdaX to "something else but device names", so i changed them to something like "/fantasydev/hdaX". see comment #13 https://bugzilla.novell.com/show_bug.cgi?id=330705#c13 thanks. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=330705#c17 --- Comment #17 from andreas bittner 2007-10-15 09:51:56 MST --- hi again, you cant be serious about this, right? this is how i see this bug from an enduser point of view: your upgrade mechanism doesnt ask/handle the partitions found in fstab properly. why on earth would your installer ask for usr and opt just fine and mount them, and simply disregard the partition for /var... it never asks for /var... and besides: how hard cand it be to analyze fstab and if you have found partitions on a physical drive and mapped them from oldname /dev/hdaX to /dev/sdaX already, then simply map all the partitions that are listed in fstab.... why does yast installer ask for /opt and /usr just fine, but never asks to point to the proper location from old /dev/hda6 = /var to /dev/sda6... why not simply exchanging/offering all the device rootnames once a device has been identified and corrected from an oldname to newname? so if i have given yast the information that my / (root) parition is on /dev/sda3 now which was listed in my old fstab as /dev/hda3, then yast knows that what was once /dev/hda is now /dev/sda.... and everything that exists in /dev/hda now is on /dev/sda... this is the most logical and basic thing there is. as sda and hda are physical disk names, and the numbers after the rootname of the physical disks are parititon numbers... how in earth could this be a problem for the installer/upgrade mechanis, and how can suse lower the importance of this bug to "enhancement" this is simply crazy and to freak out. i dont get it why i still am buying suse retail releases on and on.... i am really freaking out about this i am sorry, but i have to write this down, cos i still think i am only dreaming all this mess: you people mess up a simple upgrade process from a clean and simple installation of your very previous version of opensuse and dont support an upgrade just because customers use partitions for mountpoints your installer/tools offer? you gotta be kidding me. there is nothing so special or magic about a /var partition, but nevertheless suse messes up handling it properly, just because if who knows why some of the devs decided to switch naming convention just all of a sudden for classical hardware. and while thinking about this "problem" i have explained why i fail to see the "big problem" with finding the partitions.... if you found just one of the new names (on a physical disk/device), then you have found them all... simply replace all of the fstab entries with the old device name to the new devicename the customer/user once has identified/supplied, or the installer has properly found. this cant be that hard. or am i missing a point or is there more to this whole confusion with the naming convention change? why not asking the user just to point to all of the partitions that are listed in the customers fstab file, instead of omitting the var partition just because of who knows why. i really really dont get it. i really think i do gotta change to some other distribution for sure and advise others to do so too if this is the real philosophy of suse/novell. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=330705#c19 --- Comment #19 from Lukas Ocilka 2007-10-15 09:57:43 MST --- BTW: this affects the installation media and can't be changed for the already released ones, that's why I've changed it to enhancement and that's why I'm spending a lot of time to make it better. I'm sorry, but for openSUSE 10.3, the only way is to offer you a workaround (that article). And yes, your wishes and ideas will probably be implemented for openSUSE 11.0 but it can't be done earlier. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=330705#c21 --- Comment #21 from Lukas Ocilka 2007-10-15 10:19:05 MST --- Remastering makes sense if no other workaround exists. But an easy workaround really exists, I'll post it soon. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=330705#c23 --- Comment #23 from Lukas Ocilka 2007-10-15 10:27:37 MST --- Basically it seems to be the Bootloader issue which means: not-installation/upgrade issue anymore (it's really different). Please, file a separate bugreport. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=330705#c25 --- Comment #25 from andreas bittner 2007-10-15 10:40:34 MST --- Created an attachment (id=178580) --> (https://bugzilla.novell.com/attachment.cgi?id=178580) changed fstab to device-id entries - y2log from 10.2 to 10.3 changed the fstab lines with "yast2 disk" from /dev/hdaX to device-id lines to for example /dev/disk/by-id/ata-SAMSUNG_xxxxxxx-part1 upgrade process from 10.2 clean to 10.3 still crashes at the end with grub error while trying to install/upgrade the bootloader parts. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=330705#c27 --- Comment #27 from Lukas Ocilka 2007-10-16 10:00:55 MST --- (In reply to comment #26 from Christian Boltz)

Sidenote: In your HowTo, YaST-Disk-Overview.png is displayed as broken image. It results in a 404 error on files.opensuse.org.

Well, I just uploaded a PNG file and that's the result. Seems to be some kind of wiki bug or ...? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=330705 User abittner@stud.fh-heilbronn.de added comment https://bugzilla.novell.com/show_bug.cgi?id=330705#c29 --- Comment #29 from andreas bittner 2008-06-02 15:08:06 MDT --- hi there, back to this bug again, i did an opensuse 10.1 to 10.3 upgrade. the workaround at http://en.opensuse.org/How_To_Upgrade_System_with_Separate_/var_Partition is not complete / faulty. did you guys actually try what you have written and documented there? :( first of all, labeling a mounted partition doesnt work at all, i get constant error "-3024" or such from the yast "disk" module when trying to set the label for the /var partition and change the mounting style still in the old 10.1 system. second the screenshot http://files.opensuse.org/opensuse/en/7/78/YaST-Disk-FstabOptions.png clearly displays the radiobutton at "mount device by name", although the device label field is filled out and the whole workaround is supposed to mount the /var by label, so the radiobutton "volume label" needs to be selected ofcourse, otherwise it doesnt do anything at all to fstab. and then there is the issue that the volume label apparently cant be changed/written to a mounted partition, and booting into the old system uses all the partitions, thus needing to go to "init S" / single user mode and dismount all the disks as /var is a essential partition to many processes and stuff that needs to be actively dismounted and programs and daemons ended so that the /var partition can be cleanly dismounted and then the yast disk module being able to write its label stuff. finally, the whole process (upgrade to 10.3) didnt really work after all, the label stuff not helping that much. the packets get installed/upgraded so far so good, but the bootloader installation at the end fails utterly. i tried to look around in /etc and in /boot and all kinds of places where there could be some leftovers and problems, but during the last steps where the 10.3 upgrade tries to write the grub bootloader it gives many errors. i will upload the yast2 log directory. please do analyze the logs and fix this grub bug. i still havent managed to start this messed system. grub complains about missing bootup-screens (thats not really a problem), then the textmode grub startsup but then it gives all kinds of errors with old and new /dev/sda and /dev/hda errors and all that stuff and never boots anything. i tried to bootup some rescue / live cd opensuse and tried to look around and fix some stuff, but to no avail, im not that of a grandmaster in fixing opensuse upgrade messes :( thanks. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=330705 User locilka@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=330705#c31 --- Comment #31 from Lukas Ocilka 2008-06-04 08:43:33 MDT --- Andreas, you're right. I've tried to change the LABEL for /var partition and it failed. Anyway, using UUID worked and all disks are found even if I've changed their order. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=330705 User abittner@stud.fh-heilbronn.de added comment https://bugzilla.novell.com/show_bug.cgi?id=330705#c33 --- Comment #33 from andreas bittner 2008-06-04 08:48:38 MDT --- ok so if the uuid works does that mean that the last grub-step also works fine with using uuid instead of label after all? the only problem is now, that this other system i tried to upgrade is messed, how can i fore to reinstall the grub system and creating initrd and all this from the last step properly. even from inside a chroot on the system itself didnt work out :( thanks. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=330705 User abittner@stud.fh-heilbronn.de added comment https://bugzilla.novell.com/show_bug.cgi?id=330705#c35 --- Comment #35 from andreas bittner 2008-06-26 07:43:01 MDT --- Created an attachment (id=224566) --> (https://bugzilla.novell.com/attachment.cgi?id=224566) grub errors - upgrading clean opensuse 10.2 to 11.0 goldmaster did a cleaninstall of 10.2 today with separate /boot / /usr and /var partitions. and then upgraded to 11.0 goldmaster. install went fine apparently most of the time, it detected and renamed the old /dev/hdaX partition names to /dev/sdaX but at the end there were some errors, grub related i think, so that the grub menu still displays the old opensuse 10.2 kernel/entry selected as default after the first initial reboot after 11.0 setup/upgrade. apparently there is still something wrong with the grub configuration related to these changing partition names :( was there a separate followup bug to this issue here that was handling the grub/bootloader errors? here are the logs. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=330705 User locilka@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=330705#c36 Lukas Ocilka changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks|404114 | --- Comment #36 from Lukas Ocilka 2008-06-26 07:55:47 MDT --- See bug 404114, your GRUB error has been reported there. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=330705 User locilka@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=330705#c38 --- Comment #38 from Lukas Ocilka 2008-06-26 07:58:02 MDT --- *** This bug has been marked as a duplicate of bug 270908 *** https://bugzilla.novell.com/show_bug.cgi?id=270908 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.