Bug 15650
Summary: | NFS installs in 6.x fail on insmod'ing | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Justin Moore <jdm2d> |
Component: | anaconda | Assignee: | Brock Organ <borgan> |
Status: | CLOSED WORKSFORME | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 6.2 | ||
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: | 2000-10-19 22:07:51 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
Justin Moore
2000-08-07 15:40:37 UTC
I also downloaded the updated boot images as specified in the updates/errata section of the support pages. No luck there, either. I tried to use the new boot.img with a local CD, and then (post-install) mount an NFS share. The server logs claim it received a valid and authenticated mount request for the appropriate NFS partition, but an directory listing on the client doesn't find the partition to be mounted. The insmod'ing of the appropriate kernel modules silently fails. Sorry for the constant updates, BTW. Sent to test lab to attempt to reproduce. For whatever reason, the install will bomb in the described manner if the '--dir' specifier does not preceed the NFS directory you want to mount. No idea why the insmod fails if this is left out, though. hmmmm ... we haven't seen that behavior here in our test lab ... could you attach the kickstart file (ks.cfg) you are having the problem with ...? Please reopen this bug if you continue to have problems. |