https://bugzilla.novell.com/show_bug.cgi?id=304657#c10
--- Comment #10 from Richard Creighton
Well, it is true that "Repair" is able to some nasty things to your system, which is the dark side of the fact that it is (at least in most and common cases) able to repair it. And I understand your frustration after the broken repair, but there is no other option than asking user to confirm possible dangerous action.
However, I still think that at least bootloader configuration should be quite easy to restore: if you'd boot installation CD of 10.3, you could select Repair just there (I think at the Installation Mode screen), and once repair module is loaded, in Expert settings it is possible to run bootloader configuration which should be able to propose the correct setting. Expert settings also allow calling partitioner module, and maybe it would be possible to recover your system from that point, but I'm not sure if it would be enough.
Yes, I agree, however in this case I was never presented with that option. I was initially notified that there was my 10.2 drive (which it correctly identified as not mounted) and it discovered the MD0 to MD3 drives as well which can be seen on one of the screen shots but does not mention file systems or offerss of repair options. It directly goes into FSCK of the raw devices and never does a FSCK or other check of the MD raid devices. During the FSCK of the devices comprising the MDx devices, it reports many errors, yet it 'knew' the type was part of a raid and should not have run the test in the first place so that is one bug right there. The second bug is it did NOT detect the 2nd FS,and immediately went to work on the only one it did find which was the 10.2 FS and not the desired 10.3 FS on the MD raid device. So not only did it not offer to work on the correct FS, it apparantly did not even scan for it or detect it even though it is obvious it knew the raid device existed because it presented the info in the screenshot.
Given that the OS obviously does fully support running from a MD raid installation, the repair module should fully support that installation, which is the point of the report
Yes, there's obvious logic in this requirement, but in fact, repair module is regarded as a helper for common situation instead of tool able to fix everything done in installation.
I'll try to look into the logs and see what can be done.
I really appreciate the work you are doing. The repair function is primarily for those that are inexperienced and their systems are malfunctioning and they need help and when it makes things worse, it makes SuSE look bad as a product. I have been supporting Linux since almost it was first released and truly want it to succeed and provide an alternative to MS, but until the average non technical person can safely expect 'REPAIR' to do just that on the install disk of their chosen distribution, I am afraid Linux/SuSE will remain a 3rd world wannabe and that is a shame that I am working to overcome. -- 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.