Another MDV legacy. If you attempt to do a 64-bit NFS install, pointing the directory to "cauldron", the install program loads and starts successfully. However, as soon as you get to "Package Group Selection", the install fails, saying "An error occurred; unable to access medium 'Core 32-bit Release'" Looking in /tmp/media.cfg, Core 32-bit Release is in there with a path of ../../i586/..... The /tmp/ddebug.log shows "adding medium Core 32-bit Release" with no errors. The only thing on VT 3 is "urpmi error: unable to access Core 32-bit Release" I'm not sure what the CWD is when urpmi interprets the above path, but I'm guessing that the path was correct when the media were added, but isn't correct when urpmi tries to use them. The upshot is that 64-bit NFS installs are impossible.
can you attach your /root/drakx/report.bug.gz ?
Source RPM: (none) => drakx-installer
Created attachment 746 [details] report.bug Here you go.
Attachment 746 mime type: application/octet-stream => application/text-plain
Assignee: bugsquad => thierry.vignaud
@ Thierry another ping, for the same reason
CC: (none) => marja11
3-monthly ping
Hi, This bug was filed against cauldron, but we do not have cauldron at the moment. Please report whether this bug is still valid for Mageia 2. Thanks :) Cheers, marja
Keywords: (none) => NEEDINFO
Whiteboard: (none) => MGA2TOOKeywords: NEEDINFO => (none)
Please look at the bottom of this mail to see whether you're the assignee of this bug, if you don't already know whether you are. If you're the assignee: We'd like to know for sure whether this bug was assigned correctly. Please change status to ASSIGNED if it is, or put OK on the whiteboard instead. If you don't have a clue and don't see a way to find out, then please put NEEDHELP on the whiteboard. Please assign back to Bug Squad or to the correct person to solve this bug if we were wrong to assign it to you, and explain why. Thanks :) **************************** @ the reporter and persons in the cc of this bug: If you have any new information that wasn't given before (like this bug being valid for another version of Mageia, too, or it being solved) please tell us. @ the reporter of this bug If you didn't reply yet to a request for more information, please do so within two weeks from now. Thanks all :-D
Somehow missed the later posts on this. I'll retest.
I wonder if there's any relationship with Bug 9824.
Still happening in current cauldron.
Since only current installer can be fixed (5beta1 or higher) and unclear that it applies: @anyone: please mark whiteboard as '5beta1' (or higher if still valid), wiping NEEDINFO and please change back version to 'Cauldron'. Otherwise this one should be closed.
Version: Cauldron => 4Keywords: (none) => NEEDINFOWhiteboard: MGA2TOO => MGA4TOO
I'll retest.
NFS installs now crash well before the original error. After stage 2 gets loaded, you get a "Sending termination signals" and the machine reboots before any diagnostic info can be obtained. Booting a rescue image via NFS works OK, but no root partition was ever created on the target disk so no trace of the error remains.
Whiteboard: MGA4TOO => 5Beta1Keywords: NEEDINFO => (none)Version: 4 => Cauldron
I'll retest...
This now fails in a different way. The stage 1 install now stalls because the exported NFS directory, while correct and correctly mounted from other systems, cannot be found by the installer. tty3 contains the correct NFS name, but claims that the mount fails with "no such file or directory". It's trying to mount the NFS directory on /tmp/media, which does not exist. If I go to tty2 and mkdir /tmp/media, it still fails the same way. If I use a FQDN for the NFS host, still fails the same way. If I use an IP address it claims that the result from mount is "invalid parameter". Can this please be addressed before 8 freezes ? This bug is now 10 years old.
Summary: x86_64 NFS install can't find Core 32-bit Release media => x86_64 NFS install can't mount the NFS directory