system: pc from 2004 with 2 IDE-HDs, multiboot. SuSE 10.1 

when upgrading with factory10.3 netinstall at 2007-09-28, 
the install system probes ata_piix before piix, generic etc.
This leads to IDE-drives which were hda, hdb in former 10.1 system, to be created as sda, sdb.
Grub-config shows error "mkinitrd: no driver for /dev/hda" or sth like that. (had no time to write down error, or to reproduce. Not my system)
Boot to install stage 2 fails, for initrd seems to be not created at all.

Trying to fix with install upgrade again, "repair", "boot existing system" all failed from factory10.3 netinstall CD.
mkinitrd also shows error sth like "in line xxx:...perl5/vendor <some error>" but this not the origin of the problem.

booting with brokenmodules=ata_piix gave the /dev/hdx devices, but fixing the broken boot or just booting the system still not possible no matter how i tried - probably due to no initrd.

I fixed with booting from 10.2 CD1 "repair system", then fixed (deleted sdx) fstab entries and reconfigured grub bootparams and this created working initrd.

This bug very similar to 
https://bugzilla.novell.com/show_bug.cgi?id=297999 ,and a little like
https://bugzilla.novell.com/show_bug.cgi?id=304125 and several others involving mkinitrd and yast-grubconfig.
In fact this seems to be 2 bugs: 
1. ata_piix creating scsii-devices on upgrading a system not configured like this.
2. grub/mkinitrd script somehow confusing devices in /dev and in fstab and some other sources(?). This error seems to stay despite labled "resolved" in prior reports.

Average user won't find a way to recover from this deadlock, so "severity critical"