Bug 264041
| Summary: | Anaconda reports problem in umounting /mnt/source in FC7.90 | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | cdputnam <cdputnam> |
| Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> |
| Status: | CLOSED CANTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 8 | ||
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2007-09-21 17:54: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
cdputnam@ucsd.edu
2007-08-29 16:24:46 UTC
I have been able to work around this problem by adding "noshell" to the
boot commands. I'm having additional problems later on:
File "/usr/lib/python2.5/pickle.py",
line 971, in load_string
self_append(rep.decode("string-escape"))
File "/usr/lib/python2.5/pickle.py",
line 858, in line dispatch[key](self)
....
HAve you verified your media using the mediacheck/ The media passed the mediacheck that runs prior to install (I presume it check the entire DVD). I did not check the SHA1SUM of the downloaded iso image used to burn the DVD. I currently believe that the media was at fault as the install logs (under "noshell") complained about not being able to recognize the format of some png images. Because I was having DVD issue, I tried to and successfuly installed Fedora 7 using the LiveCD (which I did test via SHA1SUM). The Fedora 7 DVD iso, which I also only checked via the media test, had also given me a lot of grief. So sorry for the noise. But I am curious as to why the media test prior to install didn't flag either DVD as bad--does it use a less sophisticated algorithm than SHA1SUM?. Unfortuantely, it's just that different access patterns cause drives to act differently. The medaicheck is an md5sum across the data area of the CD -- but sometimes complete linear reads work fine and it's only seeking back and forth across the disc that causes problems :( I'd suggest trying different DVD media and/or burning at lower speeds as often that helps in cases like this. |