[Bug 598193] New: udev deletes device nodes
http://bugzilla.novell.com/show_bug.cgi?id=598193 http://bugzilla.novell.com/show_bug.cgi?id=598193#c0 Summary: udev deletes device nodes Classification: openSUSE Product: openSUSE 11.3 Version: Milestone 5 Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: kasievers@novell.com ReportedBy: aschnell@novell.com QAContact: qa@suse.de Found By: Development Blocker: --- udevd deletes the devices /dev/dm-X for LVM logical volumes during the installation from the GNOME Live CD. The delete is not logged with udevadm monitor but can be observed with audit. See attached 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=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c1
--- Comment #1 from Arvin Schnell
http://bugzilla.novell.com/show_bug.cgi?id=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c2
--- Comment #2 from Arvin Schnell
http://bugzilla.novell.com/show_bug.cgi?id=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c3
--- Comment #3 from Arvin Schnell
http://bugzilla.novell.com/show_bug.cgi?id=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c4
--- Comment #4 from Kay Sievers
http://bugzilla.novell.com/show_bug.cgi?id=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c5
Kay Sievers
http://bugzilla.novell.com/show_bug.cgi?id=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c6
Arvin Schnell
http://bugzilla.novell.com/show_bug.cgi?id=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c7
roeland jansen
http://bugzilla.novell.com/show_bug.cgi?id=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c8
Xinwei Hu
http://bugzilla.novell.com/show_bug.cgi?id=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c9
Jaroslaw Zachwieja
http://bugzilla.novell.com/show_bug.cgi?id=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c10
Israel smilanski
http://bugzilla.novell.com/show_bug.cgi?id=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c11
--- Comment #11 from Jaroslaw Zachwieja
clean instalation failes with "system error code - 3030".
This is because once the LV is created udev deletes it. So we have: /dev/system/tmp -> /dev/mapper/system-tmp which is all dandy, but then when you ls /dev/mapper all you get is a lousy 'control' and no system-tmp. -- 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=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c12
--- Comment #12 from roeland jansen
It's happening as early as in installation, therefore it's rather difficult to test it, this is stage1, remember we can't edit anything.
I can try and see if they are made immutable for the install
I can confirm the problem happening in Milestone 6 (well, almost 7 as of today) still. Please treat it as critical, I agree with Kay, udev should never ever delete any devmapper nodes, it's just criminal.
Indeed crimimal :-( I think M7 is imminent; will it be fixed on time? -- 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=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c13
--- Comment #13 from roeland jansen
http://bugzilla.novell.com/show_bug.cgi?id=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c14
--- Comment #14 from Jaroslaw Zachwieja
I think M7 is imminent; will it be fixed on time?
M7 is being uploaded to the mirrors right now. We've passed the deadline. We're now aiming for Jun 17 RC1. -- 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=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c15
Jaroslaw Zachwieja
http://bugzilla.novell.com/show_bug.cgi?id=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c16
--- Comment #16 from Israel smilanski
http://bugzilla.novell.com/show_bug.cgi?id=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c17
--- Comment #17 from Xinwei Hu
http://bugzilla.novell.com/show_bug.cgi?id=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c18
--- Comment #18 from Israel smilanski
http://bugzilla.novell.com/show_bug.cgi?id=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c19
--- Comment #19 from Xinwei Hu
I have just updated all new packages. The system I have updated is 11.3 (ms 7) root is on sda3 and home on dm-1.
unfortunately there is no improvment in the boot process. The relevant lines from dmesg are: [ 11.488051] device-mapper: uevent: version 1.0.3 [ 11.497874] device-mapper: ioctl: 4.17.0-ioctl (2010-03-05) initialised: dm-devel@redhat.com [ 11.595248] usbcore: registered new interface driver snd-usb-audio [ 11.680729] Adding 5245184k swap on /dev/sda6. Priority:-1 extents:1 across:5245184k [ 79.331174] device-mapper: ioctl: device doesn't appear to be in the dev hash table. [ 79.830294] loop: module loaded
note the large delay between "Adding 5245184k swap" and "device-mapper: ioctl: device doesn't appear" (~78 seconds). all this time the message is "waiting for udev to settle".
Have you rerun mkinitrd after updating ? -- 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=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c20
--- Comment #20 from Israel smilanski
http://bugzilla.novell.com/show_bug.cgi?id=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c21
--- Comment #21 from Israel smilanski
http://bugzilla.novell.com/show_bug.cgi?id=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c22
--- Comment #22 from Xinwei Hu
I have run mkinitrd
mkinitrd
Kernel image: /boot/vmlinuz-2.6.34-8-desktop Initrd image: /boot/initrd-2.6.34-8-desktop WARNING: All config files need .conf: /etc/modprobe.d/options, it will be ignored in a future release. Root device: /dev/disk/by-id/ata-ST3160023AS_3JS0MZLZ-part4 (/dev/sda4) (mounted on / as ext4) Resume device: /dev/disk/by-id/ata-ST3160023AS_3JS0MZLZ-part6 (/dev/sda6) modprobe: Module amd74xx not found. WARNING: no dependencies for kernel module 'amd74xx' found. modprobe: Module ide_pci_generic not found. WARNING: no dependencies for kernel module 'ide_pci_generic' found. Kernel Modules: thermal_sys thermal scsi_mod libata pata_amd ahci ata_generic processor fan pata_jmicron pata_marvell edd crc16 jbd2 ext4 pata_acpi sata_mv pdc_adma sata_sil sata_nv pata_atiixp pata_sil680 pata_netcell pata_it821x pata_cmd640 pata_atp867x sata_qstor pata_sis sata_sis pata_cs5520 pata_hpt3x3 sata_uli pata_mpiix pata_ns87410 sata_inic162x sata_svw pata_it8213 pata_hpt37x pata_ninja32 pata_sl82c105 pata_opti pata_via pata_artop pata_rz1000 pata_cypress pata_triflex pata_efar pata_ns87415 pata_serverworks pata_optidma pata_sch pata_sc1200 sata_promise pata_rdc pata_ali pata_radisys sata_via pata_pdc202xx_old sata_sx4 pata_pdc2027x pcmcia_core pcmcia pata_pcmcia ata_piix sata_sil24 pata_piccolo pata_oldpiix pata_hpt366 pata_cmd64x sata_vsc pata_cs5530 pata_hpt3x2n sd_mod Features: block usb resume.userspace resume.kernel Bootsplash: openSUSE (1280x1024) 46356 blocks and rebooted. exactly the same as before. the message in boot second 8 is "udevdm settle... failed."
Would you run mkinitrd with '-f dm' ? Which enables the dm feature. Also, would you let me know the output of "rpm -q --changelog device-mapper | head" ? It should be something like: * Fri May 21 2010 xwhu@novell.com - Fix mkinitrd-devmapper to use udev rules for device mapper 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=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c23
--- Comment #23 from Israel smilanski
http://bugzilla.novell.com/show_bug.cgi?id=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c24
Per Jessen
http://bugzilla.novell.com/show_bug.cgi?id=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c25
Arvin Schnell
http://bugzilla.novell.com/show_bug.cgi?id=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c26
--- Comment #26 from Xinwei Hu
no progress yet. and as you can see, I was unable to locate the new package, even in your own directories. can you send a link? You can use http://software.opensuse.org/search to search device-mapper and lvm2 package from Base:System/openSUSE_Factory .
-- 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=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c27
--- Comment #27 from Israel smilanski
http://bugzilla.novell.com/show_bug.cgi?id=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c28
--- Comment #28 from Xinwei Hu
ok. I have located device-mapper-1.02.42-24.1.x86_64.rpm and lvm2-2.02.58-23.1.x86_64.rpm and installed them. then: aziz:~ # rpm -q --changelog device-mapper | head * Fri May 21 2010 xwhu@novell.com - Fix mkinitrd-devmapper to use udev rules for device mapper
* Mon Apr 26 2010 ro@suse.de - fix pkgconfig file for device mapper
* Sat Apr 03 2010 xwhu@novell.com - Upgrade to device-mapper 1.02. - Add libdevmapper functions to support synchronisation with udev - Check udev is running when processing cookies and retain state paziz:~ # rpm -q --changelog lvm2 | head * Fri May 21 2010 xwhu@novell.com - Fix mkinitrd-lvm2 to use udev rules for lvm2
* Mon Apr 26 2010 ro@suse.de - fix lvm2-clvm specfile so that patches apply
* Sat Apr 03 2010 xwhu@novell.com - Upgrade to LVM2 2.02.58 - Rename liblvm.so to liblvm2app.so - Introduce lvconvert --use_policies paziz:~ # mkinitrd -f dm
Kernel image: /boot/vmlinuz-2.6.34-8-desktop Initrd image: /boot/initrd-2.6.34-8-desktop WARNING: All config files need .conf: /etc/modprobe.d/options, it will be ignored in a future release. Root device: /dev/disk/by-id/ata-ST3160023AS_3JS0MZLZ-part4 (/dev/sda4) (mounted on / as ext4) Resume device: /dev/disk/by-id/ata-ST3160023AS_3JS0MZLZ-part6 (/dev/sda6) modprobe: Module amd74xx not found. WARNING: no dependencies for kernel module 'amd74xx' found. modprobe: Module ide_pci_generic not found. WARNING: no dependencies for kernel module 'ide_pci_generic' found. Kernel Modules: thermal_sys thermal scsi_mod libata pata_amd ahci ata_generic processor fan pata_jmicron pata_marvell edd dm-mod dm-snapshot crc16 jbd2 ext4 pata_acpi sata_mv pdc_adma sata_sil sata_nv pata_atiixp pata_sil680 pata_netcell pata_it821x pata_cmd640 pata_atp867x sata_qstor pata_sis sata_sis pata_cs5520 pata_hpt3x3 sata_uli pata_mpiix pata_ns87410 sata_inic162x sata_svw pata_it8213 pata_hpt37x pata_ninja32 pata_sl82c105 pata_opti pata_via pata_artop pata_rz1000 pata_cypress pata_triflex pata_efar pata_ns87415 pata_serverworks pata_optidma pata_sch pata_sc1200 sata_promise pata_rdc pata_ali pata_radisys sata_via pata_pdc202xx_old sata_sx4 pata_pdc2027x pcmcia_core pcmcia pata_pcmcia ata_piix sata_sil24 pata_piccolo pata_oldpiix pata_hpt366 pata_cmd64x sata_vsc pata_cs5530 pata_hpt3x2n sd_mod Features: dm block usb resume.userspace resume.kernel Bootsplash: openSUSE (1280x1024) 47010 blocks however, no progress has been made yet.
Would you attach your initrd file here ? 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=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c29
--- Comment #29 from Israel smilanski
http://bugzilla.novell.com/show_bug.cgi?id=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c30
--- Comment #30 from Israel smilanski
http://bugzilla.novell.com/show_bug.cgi?id=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c31
Xinwei Hu
*** Bug 607869 has been marked as a duplicate of this bug. ***
Hi Arvine, I've tested the update package with GNOME Live CD M7, and it installed fine with LVM based schema. However, I still don't understand why you writing "add" into "/sys/block/dm-N/uevent". When "/sys/block/dm-N/uevent" is writable, it means dm-N is there already. It expects a writing of "change" instead I think. -- 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=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c32
--- Comment #32 from Xinwei Hu
I have tested openSUSE-KDE-LiveCD-i686-Build0625-Media.iso on the same (the above) computer. lbm2-2.02.58-2.1 device-mapper-1.02.42-2.1-x86 No dm partitions had been created while booting. I created them by dmraid -ay. installation failed with 3030 error.
This suppose to be a problem of boot.dmraid. I'm looking for an testing environment for this now. FYI. -- 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=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c33
--- Comment #33 from Per Jessen
http://bugzilla.novell.com/show_bug.cgi?id=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c34
Kay Sievers
http://bugzilla.novell.com/show_bug.cgi?id=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c35
Jaroslaw Zachwieja
http://bugzilla.novell.com/show_bug.cgi?id=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c36
Xinwei Hu
http://bugzilla.novell.com/show_bug.cgi?id=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c
Jaroslaw Zachwieja
http://bugzilla.novell.com/show_bug.cgi?id=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c37
Martin Christeson
http://bugzilla.novell.com/show_bug.cgi?id=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c38
--- Comment #38 from Israel smilanski
http://bugzilla.novell.com/show_bug.cgi?id=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c39
--- Comment #39 from Jaroslaw Zachwieja
http://bugzilla.novell.com/show_bug.cgi?id=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c40
--- Comment #40 from Per Jessen
http://bugzilla.novell.com/show_bug.cgi?id=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c41
--- Comment #41 from Cristian Rodríguez
http://bugzilla.novell.com/show_bug.cgi?id=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c42
Jaroslaw Zachwieja
http://bugzilla.novell.com/show_bug.cgi?id=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c43
--- Comment #43 from Israel smilanski
http://bugzilla.novell.com/show_bug.cgi?id=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c44
Cristian Rodríguez
http://bugzilla.novell.com/show_bug.cgi?id=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c45
--- Comment #45 from Xinwei Hu
Boot this iso
http://download.opensuse.org/factory/iso/openSUSE-NET-x86_64-Build0653-Media...
left everything by default until the partition setup screen.
select LVM setup, format the root partition as btrfs and left boot as is.
in the package selection menu, select "Minimal text only" from the "other" menu.
I just tested with Build0654, and it works fine. Haven't tried 0653 yet. -- 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=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c46
--- Comment #46 from Israel smilanski
http://bugzilla.novell.com/show_bug.cgi?id=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c47
--- Comment #47 from Jaroslaw Zachwieja
http://bugzilla.novell.com/show_bug.cgi?id=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c48
Boris Manojlovic
http://bugzilla.novell.com/show_bug.cgi?id=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c49
--- Comment #49 from Per Jessen
http://bugzilla.novell.com/show_bug.cgi?id=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c50
--- Comment #50 from Jaroslaw Zachwieja
http://bugzilla.novell.com/show_bug.cgi?id=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c
Jaroslaw Zachwieja
http://bugzilla.novell.com/show_bug.cgi?id=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c51
Arvin Schnell
http://bugzilla.novell.com/show_bug.cgi?id=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c
Stephan Kulow
http://bugzilla.novell.com/show_bug.cgi?id=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c
Arvin Schnell
http://bugzilla.novell.com/show_bug.cgi?id=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c
Arvin Schnell
http://bugzilla.novell.com/show_bug.cgi?id=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c52
--- Comment #52 from Xinwei Hu
The error 3030 is issued by libstorage (which YaST uses for partitioning) and simply means that the device node does not exist. Libstorage tests the existence of device nodes before many operations since synchronisation with udev is required.
I can also confirm that normal (no Live CD, no AutoYaST) installation with LVM fails with todays build 0673.
Hi all, May you add some reference to the build you are using, and the URL I can download and verify with ? 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=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c53
--- Comment #53 from Jaroslaw Zachwieja
http://bugzilla.novell.com/show_bug.cgi?id=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c54
Thomas Langkamp
http://bugzilla.novell.com/show_bug.cgi?id=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c55
--- Comment #55 from Xinwei Hu
Hi all,
I think I´ve got a related bug - made fresh install of M7 on and SSD (ata2; zypper dup then to RC1, all worked smooth) - but they do not recognize that two other HDDs (ata5 and 6) of my system are bundled as raid - yasts partition-manager only sees the two additional hdds, not the raid-partitions. With 11.2 that worked fine. So I would also not be able to install on that raid (it was also not recognized during installation of M7). I hope this information is useful for you. If someone gives me a hint what to hack into the command line I can give additional informations for my system....
Would you run "dmraid -ay" manually there ? It sounds software raid is not built automatically. -- 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=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c56
--- Comment #56 from Thomas Langkamp
http://bugzilla.novell.com/show_bug.cgi?id=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c57
--- Comment #57 from Thomas Langkamp
http://bugzilla.novell.com/show_bug.cgi?id=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c58
--- Comment #58 from Xinwei Hu
http://bugzilla.novell.com/show_bug.cgi?id=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c
Xinwei Hu
http://bugzilla.novell.com/show_bug.cgi?id=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c59
Arvin Schnell
http://bugzilla.novell.com/show_bug.cgi?id=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c60
Kay Sievers
http://bugzilla.novell.com/show_bug.cgi?id=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c61
Arvin Schnell
http://bugzilla.novell.com/show_bug.cgi?id=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c62
--- Comment #62 from Mario Guzman
http://bugzilla.novell.com/show_bug.cgi?id=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c63
Andreas Jaeger
http://bugzilla.novell.com/show_bug.cgi?id=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c64
--- Comment #64 from Kay Sievers
Kay, what do you suggest as short-time workaround for 11.3?
Unfortunately, I can not suggest any straight-forward workaround. I guess, the current device-mapper/lvm code we currently ship can not work as expected, it is making assumptions about uevents which are not met on common systems (see the bugs at the end).
We have RC2 next week and your comment #60 does not seem to answer #59 (at least in my understanding).
I tried to say: "the label,uuid-symlinks are usually _not_ updated for dm devices when filesystem metadata is changed. Device-mapper devices are excluded from udev's logic, because they don't behave as expected" and "using artificial events for device-mapper devices, like libstorage does, will break the current device-mapper/lvm assumptions" Which unfortunately means, with the current code, we have no simple solution for the problem. It's all work-in-progress upstream, and the lvm git repo has added a few workarounds (which we don't ship) for the most common problems: http://sourceware.org/git/?p=lvm2.git;a=blob;f=udev/10-dm.rules.in;h=0db8809... But all this is likely not well tested, and might also not fully work as expected. I guess we have only two options: to update to the current dm/lvm code or go back to the old version which does not plug into udev. But I really don't know enough about device-mapper/lvm to make a decision here. The latest comments in the corresponding Red Hat bugs seem to state that the issues are addressed: https://bugzilla.redhat.com/show_bug.cgi?id=561425 https://bugzilla.redhat.com/show_bug.cgi?id=577798 -- 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=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c65
--- Comment #65 from Martin Wilck
http://bugzilla.novell.com/show_bug.cgi?id=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c66
--- Comment #66 from Kay Sievers
Why not the solution proposed in comment #59?
Because it's only one source of the events the current dm tools don't handle properly, and we have more: packages trying to apply a new config, kernel module updates, users running 'trigger', udisks installing 'watch' events, ... -- 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=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c67
--- Comment #67 from Xinwei Hu
(In reply to comment #65)
Why not the solution proposed in comment #59?
Because it's only one source of the events the current dm tools don't handle properly, and we have more: packages trying to apply a new config, kernel module updates, users running 'trigger', udisks installing 'watch' events, ...
Let's stick with this bug first. This bug is about that rules for device-mapper doesn't work with artificial 'add' event. This is still true with the latest update, and I think it'll be true in foreseeable future. So, I think the suggestion in comment#59 is the right step to go. Then, on the other hand, I agree with Kay that the udev rules for device-mapper are broken with artificial uevents. Default assumption of source of the uevent is one thing, and avoiding racing is another. However, these issues will not affect installation process as far as I can see ... just my .2c. -- 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=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c68
--- Comment #68 from Kay Sievers
This bug is about that rules for device-mapper doesn't work with artificial 'add' event.
It's the case for every event including 'change', not only 'add'.
This is still true with the latest update, and I think it'll be true in foreseeable future.
This sounds different: https://bugzilla.redhat.com/show_bug.cgi?id=561425#c16
So, I think the suggestion in comment#59 is the right step to go.
It might only avoid one of a bunch of cases, where this will go wrong and lead to the removal of dm/lvm symlinks? -- 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=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c69
Jaroslaw Zachwieja
I guess we have only two options: to update to the current dm/lvm code or go back to the old version which does not plug into udev. But I really don't know enough about device-mapper/lvm to make a decision here.
Looking at the available time frames, may I humbly suggest to go with the rollback? (also, cheekily bumping importance as it's a SHIP_STOPPER) -- 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=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c70
--- Comment #70 from Bruno Friedmann
http://bugzilla.novell.com/show_bug.cgi?id=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c71
Xinwei Hu
(In reply to comment #67)
This bug is about that rules for device-mapper doesn't work with artificial 'add' event.
It's the case for every event including 'change', not only 'add'.
This is still true with the latest update, and I think it'll be true in foreseeable future.
This sounds different: https://bugzilla.redhat.com/show_bug.cgi?id=561425#c16
No, it's not. At least not in the git repo yet.
So, I think the suggestion in comment#59 is the right step to go.
It might only avoid one of a bunch of cases, where this will go wrong and lead to the removal of dm/lvm symlinks?
Well, I tried again to submit an update of lvm2 into Base:System. The new udev rule works like this: -> If 'add' triggered by libdevmapper, /dev/dm-* will not be removed, but all symlinks will be removed -> If 'change' triggered by libdevmapper, /dev/dm-* and all symlinks will be created. -> If 'add|change' triggered by other source, /dev/dm-* will not be removed, all symlinks will be created according to the info from IMPORT{db}. I'd like to know if this is OK from udev's point of view. If it's OK, I'll try to make this upstream then. 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=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c72
Kay Sievers
This is still true with the latest update, and I think it'll be true in foreseeable future.
This sounds different: https://bugzilla.redhat.com/show_bug.cgi?id=561425#c16
No, it's not. At least not in the git repo yet.
Sure, it's in the repo. All the IMPORT{db} stuff which is not in our package.
-> If 'add|change' triggered by other source, /dev/dm-* will not be removed,
Primary device nodes will never be removed again, because recent udev versions, like the one we ship, refuses to do that, and ignores all the instructions from the device-mapper rules.
all symlinks will be created according to the info from IMPORT{db}. I'd like to know if this is OK from udev's point of view.
The stuff in the current lvm git repo is expected to solve some of the problems. It is surely 'ok' from udev point of view, but I can tell if that is sufficient to solve the current problems, or the right way to handle that from device-mapper's view. I guess it's all still work-in-progress at the device-mapper side at the moment.
If it's OK, I'll try to make this upstream then.
With 'upstream' you mean our Factory package? -- 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=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c73
--- Comment #73 from Xinwei Hu
(In reply to commen
This is still true with the latest update, and I think it'll be true in foreseeable future.
This sounds different: https://bugzilla.redhat.com/show_bug.cgi?id=561425#c16
No, it's not. At least not in the git repo yet.
Sure, it's in the repo. All the IMPORT{db} stuff which is not in our package.
Not sure what's IMPORT you are referring to. The latest update to 10-dm.rules in upstream is made about 2 month ago. And that doesn't help to this bug.
-> If 'add|change' triggered by other source, /dev/dm-* will not be removed,
Primary device nodes will never be removed again, because recent udev versions, like the one we ship, refuses to do that, and ignores all the instructions from the device-mapper rules.
all symlinks will be created according to the info from IMPORT{db}. I'd like to know if this is OK from udev's point of view.
The stuff in the current lvm git repo is expected to solve some of the problems. It is surely 'ok' from udev point of view, but I can tell if that is sufficient to solve the current problems, or the right way to handle that from device-mapper's view. I guess it's all still work-in-progress at the device-mapper side at the moment.
If it's OK, I'll try to make this upstream then.
With 'upstream' you mean our Factory package?
Both Factory and device mapper upstream. -- 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=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c74
--- Comment #74 from Kay Sievers
http://bugzilla.novell.com/show_bug.cgi?id=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c75
--- Comment #75 from Xinwei Hu
What's with the LVM links? They will still be removed with any non-libdevmapper event, right?
LVM links will not be removed with non-libdevmapper event. -- 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=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c76
--- Comment #76 from Xinwei Hu
(In reply to comment #74)
What's with the LVM links? They will still be removed with any non-libdevmapper event, right?
LVM links will not be removed with non-libdevmapper event.
The upstream version will remove the links, the version in Base:System won't. Just want to make it clear a little bit. -- 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=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c77
--- Comment #77 from Arvin Schnell
http://bugzilla.novell.com/show_bug.cgi?id=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c78
--- Comment #78 from Kay Sievers
Kay, I have tested what you write in comment #64. But on RC1 udev apparently does watch for metadata changes even on DM devices (tested with LVM).
That's a temporary thing in the udisks rules, which are only available on GNOME installations.
So maybe removing the artificial "add" event from libstorage is the best way to fix this problem.
I still don't think so. As mentioned earlier, to remove one of many possible event sources makes the issue appear less frequently, but does not solve the underlying problem in any kind. Device mapper needs to cope with that behavior, we can not control all tools which issue these events, and there a quite a few more besides libstorage. The dm/lvm release of yesterday is supposed to solve this problem at the dm level. -- 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=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c79
--- Comment #79 from Arvin Schnell
http://bugzilla.novell.com/show_bug.cgi?id=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c80
--- Comment #80 from Kay Sievers
Even if it's a temporary thing that metadata changes are handled it works now and we need a solution now.
Keep in mind that this will only work on GNOME. Other desktops still use HAL which does not install these watch rules.
(And a final solution would also not need an artificial "add" event from libstorage.)
I don't see how we can expect these to be automatically updated on all systems. In any case it should be 'change', 'add' is reserved for coldplug, and the very first event at device creation.
I also agree that the communication between udev and device-mapper must still be fixed but I suppose this will take a lot more time.
The release of yesterday looks promising. Unlike the version we ship, it has the potential to work much better. And most of the Red Hat bugs got closed now. But as said earlier, I can't really suggest anything here, I'm just watching the reports. -- 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=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c81
--- Comment #81 from Bruno Friedmann
http://bugzilla.novell.com/show_bug.cgi?id=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c82
--- Comment #82 from Arvin Schnell
In reply to comment #80)
Keep in mind that this will only work on GNOME. Other desktops still use HAL which does not install these watch rules.
I tested with KDE. -- 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=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c83
--- Comment #83 from Kay Sievers
I tested with KDE.
Then it's coming from some other rule. It's usually not the case. But what I meant regarding the problem, is that it should _not_ matter if udev does these artificial events (with 'watch') or libstorage is doing it (writing to uevent). Both types of event sources will cause exactly the same behavior as they both don't originate from libdevmapper, and removing them from libstorage will only make the links not updated in case udev does not trigger the watch events. Some large systems, or systems using many tiny writes with 'dd', or something similar are known to have problems with udev's 'watch' and are instructed to globally switch this off with a custom rule containing 'nowatch'. In short, I would not expect, that changing libstorage will solve any of the problems we are seeing. -- 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=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c84
Xinwei Hu
http://bugzilla.novell.com/show_bug.cgi?id=598193 http://bugzilla.novell.com/show_bug.cgi?id=598193#c85 mail ignored <0.bugs.only.0@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |0.bugs.only.0@gmail.com --- Comment #85 from mail ignored <0.bugs.only.0@gmail.com> 2010-06-26 11:06:17 PDT --- (In reply to comment #84)
I updated the LVM2 package to the latest upstream release, which fixes this issue in a nice way.
Can you please clarify which update we're specifically looking for? atm, I see an update to LVM 2.0.67 from you in the last days: rpm -q --changelog lvm2-2.02.67-36.1.x86_64 | head -n 11 * Wed Jun 23 2010 xwhu@novell.com - Update to LVM.2.02.67 - Require partial option in lvchange --refresh for partial LVs - Add replicators' LVs to dtree for activation - Add lvm2app interfaces to lookup a vgname from a pvid and pvname - Fix memory leak for invalid regex pattern input - Disallow the direct removal of a merging snapshot - Fix lvconvert error message when existing mirrored LV is not found - Add LVM_SUPPRESS_LOCKING_FAILURE_MESSAGES environment variable - Improve snapshot merge metadata import validation but upstream seems to be newer: @ http://sources.redhat.com/cgi-bin/cvsweb.cgi/LVM2/VERSION?cvsroot=lvm2 latest -> CVS Tags: v2_02_68. i'm guessing that's 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=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c86
Xinwei Hu
(In reply to comment #84)
I updated the LVM2 package to the latest upstream release, which fixes this issue in a nice way.
Can you please clarify which update we're specifically looking for?
atm, I see an update to LVM 2.0.67 from you in the last days:
rpm -q --changelog lvm2-2.02.67-36.1.x86_64 | head -n 11 * Wed Jun 23 2010 xwhu@novell.com - Update to LVM.2.02.67 - Require partial option in lvchange --refresh for partial LVs - Add replicators' LVs to dtree for activation - Add lvm2app interfaces to lookup a vgname from a pvid and pvname - Fix memory leak for invalid regex pattern input - Disallow the direct removal of a merging snapshot - Fix lvconvert error message when existing mirrored LV is not found - Add LVM_SUPPRESS_LOCKING_FAILURE_MESSAGES environment variable - Improve snapshot merge metadata import validation
but upstream seems to be newer:
@ http://sources.redhat.com/cgi-bin/cvsweb.cgi/LVM2/VERSION?cvsroot=lvm2
latest -> CVS Tags: v2_02_68.
i'm guessing that's it ... ?
Yes, as the time I'm updating, 2.02.67 was still the latest. btw: You need to update device-mapper to 1.02.49. A while ago, the new packages were accepted into Factory. So I'm closing this as fixed. Thank you all for the help to resolve this 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=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c87
Elmar Stellnberger
http://bugzilla.novell.com/show_bug.cgi?id=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c88
Jaroslaw Zachwieja
http://bugzilla.novell.com/show_bug.cgi?id=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c89
--- Comment #89 from Martin Christeson
http://bugzilla.novell.com/show_bug.cgi?id=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c90
--- Comment #90 from Israel smilanski
http://bugzilla.novell.com/show_bug.cgi?id=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c91
--- Comment #91 from Israel smilanski
http://bugzilla.novell.com/show_bug.cgi?id=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c92
--- Comment #92 from Xinwei Hu
http://bugzilla.novell.com/show_bug.cgi?id=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c93
--- Comment #93 from Arvin Schnell
http://bugzilla.novell.com/show_bug.cgi?id=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c94
--- Comment #94 from Israel smilanski
http://bugzilla.novell.com/show_bug.cgi?id=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c95
--- Comment #95 from Martin Christeson
http://bugzilla.novell.com/show_bug.cgi?id=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c96
--- Comment #96 from Xinwei Hu
http://bugzilla.novell.com/show_bug.cgi?id=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c97
--- Comment #97 from Martin Christeson
http://bugzilla.novell.com/show_bug.cgi?id=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c98
--- Comment #98 from Israel smilanski
http://bugzilla.novell.com/show_bug.cgi?id=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c99
--- Comment #99 from Mario Guzman
http://bugzilla.novell.com/show_bug.cgi?id=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c100
--- Comment #100 from Mario Guzman
http://bugzilla.novell.com/show_bug.cgi?id=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c101
Mario Guzman
http://bugzilla.novell.com/show_bug.cgi?id=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c102
--- Comment #102 from Arvin Schnell
http://bugzilla.novell.com/show_bug.cgi?id=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c103
--- Comment #103 from Mario Guzman
http://bugzilla.novell.com/show_bug.cgi?id=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c
Stephan Kulow
http://bugzilla.novell.com/show_bug.cgi?id=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c104
--- Comment #104 from roeland jansen
http://bugzilla.novell.com/show_bug.cgi?id=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c105
--- Comment #105 from Xinwei Hu
I added the base/system repository and upgraded the MS7 installation to 11.3. This time it was succsesfull. However, on another system, in which / is on a "real" disk and /home is on /dev/mapper there is still the 180 seconds hang which I have mentiond above.
Hi Israel, Thanks for the feedback. Would you attach the output of "180 seconds hang" here? I'd like to see how this happens again. 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=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c106
--- Comment #106 from Xinwei Hu
In installed the latest udev and device-mapper as suggested from Base:System, rebooted and this resolved my issue. One observation, I watched the start up iterate through the device list a second time (the first was successful) but there was no harm done..
Thanks for looking into this... martin
Hi Martin, Thanks for the feedback. Could you explain a little bit more about "start up iterate through the device list a second time" ? I 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=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c107
--- Comment #107 from Sascha Peilicke
http://bugzilla.novell.com/show_bug.cgi?id=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c108
--- Comment #108 from Israel smilanski
http://bugzilla.novell.com/show_bug.cgi?id=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c109
--- Comment #109 from Sascha Peilicke
http://bugzilla.novell.com/show_bug.cgi?id=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c110
--- Comment #110 from Xinwei Hu
After upgrading to openSUSE-11.3 RC2 if got a very similar problem to Martin (comment 89), see bug #620360.
I tried to install newer device-mapper and udev packages from the Base:System repository as suggest in comment 96 from a LiveCD/chroot-environment without much success. Running "mkinitrd" in the chroot-env produces the following error:
linux:/ # mkinitrd Perl-Bootloader: 2010-07-07 13:58:54 ERROR: UDEVMAPPING: dmdev /dev/dm-7 doesn't have defined DM_NAME in udev This is what the new udev package try to fix. As a workaround, you can try "udevadm trigger" before mkinitrd. Hope this helps.
-- 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=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c111
--- Comment #111 from Sascha Peilicke
(In reply to comment #109)
After upgrading to openSUSE-11.3 RC2 if got a very similar problem to Martin (comment 89), see bug #620360.
I tried to install newer device-mapper and udev packages from the Base:System repository as suggest in comment 96 from a LiveCD/chroot-environment without much success. Running "mkinitrd" in the chroot-env produces the following error:
linux:/ # mkinitrd Perl-Bootloader: 2010-07-07 13:58:54 ERROR: UDEVMAPPING: dmdev /dev/dm-7 doesn't have defined DM_NAME in udev This is what the new udev package try to fix. As a workaround, you can try "udevadm trigger" before mkinitrd. Hope this helps.
Ok, I did 'udevadm trigger' several times, then 'mkinitrd', the Perl-Bootloader error message remains though... -- 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=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c112
--- Comment #112 from Sascha Peilicke
Ok, I did 'udevadm trigger' several times, then 'mkinitrd', the Perl-Bootloader error message remains though...
Despite these errors it worked after reboot -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c113
Volker Lang
http://bugzilla.novell.com/show_bug.cgi?id=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c114
--- Comment #114 from Volker Lang
http://bugzilla.novell.com/show_bug.cgi?id=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c115
--- Comment #115 from Xinwei Hu
Same happen to me - upgrade from 11.2 to 11.3 RC1
During upgrade process with Live CD: - part1 of RAID is win7 and was not correctly detected by boot loader - failed to "format" existing "/" and swap directories from existing 11.2 installation (error -3030) - failed to copy installation files
The tried online update (redirect repo's to 11.3 and "zypper dup" - run through quite fine - boot loader setup correctly
After restart, Linux is not working anymore - RAID set "nvidia_iaaxxx" already active - RAID set "nvidia_iaaxxx" was not activated - waiting for "???-part6" of the RAID which is I believe the "/" directory - rudimentary bash environment available - RAID on Nvidia nforce chipset 570 (ca 2 yr old system)
No attachment since Linux is not starting at all (wrote this from Win7 8-(
Hi Volker: This issue is fixed for GM. You may try the GM version of 11.3 with following steps: - Booting from 11.3 GM - Entering rescue mode - Install the latest device-mapper, udev into your 11.3 RC2 system - run 'mkinitrd' to refresh the initrd file to the latest - Reboot. Hope this help. 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.
https://bugzilla.novell.com/show_bug.cgi?id=598193
https://bugzilla.novell.com/show_bug.cgi?id=598193#c116
--- Comment #116 from Sascha Peilicke
https://bugzilla.novell.com/show_bug.cgi?id=598193
https://bugzilla.novell.com/show_bug.cgi?id=598193#c117
Xinwei Hu
http://bugzilla.novell.com/show_bug.cgi?id=598193
http://bugzilla.novell.com/show_bug.cgi?id=598193#c118
--- Comment #118 from Bernhard Wiedemann
participants (1)
-
bugzilla_noreply@novell.com