[Bug 590637] New: after kernel update new boot variant look at wrong hard drive
http://bugzilla.novell.com/show_bug.cgi?id=590637 http://bugzilla.novell.com/show_bug.cgi?id=590637#c0 Summary: after kernel update new boot variant look at wrong hard drive Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: x86-64 OS/Version: openSUSE 11.2 Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader AssignedTo: jsrain@novell.com ReportedBy: gvozdila@yahoo.com QAContact: jsrain@novell.com Found By: --- Blocker: --- Created an attachment (id=350135) --> (http://bugzilla.novell.com/attachment.cgi?id=350135) resul of fdisk -l User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; ru; rv:1.9.1.8) Gecko/20100204 SUSE/3.5.8-0.1.1 Firefox/3.5.8 I have 2 hard drives(really 3, but third do not use on boot process ). Bootloader installed on drive sda, and my /boot places on sdc (on primary partition). When new version of kernel appears, new variant of boot start to load not from hd(1,0) (in terms of grub), but from hd(0,0). it can be change when booting for one successful boot. Next, in Yast, right entry : kernel image /boot/vmlinuz-2.6.31.12-0.1-desktop RAM disk /boot/initrd-2.6.31.12-0.1-desktop root device(?) /dev/disk/by-id/raid-sil_agajbhdfcdab-part2 new wrong entry kernel image /media/system/vmlinuz-2.6.31.12-0.2-desktop RAM disk /media/system/initrd-2.6.31.12-0.2-desktop root device /dev/disk/by-id/raid-sil_agajbhdfcdab-part2 note, that /media/system is directory when old windows root-folder mount, and it places on /hda, but not on /dev/disk/by-id/raid-sil_agajbhdfcdab-part2, cause in just "link" on /hdc ... Reproducible: Always Steps to Reproduce: 1. install bootloader on 1 disk, /boot on second (on primary, but not on first partition of second disk) 2. wait for system kernel update 3. new configuration can not be load -- 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=590637 http://bugzilla.novell.com/show_bug.cgi?id=590637#c1 --- Comment #1 from andrey yakunin <gvozdila@yahoo.com> 2010-03-23 21:58:59 UTC --- Created an attachment (id=350136) --> (http://bugzilla.novell.com/attachment.cgi?id=350136) /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=590637 http://bugzilla.novell.com/show_bug.cgi?id=590637#c Jiri Srain <jsrain@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jsrain@novell.com 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=590637 http://bugzilla.novell.com/show_bug.cgi?id=590637#c2 Josef Reidinger <jreidinger@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |gvozdila@yahoo.com --- Comment #2 from Josef Reidinger <jreidinger@novell.com> 2010-03-25 12:49:26 UTC --- Please provide yast logs, it contains also log what happen during updating kernel. (http://en.opensuse.org/Bugs/YaST#I_reported_a_YaST2_bug.2C_and_now_I_am_aske...) 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=590637 http://bugzilla.novell.com/show_bug.cgi?id=590637#c3 --- Comment #3 from andrey yakunin <gvozdila@yahoo.com> 2010-03-28 16:27:42 UTC --- Created an attachment (id=351030) --> (http://bugzilla.novell.com/attachment.cgi?id=351030) yast2 logs -- 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=590637 http://bugzilla.novell.com/show_bug.cgi?id=590637#c4 --- Comment #4 from Josef Reidinger <jreidinger@novell.com> 2010-03-31 12:44:04 UTC --- Thanks for logs. I found that it start 10.1 When disc is bad recognized. There is something strange with your device mapper devices. Could you please post output of these two commands? ls -l /dev/mapper/ udevadm info -q all -n /dev/disk/by-id/raid-sil_agajbhdfcdab-part7 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=590637 http://bugzilla.novell.com/show_bug.cgi?id=590637#c5 --- Comment #5 from andrey yakunin <gvozdila@yahoo.com> 2010-04-04 15:44:39 UTC --- ls -l /dev/mapper/ итого 0 crw-rw---- 1 root root 10, 60 Апр 4 14:00 control brw-r----- 1 root disk 253, 0 Апр 4 10:00 sil_agajbhdfcdab brw-rw---- 1 root disk 253, 1 Апр 4 10:00 sil_agajbhdfcdab_part1 brw-rw---- 1 root disk 253, 2 Апр 4 10:00 sil_agajbhdfcdab_part2 brw-rw---- 1 root disk 253, 3 Апр 4 10:00 sil_agajbhdfcdab_part3 udevadm info -q all -n /dev/disk/by-id/raid-sil_agajbhdfcdab-part7 sorry, but i already "kill" one of my logic disks. so now i have only part[1,2,3] it was just extended partition with ext3 partition on it. Not RAID! not bootable. and i dont now why SuSe think it was raid :-( but i could show you sil_agajbhdfcdab-part2, it's my / /sbin/udevadm info -q all -n /dev/disk/by-id/raid-sil_agajbhdfcdab-part2 P: /devices/virtual/block/dm-2 N: dm-2 L: 50 W: 16 S: root S: block/253:2 S: disk/by-id/dm-name-sil_agajbhdfcdab_part2 S: disk/by-id/dm-uuid-part2-DMRAID-sil_agajbhdfcdab S: disk/by-uuid/92b6fe8d-8fb8-4579-b6a6-4ec4896f713a S: disk/by-id/raid-sil_agajbhdfcdab-part2 E: UDEV_LOG=3 E: DEVPATH=/devices/virtual/block/dm-2 E: MAJOR=253 E: MINOR=2 E: DEVNAME=/dev/dm-2 E: DEVTYPE=disk E: DM_NAME=sil_agajbhdfcdab E: DM_UUID=part2-DMRAID-sil_agajbhdfcdab E: DM_STATE=ACTIVE E: DM_TABLE_STATE=LIVE E: DM_OPENCOUNT=1 E: DM_LAST_EVENT_NR=0 E: DM_MAJOR=253 E: DM_MINOR=2 E: DM_TARGET_COUNT=1 E: DM_TARGET_TYPES=linear E: DM_DEPS=1 E: ID_FS_UUID=92b6fe8d-8fb8-4579-b6a6-4ec4896f713a E: ID_FS_UUID_ENC=92b6fe8d-8fb8-4579-b6a6-4ec4896f713a E: ID_FS_VERSION=1.0 E: ID_FS_TYPE=ext4 E: ID_FS_USAGE=filesystem E: DM_PART=2 E: DM_TYPE=raid E: DKD_MEDIA_AVAILABLE=1 E: DKD_DM_NAME=sil_agajbhdfcdab_part2 E: DKD_DM_UUID=part2-DMRAID-sil_agajbhdfcdab E: DKD_DM_STATE=ACTIVE E: DKD_DM_TABLE_STATE=LIVE E: DKD_DM_OPENCOUNT=1 E: DKD_DM_LAST_EVENT_NR=0 E: DKD_DM_MAJOR=253 E: DKD_DM_MINOR=2 E: DKD_DM_TARGET_COUNT=1 E: DKD_DM_TARGET_TYPES=linear E: DKD_PRESENTATION_NOPOLICY=1 E: DEVLINKS=/dev/root /dev/block/253:2 /dev/disk/by-id/dm-name-sil_agajbhdfcdab_part2 /dev/disk/by-id/dm-uuid-part2-DMRAID-sil_agajbhdfcdab /dev/disk/by-uuid/92b6fe8d-8fb8-4579-b6a6-4ec4896f713a /dev/disk/by-id/raid-sil_agajbhdfcdab-part2 -- 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=590637 https://bugzilla.novell.com/show_bug.cgi?id=590637#c Josef Reidinger <jreidinger@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium Status|NEEDINFO |ASSIGNED InfoProvider|gvozdila@yahoo.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=590637 https://bugzilla.novell.com/show_bug.cgi?id=590637#c6 Josef Reidinger <jreidinger@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO InfoProvider| |kasievers@novell.com --- Comment #6 from Josef Reidinger <jreidinger@novell.com> 2010-10-07 13:19:53 UTC --- OK, I again investigate logs with new information. I think I found reason. udev return strange informations during updating. Kay - do you have idea why it can return such strange devices? In case of dm devices I construct it as "/dev/mapper/" + udev-DM_NAME + "_part" + udev-DM_PART It looks like that udev has set as DM_NAME whole part also with partition number ,so result contain twice "part<number>" 2010-01-06 12:37:56 MILESTONE: GRUB::GetKernelDevice: From /dev/disk/by-id/raid-sil_agajbhdfcdab-part2 to /dev/mapper/sil_agajbhdfcdab_part2_part2 2010-01-06 12:37:56 MILESTONE: GRUB::GetKernelDevice: From devpts to devpts 2010-01-06 12:37:56 MILESTONE: GRUB::GetKernelDevice: From debugfs to debugfs 2010-01-06 12:37:56 MILESTONE: GRUB::GetKernelDevice: From /dev/disk/by-id/ata-SAMSUNG_SP0812N_S00MJ10Y707785-part1 to /dev/sda1 2010-01-06 12:37:56 MILESTONE: GRUB::GetKernelDevice: From proc to proc 2010-01-06 12:37:56 MILESTONE: GRUB::GetKernelDevice: From /dev/disk/by-id/raid-sil_agajbhdfcdab-part7 to /dev/mapper/sil_agajbhdfcdab_part7_part7 2010-01-06 12:37:56 MILESTONE: GRUB::GetKernelDevice: From /dev/disk/by-id/raid-sil_agajbhdfcdab-part1 to /dev/mapper/sil_agajbhdfcdab_part1_part1 2010-01-06 12:37:56 MILESTONE: GRUB::GetKernelDevice: From usbfs to usbfs 2010-01-06 12:37:56 MILESTONE: GRUB::GetKernelDevice: From sysfs to sysfs 2010-01-06 12:37:56 MILESTONE: GRUB::GetKernelDevice: From /dev/disk/by-id/raid-sil_agajbhdfcdab-part5 to /dev/mapper/sil_agajbhdfcdab_part5_part5 2010-01-06 12:37:56 MILESTONE: GRUB::GetKernelDevice: From /dev/disk/by-id/raid-sil_agajbhdfcdab-part6 to /dev/mapper/sil_agajbhdfcdab_part6_part6 -- 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=590637 https://bugzilla.novell.com/show_bug.cgi?id=590637#c7 Kay Sievers <kasievers@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kasievers@novell.com InfoProvider|kasievers@novell.com |xwhu@novell.com --- Comment #7 from Kay Sievers <kasievers@novell.com> 2010-10-07 13:26:15 UTC --- It's a device mapper property. -- 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=590637 https://bugzilla.novell.com/show_bug.cgi?id=590637#c8 --- Comment #8 from Kay Sievers <kasievers@novell.com> 2010-10-07 13:28:05 UTC --- Probably a dmraid issue, and your: construct it as "/dev/mapper/" + udev-DM_NAME + "_part" + udev-DM_PART logic can't be used 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=590637 https://bugzilla.novell.com/show_bug.cgi?id=590637#c9 Xinwei Hu <xwhu@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED CC| |xwhu@novell.com InfoProvider|xwhu@novell.com | --- Comment #9 from Xinwei Hu <xwhu@novell.com> 2010-10-11 07:25:32 UTC --- (In reply to comment #8)
Probably a dmraid issue, and your: construct it as "/dev/mapper/" + udev-DM_NAME + "_part" + udev-DM_PART logic can't be used here.
The linear mapping is created by kpartx, and partition number is part of the DM_NAME as implied with "kpartx -p_part". DM_PART is extracted from DM_NAME by kpartx_id as far as I understand. So, in short, the logic needs some changing. 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=590637 https://bugzilla.novell.com/show_bug.cgi?id=590637#c10 Josef Reidinger <jreidinger@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO InfoProvider| |xwhu@novell.com --- Comment #10 from Josef Reidinger <jreidinger@novell.com> 2010-10-11 08:27:36 UTC --- (In reply to comment #9)
(In reply to comment #8)
Probably a dmraid issue, and your: construct it as "/dev/mapper/" + udev-DM_NAME + "_part" + udev-DM_PART logic can't be used here.
The linear mapping is created by kpartx, and partition number is part of the DM_NAME as implied with "kpartx -p_part". DM_PART is extracted from DM_NAME by kpartx_id as far as I understand.
So, in short, the logic needs some changing.
Thanks.
When it was changed? and as you see output in comment #5 DM_NAME doesn't have partition number as part of it ( It will be much easier for me if it had 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=590637 https://bugzilla.novell.com/show_bug.cgi?id=590637#c11 Xinwei Hu <xwhu@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED InfoProvider|xwhu@novell.com | --- Comment #11 from Xinwei Hu <xwhu@novell.com> 2010-10-11 09:13:12 UTC --- (In reply to comment #10)
(In reply to comment #9)
(In reply to comment #8)
Probably a dmraid issue, and your: construct it as "/dev/mapper/" + udev-DM_NAME + "_part" + udev-DM_PART logic can't be used here.
The linear mapping is created by kpartx, and partition number is part of the DM_NAME as implied with "kpartx -p_part". DM_PART is extracted from DM_NAME by kpartx_id as far as I understand.
So, in short, the logic needs some changing.
Thanks.
When it was changed? and as you see output in comment #5 DM_NAME doesn't have partition number as part of it ( It will be much easier for me if it had it)
OK. We are referring to the different $DM_NAME then. The initial $DM_NAME was got via 'dmsetup export', and it is the full table name, which includes "_part" suffix. # dmsetup export -j 253 -m 1 DM_NAME=3600508b400105b5a00015000001b0000_part1 DM_UUID=part1-mpath-3600508b400105b5a00015000001b0000 DM_STATE=ACTIVE DM_TABLE_STATE=LIVE DM_OPENCOUNT=1 DM_LAST_EVENT_NR=0 DM_MAJOR=253 DM_MINOR=1 DM_TARGET_COUNT=1 DM_TARGET_TYPES=linear DM_DEPS=1 And then, it was changed via kpartx_id, when DM_UUID was begin with "partX-". That's what you see in comment #5. Can you describe how GRUB::GetKernelDevice works? -- 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=590637 https://bugzilla.novell.com/show_bug.cgi?id=590637#c12 Josef Reidinger <jreidinger@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO InfoProvider| |xwhu@novell.com --- Comment #12 from Josef Reidinger <jreidinger@novell.com> 2010-10-11 09:21:22 UTC --- (In reply to comment #11)
(In reply to comment #10)
(In reply to comment #9)
(In reply to comment #8)
Probably a dmraid issue, and your: construct it as "/dev/mapper/" + udev-DM_NAME + "_part" + udev-DM_PART logic can't be used here.
The linear mapping is created by kpartx, and partition number is part of the DM_NAME as implied with "kpartx -p_part". DM_PART is extracted from DM_NAME by kpartx_id as far as I understand.
So, in short, the logic needs some changing.
Thanks.
When it was changed? and as you see output in comment #5 DM_NAME doesn't have partition number as part of it ( It will be much easier for me if it had it)
OK. We are referring to the different $DM_NAME then.
The initial $DM_NAME was got via 'dmsetup export', and it is the full table name, which includes "_part" suffix.
# dmsetup export -j 253 -m 1 DM_NAME=3600508b400105b5a00015000001b0000_part1 DM_UUID=part1-mpath-3600508b400105b5a00015000001b0000 DM_STATE=ACTIVE DM_TABLE_STATE=LIVE DM_OPENCOUNT=1 DM_LAST_EVENT_NR=0 DM_MAJOR=253 DM_MINOR=1 DM_TARGET_COUNT=1 DM_TARGET_TYPES=linear DM_DEPS=1
And then, it was changed via kpartx_id, when DM_UUID was begin with "partX-". That's what you see in comment #5.
Can you describe how GRUB::GetKernelDevice works?
OK, how it works. It translate udev device to kernel device which is used in perl-Bootloader. For device mapper device is problem that udev points to /dev/dm-* but tools report device in format /dev/mapper/* So I use variables in udev to translate udev names to /dev/mapper/* names. If this is only problem It is not problem to check if DM_NAME contain _part* suffix and if so, don't append it from DM_PART. Does it work if I change it this way? -- 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=590637 https://bugzilla.novell.com/show_bug.cgi?id=590637#c13 Xinwei Hu <xwhu@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED InfoProvider|xwhu@novell.com | --- Comment #13 from Xinwei Hu <xwhu@novell.com> 2010-10-11 10:05:16 UTC --- (In reply to comment #12)
OK, how it works. It translate udev device to kernel device which is used in perl-Bootloader. For device mapper device is problem that udev points to /dev/dm-* but tools report device in format /dev/mapper/* So I use variables in udev to translate udev names to /dev/mapper/* names. If this is only problem It is not problem to check if DM_NAME contain _part* suffix and if so, don't append it from DM_PART. Does it work if I change it this way?
Yes, I think it should work too. -- 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=590637 https://bugzilla.novell.com/show_bug.cgi?id=590637#c14 Josef Reidinger <jreidinger@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED --- Comment #14 from Josef Reidinger <jreidinger@novell.com> 2010-10-12 07:40:52 UTC --- OK, thanks for report and information. Fixed for 11.4. -- 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=590637 https://bugzilla.novell.com/show_bug.cgi?id=590637#c15 Swamp Workflow Management <swamp@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status Whiteboard| |maint:released:sle11-sp1:38 | |296 --- Comment #15 from Swamp Workflow Management <swamp@suse.com> 2011-04-06 12:25:58 UTC --- Update released for: perl-Bootloader Products: SLE-DESKTOP 11-SP1 (i386, x86_64) SLE-SERVER 11-SP1 (i386, ia64, ppc64, s390x, x86_64) SLES4VMWARE 11-SP1 (i386, x86_64) -- 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.
http://bugzilla.novell.com/show_bug.cgi?id=590637 http://bugzilla.novell.com/show_bug.cgi?id=590637#c16 --- Comment #16 from Bernhard Wiedemann <bwiedemann@suse.com> --- This is an autogenerated message for OBS integration: This bug (590637) was mentioned in https://build.opensuse.org/request/show/51039 Factory / perl-Bootloader -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com