This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.

please boot with "rdshell rdbreak" on the kernel command line and in the shell run:

# grep end_container /etc/udev/rules.d/65-md-incremental-imsm.rules

and attach a photo of the output or just write it here.

Output is:

GOTO="end_container"
LABEL="end_container"

The same missing label is reported for "do_container", too.

How come you have a udev-151-7.fc13 installed? The current udev version in RHEL6 is udev-147-2.X.

I've also tried this with a fresh KVM install here on a RAID5 root and didn't get the error messages.

If you could let us know how to reproduce this that would be excellent.

Thanks & regards, Phil

Hmm, I think the updated udev package came from my trying to fix a different udev related issue. The initrd was generated at install time before that, so I don't think it would have affected it.

I'll see if I can get the whole 65-md-incremental-imsm.rules file from the initrd and attach it this weekend.

My general experience of trying RHEL6b in KVM (on CentOS/RHEL 5.x) generally yields considerably different results WRT stability than bare metal (I have only been able to consistently complete a successful setup with the minimal install under KVM), so I'm not sure that your KVM test makes for a validly equivalent use case.

(In reply to comment #6)
> Hmm, I think the updated udev package came from my trying to fix a different
> udev related issue. The initrd was generated at install time before that, so I
> don't think it would have affected it.
> 
> I'll see if I can get the whole 65-md-incremental-imsm.rules file from the
> initrd and attach it this weekend.

no need for that... but I would like to know your kernel command line.

Here is my kernel line from grub.conf:

kernel /vmlinuz-2.6.32-19.el6.x86_64 ro root=UUID=5ae396eb-d1d6-48fb-8f02-d7901b75c5c3 rd_MD_UUID=b9594022:1c3d0560:9557eee7:7ff48e1f rd_NO_LUKS rd_NO_LVM rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=uk selinux=0

Created attachment 426213 [details]
initramfs-2.6.32-19.el6.x86_64.img

initramfs that exhibits the described behaviour

Hi all,
what is the reproducer here? It looks like the reported udev version is not from RHEL6 so I'm in favour of close/notabug.

The reason the FC13 version of udev was reported was because I'd tried the Fedora udev to see if it fixed the problem, as I mentioned above. It didn't. The machine is currently running the Beta 2 udev:

udev-147-2.20.el6.x86_64

and the problem still exists.

Can't reproduce on RHEL6.0 Beta 2 from comment 14 on x86_64.

On ppc64 i got following message, but it's not the one from description:
udevd[75]: GOTO 'end_raidstart' has no matching label in: '/etc/udev/rules.d/65-md-incremental-imsm.rules'
udevd[75]: GOTO 'end_raidstart' has no matching label in: '/etc/udev/rules.d/65-md-incremental-imsm.rules'

Gordan, could you please describe steps to reproduce on RHEL6.0 Beta2?

The error looks similar enough that they are likely to be related. Considering I have attached the offending initramfs, I'm not sure how much more I can do to provide a reproducible case. I didn't do anything special, I just installed a minimum install straight onto onto a MD RAID5 array.

An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2011-0523.html