[Bug 543076] New: mkinitrd generates: WARNING: GRUB::GrubDev2UnixDev: No partition found for /dev/sda with 3
http://bugzilla.novell.com/show_bug.cgi?id=543076 User hedgehogshiatus@gmail.com added comment http://bugzilla.novell.com/show_bug.cgi?id=543076#c21 Summary: mkinitrd generates: WARNING: GRUB::GrubDev2UnixDev: No partition found for /dev/sda with 3 Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: i586 OS/Version: openSUSE 11.1 Status: NEW Severity: Major Priority: P5 - None Component: Kernel AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: hedgehogshiatus@gmail.com QAContact: qa@suse.de Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.3) Gecko/20090909 SUSE/3.5.3-1.2 Firefox/3.5.3 This error occurs for several users, possibly leaving machine unbootable: See here: http://www.linuxquestions.org/questions/susenovell-60/mkinitrd-failing-after... See here too: http://forums.opensuse.org/install-boot-login/420557-updates-keep-destroying... Reproducible: Always Steps to Reproduce: 1. mkinitrd_setup 2. mkinitrd -v -i /boot/initrd-`uname -r` -k /boot/vmlinuz-`uname -r` 3. Actual Results: Kernel image: /boot/vmlinuz-2.6.27.29-0.1-trace Initrd image: /boot/initrd-2.6.27.29-0.1-trace Root device: /dev/system/root (mounted on / as ext3) Resume device: /dev/system/swap [BLOCK] /dev/sda -> ata_piix [BLOCK] /dev/sda -> sd_mod [MODULES] 02-start.sh: processor thermal ahci fan jbd ext3 dm_mod edd [MODULES] 03-dm.sh: dm-multipath [MODULES] 03-dm.sh: dm-mod [MODULES] 03-dm.sh: dm-snapshot [MODULES] 03-storage.sh: ext3 [MODULES] 11-block.sh: ata_piix sd_mod [MODULES] 11-usb.sh: usbcore [MODULES] 11-usb.sh: ohci_hcd [MODULES] 11-usb.sh: uhci-hcd [MODULES] 11-usb.sh: ehci_hcd [MODULES] 11-usb.sh: usbhid [MODULES] 21-multipath.sh: dm-multipath [MODULES] 21-multipath.sh: dm-round-robin [MODULES] 21-multipath.sh: scsi-dh-emc [MODULES] 21-multipath.sh: scsi-dh-hp_sw [MODULES] 21-multipath.sh: scsi-dh-rdac [MODULES] 21-multipath.sh: scsi-dh-alua [MODULES] 61-lvm2.sh: linear Kernel Modules: hwmon thermal_sys processor thermal dock scsi_mod libata ahci fan jbd mbcache ext3 dm-mod edd scsi_dh dm-multipath dm-snapshot ata_piix crc-t10dif sd_mod usbcore ohci-hcd uhci-hcd ehci-hcd ff-memless hid usbhid dm-round-robin scsi_dh_emc scsi_dh_hp_sw scsi_dh_rdac scsi_dh_alua linear [MOUNT] Root: /dev/system/root Features: dm block usb multipath kpartx lvm2 resume.userspace resume.kernel Bootsplash: openSUSE (1280x1024) Shared libs: lib/ld-2.9.so lib/libacl.so.1.1.0 lib/libaio.so.1.0.1 lib/libattr.so.1.1.0 lib/libblkid.so.1.0 lib/libc-2.9.so lib/libcom_err.so.2.1 lib/libdevmapper-event.so.1.02 lib/libdevmapper.so.1.02 lib/libdl-2.9.so lib/libe2p.so.2.3 lib/libext2fs.so.2.4 lib/libgcc_s.so.1 lib/libgcrypt.so.11.4.4 lib/libgpg-error.so.0.4.0 lib/liblzo2.so.2.0.0 lib/libncurses.so.5.6 lib/libpthread-2.9.so lib/libreadline.so.5.2 lib/librt-2.9.so lib/libselinux.so.1 lib/libsepol.so.1 lib/libsysfs.so.2.0.1 lib/libutil-2.9.so lib/libuuid.so.1.2 lib/libvolume_id.so.1.0.1 lib/libz.so.1.2.3 lib/multipath/libmultipath.so usr/lib/libdirect-1.2.so.0.3.0 usr/lib/libdirectfb-1.2.so.0.3.0 usr/lib/libfusion-1.2.so.0.3.0 usr/lib/libglib-2.0.so.0.1800.2 usr/lib/libsplashy.so.1.0.0 usr/lib/libsplashycnf.so.1.0.0 usr/local/lib/libpcre.so.0.0.1 lib/libnss_dns-2.9.so lib/libnss_dns.so.2 lib/libnss_files-2.9.so lib/libnss_files.so.2 lib/libgcc_s.so.1 25534 blocks 2009-09-30 12:07:14 WARNING: GRUB::GrubDev2UnixDev: No partition found for /dev/sda with 3. 2009-09-30 12:07:14 WARNING: GRUB::GrubDev2UnixDev: No partition found for /dev/sda with 3. 2009-09-30 12:07:14 WARNING: GRUB::GrubDev2UnixDev: No partition found for /dev/sda with 3. 2009-09-30 12:07:14 WARNING: GRUB::GrubDev2UnixDev: No partition found for /dev/sda with 3. 2009-09-30 12:07:14 WARNING: GRUB::GrubDev2UnixDev: No partition found for /dev/sda with 3. 2009-09-30 12:07:14 WARNING: GRUB::GrubDev2UnixDev: No partition found for /dev/sda with 3. 2009-09-30 12:07:14 WARNING: GRUB::GrubDev2UnixDev: No partition found for /dev/sda with 3. 2009-09-30 12:07:14 WARNING: GRUB::GrubDev2UnixDev: No partition found for /dev/sda with 3. 2009-09-30 12:07:14 WARNING: GRUB::GrubDev2UnixDev: No partition found for /dev/sda with 3. 2009-09-30 12:07:14 WARNING: GRUB::GrubDev2UnixDev: No partition found for /dev/sda with 3. 2009-09-30 12:07:14 WARNING: GRUB::GrubDev2UnixDev: No partition found for /dev/sda with 3. 2009-09-30 12:07:14 WARNING: GRUB::GrubDev2UnixDev: No partition found for /dev/sda with 3. 2009-09-30 12:07:14 WARNING: GRUB::GrubDev2UnixDev: No partition found for /dev/sda with 3. 2009-09-30 12:07:14 WARNING: GRUB::GrubDev2UnixDev: No partition found for /dev/sda with 3. Expected Results: No warnings. localhost:~ # parted /dev/sda print Model: ATA FUJITSU MHV2100A (scsi) Disk /dev/sda: 100GB Sector size (logical/physical): 512B/512B Partition Table: msdos Number Start End Size Type File system Flags 1 32.3kB 65.8MB 65.8MB primary , , , , , lvm, , , , type=8e, , 3 65.8MB 140MB 74.0MB primary ext3 boot, , , , , , , , , type=83, , 4 140MB 16.2GB 16.0GB primary , , , , , lvm, , , , type=8e, , 2 16.2GB 100GB 83.9GB primary , , , , , lvm, , , , type=8e, , localhost:~ # hwinfo --partition|grep --context=15 /dev/sda 22: None 00.0: 11300 Partition [Created at block.412] UDI: /org/freedesktop/Hal/devices/volume_uuid_TE3G8Z_KcDm_dykS_QLET_a3Mc_oczu_ePnJHq Unique ID: bdUI.SE1wIdpsiiC Parent ID: 3OOL.fquimRS9gGB SysFS ID: /class/block/sda/sda1 Hardware Class: partition Model: "Partition" Device File: /dev/sda1 Device Files: /dev/sda1, /dev/disk/by-id/scsi-SATA_FUJITSU_MHV2100_NT23T5927VT5-part1, /dev/disk/by-id/ata-FUJITSU_MHV2100AH_NT23T5927VT5-part1, /dev/disk/by-path/pci-0000:00:1f.2-scsi-0:0:0:0-part1, /dev/disk/by-id/edd-int13_dev80-part1, /dev/disk/by-id/lvm2-pvuuid-TE3G8Z-KcDm-dykS-QLET-a3Mc-oczu-ePnJHq Config Status: cfg=no, avail=yes, need=no, active=unknown Attached to: #21 (Disk) 23: None 00.0: 11300 Partition [Created at block.412] UDI: /org/freedesktop/Hal/devices/volume_uuid_x1ZlLG_Z4Fg_BibW_EDQ1_D1rS_qP3L_X4Yv5V Unique ID: 2pkM.SE1wIdpsiiC Parent ID: 3OOL.fquimRS9gGB SysFS ID: /class/block/sda/sda2 Hardware Class: partition Model: "Partition" Device File: /dev/sda2 Device Files: /dev/sda2, /dev/disk/by-id/scsi-SATA_FUJITSU_MHV2100_NT23T5927VT5-part2, /dev/disk/by-id/ata-FUJITSU_MHV2100AH_NT23T5927VT5-part2, /dev/disk/by-path/pci-0000:00:1f.2-scsi-0:0:0:0-part2, /dev/disk/by-id/edd-int13_dev80-part2, /dev/disk/by-id/lvm2-pvuuid-x1ZlLG-Z4Fg-BibW-EDQ1-D1rS-qP3L-X4Yv5V Config Status: cfg=no, avail=yes, need=no, active=unknown Attached to: #21 (Disk) 24: None 00.0: 11300 Partition [Created at block.412] UDI: /org/freedesktop/Hal/devices/volume_uuid_36ec07ba_56a4_4d7c_abbe_5ca8558ff4b0 Unique ID: W__Q.SE1wIdpsiiC Parent ID: 3OOL.fquimRS9gGB SysFS ID: /class/block/sda/sda3 Hardware Class: partition Model: "Partition" Device File: /dev/sda3 Device Files: /dev/sda3, /dev/disk/by-id/scsi-SATA_FUJITSU_MHV2100_NT23T5927VT5-part3, /dev/disk/by-id/ata-FUJITSU_MHV2100AH_NT23T5927VT5-part3, /dev/disk/by-path/pci-0000:00:1f.2-scsi-0:0:0:0-part3, /dev/disk/by-uuid/36ec07ba-56a4-4d7c-abbe-5ca8558ff4b0, /dev/disk/by-id/edd-int13_dev80-part3 Config Status: cfg=no, avail=yes, need=no, active=unknown Attached to: #21 (Disk) 25: None 00.0: 11300 Partition [Created at block.412] UDI: /org/freedesktop/Hal/devices/volume_uuid_LGQB7E_mn5L_vsAr_Rhkq_ikaX_kADy_MV769t Unique ID: z9FV.SE1wIdpsiiC Parent ID: 3OOL.fquimRS9gGB SysFS ID: /class/block/sda/sda4 Hardware Class: partition Model: "Partition" Device File: /dev/sda4 Device Files: /dev/sda4, /dev/disk/by-id/scsi-SATA_FUJITSU_MHV2100_NT23T5927VT5-part4, /dev/disk/by-id/ata-FUJITSU_MHV2100AH_NT23T5927VT5-part4, /dev/disk/by-path/pci-0000:00:1f.2-scsi-0:0:0:0-part4, /dev/disk/by-id/edd-int13_dev80-part4, /dev/disk/by-id/lvm2-pvuuid-LGQB7E-mn5L-vsAr-Rhkq-ikaX-kADy-MV769t Config Status: cfg=no, avail=yes, need=no, active=unknown Attached to: #21 (Disk) 28: None 00.0: 11300 Partition [Created at block.412] UDI: /org/freedesktop/Hal/devices/volume_uuid_0c91ef48_4ab9_4df2_8dd4_9e685333353d Unique ID: h4pj.SE1wIdpsiiC Parent ID: fJYU.3z5PMRoMi+3 SysFS ID: /class/block/sdb/sdb1 Hardware Class: partition Model: "Partition" Device File: /dev/sdb1 Device Files: /dev/sdb1, /dev/disk/by-id/usb-Maxtor_Basics_Desktop_2HBECNVT-0:0-part1, /dev/disk/by-path/pci-0000:00:1d.7-usb-0:6:1.0-scsi-0:0:0:0-part1, /dev/disk/by-uuid/0c91ef48-4ab9-4df2-8dd4-9e685333353d Config Status: cfg=no, avail=yes, need=no, active=unknown Attached to: #27 (Disk) -- 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=543076
Libor Pecháček
http://bugzilla.novell.com/show_bug.cgi?id=543076
User hedgehogshiatus@gmail.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=543076#c1
--- Comment #1 from Hedge Hog
http://bugzilla.novell.com/show_bug.cgi?id=543076
User hedgehogshiatus@gmail.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=543076#c2
--- Comment #2 from Hedge Hog
sudo parted /dev/sda print root's password: Model: ATA WDC WD2500AAJS-7 (scsi) Disque /dev/sda : 250GB Taille des secteurs (logiques/physiques): 512B/512B Table de partition : msdos
Numéro Début Fin Taille Type Système de fichiers Fanions 1 1049kB 52,4GB 52,4GB primary ntfs démarrage, , , , , , , , , type=07, , 2 52,4GB 212GB 160GB primary ntfs , , , , , , , , , type=07, , 3 212GB 250GB 37,7GB extended , , , , , , lba, , , type=0f, , 5 212GB 214GB 2153MB logical linux-swap , , , , , , , , , type=82, , 6 214GB 250GB 35,5GB logical ext3 , , , , , , , , , type=83, , HTH -- 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=543076
http://bugzilla.novell.com/show_bug.cgi?id=543076#c3
--- Comment #3 from Patrick Smart
http://bugzilla.novell.com/show_bug.cgi?id=543076
http://bugzilla.novell.com/show_bug.cgi?id=543076#c4
--- Comment #4 from Patrick Smart
http://bugzilla.novell.com/show_bug.cgi?id=543076
http://bugzilla.novell.com/show_bug.cgi?id=543076#c6
Michal Marek
http://bugzilla.novell.com/show_bug.cgi?id=543076
http://bugzilla.novell.com/show_bug.cgi?id=543076#c7
Josef Reidinger
http://bugzilla.novell.com/show_bug.cgi?id=543076
http://bugzilla.novell.com/show_bug.cgi?id=543076#c9
Hedge Hog
http://bugzilla.novell.com/show_bug.cgi?id=543076
http://bugzilla.novell.com/show_bug.cgi?id=543076#c10
--- Comment #10 from Patrick Smart
http://bugzilla.novell.com/show_bug.cgi?id=543076
http://bugzilla.novell.com/show_bug.cgi?id=543076#c11
--- Comment #11 from Alex Savin
http://bugzilla.novell.com/show_bug.cgi?id=543076
http://bugzilla.novell.com/show_bug.cgi?id=543076#c12
Alex Savin
http://bugzilla.novell.com/show_bug.cgi?id=543076
http://bugzilla.novell.com/show_bug.cgi?id=543076#c13
Sanjay Kumar J
http://bugzilla.novell.com/show_bug.cgi?id=543076
http://bugzilla.novell.com/show_bug.cgi?id=543076#c14
Josef Reidinger
http://bugzilla.novell.com/show_bug.cgi?id=543076
http://bugzilla.novell.com/show_bug.cgi?id=543076#c15
--- Comment #15 from Josef Reidinger
Created an attachment (id=338129) --> (http://bugzilla.novell.com/attachment.cgi?id=338129) [details] result of save_y2logs /tmp/y2logs.tgz
result of save_y2logs /tmp/y2logs.tgz
I study your logs and found quite strange hardware detection. It looks like you have multipath device usual setup with LVM...but in next kernel update when problems start it detect multipath device??? and for that device it detect strange partitions. Please post output of command multipath -l -d -- 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=543076
http://bugzilla.novell.com/show_bug.cgi?id=543076#c16
--- Comment #16 from Josef Reidinger
Created an attachment (id=338137) --> (http://bugzilla.novell.com/attachment.cgi?id=338137) [details] other result of save_y2logs /tmp/y2logs.tgz
In case another one is useful.
I study your logs and problem in your case is that kernel change its kernel device name which could happen and for this case we introduce persistent device names ( via udev). So if you upgrade from older version or install freshly and explicit set mount by kernel device it is written in device map and has problem id kernel switch device name. Sorry in this case I cannot help you. -- 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=543076
http://bugzilla.novell.com/show_bug.cgi?id=543076#c17
Josef Reidinger
http://bugzilla.novell.com/show_bug.cgi?id=543076
http://bugzilla.novell.com/show_bug.cgi?id=543076#c18
--- Comment #18 from Sanjay Kumar J
http://bugzilla.novell.com/show_bug.cgi?id=543076
http://bugzilla.novell.com/show_bug.cgi?id=543076#c19
--- Comment #19 from Andreas Kilgus
http://bugzilla.novell.com/show_bug.cgi?id=543076
http://bugzilla.novell.com/show_bug.cgi?id=543076#c20
--- Comment #20 from Andreas Kilgus
http://bugzilla.novell.com/show_bug.cgi?id=543076
http://bugzilla.novell.com/show_bug.cgi?id=543076#c21
Andreas Kilgus
http://bugzilla.novell.com/show_bug.cgi?id=543076
http://bugzilla.novell.com/show_bug.cgi?id=543076#c22
Josef Reidinger
http://bugzilla.novell.com/show_bug.cgi?id=543076
http://bugzilla.novell.com/show_bug.cgi?id=543076#c23
--- Comment #23 from Andreas Kilgus
http://bugzilla.novell.com/show_bug.cgi?id=543076
http://bugzilla.novell.com/show_bug.cgi?id=543076#c24
Josef Reidinger
Any ideas or patches I can test in the wild?
I check logs and it looks like I already fixing such problem. What version of perl-Bootloader do you have? 0.5.12 (it contains fix for issue)?? -- 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=543076
http://bugzilla.novell.com/show_bug.cgi?id=543076#c25
--- Comment #25 from Andreas Kilgus
http://bugzilla.novell.com/show_bug.cgi?id=543076
http://bugzilla.novell.com/show_bug.cgi?id=543076#c26
--- Comment #26 from Andreas Kilgus
http://bugzilla.novell.com/show_bug.cgi?id=543076
http://bugzilla.novell.com/show_bug.cgi?id=543076#c27
--- Comment #27 from Andreas Kilgus
http://bugzilla.novell.com/show_bug.cgi?id=543076
http://bugzilla.novell.com/show_bug.cgi?id=543076#c28
Josef Reidinger
With perl-Bootloader 0.5.12 the "No partition found for [...]" messages have vanished, running mkinitrd shows the usual output only - that's very gratifying. :)
Since I do not know what kind of changes you applied to perl-Bootloader: Do I have to take care of or inspect something that might have gone wrong silently to assure that the machine will reboot successfully?
Thanks to confirm fix. With fix and without any warning everything works as expected and you do not need worry. Without fix it depends how many disc you have. If you have only one or boot from first disc (from BIOS perspective), then fallback works good. Of course if you check menu.lst after install of new kernel it ensure that everything is OK (in some caseit can cause bad root() argument in 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=543076
http://bugzilla.novell.com/show_bug.cgi?id=543076#c29
--- Comment #29 from Patrick Smart
http://bugzilla.novell.com/show_bug.cgi?id=543076
http://bugzilla.novell.com/show_bug.cgi?id=543076#c30
--- Comment #30 from Andreas Kilgus
(In reply to comment #27)
Since I do not know what kind of changes you applied to perl-Bootloader: Do I have to take care of or inspect something that might have gone wrong silently to assure that the machine will reboot successfully?
Thanks to confirm fix. With fix and without any warning everything works as expected and you do not need worry.
The machine booted - there was some trouble with the network device, but grub et al worked fine. Meanwhile I upgraded my notebook from openSUSE 11.2 to 11.3 online - and here we go again: Several "GrubDev2UnixDev: No partition found [...]" messages appear when running mkinitrd. perl-Bootloader-0.5.12-4.1.i586 (from YaST:/Head) kernel-desktop-2.6.34-12.3.i586 grub-0.97-171.1.i586 I let "yast2 bootloader" already suggest a new setup and cleaned menu.lst manually, too, so no double entries, nothing that appears to be faulty. Which files / information do you want me to provide? -- 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=543076
http://bugzilla.novell.com/show_bug.cgi?id=543076#c31
--- Comment #31 from Josef Reidinger
I have installed 11.3 and I think I remember seeing all the warnings are upgrade time. Now I ran mkinitrd manually and it just went smoothly. Does that make sense?
Yes, unless kernel pre require new version of perl-bootloader, then old one can be used during 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=543076
http://bugzilla.novell.com/show_bug.cgi?id=543076#c32
Josef Reidinger
(In reply to comment #28)
(In reply to comment #27)
Since I do not know what kind of changes you applied to perl-Bootloader: Do I have to take care of or inspect something that might have gone wrong silently to assure that the machine will reboot successfully?
Thanks to confirm fix. With fix and without any warning everything works as expected and you do not need worry.
The machine booted - there was some trouble with the network device, but grub et al worked fine.
Meanwhile I upgraded my notebook from openSUSE 11.2 to 11.3 online - and here we go again: Several "GrubDev2UnixDev: No partition found [...]" messages appear when running mkinitrd.
perl-Bootloader-0.5.12-4.1.i586 (from YaST:/Head) kernel-desktop-2.6.34-12.3.i586 grub-0.97-171.1.i586
I let "yast2 bootloader" already suggest a new setup and cleaned menu.lst manually, too, so no double entries, nothing that appears to be faulty.
Which files / information do you want me to provide?
OK, please provide yast logs. It shows whole upgrade. http://en.opensuse.org/openSUSE:Bugreport_YaST#I_reported_a_YaST2_bug.2C_and... -- 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=543076
http://bugzilla.novell.com/show_bug.cgi?id=543076#c33
--- Comment #33 from Andreas Kilgus
http://bugzilla.novell.com/show_bug.cgi?id=543076
http://bugzilla.novell.com/show_bug.cgi?id=543076#c34
--- Comment #34 from Josef Reidinger
Created an attachment (id=379157) --> (http://bugzilla.novell.com/attachment.cgi?id=379157) [details] Upgrade-Log et al
Ok, here's the wanted tgz.
OK, thanks. I see in history that you were bad device map, which contain parition instead disc. But last upgrade is correct and problem is in udev, which doesn't report anything. Could you please try to run command `udevadm info -q all -n /dev/sda` ? ( I already see this issue in one case, but user doesn't communicate ) -- 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=543076
http://bugzilla.novell.com/show_bug.cgi?id=543076#c35
--- Comment #35 from Andreas Kilgus
Could you please try to run command `udevadm info -q all -n /dev/sda` ? ( I already see this issue in one case, but user doesn't communicate )
Output (typed manually due to temporary lack of network, I hope without mistakes): P: /devices/pci0000:00/0000:00:1f.1/host0/target0:0:0/0:0:0:0/block/sda E: UDEV_LOG=3 E: DEVPATH=/devices/pci0000:00/0000:00:1f.1/host0/target0:0:0/0:0:0:0/block/sda E: SUBSYSTEM=block E: MAJOR=8 E: MINOR=0 E: DEVNAME=sda E: DEVTYPE=disk -- 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=543076
http://bugzilla.novell.com/show_bug.cgi?id=543076#c36
Josef Reidinger
http://bugzilla.novell.com/show_bug.cgi?id=543076
http://bugzilla.novell.com/show_bug.cgi?id=543076#c37
Kay Sievers
http://bugzilla.novell.com/show_bug.cgi?id=543076
http://bugzilla.novell.com/show_bug.cgi?id=543076#c38
Josef Reidinger
It's probably the same as the other issues: a new udev version installed on the running system can not read the database of the old udev version, which has created the database.
There is currently no support for such setups from the udev side. Updating udev to a different version might result in loss of some database entries. Such changes don't happen often, but other requirements forced a change in the database format between udev from 11.2 and 11.3. That's usually not a problem for other tools.
Isn't it just the same ordering issue, we've seen already, between updating udev and the bootloader at the same time?
So if I prerequire new version of new udev can I avoid such problem? -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=543076
http://bugzilla.novell.com/show_bug.cgi?id=543076#c39
Kay Sievers
Isn't it just the same ordering issue, we've seen already, between updating udev and the bootloader at the same time?
So if I prerequire new version of new udev can I avoid such problem?
What means 'prerequire' in that context? The problem is that the 11.3 udev can not read parts of the still running 11.2 udev database. We need to make sure, that during an upgrade, the bootloader is updated before udev, because the udev update renders parts of the information you seem to need inaccessible. -- 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=543076
http://bugzilla.novell.com/show_bug.cgi?id=543076#c40
Josef Reidinger
http://bugzilla.novell.com/show_bug.cgi?id=543076
http://bugzilla.novell.com/show_bug.cgi?id=543076#c41
Michal Marek
http://bugzilla.novell.com/show_bug.cgi?id=543076
http://bugzilla.novell.com/show_bug.cgi?id=543076#c42
--- Comment #42 from Andreas Kilgus
http://bugzilla.novell.com/show_bug.cgi?id=543076
http://bugzilla.novell.com/show_bug.cgi?id=543076#c43
--- Comment #43 from Felix Miata
IMO we should stop pretending that we support zypper dup to a new openSUSE version.
How else would you that Factory get updated from milestone to milestone? Maybe zypper was too grand a scheme for available resources and apt or yum should have been used instead? IMO any udev version that cannot read an older udev version's DB is a broken udev unsuited for a GM release. -- 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=543076
http://bugzilla.novell.com/show_bug.cgi?id=543076#c44
--- Comment #44 from Andreas Kilgus
Sorry, I have no idea how to ensure this from the kernel package side. IMO we should stop pretending that we support zypper dup to a new openSUSE version.
My personal statistic (three machines with and without raid, complex and minimalistic setups) isn't that bad: 10.3 -> 11.0 -> 11.1 -> 11.2 worked flawlessly on two machines, one of them now in trouble at 11.2 -> 11.3, the third one tumbled at 11.1 -> 11.2 though its upgrades 10.3 -> 11.0 -> 11.1 were no big deal. So "zypper dup" is not perfect, but far from being completely dysfunctional, too. -- 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=543076
http://bugzilla.novell.com/show_bug.cgi?id=543076#c45
--- Comment #45 from Alex Savin
Sorry, I have no idea how to ensure this from the kernel package side. IMO we should stop pretending that we support zypper dup to a new openSUSE version.
upgrade openSUSE - its must have feature (In reply to comment #43)
(In reply to comment #41) IMO any udev version that cannot read an older udev version's DB is a broken udev unsuited for a GM release. +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=543076
http://bugzilla.novell.com/show_bug.cgi?id=543076#c46
--- Comment #46 from Andreas Kilgus
After having called "update-bootloader --refresh" just once mkinitrd completes without throwing "No partition found [...]" messages.
Cosmetic only? Side effects? Or a possible step towards a solution?
Hm, developers (including myself) often complain that bug reporters don't provide necessary infos, even on request. Developers not reacting to bug reporters willing to provide infos don't encourage either ... ;-) Therefore: Any logs you're interested in? Something I'm proposed to try to enlighten why "update-bootloader --refresh" killed the warnings? -- 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=543076
http://bugzilla.novell.com/show_bug.cgi?id=543076#c47
--- Comment #47 from Josef Reidinger
(In reply to comment #42)
After having called "update-bootloader --refresh" just once mkinitrd completes without throwing "No partition found [...]" messages.
Cosmetic only? Side effects? Or a possible step towards a solution?
Hm, developers (including myself) often complain that bug reporters don't provide necessary infos, even on request. Developers not reacting to bug reporters willing to provide infos don't encourage either ... ;-)
Therefore: Any logs you're interested in? Something I'm proposed to try to enlighten why "update-bootloader --refresh" killed the warnings?
Hi, problem is that we know where is problem, but don't have any idea how to fix it, so now we try to find possible solutions. -- 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=543076
https://bugzilla.novell.com/show_bug.cgi?id=543076#c48
Josef Reidinger
https://bugzilla.novell.com/show_bug.cgi?id=543076
https://bugzilla.novell.com/show_bug.cgi?id=543076#c49
Stephan Kulow
https://bugzilla.novell.com/show_bug.cgi?id=543076
https://bugzilla.novell.com/show_bug.cgi?id=543076#c50
Josef Reidinger
well, can you skip the action if you recognize the situation? If so, I would suggest to do so and have udev %post call update-bootloader. But perhaps I misunderstood the problem.
No, problem occur if udev installed before new kernel. In this case udev stop returning new devices and when new kernel is installed it cannot properly add new entry to bootloader entry. see comment #39 -- 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=543076
https://bugzilla.novell.com/show_bug.cgi?id=543076#c51
Stephan Kulow
https://bugzilla.novell.com/show_bug.cgi?id=543076
https://bugzilla.novell.com/show_bug.cgi?id=543076#c52
Josef Reidinger
https://bugzilla.novell.com/show_bug.cgi?id=543076
https://bugzilla.novell.com/show_bug.cgi?id=543076#c53
--- Comment #53 from Kay Sievers
https://bugzilla.novell.com/show_bug.cgi?id=543076
https://bugzilla.novell.com/show_bug.cgi?id=543076#c
Kay Sievers
https://bugzilla.novell.com/show_bug.cgi?id=543076
https://bugzilla.novell.com/show_bug.cgi?id=543076#c54
Kay Sievers
https://bugzilla.novell.com/show_bug.cgi?id=543076
https://bugzilla.novell.com/show_bug.cgi?id=543076#c55
Kay Sievers
https://bugzilla.novell.com/show_bug.cgi?id=543076
https://bugzilla.novell.com/show_bug.cgi?id=543076#c56
Christian Boltz
Closing, as it seems, we can't work around this. We'll need to try to avoid such issues in the future.
I can imagine two possible workarounds - at least I think so ;-) a) easy: add Requires: kernel >= $kernel_version_in_11.3 to the udev package and release it as update for 11.3. This should change the install order in zypper (needs to be tested for circular dependencies, but in theory it should work). b) slightly more complex method, but should work for sure: part 1: let the old package write the current boot partition to a tempfile in the %preun script. Release this package as update for 11.2. (In reply to comment #34)
[...] problem is in udev, which doesn't report anything.
Thats part 2 - release a new udev package for 11.3 that reads the tempfile generated above as a fallback. Both methods will work for people that include the 11.3 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=543076
https://bugzilla.novell.com/show_bug.cgi?id=543076#c57
--- Comment #57 from Kay Sievers
https://bugzilla.novell.com/show_bug.cgi?id=543076
https://bugzilla.novell.com/show_bug.cgi?id=543076#c58
Kay Sievers
participants (1)
-
bugzilla_noreply@novell.com