Description of problem: set other mirror from XFCE or other failed: ..retrieving failed: wget failed: exited with 8 no metadata found for medium "Core Release Debug (distrib47)" ...retrieving failed: wget failed: exited with 8 issue its also add new not dissable or set other as default. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3.
Created attachment 15323 [details] issue set mirror other
This is clearly a MIRRORs issue. CC'ing sturmvogel & Morgan who know more about this.
Summary: ..retrieving failed: wget failed: exited with 8 no metadata found for medium "Core Release Debug (distrib47)" ...retrieving failed: wget failed: exited with 8 => retrieving failed: wget failed: exited with 8 on all nominated mediaCC: (none) => fri, sturm-fr
Yes, can be a mirror problem. Try setting mirror http://mirror.accum.se/ see details how to in https://wiki.mageia.org/en/Mageia_9_Errata#Downloading_software You could also try another downloader: curl or aria2 How to change downloader is described at same link (the example is chioosing wget)
Source RPM: mageia - edit mirror in settings. => (none)
CC'ing also DaveH who is something of a MIRRORS expert. If you reply, Dave - keep any advice simple, please;
CC: (none) => davidwhodgins
>Yes, can be a mirror problem. Well, there's no detail here on the file wget is failing on, but I'm getting the same problem trying to do a fresh install from cauldron, and the wget 8 failure is occurring on the pubkey files in spite of the fact that the firles are there in the repository and have correct ownership and permissions. In a thread in dev Jose suggested removing all the pubkey files, and so far this is working (the install hasn't finished yet). I don't yet know why this should have worked (if it really did), and why these files should be in cauldron if they block install. But it may be germane here.
CC: (none) => ftg
First, if I remember correctly, not all mirrors carry the debug repos, especially for cauldron. The output of "urpmq --list-url" can be used to see which mirror it's using. One mirror that does have the debug repos is Princeton. http://mirror.math.princeton.edu/pub/mageia/distrib/cauldron/x86_64/media/debug/core/ Check the mirror that's being selected. If it doesn't have the debug and you need the debug repos, you'll have to remove the media that have already been added "urpmi.removemedia -a" as root, then in rpmdrake add a specific mirror by selecting Options, then Media Manager, then File, then Add a specific media mirror and follow the prompts. The other possibility is a timing issue. In a stable release, the release repo does not get updated, and the updates repo gets things copied from the testing repo, so the meta data for those repos are always available. In the testing repos for a stable release, and all repos for cauldron, the meta data gets rebuilt every time a package is built for that repo. That can and does lead to race conditions where rpmdrake gets the name of the file containing the meta data such as http://mirror.math.princeton.edu/pub/mageia/distrib/cauldron/x86_64/media/debug/core/release/media_info/20260120-223558-hdlist.cz but by time it goes to actually download it, that file has been deleted, having been replaced by a newer file. For people using cauldron, or people using the testing repos, it may mean having to make multiple attempts to get the meda added.
Just fyi, from "man wget" the message for that exit status means ... 8 Server issued an error response. For Mageia mirrors, that is almost always file not found.
CC: (none) => stephengermany
...retrieving failed: wget failed: exited with 5 unable to access the distribution medium (no media.cfg file found) Medium: distrib (https://ftp.sun.ac.za/ftp/pub/mirrors/mageia/distrib/10/x86_64)
Unable to add medium, errors reported: ...retrieving failed: wget failed: exited with 8 no metadata found for medium "Core Release Debug (distrib2)" ...retrieving failed: wget failed: exited with 8 no metadata found for medium "Core Updates Debug (distrib4)" ...retrieving failed: wget failed: exited with 8 no metadata found for medium "Core Updates Testing Debug (distrib6)" ...retrieving failed: wget failed: exited with 8 no metadata found for medium "Core Backports Debug (distrib8)" ...retrieving failed: wget failed: exited with 8 no metadata found for medium "Core Backports Testing Debug (distrib10)" ...retrieving failed: wget failed: exited with 8 no metadata found for medium "Nonfree Release Debug (distrib12)" ...retrieving failed: wget failed: exited with 8 no metadata found for medium "Nonfree Updates Debug (distrib14)" ...retrieving failed: wget failed: exited with 8 no metadata found for medium "Nonfree Updates Testing Debug (distrib16)" ...retrieving failed: wget failed: exited with 8 no metadata found for medium "Nonfree Backports Debug (distrib18)" ...retrieving failed: wget failed: exited with 8 no metadata found for medium "Nonfree Backports Testing Debug (distrib20)" ...retrieving failed: wget failed: exited with 8 no metadata found for medium "Tainted Release Debug (distrib22)" ...retrieving failed: wget failed: exited with 8 no metadata found for medium "Tainted Updates Debug (distrib24)" ...retrieving failed: wget failed: exited with 8 no metadata found for medium "Tainted Updates Testing Debug (distrib26)" ...retrieving failed: wget failed: exited with 8 no metadata found for medium "Tainted Backports Debug (distrib28)" ...retrieving failed: wget failed: exited with 8 no metadata found for medium "Tainted Backports Testing Debug (distrib30)" ftp://ftp.sun.ac.za/pub/mirrors/mageia/distrib/10/x86_64/media/core/backports_testing
https://ftp.sun.ac.za/ftp/pub/mirrors/mageia/distrib/cauldron/x86_64/media/debug/ That mirror is one that does not carry the debug repositories. If "urpmq --list-media active" shows all of the release repos have been added, that's all that's required for the installation to work. If you need the debug repos then choose a different mirror manually. Keep in mind, the speed that you can download things from a mirror depends more on the upload speed of that mirror rather then the geographical distance. A far away mirror such as https://distrib-coffee.ipsl.jussieu.fr/pub/linux/Mageia/ may actually be faster then a closer mirror.
@Lars please try the Swedish mirror as I suggeted in comment 3. It have all repos, is always quickly updated, fast, and local to us.
Created attachment 15343 [details] Issue boot not works Can you confirm sweden works? Its reboot to early not install everthing and give error.
* From the screenshot first rows I note filesystem problems! * And that error 5 is *local*, due to that. So either the disk is bad or the filesystem have been damaged by getting detached in use or other havoc. BTW you seem to have a lot of discs and partitions. Experimenting? :-) You should save any valauble data to other media or cloud, then test that drive thoroughly or discard it. Then make a new fresh install. I did several updates to three machines today, using http://mirror.accum.se/ as usual, no problems.
Setting this bug invalid as no system can work on a damaged filesystem/drive.
Resolution: (none) => INVALIDStatus: NEW => RESOLVED
HDD works with mageia 9 installed 1054 updates. Issue here its reboot before everthings is installed its can be a bug.
its possible to add software that make recovery possible windows have it. rsync or Mageia Control Center's Backup drakbackup but i think need more space.
(In reply to lars martin from comment #15) > HDD works with mageia 9 installed 1054 updates. Just because something else works on a different place on disk does not mean the whole disk is OK. You should at least check the SMART status of the drive, and also let it perform a thorough test. > Issue here its reboot before everthings is installed its can be a bug. No one else have reported that so far. Apart from checking the drive, also let memory test run overnight, and let it use all CPU cores. Apart from memory modules failing, I also have had main board and also intermittent single core CPU failure - caught by getting "memory failures" just for a specific core in the CPU. I also have had "disk failures" because if bad cables, both power and data, to drives. (In reply to lars martin from comment #16) > its possible to add software that make recovery possible windows have it. > > rsync or Mageia Control Center's Backup drakbackup but i think need more > space. There are several methods for recovery Maybe you want to learn to use LVM, so you can take snapshots efficiently. (web search LVM snapshot) Of course you need to install the system using LVM then (supported by our installer)
Created attachment 15350 [details] Issue fix? But how to fix it? Its did not possible to fix?
Created attachment 15351 [details] How to fix?
You need to run fsck on the filesytem in the partition. For example, "fsck /dev/sda1" or "/dev/nvme0n1p1". I'd run it for all of the partitions you're using for that install.
Lars, det är uppenbart att du saknar grundläggande kunskaper i att förstå, hantera och felsöka linuxsystem. Dina insatser hjälper oss inte att utveckla Mageia. - tvärtom lägger vi en massa tid på att försöka förstå dig och hjälpa dig. Leta istället upp någon bra bok att läsa, och ett forum för nybörjare, och utbilda dig och öva på någon känd stabil distribution (Mageia 9, en släppt Fedora, Ubuntu, eller annan...) --- Lars, it is obvious you do not know basics of understanding, handling and fixing Linux systems. Your efforts here do not help us to develop Mageia. - On the contrary, it consumes much time to both understand you and help you. Instead, you should find a good book to read, a forum for beginners, and use a known stable distribution to practice on. (Mageia 9, or a released Fedore, Ubuntu, whatever...)
CC: (none) => lewyssmith