Description of problem: I've been attempting a net install using Cauldron x86_64 boot.iso boot.iso 03/17/16 And I keep getting error messages. Mostly with the fact that the media is not all there. Typical errors are: Retrieving Failed: curl failed: exited with 56 No metadata found for medium "tainted updates" Retrieving Failed: curl failed: exited with 56 No metadata found for medium "nonfree 32bit release" Retrieving Failed: curl failed: exited with 56 Repo is mirrors.kernel.org
(In reply to William Kenney from comment #0) > > No metadata found for medium "nonfree 32bit release" > Retrieving Failed: curl failed: exited with 56 > > Repo is mirrors.kernel.org This bug is most likely invalid. There is nothing we can do when a mirror is temporarily having problems. However, if it also happens with a different mirror, then please put report.bug on a USB key as explained here: https://wiki.mageia.org/en/Triage_guide#Traditional_installer compress it with xz: xz report.bug and then attach report.bug.xz to this bug report. Thanks :-)
Status: NEW => UNCONFIRMEDCC: (none) => marja11Ever confirmed: 1 => 0
Can we use: distrib-coffee.ipsl.jussieu.fr as the gold standard. If it fails there twice in a row separated by an hour or so it's definitely broke?
(In reply to William Kenney from comment #2) > Can we use: > > distrib-coffee.ipsl.jussieu.fr > > as the gold standard. If it fails there twice in a row separated by an hour > or so it's definitely broke? Even distrib-coffee has a hiccup from time to time, albeit less often than mirrors.kernels.org. Besides, it doesn't have a lot of bandwidth, setting it as standard will not only make many QA testers use it, but others who follow QA ml or bugs ml, too, and that might snowball into distrib-coffee getting too overloaded. If it is impossible to test with two different mirrors (preferably both tier one, or at least syncing from different tier1 mirrors), can you then at least check http://mirrors.mageia.org/status between your attempts and after your last attempt? For traditional installer bugs, we always need logs, it would be great if you'd manage to always attach them. https://wiki.mageia.org/en/Triage_guide#Traditional_installer
(In reply to Marja van Waes from comment #3) > Even distrib-coffee has a hiccup from time to time, albeit less often than > mirrors.kernels.org. FWIW both of these mirrors failed today to install using boot.iso. > For traditional installer bugs, we always need logs Well that would be nice but if the system fails during the install there's no way to get to the logs. At least that I know of. I'll try again in a couple days. I really await the Live media as a stake in the ground.
(In reply to William Kenney from comment #4) > > Well that would be nice but if the system fails during the install > there's no way to get to the logs. At least that I know of. > You mean it totally freezes? I understood it was after the partitioning step that you got those errors, correct? If you system didn't totally freeze, then you can grab logs by inserting a USB key, switchig to TTY2, and tyoing "bug" Please read https://wiki.mageia.org/en/Triage_guide#Traditional_installer it gives additional information for when the above doesn't work.
Keywords: (none) => NEEDINFO
(In reply to Marja van Waes from comment #5) > (In reply to William Kenney from comment #4) > If you system didn't totally freeze, then you can grab logs by inserting a > USB key, switchig to TTY2, and tyoing "bug" > > Please read https://wiki.mageia.org/en/Triage_guide#Traditional_installer > it gives additional information for when the above doesn't work. Only the DE ( Plasma5 & IcdWM ) desktops freeze. I am waiting for the next set of Live media before I revisit all these M6 bugs.
Successful install on real hardware using latest x86_64 boot.iso today. Marking as resolved.
Status: UNCONFIRMED => RESOLVEDResolution: (none) => FIXED