Originally posted as "Problem installing Centos 6.4/6.5 from USB stick seen as HDD by BIOS"
Further testing seems to indicate there is some odd issue with the file names in the repodata directory.
During installation, after the partitioning stage, anaconda logs an error trying to access the file repodata/0dafccfdbf892f02acca8267ade4bdcee7280a682e65dc7e29145f3341fd7a8c-primary.sqlite.bz2
checking the USB drive as well as the downloaded ISO shows that the file is named repodata/0dafccfdbf892f02acca8267ade4bdcee7280a682e65dc7e29145f3341fd7a8c
It seems that the filenames are truncated after the first dash e.g. b4e0b9342ef85d3059ff095fa7f140f654c2cb492837de689a58c581207d9632 should be b4e0b9342ef85d3059ff095fa7f140f654c2cb492837de689a58c581207d9632-c6-x86_64-comps.xml
Renaming the files on the USB drive according to the information in repodata/TRANS.TBL appear to fix the problem and anaconda was able to proceed to package selection.
The DVD ISO checksum is correct. I also compared the checksum files from another server in case the mirror I used had an outdated/bad version.
Is the problem with the ISO, or is anaconda supposed to had figured out the filename based on TRANS.TBL but not doing so.
The problem originally started with a C6.4 install but I've wiped that ISO so am unable to verify if the cause is the same.
From: Emmanuel Noobadmin centos.admin@gmail.com
checking the USB drive as well as the downloaded ISO shows that the file is named repodata/0dafccfdbf892f02acca8267ade4bdcee7280a682e65dc7e29145f3341fd7a8c It seems that the filenames are truncated after the first dash e.g. b4e0b9342ef85d3059ff095fa7f140f654c2cb492837de689a58c581207d9632 should be b4e0b9342ef85d3059ff095fa7f140f654c2cb492837de689a58c581207d9632-c6-x86_64-comps.xml
My ISO seems fine... 83221db52687c7b857e65bfe60787838 CentOS-6.5-x86_64-bin-DVD1.iso # mount -o loop CentOS-6.5-x86_64-bin-DVD1.iso /mnt/cdrom # ls /mnt/cdrom/repodata/ 0dafccfdbf892f02acca8267ade4bdcee7280a682e65dc7e29145f3341fd7a8c-primary.sqlite.bz2 495d3964f864fbab835ea1afb8a5272352cd12ded13d607205109fefaddd0ab6-primary.xml.gz 594d4bb4a79ed01d66635adbcf76c45ca4a85b30fc3e3c3c28316e64f0a83f21-filelists.sqlite.bz2 5af8199bd0ffb441c34ef946582d0d06c1ad770755e631690771e0bceb0ad222-other.xml.gz 6ac72f497df511cc2dc584eaa59779884fc572c1618e7c62dbd631ab8babf53d-filelists.xml.gz TRANS.TBL b4e0b9342ef85d3059ff095fa7f140f654c2cb492837de689a58c581207d9632-c6-x86_64-comps.xml ca525c73086186bfcb81ad9edd45796026dac7e4e50524e0f2daf901532aaf66-c6-x86_64-comps.xml.gz fdd542ef36b0cde54ee0521fae90b98911db06483163aa1c049995b6d109349b-other.sqlite.bz2 repomd.xml
I did not follow the previous thread but are you putting the iso file on the key or are you extracting the iso content to a folder on the key...?
JD
On 1/23/14, John Doe jdmls@yahoo.com wrote:
I did not follow the previous thread but are you putting the iso file on the key or are you extracting the iso content to a folder on the key...?
USB drive was created using Fedora's LiveUSB Creator which I believe extracts the ISO content. However, viewing the original ISO shows the filenames are already truncated, so I don't think it would had made a difference if the ISO was placed on disk or extracted.
On 01/23/2014 06:23 AM, Emmanuel Noobadmin wrote:
On 1/23/14, John Doe jdmls@yahoo.com wrote:
I did not follow the previous thread but are you putting the iso file on the key or are you extracting the iso content to a folder on the key...?
USB drive was created using Fedora's LiveUSB Creator which I believe extracts the ISO content. However, viewing the original ISO shows the filenames are already truncated, so I don't think it would had made a difference if the ISO was placed on disk or extracted.
If you want to create an installable version of the 6.5 DVD onto a usb key, do it like this:
dd if=<path_to_iso>/ of=<device>
so, if I was in the directory that has the iso and if my usb key was /dev/sdc (note, do not use a partition, but the device name of the key ... this makes the key ONLY a copy of the DVD and all other content is lost), then I would use this command:
dd if=CentOS-6.5-x86_64-bin-DVD1.iso of=/dev/sdc
Then boot from the usb key.
Obviously there is some issue the extraction process on the filesystem / os you are using and the loop mount and / or the livecd creator you are using ... as our ISOs do install and the files are named properly on them to get them to install.
On 1/25/14, Johnny Hughes johnny@centos.org wrote:
dd if=CentOS-6.5-x86_64-bin-DVD1.iso of=/dev/sdc
Then boot from the usb key.
Obviously there is some issue the extraction process on the filesystem / os you are using and the loop mount and / or the livecd creator you are using ... as our ISOs do install and the files are named properly on them to get them to install.
Thanks for pointing out that possibility. The Fedora LiveUSB creator previously worked for a C6.5 LiveCD to HDD install so it never occurred to me that the problem was in that direction. Using the dd method on another CentOS machine with the same ISO worked so it looks like some kind of limitation on Win7 instead.
-
Emmanuel Noobadmin -
John Doe -
Johnny Hughes