RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1371854 - "FSError: umount failed" when installation manually with GUI
Summary: "FSError: umount failed" when installation manually with GUI
Keywords:
Status: CLOSED DUPLICATE of bug 1322439
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: anaconda
Version: 7.3
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Anaconda Maintenance Team
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-31 09:31 UTC by Yanqiu Zhang
Modified: 2016-09-01 14:14 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-09-01 14:14:27 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
anaconda.log (4.29 KB, text/plain)
2016-08-31 09:31 UTC, Yanqiu Zhang
no flags Details
anaconda-tb-Kn5G7L (225.22 KB, text/plain)
2016-08-31 09:34 UTC, Yanqiu Zhang
no flags Details
anaconda-yum.conf (373 bytes, text/plain)
2016-08-31 09:35 UTC, Yanqiu Zhang
no flags Details

Description Yanqiu Zhang 2016-08-31 09:31:35 UTC
Created attachment 1196274 [details]
anaconda.log

Description of problem:
"FSError: umount failed" when installation manually with GUI

Version-Release number of selected component (if applicable):
os tree:RHEL-7.3-20160825.1

How reproducible:
100%

Steps to Reproduce:
1.Download vmlinuz and initrd.img files from tree and put them in /boot
2.Edit /etc/grub.d/40_custom
3.Run #grub2-mkconfig -o /boot/grub2/grub.cfg
4. Reboot the machine and choose the new boot option to install the system

Actual results:
When the GUI sreen shows, a window pops up prompting error:"This program has encountered an unknown error..."
Clicked "More info", it shows "FSError: umount failed". Pls refer to attachment: anaconda.log.

Expected results:
This error should not occur, users should be able to proceed the language selecting and other operations 

Additional info:

Comment 1 Yanqiu Zhang 2016-08-31 09:34:28 UTC
Created attachment 1196275 [details]
anaconda-tb-Kn5G7L

Comment 2 Yanqiu Zhang 2016-08-31 09:35:13 UTC
Created attachment 1196277 [details]
anaconda-yum.conf

Comment 3 Yanqiu Zhang 2016-08-31 12:48:05 UTC
Sorry, I find an another important condition to reproduce this issue in test steps, there is a installation cd in the cdrom.

Comment 4 Jan Stodola 2016-09-01 14:14:27 UTC
This looks like bug 1322439, so I'm going to close it as a duplicate.
Feel free to reopen if you think this is a different issue.

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


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