https://bugzilla.novell.com/show_bug.cgi?id=684291 https://bugzilla.novell.com/show_bug.cgi?id=684291#c zj jia 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#c2 Steffen Winterfeldt changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |rschweikert@novell.com --- Comment #2 from Steffen Winterfeldt 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#c4 Steffen Winterfeldt changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |snwint@novell.com AssignedTo|snwint@novell.com |nfbrown@novell.com --- Comment #4 from Steffen Winterfeldt 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#c6 Robert Schweikert changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|rschweikert@novell.com | --- Comment #6 from Robert Schweikert 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#c10 Neil Brown changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED CC| |mmarek@novell.com --- Comment #10 from Neil Brown 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#c12 Neil Brown changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO InfoProvider| |rschweikert@novell.com --- Comment #12 from Neil Brown 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#c Swamp Workflow Management 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 changed: What |Removed |Added ---------------------------------------------------------------------------- Status Whiteboard|maint:planned:update |maint:running:41576:moderat | |e --- Comment #14 from Swamp Workflow Management 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#c20 --- Comment #20 from Robert Schweikert 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#c22 Swamp Workflow Management 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 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#c Swamp Workflow Management 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.