| Summary: | OS initial installation fail when mounting VFAT filesystem on mdadm RAID 1 | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Ta-chang <ta.chang1972> |
| Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> |
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 19 | CC: | agk, amulhern, anaconda-maint-list, dledford, dshea, g.kaviyarasu, Jes.Sorensen, jonathan, mkolman, sbueno, ta.chang1972, vanmeeuwen+fedora |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i686 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-10-17 13:40:40 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Ta-chang
2013-10-16 11:30:16 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 > 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. 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 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. 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.
If you can, please reporoduce and investigate this issue on your side. |