https://bugzilla.novell.com/show_bug.cgi?id=309040#c14
--- Comment #14 from Richard Creighton
See comment #7:
--- cut --- But for now, the root cause is the IDE/SATA issue followed by the upgrade bootloader failure which is the subject of this bug. Is the install upgrade bootloader different than the install new bootloader? It would seem so. --- cut ---
I have to admit that I'm totally lost in this bug...
Good morning Lukas. This bug started out because 10.3 could not update my 10.2 MD Raid installation. It evolved into something having little to do with MD Raid and something to do with the IDE/SATA renaming decision and implementation. This has generated, and is continuing to generate bug reports even in the GM from what I am seeing, and there are three main issues that have surfaced while debuging this original issue. First, The installer has problems determining that a current MD Raid partition exists for upgrading and using that structure the same as it would as if it were a physical structure. 10.2 did this properly. Secondly, Because the IDE drive gets renamed from HDxx to SDAx during the upgrade but after the files are installed onto the SATA drives, when the MBR is updated and the /boot and GRUB files are updated, the installer expects to put them on what was SDAx (the SATA drive that has the new installation) but due to the renaming, SDAx is now the IDE drive which is the drive that gets the new MBR and /boot information by error. Third, The repair program absolutely knows nothing about MD Raid and insists on 'repairing' the raw SATA partitions and not the MD raid file system contained on them. As the repair program is running fsck which checks file systems, it should check file systems, not physical devices those file systems reside on., eg, it should check fsck /dev/md1 not fsck /dev/sdb1 when sdb1 is part of a MD array. Thus, this bug really should be divided into 3 bugs for admin purposes, but that isn't my perogative as a user. I reported the base problem and am hoping to amplify my findings as to the cause based upon months of research and experimentation. I am not a systems programmer but I am willing to try to solve the problem. It appears this problem is going to bite SuSE hard in several areas in GM when people with IDE equipment start trying to upgrade vs new installs. I hope this helps. -- 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.