Bug 714483

Summary:	Fedora Live usb
Product:	[Fedora] Fedora	Reporter:	Richard Marchesi <richard.marchesi>
Component:	mdadm	Assignee:	Doug Ledford <dledford>
Status:	CLOSED CANTFIX	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	15	CC:	agk, dennis, dledford, mbroz
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:	2011-07-15 00:12:20 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 Richard Marchesi 2011-06-19 15:06:41 UTC

Description of problem:

boot from usb live fedora 15 breaks my current system which is ubuntu 10.04, which is 3 disk raid0
/md0
/md1
/md1
it becomes for some reason
/md125
/md126
/md0

which makes the system unbootable

very strange as i didnt install anything, only booted the live fedora system.  


Version-Release number of selected component (if applicable):
f15

How reproducible:


Steps to Reproduce:
1. boot with live usb into the live system
2. reboot pc as per normal
3.
  
Actual results:
stops workin at boot with his error
error: non such disk.
grub rescue>

Expected results:
system should boot as per normal

Additional info:

Comment 1 Doug Ledford 2011-07-15 00:12:20 UTC

There is no coordination between Fedora mdadm usage and Ubuntu mdadm usage.  In particular, there are different superblock versions that are likely in use and different methods of numbering arrays.  Fedora is switching away from numbering arrays entirely and going to name based array recognition.  It's possible that something in our mdadm usage caused the superminor number in your existing arrays to get updated, resulting in this change in names, but this sort of cross distro interaction is not likely something I can properly debug (especially as I don't even know what the live USB image does to bring the arrays up).  If anyone can fix this, it's likely going to have to be the live image people, not me.