Bug 765718

Summary:	3.1.1.4 kernel panic invalid raid superblock magic
Product:	[Fedora] Fedora	Reporter:	fjfalcon <fjfalcon>
Component:	kernel	Assignee:	Kernel Maintainer List <kernel-maint>
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	16	CC:	gansalmon, itamar, jforbes, jonathan, kernel-maint, madhu.chinakonda
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:	2012-11-14 14:58:25 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description fjfalcon 2011-12-09 08:37:59 UTC

Description of problem:
I upgrated from fedora 14 to fedora 16.
I have / on raid 1.
When i trying to boot from new kernel i get following message
invalid raid superblock magic
Version-Release number of selected component (if applicable):
3.1.1.4 and earlier from 2.40

How reproducible:
Boot into last kernel

Steps to Reproduce:
Create raid1 on / in fedora 14 (x86_64) 
upgrade to fedora 16.
Boot into last kernel
  
Actual results:
Kernel Panic

Expected results:
System boot.

Additional info:
/dev/sda1 /dev/sdb1 - raid1 - boot
/dev/sda2 /dev/sdb2 - raid1 - /

Comment 1 Dave Jones 2012-03-22 17:05:21 UTC

[mass update]
kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository.
Please retest with this update.

Comment 2 Dave Jones 2012-03-22 17:08:29 UTC

[mass update]
kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository.
Please retest with this update.

Comment 3 Dave Jones 2012-03-22 17:19:09 UTC

[mass update]
kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository.
Please retest with this update.

Comment 4 fjfalcon 2012-03-22 19:19:13 UTC

Have restarted system after kernel upgrade... some problem afaik, cause system won't boot. 
Will check in 10-11 hours for more info.

Comment 5 fjfalcon 2012-03-23 06:17:41 UTC

Nope, with kernel 3.3.0-4 everything same.

Comment 6 Josh Boyer 2012-09-18 16:08:35 UTC

Are you still seeing this with the 3.4 or 3.5 kernel updates?  If so, could you please attach the backtrace that is printed out?

Comment 7 Dave Jones 2012-10-23 15:30:43 UTC

# Mass update to all open bugs.

Kernel 3.6.2-1.fc16 has just been pushed to updates.
This update is a significant rebase from the previous version.

Please retest with this kernel, and let us know if your problem has been fixed.

In the event that you have upgraded to a newer release and the bug you reported
is still present, please change the version field to the newest release you have
encountered the issue with.  Before doing so, please ensure you are testing the
latest kernel update in that release and attach any new and relevant information
you may have gathered.

If you are not the original bug reporter and you still experience this bug,
please file a new report, as it is possible that you may be seeing a
different problem. 
(Please don't clone this bug, a fresh bug referencing this bug in the comment is sufficient).

Comment 8 Justin M. Forbes 2012-11-14 14:58:25 UTC

With no response, we are closing this bug under the assumption that it is no longer an issue. If you still experience this bug, please feel free to reopen the bug report.