Bug#279320: Package: installation-reports
Package: installation-reports
Debian-installer-version: 23-Oct-2004 Debian GNU/Linux testing "Sarge" - Official Snapshot i386 Binary-1 CD (downloaded using jigdo via ftp.coe.psu.ac.th)
uname -a: never got to a shell prompt outside of the testing CD itself
Date: 2-Nov-2004 09:00 GMT
Method: Booted off of CD listed above
Machine: Dell Inspiron 3700 laptop
Processor: Pent III 450Mhz
Memory: 192 Mb
Root Device: never got this far
Root Size/partition table: never got this far
Output of lspci and lspci -n: never got this far
Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
Initial boot worked: [ O]
Configure network HW: [ O]
Config network: [ O]
Detect CD: [ O]
Load installer modules: [ E]
Detect hard drives: [ ]
Partition hard drives: [ ]
Create file systems: [ ]
Mount partitions: [ ]
Install base system: [ ]
Install boot loader: [ ]
Reboot: [ ]
Comments/Problems:
FAILURE
Trying to install sarge using sarge installer on official testing CD #1. When it comes time to "Load installer components from CD" get this error:
Failed to copy file from CDROM.
&
No valid Debian CD-ROM
Using left_alt-f4, I see the following:
anna [3143]: grep:
/cdrom/dists//Release:
No such file or directory
I went to the shell using left_alt-f2 and could see there was a /cdrom/dists directory which contained a "sarge" subdirectory, and some files (not subdirectories) like "testing", "stable", and "frozen". I tried unmounting and remounting the cdrom as suggested in a workaround in posting called "Bug#250323: more information", but this did not help.
I went through the file cdrom-retriever and saw maybe the $suite variable might be null, which would give the // seen in the error message, but I'm totally new to all of this so I don't know if that's a real clue.
I also did an md5sum check on my CD and all of them were OK, except some files listed in md5sum.txt were missing altogether on the CD, for example "/dists/testing/main/debian-installer/binary-i386/Packages" and ".../Packages.gz". However, as copies of these are kept in the /dists/sarge tree, I assumed this was not the issue.
Did I miss a parameter or something where you set the directory it needs to be dists/sarge?
-Tony Stallone
Reply to: