[Bug 795838] New: Installation on /dev/sdb fails on both: new installation or update from 12.1
https://bugzilla.novell.com/show_bug.cgi?id=795838 https://bugzilla.novell.com/show_bug.cgi?id=795838#c0 Summary: Installation on /dev/sdb fails on both: new installation or update from 12.1 Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Critical Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: hw01@heisch.inka.de QAContact: jsrain@suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; de; rv:1.9.2.13) Gecko/20101203 SUSE/3.6.13-0.1.1 Firefox/3.6.13 Starting Situation: ------------------- /dev/sda contains a (productive) opensuse 11.1 (Kde 3.5 :-) /dev/sdb has had a working opensuse 12.1 (only for software tests KDE4.. :-( Boot loader went to /dev/sdb, and from there to /dev/sda to start 11.1. Installation: ------------ While new installation of 12.2 on /dev/sdb : could not update by net. After first reboot: none of both installations could be started. I repaired the boot for /dev/sda for 11.1 to do my work. To get rid of the problem, I reinstalled 12.1 to try an update to 12.2 Reinstallation of 12.1 worked without a problem. After Updating to 12.2, I could not start 12.2, but with the help of the fallback, I am able to start 11.1, my productive system. What goes wrong? ---------------- Looking at /dev/sdb1/boot/grub/device.map: - - - - - - - - - - - - - - - (hd2) /dev/disk/by-id/ata-SanDisk_SDSSDP064G_121977404574 (hd1) /dev/disk/by-id/ata-ST31000528AS_5VP2Y163 (hd0) /dev/disk/by-id/ata-ST500DM002-1BD142_W2AFJ83S ....... looks OK .. and looking at /dev/sdb1/boot/grub/menu.lst: - - - - - - - - - - - - - - - # Modified by YaST2. Last modification on Mo Dez 24 16:54:22 CET 2012 # THIS FILE WILL BE PARTIALLY OVERWRITTEN by perl-Bootloader # For the new kernel it try to figure out old parameters. In case we are not able to recognize it (e.g. change of flavor or strange install order ) it it use as fallback installation parameters from /etc/sysconfig/bootloader default 3 timeout 8 gfxmenu (hd1,0)/boot/message ###Don't change this comment - YaST2 identifier: Original name: linux### title Desktop -- openSUSE 12.2 - 3.4.6-2.10 kernel (hd0,0)/boot/vmlinuz-3.4.6-2.10-desktop root=/dev/sdb1 ^^^^^ resume=/dev/disk/by-id/ata-ST500DM002-1BD142_W2AFJ83S-part2 splash=silent quiet video=1280x1024 showopts vga=0x31a initrd (hd0,0)/boot/initrd-3.4.6-2.10-desktop ^^^^^ ###Don't change this comment - YaST2 identifier: Original name: failsafe### title Failsafe -- openSUSE 12.2 - 3.4.6-2.10 kernel (hd0,0)/boot/vmlinuz-3.4.6-2.10-desktop root=/dev/sdb1 ^^^^^ showopts apm=off noresume edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 nomodeset x11failsafe vga=0x31a initrd (hd0,0)/boot/initrd-3.4.6-2.10-desktop ^^^^^^ ###Don't change this comment - YaST2 identifier: Original name: linux### title GNU GRUB 2 -- openSUSE 12.2 - GNU GRUB 2 kernel (hd0,0)/boot/grub2/core.img root=/dev/sdb1 ^^^^^ resume=/dev/disk/by-id/ata-ST500DM002-1BD142_W2AFJ83S-part2 splash=silent quiet video=1280x1024 showopts vga=0x31a ###Don't change this comment - YaST2 identifier: Original name: SUSE LINUX 11.1 (/dev/sda1)### title SUSE LINUX 11.1 (/dev/sda1) rootnoverify (hd0,0) chainloader +1 ###Don't change this comment - YaST2 identifier: Original name: floppy### title Diskette rootnoverify (hd0) chainloader +1 .............. for me, it looks like the marked parts (^^^^) are pointing to the wrong disk. BTW: Bug report 773576 ======================= is pointing to the same problem. it was Opened: 2012-07-29 22:35 UTC Last modified: 2012-09-07 19:52:49 UTC Remember: we are not talking about one bug in one package, we are talking about the grave bugs of the installation. Bug 773576 was reported over 5 month ago, last time modified over 3 month ago Problem solved? NO, Who cares .. we a preparing a new release ...:-)) I'm selling communications software between Linux and the Siemens plc family Simatic ( http:/sites.inka.de/heisch ). We started with Suse in 1994 and always used Suse as development platform and for applications in industry. In times of Suse 6.3 or 8.1, it was quite easier to install Suse than Windows and also easier to switch to a other hd. ..and I'm sure that there would have been no need to write this bug report, 3 months after the release of the "stable" version. Meanwhile, I'm not quite sure, that opensuse still has the quality to be used in industrial installations. (KDE4 is not, but that's not your problem.) Reproducible: Always Steps to Reproduce: 1. 2 Disks, installing any no 12.2 OS on first disk 2. Installing 12.2 on second disk. Problem should happen after reboot. Actual Results: s.o. Expected Results: s.o. -- 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=795838
https://bugzilla.novell.com/show_bug.cgi?id=795838#c
Werner Heisch
https://bugzilla.novell.com/show_bug.cgi?id=795838
https://bugzilla.novell.com/show_bug.cgi?id=795838#c1
Jiaying ren
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; de; rv:1.9.2.13) Gecko/20101203 SUSE/3.6.13-0.1.1 Firefox/3.6.13
Starting Situation: ------------------- /dev/sda contains a (productive) opensuse 11.1 (Kde 3.5 :-) /dev/sdb has had a working opensuse 12.1 (only for software tests KDE4.. :-(
Boot loader went to /dev/sdb, and from there to /dev/sda to start 11.1.
Hi~Werner. Thank you for your report. Would you please attach your grub/grub2 config? -- 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=795838
https://bugzilla.novell.com/show_bug.cgi?id=795838#c2
--- Comment #2 from Werner Heisch
Hi~Werner. Thank you for your report. Would you please attach your grub/grub2 config?
Hi Jiaying ren. How can I find it? /boot/grub does not have a file or directory grub2. I can offer you /boot/grub2 but that's a big stuff, too big to post here. I've packed the whole /boot directory into a tgz-file but it's about 55MB. (My first suse distri was smaller. Are we really talking about a boot loader? The first ones have resided in the MBR. ) I can imagine, that I do not have a /boot/grub/grub2 hierarchy, because I made an update from 12.1. Is this right ? If not: Tell me which file(s) do you need? BTW: I found a way to start 12.2: I have edited /dev/sdb1/boot/grub/menu.lst and changed the according (hd0,0) to (hd1,0) then it works. But of course, that's a work around, not a solution. -- 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=795838
https://bugzilla.novell.com/show_bug.cgi?id=795838#c
Jiaying ren
https://bugzilla.novell.com/show_bug.cgi?id=795838
https://bugzilla.novell.com/show_bug.cgi?id=795838#c3
Michael Chang
https://bugzilla.novell.com/show_bug.cgi?id=795838
https://bugzilla.novell.com/show_bug.cgi?id=795838#c4
--- Comment #4 from Michael Chang
https://bugzilla.novell.com/show_bug.cgi?id=795838
https://bugzilla.novell.com/show_bug.cgi?id=795838#c5
--- Comment #5 from Werner Heisch
https://bugzilla.novell.com/show_bug.cgi?id=795838
https://bugzilla.novell.com/show_bug.cgi?id=795838#c6
--- Comment #6 from Werner Heisch
https://bugzilla.novell.com/show_bug.cgi?id=795838
https://bugzilla.novell.com/show_bug.cgi?id=795838#c7
--- Comment #7 from Werner Heisch
https://bugzilla.novell.com/show_bug.cgi?id=795838
https://bugzilla.novell.com/show_bug.cgi?id=795838#c8
Michael Chang
From the very beginning the log has pointed to the root cause ..
2012-12-24 16:37:31 MILESTONE: *** WARNING: No UDEV mapping! *** It cause perl-Bootlader's GetKernelDevice() failed to translate device names to kernel device names 2012-12-24 16:53:58 MILESTONE: GRUB::GetKernelDevice: From /dev/disk/by-id/ata-ST31000528AS_5VP2Y163 to /dev/disk/by-id/ata-ST31000528AS_5VP2Y163 It should translate to sdb and output sth like this GRUB::GetKernelDevice: From /dev/disk/by-id/ata-ST31000528AS_5VP2Y163 to /dev/sdb Finally the fallback device is used (hd0) as no matched "kernel device" can be found in udevmap 2012-12-24 16:53:58 WARNING: GRUB::UnixDev2GrubDev: Unknown device/partition, using fallback 2012-12-24 16:53:58 MILESTONE: GRUB::UnixDev2GrubDev: Translated UNIX partition -> GRUB device: /dev/disk/by-id/ata-ST31000528AS_5VP2Y163-part1 to (hd0,0) 2012-12-24 16:53:58 MILESTONE: Set GRUB's root to (hd0,0) Probably udevadm info -q all -n $dev 2>/dev/null Has no output *during the update*, I can't tell why .. And an attempt to fix the issue in git commit from Steffen https://github.com/openSUSE/perl-bootloader/commit/46c82d61f4a9e12999aec16f2... Steffen any other good idea? I conclude this is udev problem for 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.
https://bugzilla.novell.com/show_bug.cgi?id=795838
https://bugzilla.novell.com/show_bug.cgi?id=795838#c9
--- Comment #9 from Michael Chang
Hi Michael, (with the best wishes for the new year),
Thanks a lot. And wish you a brilliant year too. :)
BTW: I believe, it would be a good idea, to decide between /dev/disk/by-id/ ... and /dev/sd(a.b.c....) while istalling the system.
We use persistent device name (/dev/disk/by-id/...) over the kernel device name is to tackle with the potential problem as the kernel device name is floating (that is if you change your hw configration (add/remove disks or place the disk to other machine) you may fail with boot or bootloader install as the kernel device name changes ..) You could edit device.map manually if your prefer /dev/sd[a-z] .. it should remain to work. However can't agree with you more, as we see many examples on how linux is ruined these year by *monster* software which claims it did all things right. -- 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.
>>>>>>>>>>>>>>>>>>>> /dev/sda2 swap swap defaults 0 0 /dev/sda1 / ext3 acl,user_xattr 1 1 /dev/sda3 /home ext3 acl,user_xattr 1 2 /dev/sda5 /v1 ext3 acl,user_xattr 1 2 /dev/sda6 /v2 ext3 acl,user_xattr 1 2
https://bugzilla.novell.com/show_bug.cgi?id=795838
https://bugzilla.novell.com/show_bug.cgi?id=795838#c10
Werner Heisch
>>>>>>>>>>>>>>>>>>>> (hd2) /dev/disk/by-id/ata-SanDisk_SDSSDP064G_121977404574 (hd1) /dev/disk/by-id/ata-ST31000528AS_5VP2Y163 (hd0) /dev/disk/by-id/ata-ST500DM002-1BD142_W2AFJ83S <<<<<<<<<<<<<<<<<<<<<<<<<<<
My (sda1) boot/grub/menu.lst looks like this:
>>>>>>>>>>>>>>>>>>>> # Modified by YaST2. Last modification on Fr Dez 14 04:02:07 CET 2012 default 0 timeout 8 gfxmenu (hd0,0)/boot/message
###Don't change this comment - YaST2 identifier: Original name: linux### title SUSE LINUX 11.1 root (hd0,0) kernel /boot/vmlinuz root=/dev/disk/by-id/ata-ST500DM002-1BD142_W2AFJ83S-part1 repair=1 resume=/dev/disk/by-id/ata-ST500DM002-1BD142_W2AFJ83S-part2 splash=silent showopts vga=0x31a initrd /boot/initrd ###Don't change this comment - YaST2 identifier: Original name: failsafe### title Failsafe -- SUSE LINUX root (hd0,0) kernel /boot/vmlinuz root=/dev/disk/by-id/ata-ST500DM002-1BD142_W2AFJ83S-part1 showopts ide=nodma apm=off noresume edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 x11failsafe vga=0x31a initrd /boot/initrd title opensuse 12.2 root (hd0,0) kernel /boot/vmlinuz root=/dev/sdb1 repair=1 resume=/dev/sdb1 splash=silent showopts vga=0x31a initrd /boot/initrd <<<<<<<<<<<<<<<<<<<<<<<<<<< -- 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=795838
https://bugzilla.novell.com/show_bug.cgi?id=795838#c11
--- Comment #11 from Michael Chang
Hi Michael, Hi Steffen,
maybe an reason: Before installing 12.2 I have cloned my productive system on /dev/sda to a new disk.
IMHO this is fine. As fstab is for sysv init, not for bootloader and you adjusted your menu.lst correctly. One potential problem is that if you don't adjust sda1's device.map correctly will lead to device not found (as you clone your disk to the other, the by-id name differs) when reinstalling bootloader, but this is not the issue we are in discuss.
I've edited /etc/fstab not using /dev/disk/by-id/.. because I do not like it.
>>>>>>>>>>>>>>>>>>>>> /dev/sda2 swap swap defaults 0 0 /dev/sda1 / ext3 acl,user_xattr 1 1 /dev/sda3 /home ext3 acl,user_xattr 1 2 /dev/sda5 /v1 ext3 acl,user_xattr 1 2 /dev/sda6 /v2 ext3 acl,user_xattr 1 2
My (sda1) /etc/fstab looks like this: proc /proc proc defaults 0 0 sysfs /sys sysfs noauto 0 0 debugfs /sys/kernel/debug debugfs noauto 0 0 usbfs /proc/bus/usb usbfs noauto 0 0 devpts /dev/pts devpts mode=0620,gid=5 0 0 /dev/disk/by-id/ata-SanDisk_SDSSDP064G_121977404574-part2 /ssd ext3 acl,user_xattr 1 2 <<<<<<<<<<<<<<<<<<<<<<<<<<<
My (sda1) boot/grub/device.map looks like this:
>>>>>>>>>>>>>>>>>>>>> (hd2) /dev/disk/by-id/ata-SanDisk_SDSSDP064G_121977404574 (hd1) /dev/disk/by-id/ata-ST31000528AS_5VP2Y163 (hd0) /dev/disk/by-id/ata-ST500DM002-1BD142_W2AFJ83S
Better make sure /dev/disk/by-id/ata-ST500DM002-1BD142_W2AFJ83S exists or use /dev/sda or new disk's by-id device name. You may encounter bootloader installation fail when, for eg, grub package updates if the information incorrect here. Regards, Michael -- 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=795838
https://bugzilla.novell.com/show_bug.cgi?id=795838#c12
Michael Chang
https://bugzilla.novell.com/show_bug.cgi?id=795838
https://bugzilla.novell.com/show_bug.cgi?id=795838#c
Michael Chang
https://bugzilla.novell.com/show_bug.cgi?id=795838
https://bugzilla.novell.com/show_bug.cgi?id=795838#c13
Frederic Crozat
https://bugzilla.novell.com/show_bug.cgi?id=795838
https://bugzilla.novell.com/show_bug.cgi?id=795838#c14
Robert Milasan
https://bugzilla.novell.com/show_bug.cgi?id=795838
https://bugzilla.novell.com/show_bug.cgi?id=795838#c15
--- Comment #15 from Michael Chang
https://bugzilla.novell.com/show_bug.cgi?id=795838
https://bugzilla.novell.com/show_bug.cgi?id=795838#c16
--- Comment #16 from Michael Chang
I really don't know what should be blamed here, as it's not likely to fail anyhow. The one possibility to me is that udev returns no useful info.
For ex, like crash but this is just wild guess and no clue .. unfortunately. -- 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=795838
https://bugzilla.novell.com/show_bug.cgi?id=795838#c17
--- Comment #17 from Michael Chang
https://bugzilla.novell.com/show_bug.cgi?id=795838
https://bugzilla.novell.com/show_bug.cgi?id=795838#c18
Michael Chang
https://bugzilla.novell.com/show_bug.cgi?id=795838
https://bugzilla.novell.com/show_bug.cgi?id=795838#c19
--- Comment #19 from Robert Milasan
participants (1)
-
bugzilla_noreply@novell.com