Bug 591369 - unable to fetch DUD from nfs
unable to fetch DUD from nfs
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: anaconda (Show other bugs)
All Linux
high Severity high
: beta
: ---
Assigned To: Martin Sivák
Release Test Team
Depends On: 592225
  Show dependency treegraph
Reported: 2010-05-11 23:08 EDT by CAI Qian
Modified: 2010-07-02 16:49 EDT (History)
2 users (show)

See Also:
Fixed In Version: anaconda-13.21.42-1
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-07-02 16:49:09 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
screenshot (15.80 KB, image/png)
2010-05-12 02:38 EDT, CAI Qian
no flags Details

  None (edit)
Description CAI Qian 2010-05-11 23:08:57 EDT
Description of problem:
DUD failed for failed for NFS method,
INFO:  file location: nfs:
INFO:  mounted loopback device /tmp/dirvers on /dev/loop6 as /tmp/dd.img
ERROR: can't find driver disk identifier, bad driver disk
ERROR: not a valid driver disk

Version-Release number of selected component (if applicable):
RHEL6 public beta 1

How reproducible:
Comment 1 Martin Sivák 2010-05-12 02:32:38 EDT
Does it really say "dirvers"? And can you put the directory structure of the driverdisc here too?
Comment 2 CAI Qian 2010-05-12 02:38:53 EDT
Created attachment 413337 [details]

Yes, it said drivers.
Comment 3 CAI Qian 2010-05-12 02:40:13 EDT
The structure is the same here too.
# find ./
Comment 4 CAI Qian 2010-05-15 00:25:24 EDT
Martin, when Ctrl-Z dropped in a busybox, I can see there is no networking, so the NFS did not mount.
Comment 6 Martin Sivák 2010-05-18 10:37:15 EDT
Most of the problems should be fixed in next anaconda version anaconda-13.21.42-1
Comment 8 releng-rhel@redhat.com 2010-07-02 16:49:09 EDT
Red Hat Enterprise Linux Beta 2 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.

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