[Bug 684291] New: device names not updated by zypper dup on Raid0 system
https://bugzilla.novell.com/show_bug.cgi?id=684291 https://bugzilla.novell.com/show_bug.cgi?id=684291#c0 Summary: device names not updated by zypper dup on Raid0 system Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: rschweikert@novell.com QAContact: qa@suse.de Found By: --- Blocker: --- Ran zypper dup to update from oS 11.3 to oS 11.4 on a system with 2 550 GB drives setup in a RAID 0 config in the BIOS (thus dmraid). After all packages were installed I rebooted the system, but upon reboot the machine could not find the root partition. The partition setup part1 -> /boot (ext2) part2 -> swap part3 -> / (xfs) I received the message Waiting for .......to appear in addition to the problem described in 684113 (dmraid missing) the second problem during this dup operation was that the raid0 drives are identified differently with the new kernel. However, non of the pertinent files were updated /etc/fstab /boot/grub/menu.lst /etc/sysconfig/bootloader were all still pointing to the old device naming that no longer exists. -- 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=684291 https://bugzilla.novell.com/show_bug.cgi?id=684291#c zj jia <zjjia@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |zjjia@novell.com AssignedTo|bnc-team-screening@forge.pr |zypp-maintainers@forge.prov |ovo.novell.com |o.novell.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=684291 https://bugzilla.novell.com/show_bug.cgi?id=684291#c1 Duncan Mac-Vicar <dmacvicar@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dmacvicar@novell.com AssignedTo|zypp-maintainers@forge.prov |snwint@novell.com |o.novell.com | --- Comment #1 from Duncan Mac-Vicar <dmacvicar@novell.com> 2011-05-17 14:58:02 UTC --- This is not handled by libzypp but perl-Bootloader or kernel post-install scripts. -- 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=684291 https://bugzilla.novell.com/show_bug.cgi?id=684291#c2 Steffen Winterfeldt <snwint@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |rschweikert@novell.com --- Comment #2 from Steffen Winterfeldt <snwint@novell.com> 2011-05-17 17:08:41 CEST ---
problem during this dup operation was that the raid0 drives are identified differently
Differently in what 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=684291 https://bugzilla.novell.com/show_bug.cgi?id=684291#c3 Robert Schweikert <rschweikert@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|rschweikert@novell.com | --- Comment #3 from Robert Schweikert <rschweikert@novell.com> 2011-05-17 16:54:31 UTC --- Prior to the update to 11.4, the fstab entry was as follows: /dev/disk/by-id/md-uuid-1222f6e8:fef6ea76:035f7613:f442ef6a-part3 As of 11.4 this works: /dev/mapper/isw_cbdadbheb_ARRAYp3 Also disk/by-id no longer shows the old name: -> ls /dev/disk/by-id/md-uuid-1* ls: No match. -- 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=684291 https://bugzilla.novell.com/show_bug.cgi?id=684291#c4 Steffen Winterfeldt <snwint@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |snwint@novell.com AssignedTo|snwint@novell.com |nfbrown@novell.com --- Comment #4 from Steffen Winterfeldt <snwint@novell.com> 2011-05-18 10:32:59 CEST --- That's not a bootloader config issue. p-bl cannot know in what way device names may change after a reboot. /dev/disk/by-* device names are meant to be stable across releases. Maybe a bug in the raid packages causes this. -- 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=684291 https://bugzilla.novell.com/show_bug.cgi?id=684291#c5 Neil Brown <nfbrown@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |rschweikert@novell.com --- Comment #5 from Neil Brown <nfbrown@novell.com> 2011-05-31 01:38:59 UTC --- If the name was 'md-uuid-*' in 11.3, then it wasn't using dmraid, it must have been using mdadm... The problem is that both 'dmraid' and 'mdadm' can manage this style of array. So if you have both installed then there could be some confusion as to which is responsible. Maybe you didn't have dmraid installed with 11.3?? Maybe we need to get dmraid and mdadm to use the same 'by-id' name for the same device... In 11.4, when /dev/mapper/isw.... works, what names appear in /dev/disk/by-id/ ?? -- 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=684291 https://bugzilla.novell.com/show_bug.cgi?id=684291#c6 Robert Schweikert <rschweikert@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|rschweikert@novell.com | --- Comment #6 from Robert Schweikert <rschweikert@novell.com> 2011-05-31 11:40:32 UTC --- ls /dev/disk/by-id/ ata-HL-DT-ST_DVD+_-RW_GH50N_7F9CA061CCD8 raid-DMRAID-isw_cbdadbheb_ARRAY-part2 ata-ST3500418AS_9VM1WA1D raid-DMRAID-isw_cbdadbheb_ARRAY-part3 ata-ST3500418AS_9VM1WA1D-part1 raid-isw_cbdadbheb_ARRAY ata-ST3500418AS_9VM1WA1D-part2 raid-isw_cbdadbheb_ARRAYp1 ata-ST3500418AS_9VM1WA1D-part3 raid-isw_cbdadbheb_ARRAYp2 ata-ST3500418AS_9VM1XE2L raid-isw_cbdadbheb_ARRAYp3 dm-name-isw_cbdadbheb_ARRAY raid-isw_cbdadbheb_ARRAY-part1 dm-name-isw_cbdadbheb_ARRAYp1 raid-isw_cbdadbheb_ARRAY-part2 dm-name-isw_cbdadbheb_ARRAYp2 raid-isw_cbdadbheb_ARRAY-part3 dm-name-isw_cbdadbheb_ARRAYp3 scsi-SATA_ST3500418AS_9VM1WA1D dm-name-isw_cbdadbheb_ARRAY_part1 scsi-SATA_ST3500418AS_9VM1WA1D-part1 dm-name-isw_cbdadbheb_ARRAY_part2 scsi-SATA_ST3500418AS_9VM1WA1D-part2 dm-name-isw_cbdadbheb_ARRAY_part3 scsi-SATA_ST3500418AS_9VM1WA1D-part3 dm-uuid-DMRAID-isw_cbdadbheb_ARRAY scsi-SATA_ST3500418AS_9VM1XE2L dm-uuid-DMRAID-isw_cbdadbheb_ARRAYp1 wwn-0x5000c50015547d2b dm-uuid-DMRAID-isw_cbdadbheb_ARRAYp2 wwn-0x5000c5001554a097 dm-uuid-DMRAID-isw_cbdadbheb_ARRAYp3 wwn-0x5000c5001554a097-part1 dm-uuid-part1-DMRAID-isw_cbdadbheb_ARRAY wwn-0x5000c5001554a097-part2 dm-uuid-part2-DMRAID-isw_cbdadbheb_ARRAY wwn-0x5000c5001554a097-part3 dm-uuid-part3-DMRAID-isw_cbdadbheb_ARRAY wwn-0x5001480000000000 raid-DMRAID-isw_cbdadbheb_ARRAY-part1 -- 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=684291 https://bugzilla.novell.com/show_bug.cgi?id=684291#c7 --- Comment #7 from Neil Brown <nfbrown@novell.com> 2011-06-02 06:24:25 UTC --- *** Bug 684113 has been marked as a duplicate of this bug. *** http://bugzilla.novell.com/show_bug.cgi?id=684113 -- 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=684291 https://bugzilla.novell.com/show_bug.cgi?id=684291#c10 Neil Brown <nfbrown@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED CC| |mmarek@novell.com --- Comment #10 from Neil Brown <nfbrown@novell.com> 2011-06-09 06:42:39 UTC --- OK, I've figured out what happened. Under 11.3 you were using mdadm to manage your platform-RAID arrays. When you upgraded to 11.4, something went wrong and the mkinitrd setup script for md didn't recognise your array. So it didn't install the md modules or tools in the initrd, so the initrd couldn't assembly your RAID array. You thought that dmraid had been managing the arrays so built an initrd with dmraid support and it assembled the arrays but gave them a different name than the name that mdadm gave them, so you were a little closer but it still didn't work. You had to edit /etc/fstab etc to use the new names, and now it works. I'm a bit confused as to why the setup script didn't put any md stuff in the initrd, but it clearly didn't. In any case if it had it wouldn't have worked. It seems that when I "fixed" the udev rules to avoid a race condition, I also "broken" them so that partitions weren't handled properly. So had it assembled the md arrays, it wouldn't have created the 'partXX' devices in /dev/disk/... and it wouldn't have worked anyway. I'm guess that part of the install process involved telling udev to recreate all links, and that make it remove the partition links in /dev/disk. Then when mkinitrd ran the md setup script it couldn't find the like, got confused and gave up. So I'll fix the udev rules file to do the right thing. You can just leave things as they are if you like, or we could convert back to using mdadm just to make sure it works. If you would like to try converting back, let me know and I'll see if I can work out the easiest way to do 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=684291 https://bugzilla.novell.com/show_bug.cgi?id=684291#c11 --- Comment #11 from Robert Schweikert <rschweikert@novell.com> 2011-06-09 12:39:24 UTC --- I do not care much about how the RAID is managed md or dm. What I mostly care about would be to get back to a system where I can boot without manual intervention. At this point (presume because the udev rules are not creating the proper links) I always end up in a shell at boot time where I run dmraid -r dmraid -ay Ctrl-D Then boot resumes and the system starts as expected. Just having an initrd that eliminates this step would be great. -- 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=684291 https://bugzilla.novell.com/show_bug.cgi?id=684291#c12 Neil Brown <nfbrown@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO InfoProvider| |rschweikert@novell.com --- Comment #12 from Neil Brown <nfbrown@novell.com> 2011-06-14 05:39:27 UTC --- The reason that it doesn't create the correct links is that /lib/mkinitrd/boot/21-dmraid.sh (which is copied into the initrd) runs dmraid as: /sbin/dmraid -a y -p The '-p' says "don't create partitions" which causes you problems because you need partitions. So you could just edit that file, run "mkinitrd" and it should reboot perfectly. However I'm not confident about removing that "-p" in the distro as it is presumably there for a reason and theoretically people cold depend on it. I would like to see if we can convert it back to using md. This would involve: 1/ edit /lib/udev/rules.d/64-md-raid.rules to replace TEST!="md/array_state", GOTO="md_end" with ENV{DEVTYPE}=="disk",TEST!="md/array_state", GOTO="md_end" 2/ re-create the initrd with md support: mkinitrd -f md 3/ Restore the old fstab and menu.lst files (from fstab.bck and menu.lst.old). 4/ reboot and when you get the prompt: dmraid -an mdadm -As Ctrl-D If that doesn't work (which I think it will) try: mdadm -Ss mdadm -I /dev/sda mdadm -I /dev/sdb 5/ When you have the system booted again, make a new initrd mkinitrd and make sure it boots safely. Please let me know how it goes. -- 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=684291 https://bugzilla.novell.com/show_bug.cgi?id=684291#c13 Neil Brown <nfbrown@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- InfoProvider|rschweikert@novell.com |maint-coord@suse.de --- Comment #13 from Neil Brown <nfbrown@novell.com> 2011-06-14 06:03:24 UTC --- Hi Maintenance: We need an update for mdadm for SLE-11-SP1 to fix this issue. An earlier update broke handling of partitions in md devices. (I have submitted an update for -SP2 already). -- 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=684291 https://bugzilla.novell.com/show_bug.cgi?id=684291#c Swamp Workflow Management <swamp@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status Whiteboard| |maint:planned:update -- 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=684291 https://bugzilla.novell.com/show_bug.cgi?id=684291#c Swamp Workflow Management <swamp@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status Whiteboard| |maint:planned:update -- 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=684291 https://bugzilla.novell.com/show_bug.cgi?id=684291#c14 Swamp Workflow Management <swamp@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status Whiteboard|maint:planned:update |maint:running:41576:moderat | |e --- Comment #14 from Swamp Workflow Management <swamp@suse.com> 2011-06-14 11:09:59 UTC --- The SWAMPID for this issue is 41576. This issue was rated as moderate. Please submit fixed packages until 2011-06-28. Also create a patchinfo file using this link: https://swamp.suse.de/webswamp/wf/41576 -- 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=684291 https://bugzilla.novell.com/show_bug.cgi?id=684291#c19 --- Comment #19 from Bernhard Wiedemann <bwiedemann@novell.com> 2011-06-21 09:00:15 CEST --- This is an autogenerated message for OBS integration: This bug (684291) was mentioned in https://build.opensuse.org/request/show/74241 11.4 / mdadm -- 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=684291 https://bugzilla.novell.com/show_bug.cgi?id=684291#c20 --- Comment #20 from Robert Schweikert <rschweikert@suse.com> 2011-07-07 17:55:16 UTC --- (In reply to comment #12)
The reason that it doesn't create the correct links is that /lib/mkinitrd/boot/21-dmraid.sh (which is copied into the initrd) runs dmraid as:
/sbin/dmraid -a y -p
The '-p' says "don't create partitions" which causes you problems because you need partitions. So you could just edit that file, run "mkinitrd" and it should reboot perfectly.
However I'm not confident about removing that "-p" in the distro as it is presumably there for a reason and theoretically people cold depend on it.
I would like to see if we can convert it back to using md. This would involve:
1/ edit /lib/udev/rules.d/64-md-raid.rules to replace
TEST!="md/array_state", GOTO="md_end"
with
ENV{DEVTYPE}=="disk",TEST!="md/array_state", GOTO="md_end"
2/ re-create the initrd with md support:
mkinitrd -f md
3/ Restore the old fstab and menu.lst files (from fstab.bck and menu.lst.old).
4/ reboot and when you get the prompt:
dmraid -an mdadm -As Ctrl-D If that doesn't work (which I think it will) try:
mdadm -Ss mdadm -I /dev/sda mdadm -I /dev/sdb
5/ When you have the system booted again, make a new initrd
mkinitrd
and make sure it boots safely.
Please let me know how it goes.
Alright!! Thanks, this worked, the machine once again boots without manual intervention. :) -- 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=684291 https://bugzilla.novell.com/show_bug.cgi?id=684291#c21 Neil Brown <nfbrown@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED --- Comment #21 from Neil Brown <nfbrown@novell.com> 2011-07-11 06:22:37 UTC ---
Thanks, this worked, the machine once again boots without manual intervention.
Great. Thanks for the confirmation. I think we are all done here, so closing as 'fixed'. -- 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=684291 https://bugzilla.novell.com/show_bug.cgi?id=684291#c22 Swamp Workflow Management <swamp@suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status Whiteboard|maint:running:41576:moderat |maint:running:41576:moderat |e |e maint:released:11.4:41703 --- Comment #22 from Swamp Workflow Management <swamp@suse.de> 2011-07-12 08:40:46 UTC --- Update released for: mdadm, mdadm-debuginfo, mdadm-debugsource Products: openSUSE 11.4 (debug, i586, 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.
https://bugzilla.novell.com/show_bug.cgi?id=684291 https://bugzilla.novell.com/show_bug.cgi?id=684291#c23 Swamp Workflow Management <swamp@suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status Whiteboard|maint:running:41576:moderat |maint:running:41576:moderat |e maint:released:11.4:41703 |e maint:released:11.4:41703 | |maint:released:sle11-sp1:41 | |702 --- Comment #23 from Swamp Workflow Management <swamp@suse.de> 2011-07-12 10:56:37 UTC --- Update released for: mdadm, mdadm-debuginfo, mdadm-debugsource Products: SLE-DEBUGINFO 11-SP1 (i386, ia64, ppc64, s390x, x86_64) 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.
https://bugzilla.novell.com/show_bug.cgi?id=684291 https://bugzilla.novell.com/show_bug.cgi?id=684291#c Swamp Workflow Management <swamp@suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status Whiteboard|maint:running:41576:moderat |maint:released:11.4:41703 |e maint:released:11.4:41703 |maint:released:sle11-sp1:41 |maint:released:sle11-sp1:41 |702 |702 | -- 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.
participants (1)
-
bugzilla_noreply＠novell.com