https://bugzilla.novell.com/show_bug.cgi?id=304657 Summary: Yast2 repair doesn't check or repair system installed on MD Raid Product: openSUSE 10.3 Version: Beta 2 Platform: i686 OS/Version: openSUSE 10.3 Status: NEW Severity: Major Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: rccj@ricreig.com QAContact: jsrain@novell.com Found By: Beta-Customer Created an attachment (id=159847) --> (https://bugzilla.novell.com/attachment.cgi?id=159847) Folder containing several supporting files and screenshots I installed Beta 2 on a MDRaid system in its entirety IAW the HowTo on the OpenSUSE.org website starting with Alpha 5. Upgrading to Beta 2, I wanted to verify the installation so I tried the INSTALLATION REPAIR on the CD. It tried to repair everything EXCEPT the installed beta 2 system. I had a 10.2 system on a IDE drive that it went after and it ignored the MD partitions but tried to mount the drives making up the MD array. It also tried to modify the 10.2 GRUB and FSTAB. I rebooted the 10.3 and ran yast2-repair which did the same thing and I was able to document what it looked like as an attachment. I am attaching my partition tables (note the 10.2 drive was NOT mounted) the fstab of the running 10.3 system, the 10.3 grub files and various screen shots of the 'repair' sequence showing that it initially knew about the fact that the md0,1,2,3 partitions existed and were mounted and the sda partitions were not yet wnen it started doing fsck tests, it started doing it on the wrong drives including the drives associated with the wrong OS version, not the 10.3 version on the MD raid partitions. The first time this happened, I did it in 'auto' and it 'fixed' everything "real good". I spent several days unfixing it. It ruined a perfecly good 10.2 installation. For this test I skipped or refused all repairs but the repair program WILL NOT allow an ABORY which I consider another bug. -- 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.