hi, i just upgraded an opensuse 10.2 (x86, download edtion) to the 10.3 goldmaster (x86, download edition). the releasenotes talk about this libata, pata, sata renaming stuff all right, but i'd never expected this complete desaster while upgrading my system. shutdown of opensuse 10.2 booting from opensuse 10.3 media (dvd iso image, burned to dvd, did media check before starting install, everything allright). first: opensuse 10.3 installer never found my previous system. the list was completely empty. so i had to check "show all partitions" or whats it called. then it came up with one opensuse 10.2 entry for my / (root) partition. allright. i had to answer some "/dev/hdaX not found" messages and was able to point to /dev/sdaX instead.... then it started to install, but at the end of the first installation step when writing the bootloader and initrd stuff, it gave me hugeloads of errors, still talking about old /dev/hdaX stuff and that it cand do all sorts of things :( so my system was completely trashed from there. trying to boot my harddisk still in the setup-mode gaves me loads of grub errors, this and that grub entries, lines and so forth not found and nothing happend. none of the grub entries worked or didn anything. it complained something about wrong entries like /dev/sda2,1 or /dev/sda2,x so i tried to boot once again from the 10.3 dvd media, and told the system to boot the installed system. to no avail. then once more, the menu "repair system"... loaded up some kernel files, and immediately resetted after that. always able to reproduce this reset-bug. whats going on with that function... is that actually supposed to work? then booted once again the 10.3 dvd, and selected install - then inside yast - other options, repair system.... to no avail again... it loads something and then gives me textmode (yast ncurses) with red error box, that some error has occured. end of story. so i tried to boot up 10.3 dvd with rescue, went into rescue login. mounted my partions into /mnt/ and /mnt/boot /mnt/var /mnt/opt and so on... tried to manually edit my /etc/fstab file, there were still loads of /dev/hdaX entries there. changed them to /dev/sdaX then i looked into /boot/ and thought that i might need to mkinitrd to be able to bootup the new system still in setupmode. i tried chroot /mnt/ but i couldnt do mkinitrd in there, as it complained about missing /dev/... and /proc/.... stuff it couldnt access. fdisk -l didnt work either, and the whole /proc/ was missing.... so i tried some final boot with the 10.3 media, selected install once more, and selected "upgrade" once again, over my partly upgraded (first step only) system. it only wanted to upgrade/install 2 more packages (some berkeley db rpms i think), then tried to write the booloater and initrd stuff all over again, and this time it succeeded. i guess because i had manually modified and fixed my /etc/fstab file in rescue mode before and the 10.3 installer also didnt complain about old /dev/hdaX entries at the beginning any more.... so now my system seems to be back online after this nightmare upgrade am i the only one to always get these install/upgrade troubles. i hate so write it again, but it has been many years back, that i didnt suffer from any upgrade problems with suse/opensuse. and i think i have pretty basic setups, no fancy disks, hardware, simple partitioning and nothing funny at all. still, suse linux manages to trash my system each and every time again, and the setup and other yast-modules crash on me on a frequent basis. :(( -- To unsubscribe, e-mail: opensuse-testing+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-testing+help@opensuse.org