Geek Answers Handbook

Failed to read package metadata. This may be due to the lack of a repodata directory. Make sure the installation tree is created correctly.

I am new to installing centos. I downloaded the minimum version of centos 6.5, about 339.7 MB in size. I am trying to install this using the GUI, but after selecting the disk option, I got an error that appears after selecting the country. This is a complete message,

Unable to read package metadata. This may be due to missing repodata directory. Please ensure that your install tree has been correctly generated. Failare: repodata/743fec56b2af0ce8d6ec82c47a4efafc2a4d18cddfa9683f29611cb18d1a33de-primary.sqlite.bz2 from anaconda-CentOS-201311271240.i386: [Ermo 256] No more mirrors to try.

Sorry, but I'm new here, so I can’t post the exact image here.

+9
centos centos6
source share
4 answers

I believe that I had the same problem and I was able to solve it.

There are no extension files in the / repodata folder and do not match their full names in the TRANS.TBL file in the same directory.

Rename all files according to the TRANS.TBL file, then try installing again.

Please let everyone know if this works for you.

In the past, I would just put a URL pointing to the correct files on the server, I feel that most people use this workaround and why it is not as hot as it should be. I hope this will be fixed in .ISO.

Thanks,

Yourfriend

+22
source share

It worked for me. I renamed all 8 files. that is, 0e371b19e547b9d7a7e8acc4b8c0c7c074509d33653cfaef9e8f4fd1d62d95de 0e371b19e547b9d7a7e8acc4b8c0c7c074509d33653cfaef9e8f4fd1d

The correct file name is indicated in the file "repomd" in the repodata folder example - location href = "repodata / b124f0ec5323cfee56b420906a3103f0daef656dde3f7ac8220120aa7504e57a-primary.xml.gz"

+9
source share

I had exactly the same problem; in the "repodata" directory, the file "repmod" xml is opened. The distorted file name in the repmond xml file. Matching lines found. 8 files specified in the .xml file were renamed. and he worked like a charm

Thanks to "Friend"

+1
source share

I have the same problem. Even if you manage to go through this step, you will later encounter other errors related to file names.

The main reason was using Unetbootin to create bootable media. I switched to Rufus and now everything works fine.

0
source share

More articles:


All Articles