https://bugzilla.novell.com/show_bug.cgi?id=788224 https://bugzilla.novell.com/show_bug.cgi?id=788224#c2 Scott Couston <secure@aphofis.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium Status|CLOSED |REOPENED CC| |monkey9@iae.nl, | |secure@aphofis.com Component|Bootloader |Installation Found By|--- |System Test AssignedTo|jsrain@suse.com |bnc-team-screening@forge.pr | |ovo.novell.com Resolution|WONTFIX | Summary|Bring back the repair |Bring Back the Repair |options inside the |Options Inside the |installation on the install |Installation on a New |media. |Install! Severity|Enhancement |Major OS/Version|SUSE Other |openSUSE 12.2 --- Comment #2 from Scott Couston <secure@aphofis.com> 2013-05-26 17:17:09 EST --- Sorry Jiri I am going to come in and join Robby about the Repair Option with the Installation Program. What we are both trying to say is that we dont want another heading on the Installation boot program and we dont want to change one thing about the Rescue System Option that no one really knows how and what is does. During the New Install and when we got to the selection of either Gnome, KDE and Other Desktop, one of the 'other' selection was repair existing installation. It is here when we selected Other we saw the option to REPAIRING the existing Installation. Its probably still in Yast 2 text based. This Repair option offered two (from Memory) type tools. An automatic repair process which checked the validity of the Volume descriptors, Root Partition, Active Partition and and HDD that fell off the partitioning description files. It also provided an automatic option to fix and mount point or remove a whole HDD drive in the case of complete failure and then rewrite the complete boot loader information. The Manual Repair Process gave the ability to use which of the above tools we run manually. All in all the Module probably needs NO maintenance as it give gives us The Partitioner. Tools for checking the drives which were non-mounted at this point in time. Tools for examining the HDD's surface ananysis. Tools to change the boot loaded after we repaired the mount points that had fallen away by, say a defective sector on the physical HDD. Tools for checking all the RAM registers over night. Tools for testing non destructive as well as destructive HDD Analysis read/write/read an upon an invalid re-read the block was marked as bad and a new sector was created containing the original read and first read. Tools for re-writing of the boot loader files. Repair gave us a Graphic representation for loading the O/S Kernel and other services; having all current mount points no yet mounted and the tools to correct the volume descriptors etc. I think its still there sitting and whats the worse going to happen if we put it back and it fails to repair. All of us are under no illusion that repair tools are sometimes well out of the scope of fixing everything. I still believe that every new install wound run a comp-serve over all of the HDD's before formatting them - what what would a user know...:-) Robby I hope this is o.k with you mate -- 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.