[Bug 500874] New: Still Broken: Bug 445602 - Yast Installer Boot Loader Fails to Create Proper Entry for Existing RAID Array
http://bugzilla.novell.com/show_bug.cgi?id=500874 Summary: Still Broken: Bug 445602 - Yast Installer Boot Loader Fails to Create Proper Entry for Existing RAID Array Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: x86-64 OS/Version: openSUSE 11.1 Status: NEW Severity: Critical Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: kcjacobsen@ingenity.ca QAContact: jsrain@novell.com Found By: --- User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.8) Gecko/2009032609 Firefox/3.0.8 The install script did not see the existing hardware RAID1 and created non-existent mdraid entries and an un-usable base base kernel with a few shell scripts. Reproducible: Always Steps to Reproduce: Performed an update on OpenSuse via zypper against: http://download.opensuse.org/distribution/11.1/repo/oss Added other repositories Did a zypper dup Rebooted... Actual Results: All logging done to console :( Trying Manual Resume from /dev/mapper/ddf1_MIRROR1_Part4 Resume device /dev/mapper/ddf1_MIRROR1_Part4 not found Waiting for Device /dev/mapper/ddf1_MIRROR1_Part2 to appear could not find /dev/mapper/ddf1_MIRROR1_Part2 ..exiting to /bin/sh $ <--ended up with useless prompt, min kernel and no utilities or configuration Expected Results: A booted and working system as it was before the upgrade. Refer to Closed Bug >> 445602 -- 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=500874 User csxia@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=500874#c1 Chengshun Xia <csxia@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium Status|NEW |ASSIGNED CC| |csxia@novell.com --- Comment #1 from Chengshun Xia <csxia@novell.com> 2009-05-05 00:31:26 MDT --- Hi, Josef if you are not the right one who this bug should be assigned to, please assign it back to me thanks -- 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=500874 User jreidinger@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=500874#c2 Josef Reidinger <jreidinger@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO CC| |jreidinger@novell.com Info Provider| |kcjacobsen@ingenity.ca AssignedTo|bnc-team-screening@forge.pr |jreidinger@novell.com |ovo.novell.com | --- Comment #2 from Josef Reidinger <jreidinger@novell.com> 2009-05-07 08:02:26 MDT --- Please could you attach YaST logs from system? I need to know what is wrong with names. If you cannot boot you can get it from rescue mode and copy it. http://en.opensuse.org/Bugs/YaST#I_reported_a_YaST2_bug.2C_and_now_I_am_aske... Also please provide youyr version of perl-Bootloader (rpm -q perl-Bootloader) I only need ensure, that you have updated version. Thanks -- 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=500874 User ian.cheong@acm.org added comment http://bugzilla.novell.com/show_bug.cgi?id=500874#c3 Ian Cheong <ian.cheong@acm.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ian.cheong@acm.org --- Comment #3 from Ian Cheong <ian.cheong@acm.org> 2009-10-17 22:22:23 MDT --- Perhaps this bug relates to known RAID bugs which have been fixed. I have had huge problems trying to restore bootability after a RAID repair fallover, which may not have even been necessary in the first place. I think there are problems when the multiple tools that attempt to repair or create RAID leave settings in multiple places and don't all fix everything: vis fdisk parted mdadm fstab device.map menu.lst superblock errors required superblock partition to be deleted Eventually I had to manually delete a /dev/md0 line in fstab for a non-existent raid array. Yast partitioner reported partitions allocated to RAID but no RAID device. -- 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=500874 User ian.cheong@acm.org added comment http://bugzilla.novell.com/show_bug.cgi?id=500874#c4 Ian Cheong <ian.cheong@acm.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|kcjacobsen@ingenity.ca | --- Comment #4 from Ian Cheong <ian.cheong@acm.org> 2009-10-18 00:30:46 MDT --- Also note that yast partitioner GUI variably permitted access to bootloader repair settings - sometimes all options were available. Sometimes options were missing from the screen. There is no setting to change "kernel" loading of a partition, despite the fact that trying to load the damaged raid array failed and the kernel insisted on attempting to automatically load it with every reboot. -- 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=500874 User jreidinger@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=500874#c5 Josef Reidinger <jreidinger@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |kcjacobsen@ingenity.ca --- Comment #5 from Josef Reidinger <jreidinger@novell.com> 2009-10-20 05:34:46 MDT --- Please don't mix repair and bootloader issues. And still yast2 logs is not provided, without it is hard to know what is going wrong. -- 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=500874 User ian.cheong@acm.org added comment http://bugzilla.novell.com/show_bug.cgi?id=500874#c6 --- Comment #6 from Ian Cheong <ian.cheong@acm.org> 2009-10-20 06:32:41 MDT --- This is not my bug. Perhaps it is misnamed, because the behaviour described doesn't sound different to other RAID bugs. Perhaps it should be moved to a duplicate bug like Bug 548132 or other RAID bugs that have been fixed, especially since input from the originator died out 5 months ago. I started writing here after searching first to make sure I wasn't duplicating a bug. I can't presently help with logs, because my system boots fine. And I reformatted the drives to get around previously intractable problems. -- 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=500874 User jreidinger@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=500874#c7 --- Comment #7 from Josef Reidinger <jreidinger@novell.com> 2009-10-20 06:46:21 MDT --- Bootloader is quite sensitive and without logs I cannot decide what is roots of problems. YaST is quite complex tool which depend on many another tools and different reasons could causes same looking problem. So I don't close bugs until I am sure that it is same problem. -- 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=500874 http://bugzilla.novell.com/show_bug.cgi?id=500874#c8 Jozef Uhliarik <juhliarik@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |CLOSED CC| |juhliarik@novell.com Info Provider|kcjacobsen@ingenity.ca | Resolution| |NORESPONSE --- Comment #8 from Jozef Uhliarik <juhliarik@novell.com> 2010-02-16 14:45:59 UTC --- 9 months without response from Ken Jacobsen. -> I close bug like NORESPONSE. -- 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