[Bug 591700] New: System fails to boot after "zypper up" from 11.3 M2 to M4
http://bugzilla.novell.com/show_bug.cgi?id=591700 http://bugzilla.novell.com/show_bug.cgi?id=591700#c0 Summary: System fails to boot after "zypper up" from 11.3 M2 to M4 Classification: openSUSE Product: openSUSE 11.3 Version: Milestone 4 Platform: Other OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: Bootloader AssignedTo: jsrain@novell.com ReportedBy: kkaempf@novell.com QAContact: jsrain@novell.com Found By: Development Blocker: --- /boot/grub/menu.lst is wrong after "zypper up" (see attachment) - It contains multiple entries (2.6.33-5-default, which is not installed) - The first entries have the wrong disk ( hd(1,0) vs hd(0,0) ) - The second entries have the wrong kernel ( 2.6.33-5 vs 2.6.3-6 ) -- 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=591700 http://bugzilla.novell.com/show_bug.cgi?id=591700#c1 --- Comment #1 from Klaus Kämpf <kkaempf@novell.com> 2010-03-28 13:42:30 UTC --- Created an attachment (id=351026) --> (http://bugzilla.novell.com/attachment.cgi?id=351026) /boot/grub/menu.lst -- 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=591700 http://bugzilla.novell.com/show_bug.cgi?id=591700#c2 --- Comment #2 from Klaus Kämpf <kkaempf@novell.com> 2010-03-28 13:44:03 UTC --- Created an attachment (id=351027) --> (http://bugzilla.novell.com/attachment.cgi?id=351027) Complete /var/log/YaST2 -- 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=591700 http://bugzilla.novell.com/show_bug.cgi?id=591700#c Jiri Srain <jsrain@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|jsrain@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=591700 http://bugzilla.novell.com/show_bug.cgi?id=591700#c3 --- Comment #3 from Klaus Kämpf <kkaempf@novell.com> 2010-03-29 11:24:04 UTC --- Its one of these BIOS-disk-order vs. Kernel-disk-order problems. The system has SATA and IDE controller, both with a disk attached. The kernel sees the IDE disk first (/dev/sda), SATA second (/dev/sdb). However, the SATA drive is the boot drive so to grub hd(0,0) is the right value. -- 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=591700 http://bugzilla.novell.com/show_bug.cgi?id=591700#c4 Josef Reidinger <jreidinger@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P2 - High Status|NEW |ASSIGNED --- Comment #4 from Josef Reidinger <jreidinger@novell.com> 2010-03-30 08:01:58 UTC --- (In reply to comment #3)
Its one of these BIOS-disk-order vs. Kernel-disk-order problems.
The system has SATA and IDE controller, both with a disk attached. The kernel sees the IDE disk first (/dev/sda), SATA second (/dev/sdb). However, the SATA drive is the boot drive so to grub hd(0,0) is the right value.
This should not be problem, as we use udev links. Problem is that in some time hd0,0 is written instead of correct entry. I must dig logs to find where this happen (sometime between 06.03 and 28.3 - first refresh which doesn't change anything read (hd0,0)) -- 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=591700 http://bugzilla.novell.com/show_bug.cgi?id=591700#c5 --- Comment #5 from Klaus Kämpf <kkaempf@novell.com> 2010-03-30 08:18:56 UTC --- (In reply to comment #4)
This should not be problem, as we use udev links.
Indeed. Linux is using by-id links and doesn't care about disk order. But grub has huge problems.
Problem is that in some time hd0,0 is written instead of correct entry.
In my case, hd(0,0) is the right entry since hd(0,0) == first disk in BIOS boot order. The bug is that grubs menu.lst contained hd(1,0) since the 'boot' disk shows up as sdb in Linux Actually, there are two bugs since menu.lst still contained the boot entries for the previous (Milestone 2) kernel ! -- 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=591700 http://bugzilla.novell.com/show_bug.cgi?id=591700#c6 --- Comment #6 from Josef Reidinger <jreidinger@novell.com> 2010-03-30 08:46:10 UTC --- (In reply to comment #5)
(In reply to comment #4)
This should not be problem, as we use udev links.
Indeed. Linux is using by-id links and doesn't care about disk order.
But grub has huge problems.
Problem is that in some time hd0,0 is written instead of correct entry.
In my case, hd(0,0) is the right entry since hd(0,0) == first disk in BIOS boot order. The bug is that grubs menu.lst contained hd(1,0) since the 'boot' disk shows up as sdb in Linux
Actually, there are two bugs since menu.lst still contained the boot entries for the previous (Milestone 2) kernel !
Boot order is stored in /boot/grub/device.map so if you change boot order in BIOS you must regenerate whole boot configuration. Otherwise yast2-bootloader should store correct order and I use this order. It is not two bugs just two effects of one bug :) -- 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=591700 http://bugzilla.novell.com/show_bug.cgi?id=591700#c7 --- Comment #7 from Klaus Kämpf <kkaempf@novell.com> 2010-03-31 08:06:43 UTC --- (In reply to comment #6)
Boot order is stored in /boot/grub/device.map
Do you need this file for debugging ?
so if you change boot order in BIOS
I didn't change anything in the BIOS. The system booted fine with M2.
It is not two bugs just two effects of one bug :)
I see two bugs here 1. Wrong disk choosen (hd(1,0)) 2. Invalid boot entry (pointing to old kernel image) -- 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=591700 http://bugzilla.novell.com/show_bug.cgi?id=591700#c8 --- Comment #8 from Klaus Kämpf <kkaempf@novell.com> 2010-04-13 20:25:39 UTC --- /boot/grub/device.map shows (hd2) /dev/disk/by-id/usb-WDC_WD16_00JB-00GVC0-0:0 (hd1) /dev/disk/by-id/ata-WDC_WD10EARS-00Y5B1_WD-WCAV56153591 (hd3) /dev/disk/by-id/usb-Ut165_USB2FlashStorage_08032651d04575-0:0 (hd0) /dev/disk/by-id/ata-SAMSUNG_SP1654N_S0GEJ1FL700392 which is *wrong* since WS10EARS (reported as hd1) was used for booting -- 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=591700 http://bugzilla.novell.com/show_bug.cgi?id=591700#c9 --- Comment #9 from Klaus Kämpf <kkaempf@novell.com> 2010-04-13 20:28:09 UTC --- After upgrading to 11.3 M5, menu.lst has again (hd1,0) :-( Interestingly enough, menu.lst also has "gfxmenu (hd0,0)/message", which is correct! -- 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=591700 http://bugzilla.novell.com/show_bug.cgi?id=591700#c10 Josef Reidinger <jreidinger@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO CC| |juhliarik@novell.com InfoProvider| |kkaempf@novell.com --- Comment #10 from Josef Reidinger <jreidinger@novell.com> 2010-04-14 06:26:35 UTC --- Could you attach fresh logs after the latest update? There is something wrong with information about disc which I must discover and maybe it will be easier to find. I add jozo to bug as he is the one who propose device.map. I just use it. -- 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=591700 http://bugzilla.novell.com/show_bug.cgi?id=591700#c11 --- Comment #11 from Klaus Kämpf <kkaempf@novell.com> 2010-04-14 12:17:02 UTC --- As soon as I get this system to boot again (M5 kernel hangs at "doing fast boot" :-() -- 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=591700 http://bugzilla.novell.com/show_bug.cgi?id=591700#c12 --- Comment #12 from Klaus Kämpf <kkaempf@novell.com> 2010-04-16 18:58:08 UTC --- Created an attachment (id=355079) --> (http://bugzilla.novell.com/attachment.cgi?id=355079) /var/log/YaST2 This is complete /var/log/YaST2 -- 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=591700 http://bugzilla.novell.com/show_bug.cgi?id=591700#c13 --- Comment #13 from Klaus Kämpf <kkaempf@novell.com> 2010-04-16 19:03:03 UTC --- Now I have a second system with similar symptoms. This time the disk # is correct but the partition # is wrong. This occured with an openSUSE 11.2 -> 11.3 M5 upgrade via 'zypper dup' Logs follow -- 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=591700 http://bugzilla.novell.com/show_bug.cgi?id=591700#c14 --- Comment #14 from Klaus Kämpf <kkaempf@novell.com> 2010-04-16 19:22:33 UTC --- The device.map of the second system is not very spectacular ;-) (hd0) /dev/disk/by-id/ata-WDC_WD1600BEVS-00UST0_WD-WXEY07S93095 -- 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=591700 http://bugzilla.novell.com/show_bug.cgi?id=591700#c15 Klaus Kämpf <kkaempf@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED InfoProvider|kkaempf@novell.com | --- Comment #15 from Klaus Kämpf <kkaempf@novell.com> 2010-04-16 19:23:57 UTC --- Created an attachment (id=355085) --> (http://bugzilla.novell.com/attachment.cgi?id=355085) /var/log/YaST2 (wrong partition) This is /var/log/YaST2 of the system with wrong partition in the bootloader -- 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=591700 http://bugzilla.novell.com/show_bug.cgi?id=591700#c16 Josef Reidinger <jreidinger@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO CC| |kasievers@novell.com InfoProvider| |kkaempf@novell.com --- Comment #16 from Josef Reidinger <jreidinger@novell.com> 2010-04-19 07:08:17 UTC --- (In reply to comment #15)
Created an attachment (id=355085) --> (http://bugzilla.novell.com/attachment.cgi?id=355085) [details] /var/log/YaST2 (wrong partition)
This is /var/log/YaST2 of the system with wrong partition in the bootloader
Hi, in this case it looks like udev is totally broken after kernel update and it cause problem with partition because it cannot translate partition information. Please provide output of these script to ensure if problem happen only after kernel update or it is still present: udevadm info -q all -n /dev/dm-0 udevadm info -q all -n /dev/sda2 thanks Kay - if you know about similar problem in current factory please add note. -- 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=591700 http://bugzilla.novell.com/show_bug.cgi?id=591700#c17 --- Comment #17 from Klaus Kämpf <kkaempf@novell.com> 2010-04-19 08:42:50 UTC --- Created an attachment (id=355218) --> (http://bugzilla.novell.com/attachment.cgi?id=355218) udevadm for dm-0 -- 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=591700 http://bugzilla.novell.com/show_bug.cgi?id=591700#c18 Klaus Kämpf <kkaempf@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED InfoProvider|kkaempf@novell.com | --- Comment #18 from Klaus Kämpf <kkaempf@novell.com> 2010-04-19 08:43:50 UTC --- Created an attachment (id=355219) --> (http://bugzilla.novell.com/attachment.cgi?id=355219) udevadm for sda2 Guys, remember that I did a 'zypper dup' which means that the old (11.2) kernel was still running during the upgrade ! -- 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=591700 http://bugzilla.novell.com/show_bug.cgi?id=591700#c Josef Reidinger <jreidinger@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #355218|application/octet-stream |text/plain mime type| | -- 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=591700 http://bugzilla.novell.com/show_bug.cgi?id=591700#c Josef Reidinger <jreidinger@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #355219|application/octet-stream |text/plain mime type| | -- 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=591700 http://bugzilla.novell.com/show_bug.cgi?id=591700#c19 Josef Reidinger <jreidinger@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO InfoProvider| |kasievers@novell.com --- Comment #19 from Josef Reidinger <jreidinger@novell.com> 2010-04-19 11:07:38 UTC --- Kay - it looks like incosistent between udev return during update (where it doesn't know DM_NAME for dm-0 and also other mapping looks like doesn't exist for block devices. Do you know what could happen in this case? -- 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=591700 http://bugzilla.novell.com/show_bug.cgi?id=591700#c20 Kay Sievers <kasievers@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED InfoProvider|kasievers@novell.com | --- Comment #20 from Kay Sievers <kasievers@novell.com> 2010-04-19 11:28:17 UTC --- A version upgrade of udev might not convert all the information in the udev database. As a result, during the upgrade, some dynamic information will no longer be available when the new udev binaries are installed along with the old database. The values need to be re-evaluated, by rebooting the system, or "udevadm trigger" needs to be run for the devices in question. I don't know how to solve this from the udev side, running "udevadm trigger" when updating udev is known to cause problems in some cases. It should not in theory, but especially things like device-mapper may break their udev setup, if we emit additional events. I guess, we need to make sure, that a bootloader update happens before the udev update, if the bootloader depends on non-core/non-kernel properties from the udev database. -- 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=591700 http://bugzilla.novell.com/show_bug.cgi?id=591700#c21 Josef Reidinger <jreidinger@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO InfoProvider| |mmarek@novell.com --- Comment #21 from Josef Reidinger <jreidinger@novell.com> 2010-04-19 11:32:29 UTC --- Michal - please see comment #20 is possible to ensure in packages that update of kernel happen before update of udev? -- 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=591700 http://bugzilla.novell.com/show_bug.cgi?id=591700#c22 --- Comment #22 from Klaus Kämpf <kkaempf@novell.com> 2010-04-19 11:35:37 UTC --- Sounds like bootloader would need a versioned(!) "Require(post):" to the udev version in the build environment. This should ensure that an updated udev is available at the time the post-install scripts are run. -- 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=591700 http://bugzilla.novell.com/show_bug.cgi?id=591700#c23 Michal Marek <mmarek@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED CC| |mmarek@novell.com InfoProvider|mmarek@novell.com | --- Comment #23 from Michal Marek <mmarek@novell.com> 2010-04-19 11:39:52 UTC --- That would be quite a strict dependency though. Another option would be making udev depend on the kernel (unversioned), which would look a bit silly OTOH. -- 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=591700 http://bugzilla.novell.com/show_bug.cgi?id=591700#c24 Josef Reidinger <jreidinger@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jreidinger@novell.com AssignedTo|jreidinger@novell.com |kasievers@novell.com --- Comment #24 from Josef Reidinger <jreidinger@novell.com> 2010-04-19 11:52:50 UTC --- so strict version dependency looks also for me too much, but udev dependency on kernel sounds like simple working solution. Kay - could you add dependency on kernel? 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=591700 http://bugzilla.novell.com/show_bug.cgi?id=591700#c25 --- Comment #25 from Klaus Kämpf <kkaempf@novell.com> 2010-04-19 11:57:51 UTC --- How can an unversioned dependency work during "zypper dup" ? -- 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=591700 http://bugzilla.novell.com/show_bug.cgi?id=591700#c26 Michal Marek <mmarek@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO InfoProvider| |zypp-maintainers@forge.prov | |o.novell.com --- Comment #26 from Michal Marek <mmarek@novell.com> 2010-04-19 12:03:31 UTC --- If there are no cycles, the install order is given by the topological sort of the dependency graph. That's what I've been told at least :-), but let's ask the zypp developers before adding any hacks. -- 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=591700 http://bugzilla.novell.com/show_bug.cgi?id=591700#c27 Klaus Kämpf <kkaempf@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED InfoProvider|zypp-maintainers@forge.prov | |o.novell.com | --- Comment #27 from Klaus Kämpf <kkaempf@novell.com> 2010-04-19 12:41:13 UTC --- That was not my question. If you're doing an unversioned dependency, a "zypper dup" will fulfill all dependencies based on the _old_ packages. I don't see how this will fix the reported bug. -- 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=591700 http://bugzilla.novell.com/show_bug.cgi?id=591700#c28 Josef Reidinger <jreidinger@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aj@novell.com --- Comment #28 from Josef Reidinger <jreidinger@novell.com> 2010-04-19 14:10:26 UTC --- *** Bug 596833 has been marked as a duplicate of this bug. *** http://bugzilla.novell.com/show_bug.cgi?id=596833 -- 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=591700 http://bugzilla.novell.com/show_bug.cgi?id=591700#c29 --- Comment #29 from Klaus Kaempf <kkaempf@novell.com> 2010-04-20 08:00:09 UTC --- jfyi, "mkinitrd" shows multiple lines of 2010-04-20 09:58:45 WARNING: GRUB::GrubDev2UnixDev: No partition found for /dev/sda with 1. -- 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=591700 http://bugzilla.novell.com/show_bug.cgi?id=591700#c30 --- Comment #30 from Josef Reidinger <jreidinger@novell.com> 2010-04-20 08:08:29 UTC --- (In reply to comment #29)
jfyi, "mkinitrd" shows multiple lines of 2010-04-20 09:58:45 WARNING: GRUB::GrubDev2UnixDev: No partition found for /dev/sda with 1.
Yes, this also prints pbl, it is result of failed consistent name translation. -- 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=591700 http://bugzilla.novell.com/show_bug.cgi?id=591700#c31 Klaus Kämpf <kkaempf@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Version|Milestone 4 |Milestone 6 Summary|System fails to boot after |System fails to boot after |"zypper up" from 11.3 M2 to |"zypper dup" |M4 | --- Comment #31 from Klaus Kämpf <kkaempf@novell.com> 2010-05-01 17:45:42 UTC --- Still not fixed in M6 Grubs menu.lst contains hd(1,0) while hd(0,0) is boot disk in BIOS disk order device.map is: (hd2) /dev/disk/by-id/usb-WDC_WD16_00JB-00GVC0-0:0 (hd1) /dev/disk/by-id/ata-WDC_WD10EARS-00Y5B1_WD-WCAV56153591 (hd3) /dev/disk/by-id/usb-Ut165_USB2FlashStorage_08032651d04575-0:0 (hd0) /dev/disk/by-id/ata-SAMSUNG_SP1654N_S0GEJ1FL700392 which reflects the *kernel* order not the BIOS order :-/ -- 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=591700 http://bugzilla.novell.com/show_bug.cgi?id=591700#c32 --- Comment #32 from Josef Reidinger <jreidinger@novell.com> 2010-05-03 05:04:18 UTC --- jozo - device.map proposal is your job. please look if you find something strange here. -- 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=591700 http://bugzilla.novell.com/show_bug.cgi?id=591700#c33 Klaus Kämpf <kkaempf@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P2 - High |P1 - Urgent Version|Milestone 6 |Milestone 7 Summary|System fails to boot after |System fails to boot after |"zypper dup" |"zypper dup" (wrong 'root' | |in menu.lst) --- Comment #33 from Klaus Kämpf <kkaempf@novell.com> 2010-06-17 18:58:43 UTC --- So it happened again. Interestingly, "zypper dup" from M6 to M7 went flawless. However, "zypper dup" from M7 to RC1 rewrote the "root" entry in menu.lst again -- 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=591700 http://bugzilla.novell.com/show_bug.cgi?id=591700#c Kay Sievers <kasievers@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|kasievers@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=591700 http://bugzilla.novell.com/show_bug.cgi?id=591700#c34 Josef Reidinger <jreidinger@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO InfoProvider| |kkaempf@novell.com --- Comment #34 from Josef Reidinger <jreidinger@novell.com> 2010-06-18 07:18:18 UTC --- Yes, it is interesting that it sometime work and sometime not. Please provide fresh logs and I try find what is difference between these two updates. -- 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=591700 http://bugzilla.novell.com/show_bug.cgi?id=591700#c35 --- Comment #35 from Klaus Kämpf <kkaempf@novell.com> 2010-06-18 14:13:25 UTC --- Created an attachment (id=370107) --> (http://bugzilla.novell.com/attachment.cgi?id=370107) Fresh files from /var/log/YaST2 -- 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=591700 http://bugzilla.novell.com/show_bug.cgi?id=591700#c36 Klaus Kämpf <kkaempf@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED InfoProvider|kkaempf@novell.com | --- Comment #36 from Klaus Kämpf <kkaempf@novell.com> 2010-06-18 14:14:06 UTC --- Created an attachment (id=370108) --> (http://bugzilla.novell.com/attachment.cgi?id=370108) zypper.log and zypp/ -- 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=591700 http://bugzilla.novell.com/show_bug.cgi?id=591700#c37 Josef Reidinger <jreidinger@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO InfoProvider| |kkaempf@novell.com --- Comment #37 from Josef Reidinger <jreidinger@novell.com> 2010-06-21 09:55:48 UTC --- Klaus - does zypper dup change device.map? It should not change it. Do you have correct one? I also cannot find any valid menu.lst each one which I see in logs has broken hd(0,0) so is menu.lst fixed before upgrade? (perl-Bootloader during update/upgrade doesn't 'fix' menu, it just try to change in same way as it works before) -- 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=591700 http://bugzilla.novell.com/show_bug.cgi?id=591700#c38 Klaus Kämpf <kkaempf@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED InfoProvider|kkaempf@novell.com | --- Comment #38 from Klaus Kämpf <kkaempf@novell.com> 2010-06-21 10:06:38 UTC --- (In reply to comment #37)
Klaus - does zypper dup change device.map? How should I know ? It should not change it. Do you have correct one?
There is no 'correct' or 'wrong' device.map Whats wrong is the detection of which device was used for booting
I also cannot find any valid menu.lst each one which I see in logs has broken hd(0,0) so is menu.lst fixed before upgrade? I manually fix menu.lst because I cannot boot otherwise.
(perl-Bootloader during update/upgrade doesn't 'fix' menu, it just try to change in same way as it works before)
How does perl-Bootloader determine what to use as 'root' 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=591700 http://bugzilla.novell.com/show_bug.cgi?id=591700#c39 Josef Reidinger <jreidinger@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO InfoProvider| |kkaempf@novell.com --- Comment #39 from Josef Reidinger <jreidinger@novell.com> 2010-06-21 10:16:26 UTC --- (In reply to comment #38)
(In reply to comment #37)
Klaus - does zypper dup change device.map? How should I know ? It should not change it. Do you have correct one?
There is no 'correct' or 'wrong' device.map Whats wrong is the detection of which device was used for booting
device.map reflect order of booting for x86 based machines. BIOS code 0x80 is for first device to boot etc...it is important mainly when you write boot code to MBR.
I also cannot find any valid menu.lst each one which I see in logs has broken hd(0,0) so is menu.lst fixed before upgrade? I manually fix menu.lst because I cannot boot otherwise.
Interesting is that I cannot find correct one logs. Could you specify date when you update ( There is quite a lot of message, so time could help me to better identify it).
(perl-Bootloader during update/upgrade doesn't 'fix' menu, it just try to change in same way as it works before)
How does perl-Bootloader determine what to use as 'root' device ?
When you update the root device is device which is mounted under /boot (or / if /boot is not separated). So it try to find if there is some device which has as root device which is mounted as /boot. If it is not found then add default arguments and add it. Of course if it is broken before update it doesn't remove old entries as It think that it is for another system. -- 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=591700 http://bugzilla.novell.com/show_bug.cgi?id=591700#c40 Klaus Kämpf <kkaempf@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED InfoProvider|kkaempf@novell.com | --- Comment #40 from Klaus Kämpf <kkaempf@novell.com> 2010-07-06 09:30:01 UTC --- Why does bootloader try to newly guess grubs root() device during upgrade ? It should just leave it alone ! -- 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=591700 http://bugzilla.novell.com/show_bug.cgi?id=591700#c41 --- Comment #41 from Klaus Kämpf <kkaempf@novell.com> 2010-07-06 18:28:21 UTC --- RC2 still breaks the grub configuration :-/ -- 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=591700 http://bugzilla.novell.com/show_bug.cgi?id=591700#c Klaus Kämpf <kkaempf@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Version|Milestone 7 |RC 2 -- 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=591700 http://bugzilla.novell.com/show_bug.cgi?id=591700#c42 --- Comment #42 from Josef Reidinger <jreidinger@novell.com> 2010-07-07 07:00:38 UTC --- (In reply to comment #40)
Why does bootloader try to newly guess grubs root() device during upgrade ? It should just leave it alone !
Because some users have more then one image section with different roots, so set root to /boot is done always as part of workflow ( it is part of pbl abstraction for another bootloader, you always set root by unix device and for grub it is translated to grub 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.
https://bugzilla.novell.com/show_bug.cgi?id=591700 https://bugzilla.novell.com/show_bug.cgi?id=591700#c43 --- Comment #43 from Josef Reidinger <jreidinger@novell.com> 2010-10-12 08:32:22 UTC --- OK, I investigate issue with bad partition and it is same issue as in bug #543076 Issue with disc order I still investigating as I still don't find when it switch from working state to non-working one and why. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=591700 https://bugzilla.novell.com/show_bug.cgi?id=591700#c44 --- Comment #44 from Felix Miata <mrmazda@earthlink.net> 2010-10-12 13:58:21 UTC --- http://lists.opensuse.org/opensuse/2010-09/msg01405.html is a thread that may indicate a problem unpreventable except possibly via motherboard BIOS update. It seems some BIOS are disposed to change boot priority/BIOS disk order at the slightest provocation that may or may not come from actually entering BIOS setup or changing anything in BIOS setup, but might come from any transient or worse problem with BIOS HD0 during POST, or from HD replacement. Once this happens, /boot/grub/device.map may no longer be correct. It allows by-label, by-uuid, etc. to work for fstab & cmdline, but not necessarily for bootloader and/or initrd issues. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=591700 https://bugzilla.novell.com/show_bug.cgi?id=591700#c45 Christian Boltz <suse-beta@cboltz.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |suse-beta@cboltz.de --- Comment #45 from Christian Boltz <suse-beta@cboltz.de> 2010-10-17 16:37:40 CEST --- I had a similar problem after a zypper dup from 11.2 to 11.3 - menu.lst contained hd(0,0) instead of hd(0,1), which (obviously) broke booting. What should I do? a) report more details here b) open a new bugreport c) nothing - if you think it is the same bug as described here ? BTW: If I get this bugreport right, it affects only zypper dup. This should even be fixable by releasing an update for 11.3 - at least for those people who include the update repo when running zypper dup. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=591700 https://bugzilla.novell.com/show_bug.cgi?id=591700#c46 --- Comment #46 from Josef Reidinger <jreidinger@novell.com> 2010-10-18 07:17:54 UTC --- (In reply to comment #45)
I had a similar problem after a zypper dup from 11.2 to 11.3 - menu.lst contained hd(0,0) instead of hd(0,1), which (obviously) broke booting. What should I do? a) report more details here b) open a new bugreport c) nothing - if you think it is the same bug as described here ?
BTW: If I get this bugreport right, it affects only zypper dup. This should even be fixable by releasing an update for 11.3 - at least for those people who include the update repo when running zypper dup.
I think that your problem is little different and is affected by change of udev DB format which leads to situation, that if udev is upgraded earlier then kernel, kernel cannot get translation between udev links and kernel device, which leads to bad GRUB device. more in bug #543076 -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=591700 https://bugzilla.novell.com/show_bug.cgi?id=591700#c47 --- Comment #47 from Christian Boltz <suse-beta@cboltz.de> 2010-10-19 00:44:37 CEST --- (In reply to comment #46)
I think that your problem is little different and is affected by change of udev DB format which leads to situation, that if udev is upgraded earlier then kernel, kernel cannot get translation between udev links and kernel device, which leads to bad GRUB device. more in bug #543076
Yes, that sounds like a valid explanation, and rpm -qi confirms that udev was installed earlier than the kernel. Maybe I'm thinking too simple, but shouldn't this be solvable be releasing an udev update that requries kernel >= $11.3_original_kernel to give the solver a hint about the installation order? (Precondition is of course that the update repo is added when running zypper dup.) -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=591700 https://bugzilla.novell.com/show_bug.cgi?id=591700#c48 --- Comment #48 from Josef Reidinger <jreidinger@novell.com> 2010-11-30 18:53:05 UTC --- (In reply to comment #47)
(In reply to comment #46)
I think that your problem is little different and is affected by change of udev DB format which leads to situation, that if udev is upgraded earlier then kernel, kernel cannot get translation between udev links and kernel device, which leads to bad GRUB device. more in bug #543076
Yes, that sounds like a valid explanation, and rpm -qi confirms that udev was installed earlier than the kernel.
Maybe I'm thinking too simple, but shouldn't this be solvable be releasing an udev update that requries kernel >= $11.3_original_kernel to give the solver a hint about the installation order? (Precondition is of course that the update repo is added when running zypper dup.)
Hi, discussion about possible solution please post to mentioned bug, as it is hard to track it in more bug reports. Thanks -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=591700 https://bugzilla.novell.com/show_bug.cgi?id=591700#c50 Jean-Daniel Dodin <jdd@dodin.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jdd@dodin.org --- Comment #50 from Jean-Daniel Dodin <jdd@dodin.org> 2011-11-11 14:19:44 UTC --- seems this problem is still not solved with 12.1 (https://bugzilla.novell.com/show_bug.cgi?id=691060) - the best solution (on my computers) is to simply remove the root=(hdX,Y) line wich is unusefull see also https://bugzilla.novell.com/show_bug.cgi?id=728524 -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=591700 https://bugzilla.novell.com/show_bug.cgi?id=591700#c51 Michael Chang <mchang@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hw01@heisch.inka.de --- Comment #51 from Michael Chang <mchang@suse.com> 2013-01-08 06:53:19 UTC --- *** Bug 795838 has been marked as a duplicate of this bug. *** http://bugzilla.novell.com/show_bug.cgi?id=795838 -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=591700 https://bugzilla.novell.com/show_bug.cgi?id=591700#c52 --- Comment #52 from Klaus Kämpf <kkaempf@suse.com> 2013-01-28 08:53:37 UTC --- Wow, this bug is marked as P1/Critical for months and 12.3 Beta 1 still suffers from it. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=591700 https://bugzilla.novell.com/show_bug.cgi?id=591700#c54 Steffen Winterfeldt <snwint@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED --- Comment #54 from Steffen Winterfeldt <snwint@suse.com> 2013-01-28 14:51:54 CET --- The issue has been solved in 12.3. Background: the issue was caused by udevd loosing part of its database after an update. If the udev update happened before the kernel update, updating the bootloader config may fail. Several band-aids had been added to perl-Bootloader to work around this. 12.3 solves this by not using udev in perl-Bootloader anymore. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=591700 https://bugzilla.novell.com/show_bug.cgi?id=591700#c55 Klaus Kämpf <kkaempf@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED | --- Comment #55 from Klaus Kämpf <kkaempf@suse.com> 2013-01-28 14:05:30 UTC --- Huh ? A 'zypper dup' from 12.2 (latest updates applied) to 12.3 Beta1 did NOT result in a correct menu.lst -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=591700 https://bugzilla.novell.com/show_bug.cgi?id=591700#c56 Steffen Winterfeldt <snwint@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEEDINFO InfoProvider| |kkaempf@suse.com --- Comment #56 from Steffen Winterfeldt <snwint@suse.com> 2013-01-28 16:39:24 CET --- Logs? /var/log/pbl.log /var/log/YaST2/perl-BL-standalone-log /var/log/zypp/history -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=591700 https://bugzilla.novell.com/show_bug.cgi?id=591700#c57 --- Comment #57 from Klaus Kämpf <kkaempf@suse.com> 2013-02-02 12:00:29 UTC --- Created an attachment (id=523110) --> (http://bugzilla.novell.com/attachment.cgi?id=523110) pbl.log -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=591700 https://bugzilla.novell.com/show_bug.cgi?id=591700#c58 --- Comment #58 from Klaus Kämpf <kkaempf@suse.com> 2013-02-02 14:40:08 UTC --- Created an attachment (id=523112) --> (http://bugzilla.novell.com/attachment.cgi?id=523112) perl-BL-standalone-log -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=591700 https://bugzilla.novell.com/show_bug.cgi?id=591700#c59 Klaus Kämpf <kkaempf@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |REOPENED InfoProvider|kkaempf@suse.com | --- Comment #59 from Klaus Kämpf <kkaempf@suse.com> 2013-02-02 14:41:11 UTC --- Created an attachment (id=523113) --> (http://bugzilla.novell.com/attachment.cgi?id=523113) zypp history -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=591700 https://bugzilla.novell.com/show_bug.cgi?id=591700#c60 --- Comment #60 from Klaus Kämpf <kkaempf@suse.com> 2013-02-10 11:52:39 UTC --- 'zypper dup' from 12.3-Beta1 to 12.3-RC1 still shows this 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.
https://bugzilla.novell.com/show_bug.cgi?id=591700 https://bugzilla.novell.com/show_bug.cgi?id=591700#c61 --- Comment #61 from Klaus Kämpf <kkaempf@suse.com> 2013-02-10 11:54:52 UTC --- Created an attachment (id=524046) --> (http://bugzilla.novell.com/attachment.cgi?id=524046) pbl.log -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=591700 https://bugzilla.novell.com/show_bug.cgi?id=591700#c62 --- Comment #62 from Klaus Kämpf <kkaempf@suse.com> 2013-02-10 11:55:30 UTC --- Created an attachment (id=524047) --> (http://bugzilla.novell.com/attachment.cgi?id=524047) perl-BL-standalone -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=591700 https://bugzilla.novell.com/show_bug.cgi?id=591700#c63 --- Comment #63 from Klaus Kämpf <kkaempf@suse.com> 2013-02-10 11:55:59 UTC --- Created an attachment (id=524048) --> (http://bugzilla.novell.com/attachment.cgi?id=524048) history -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=591700 https://bugzilla.novell.com/show_bug.cgi?id=591700#c64 --- Comment #64 from Klaus Kämpf <kkaempf@suse.com> 2013-03-02 15:46:39 UTC --- Still unchanged with openSUSE 12.3 RC2 -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=591700 https://bugzilla.novell.com/show_bug.cgi?id=591700#c65 Duncan Mac-Vicar <dmacvicar@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P1 - Urgent |P3 - Medium Severity|Critical |Major --- Comment #65 from Duncan Mac-Vicar <dmacvicar@suse.com> 2013-03-04 10:30:19 UTC --- Fixing Severity and Urgency according to common guidelines. Severity: moved to Major (major loss of functionality, but no data corruption to be critial) Importancy: Moved to Medium. There is no reason for this bug to be "Urgent". Reporter can't set urgency unless it is the openSUSE project manager himself. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=591700 https://bugzilla.novell.com/show_bug.cgi?id=591700#c66 Steffen Winterfeldt <snwint@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |FIXED --- Comment #66 from Steffen Winterfeldt <snwint@suse.com> 2013-03-04 11:47:29 CET --- The logs show consistently (hd0,0) in menu.lst. I see nothing wrong with that. See also comment 37. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=591700 https://bugzilla.novell.com/show_bug.cgi?id=591700#c68 Duncan Mac-Vicar <dmacvicar@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED | --- Comment #68 from Duncan Mac-Vicar <dmacvicar@suse.com> 2013-03-05 09:28:24 UTC --- Steffen, line 450119 from perl-BL-standalone shows root (hd2,0) for the first and second entry (12.3 and failsafe) but (hd0,0) for the Beta2 entry that comes later. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=591700 https://bugzilla.novell.com/show_bug.cgi?id=591700#c Duncan Mac-Vicar <dmacvicar@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEEDINFO InfoProvider| |snwint@suse.com -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=591700 https://bugzilla.novell.com/show_bug.cgi?id=591700#c69 Steffen Winterfeldt <snwint@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED InfoProvider|snwint@suse.com | Resolution| |FIXED --- Comment #69 from Steffen Winterfeldt <snwint@suse.com> 2013-03-05 15:00:13 CET --- The relevant part of the log starts with 2013-01-26 15:14:14 <1> pbl-2235.1 at this point the bootloader config is already broken ((hd0,0) holding the boot files is not mounted). pbl comes up with the correct (hd2,0) for the new entry. The existing 12.2 entry is kept unchanged as it doesn't know what to make of it. So everything looks fine to me. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=591700 https://bugzilla.novell.com/show_bug.cgi?id=591700#c70 Werner Heisch <hw01@heisch.inka.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED | --- Comment #70 from Werner Heisch <hw01@heisch.inka.de> 2013-03-29 14:57:38 UTC --- Installing opensuse 12.3, it still does not work on second hdd !! ( Remarkable: first report for this bug was from 28.03.2010, yesterday was the 3 anniversary) Starting Situation: Hardware: Acer Aspire V3-771G Intel Core I7-3630M (64Bit) 32GB RAM HDD0 : Crucial Micron RealSSD C400 256GB (MTFDDAK256MAM) HDD1 : Toshiba MQ01ABD100 (1TB) On HDD0: a preinstalled Windows 8 on HDD0 on HDD1: formated by Windows 8 This was the original situation. I tried to install opensuse *12.2* on HDD1 by shortening the Windows-HDD1-partition and creating new EXT4-partitions and a swap partition. This installation failed. (known situation: see me original bug report 795838) After deleting Windows 8 and formating the hdds, the installation of suse 12.2 failed again ( same as 12.3, it tried it at this moment). (Because Installation F3->"Text mode" is not text mode, I can not tell you the reason.) I tried again with F5->save settings, than Installation on opensuse 12.2 works. After having installed opensuse 12.2 on hdd0 and parts of hdd1, I tried to install opensuse 12.3 on the free parts of hdd1 and got the same results as for the installation of 12.2. Conclusions: - After reading the discussion to this bug, I think, bugzilla should have an additional Status "annoyed by discussions" because "Resolved" normally means something different. - If it is not possible to repair bugs in a boot process in the time over 3 years, normally it would be a good reason to think about the general design. - Since 1996, I used Suse as 2. operation system behind Windows on different PCs. The installation has been easy ( at least since V 4.4.1) Today, one needs at least experience or better: insider knowledge to handle this. Good for winning new linux users ? - Maybe, there are reasons to use disk-by-id for fixed hdds, but until yet,I found none. For industrial use it's a curse. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=591700 https://bugzilla.novell.com/show_bug.cgi?id=591700#c71 --- Comment #71 from Steffen Winterfeldt <snwint@suse.com> 2013-04-02 09:01:49 CEST --- Please don't hijack other bugs. The reported issue _had_ been fixed. This is not a general 'boot config broken after update' catch-all bug. That said, please attach logs and we'll see. /var/log/pbl.log /var/log/zypp/history -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=591700 https://bugzilla.novell.com/show_bug.cgi?id=591700#c Steffen Winterfeldt <snwint@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEEDINFO InfoProvider| |hw01@heisch.inka.de -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=591700 https://bugzilla.novell.com/show_bug.cgi?id=591700#c72 --- Comment #72 from Werner Heisch <hw01@heisch.inka.de> 2013-04-10 00:59:58 UTC --- Hi Steffen, it was not my intention to hijack the bugs. I reported the bug 795838 and it has been regarded as equal to this one. But coming to the point. After a lot of different tries to install 12.2 or 12,3 I found, that the problems result from an other problem: parted reports, that it cannot read /dev/sda. This is the SSD Crucial Micron RealSSD C400 256GB (MTFDDAK256MAM). In Bios, I've changed to hdd1 ( /dev/sdb ) as the booting device and now I am booting from this hd. in /boot/grub2/device.map the Toshiba-(classical hd) is regarded as (hd0) while The SSD is regardes as (hd1). Again: It seems to be a parted-problem associated with the micron SSD. If you still need the requested log files I will send it to you, but I believe, it is not necessary here. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=591700 https://bugzilla.novell.com/show_bug.cgi?id=591700#c73 Steffen Winterfeldt <snwint@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED InfoProvider|hw01@heisch.inka.de | Resolution| |FIXED --- Comment #73 from Steffen Winterfeldt <snwint@suse.com> 2014-08-15 11:30:35 CEST --- please check again with 13.2, we have a different situation using grub2 now -- 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.
participants (1)
-
bugzilla_noreply＠novell.com