[Bug 547959] New: Yast repairer unable to repair boot configuration - device.map error
http://bugzilla.novell.com/show_bug.cgi?id=547959 Summary: Yast repairer unable to repair boot configuration - device.map error Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: x86-64 OS/Version: openSUSE 11.1 Status: NEW Severity: Major Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: ian.cheong@acm.org QAContact: jsrain@novell.com Found By: --- User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_5_8; en-us) AppleWebKit/531.9 (KHTML, like Gecko) Version/4.0.3 Safari/531.9 Automatic repair fails to fix device.map. Even a clean build of device.map by command line grub results in error message. I suspect this is tied up with RAID1 bugs, since the repairer mucked up a RAID1 array and booting problems started after that. Repair tool says it will repair, but results in failed repair and attempts to repair again. Reports finished but doesn't work on reboot or re-repair. Possibly problems are caused by inconsistency between device.map and fstab. Reproducible: Always Steps to Reproduce: 1. 2. 3. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=547959 zhu rensheng <rszhu@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rszhu@novell.com AssignedTo|bnc-team-screening@forge.pr |jsuchome@novell.com |ovo.novell.com | -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=547959 Jiří Suchomel <jsuchome@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|jsuchome@novell.com |jreidinger@novell.com -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=547959 User jreidinger@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=547959#c1 Josef Reidinger <jreidinger@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P4 - Low Status|NEW |ASSIGNED --- Comment #1 from Josef Reidinger <jreidinger@novell.com> 2009-10-20 05:30:59 MDT --- Repair detection of validness of device.map is broken and even if device.map is correct it is reported as broken. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=547959 User ian.cheong@acm.org added comment http://bugzilla.novell.com/show_bug.cgi?id=547959#c2 --- Comment #2 from Ian Cheong <ian.cheong@acm.org> 2009-10-20 06:26:19 MDT --- Thanks for confirming that. Do you need any more information? -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=547959 User jreidinger@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=547959#c3 --- Comment #3 from Josef Reidinger <jreidinger@novell.com> 2009-10-20 06:34:10 MDT --- No, I have enough information, just time lacking to fix it, as it is not so easy to decide when device map is correct and when not. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=547959 User ian.cheong@acm.org added comment http://bugzilla.novell.com/show_bug.cgi?id=547959#c4 --- Comment #4 from Ian Cheong <ian.cheong@acm.org> 2009-10-20 07:07:09 MDT --- I'm guessing that the issue is not so much of "correctness" as "consistency". If a manual rebuild of device.map using grub results in a "correct" but inconsistent system which reports as broken, there should be an easy way to force consistency with a known intervention like a clean rebuild of device.map. If there are devices not detected, they can be added later. Is there documentation of the "failsafe" systems of redundant information used to repair systems? The ultimate arbiter of truth is a human to double check between a few options, and a way to keep a record of all (or a large number) attempts so they can be rolled back/forth easily. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=547959 http://bugzilla.novell.com/show_bug.cgi?id=547959#c5 Josef Reidinger <jreidinger@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |WONTFIX --- Comment #5 from Josef Reidinger <jreidinger@novell.com> 2010-06-23 08:29:30 UTC --- yast2-repair is dropped now, so no fixes will be done -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com