Bug 1019771 - OS initial installation fail when mounting VFAT filesystem on mdadm RAID 1
Summary: OS initial installation fail when mounting VFAT filesystem on mdadm RAID 1
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 19
Hardware: i686
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-16 11:30 UTC by Ta-chang
Modified: 2013-10-17 13:40 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-10-17 13:40:40 UTC
Type: Bug


Attachments (Terms of Use)

Description Ta-chang 2013-10-16 11:30:16 UTC
Description of problem:
OS initial installation fail when mounitng VFAT filesystem on mdadm RAID 1

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


How reproducible:
You will be able to reproduce this issue only by creating and mounting VAFT filesystem during initial OS installation.

Steps to Reproduce:
1.create VFAT filesystem on mdadm RAID 1 and finish it

Actual results:
OS installation fail whenever you create and mount VFAT filesystem

Expected results:
(Unknown)

Additional info:

Comment 1 Jes Sorensen 2013-10-16 11:38:59 UTC
Please provide details on what fails and how?

Does the installer crash?

Does this work if you try to create a VFAT file system on a normal disk
partition (non RAID)?

Jes

Comment 2 Ta-chang 2013-10-16 14:05:06 UTC
> Please provide details on what fails and how?

It seemed to be a kind of python error, but I don't remember the detail of it.

> Does the installer crash?

I think somewhat so because the only choice I could make was system reboot when this issue occurred, although I knew it was inevitable after then...

> Does this work if you try to create a VFAT file system on a normal disk
partition (non RAID)?

I've not tried so and known its real result yet. And I've already installed Fedora 18 for a work-around so that I can manage some system application
on it ASAP. The OS works fine until now and personally I think this issue
is unique on Fedora 19.

Moreover, I have no substitute environment, especially for validation of it.
So, I will not be able to do on my own one later until this issue is fully fixed.

Comment 3 Jes Sorensen 2013-10-16 14:32:21 UTC
If you are seeing a python error, then it will be Anaconda failing, and not
mdadm. The bug should go there - so I am reassigning it to anaconda

Comment 4 David Shea 2013-10-16 14:54:13 UTC
Attach the log files from /tmp to this bug as individual, text/plain attachments. In particular, we need the anaconda-tb-* file containing the traceback data.

Comment 5 Ta-chang 2013-10-16 23:11:35 UTC
Refer to my previous post below on this thread.

> Moreover, I have no substitute environment, especially for validation of it.
So, I will not be able to do on my own one later until this issue is fully fixed.

My answer to your request is basically 'I can't do'. In addition, I can't get any core or log files when this issue occurres because OS setup won't finish and I won't be able to access any filesystem...

Your underestanding and consideration of my present background would be greatly appreciated.

Comment 6 Ta-chang 2013-10-16 23:13:25 UTC
If you can, please reporoduce and investigate this issue on your side.


Note You need to log in before you can comment on or make changes to this bug.