Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 187371

Summary: kernel 2080_FC5 breaks dmraid initializing
Product: [Fedora] Fedora Reporter: Dan Book <grinnz>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED DUPLICATE QA Contact: Brian Brock <bbrock>
Severity: high Docs Contact:
Priority: medium    
Version: 5CC: wtogami
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-04-10 15:42:04 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Dan Book 2006-03-30 16:21:18 UTC
Description of problem:
With the kernel released with FC5, dmraid installing and booting worked
flawlessly for my NVRAID0 array. I recently updated several packages, including
the kernel, and restarted into the new kernel, hoping to be able to finally have
a decent video driver easily installable. Unfortunately, although grub still
works fine, as soon as it gets to the message "Red Hat nash version 5.0.32
starting" it outputs the errors:
device-mapper: dm-stripe: Target length not divisible by chunk size
device-mapper: reload ioctl failed: Invalid argument
And successively can't find any partitions, and kernel panics.
Booting back into the old kernel with no other changes still works fine.

Version-Release number of selected component (if applicable):
2.6.16-1.2080_FC5

How reproducible:
Always

Steps to Reproduce:
1. Install kernel 2.6.16-1.2080_FC5 on a dmraid-interfaced array
2. Attempt to boot the kernel
  
Actual results:
Kernel panic - can't load dmraid

Expected results:
Successful boot

Additional info:
I'll install the test kernel 2069 to see if it has the same issue. If you have
any easy method for obtaining the log of the boot since it isn't finding any
partitions to save the log, let me know.

Comment 1 Dan Book 2006-03-31 03:23:49 UTC
Same problem with 2.6.16-1.2069_FC5

Comment 2 Yuji Tsuchimoto 2006-04-03 12:11:12 UTC
The same problem with 2.6.16-1.2084_FC5.x86_64


Comment 3 Martin Bürge 2006-04-10 12:02:01 UTC
I think that's the same probleme here:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=186842

Comment 4 Dan Book 2006-04-10 15:42:04 UTC
Thanks for letting me know.

*** This bug has been marked as a duplicate of 186842 ***