[Bug 623268] New: LVM support was lost for booting of updated system.
http://bugzilla.novell.com/show_bug.cgi?id=623268 http://bugzilla.novell.com/show_bug.cgi?id=623268#c0 Summary: LVM support was lost for booting of updated system. Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: x86-64 OS/Version: openSUSE 11.3 Status: NEW Severity: Major Priority: P5 - None Component: Update Problems AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: Markus.Elfring@web.de QAContact: jsrain@novell.com Found By: --- Blocker: --- I updated a couple of software components from current packages on Friday. Yesterday I was surprised that all Linux kernels I could select from the GRUB menu could not find the root file system which is contained in a logical volume. I reactivated an old kernel with the corresponding initial RAM disk to get a working openSUSE back. I am curious which update "dropped" the LVM2 support to boot as expected from /dev/mapper/system-root"". Which ways would be recommended to repair the contents of the other RAM disks? -- 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=623268
http://bugzilla.novell.com/show_bug.cgi?id=623268#c
yang xiaoyu
http://bugzilla.novell.com/show_bug.cgi?id=623268
http://bugzilla.novell.com/show_bug.cgi?id=623268#c1
--- Comment #1 from Xinwei Hu
http://bugzilla.novell.com/show_bug.cgi?id=623268
http://bugzilla.novell.com/show_bug.cgi?id=623268#c2
--- Comment #2 from Markus Elfring
http://bugzilla.novell.com/show_bug.cgi?id=623268
http://bugzilla.novell.com/show_bug.cgi?id=623268#c3
--- Comment #3 from Xinwei Hu
Created an attachment (id=376728) --> (http://bugzilla.novell.com/attachment.cgi?id=376728) [details] change logs
Which tools can add the required module(s) for support of logical volume management to the RAM disk in a "convenient" and safe way?
Hi Markus: I assume you are referring to initrd. If this is the case, you can get to it via "mkinitrd -f lvm2" (refer to man mkinitrd for details). -- 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=623268
http://bugzilla.novell.com/show_bug.cgi?id=623268#c4
--- Comment #4 from Markus Elfring
http://bugzilla.novell.com/show_bug.cgi?id=623268
http://bugzilla.novell.com/show_bug.cgi?id=623268#c5
--- Comment #5 from Xinwei Hu
(In reply to comment #3)
I refer to the proper completion of initial ram file systems. I would like to be sure that the required modules or features will be added with a version that will really fit to the target kernels.
Should the update process ask the user (or system administrator) about potential adjustments for initrd files which do not belong to affected kernel images of the current distribution upgrade?
Is the parameter "-k kernel_list" used during the update so that selected files can be left unchanged?
Which command triggered the deletions that damaged LVM support?
Theoretically, no commands should do that. My first thought was it's a duplicate of bnc#619461, which seems to be wrong now. And I cannot reproduce this issue in my environment so far yet. Can you provide me some way to reproduce this issue ? Thanks a lot. -- 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=623268
http://bugzilla.novell.com/show_bug.cgi?id=623268#c6
--- Comment #6 from Markus Elfring
http://bugzilla.novell.com/show_bug.cgi?id=623268
http://bugzilla.novell.com/show_bug.cgi?id=623268#c7
--- Comment #7 from Xinwei Hu
(In reply to comment #5)
I can give you more installation details from my side if you need it. Which software packages contain update instructions for initrd files?
There're a couple of scripts in /lib/mkinitrd/scripts. When you call 'mkinitrd', the scripts in /lib/mkinitrd/setup will be used to setup, and scripts in /lib/mkinitrd/boot will be copied into the initrd file. Hope this helps. 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=623268
http://bugzilla.novell.com/show_bug.cgi?id=623268#c8
--- Comment #8 from Markus Elfring
Hope this helps.
Not really in the direction I need ... Would we like to identify the concrete update instructions which damaged the LVM support on my system? -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=623268
http://bugzilla.novell.com/show_bug.cgi?id=623268#c9
--- Comment #9 from Xinwei Hu
(In reply to comment #7)
Hope this helps.
Not really in the direction I need ...
Would we like to identify the concrete update instructions which damaged the LVM support on my system?
I think /var/log/YaST2/mkinitrd.log will be a good start. -- 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=623268
http://bugzilla.novell.com/show_bug.cgi?id=623268#c10
--- Comment #10 from Markus Elfring
https://bugzilla.novell.com/show_bug.cgi?id=623268
https://bugzilla.novell.com/show_bug.cgi?id=623268#c11
Anniyka Wandersmann
https://bugzilla.novell.com/show_bug.cgi?id=623268
https://bugzilla.novell.com/show_bug.cgi?id=623268#c12
--- Comment #12 from Anniyka Wandersmann
etc/modprobe.d/nvidia.conf 161a160 lib64/libsepol.so.1 174,237c173,250
310,311d322 < sbin/mdadm < sbin/mdmon anniys:~ # diff init.main init.new | grep -v lib/ 45d44 < boot/51-md.sh 64d62 < config/md.sh 78d75 < etc/mdadm.conf 95a93
etc/modprobe.d/nvidia.conf 161a160 lib64/libsepol.so.1 174,237c173,229
310,311d301 < sbin/mdadm < sbin/mdmon anniys:~ # pvdisplay /dev/md1 --- Physical volume --- PV Name /dev/md1 VG Name vg00 PV Size 440,71 GiB / not usable 2,44 MiB Allocatable yes PE Size 4,00 MiB Total PE 112821 Free PE 42336 Allocated PE 70485 PV UUID rGO4WX-e3bc-31YG-4p1Y-H5G6-kVW5-HjjGjR vg01 is not on an md-device -- 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=623268
https://bugzilla.novell.com/show_bug.cgi?id=623268#c13
--- Comment #13 from Markus Elfring
I can not boot with a kernel from 11.3 (original or selfmade) as vg00 remains lost.
The self-compiled kernels 2.6.34 and 2.6.35 that I cloned from the Git repository at "kernel.org" worked with LVM support as usual in my use case. -- 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=623268
https://bugzilla.novell.com/show_bug.cgi?id=623268#c14
Xinwei Hu
https://bugzilla.novell.com/show_bug.cgi?id=623268
https://bugzilla.novell.com/show_bug.cgi?id=623268#c15
Michal Marek
https://bugzilla.novell.com/show_bug.cgi?id=623268
https://bugzilla.novell.com/show_bug.cgi?id=623268#c16
Markus Elfring
https://bugzilla.novell.com/show_bug.cgi?id=623268
https://bugzilla.novell.com/show_bug.cgi?id=623268#c17
Michal Marek
participants (1)
-
bugzilla_noreply@novell.com