On Mon, Nov 08, 1999 at 07:25:58PM -0500, [EMAIL PROTECTED] wrote
> I get the following error when using the multi-CD "install" feature of
> dselect.
>
> Wrong disk. I need "Debian GNU/Linux Slink (2.1) 1/4 main binary-i386 section
> 1 SAM19990306", but i found "Debian GNU/Linux Slink (2.1) 1/4 main
> binary-i386 section 1 SAM19990706".
>
> My translation would be that one is dated June 3, 1999....and the other June
> 7, 1999. I have made bold the part that tells me this. Does any one
> agree/disagree....is this a reason for not letting me install?? Is there a
> way around it?
>
Assuming that the disks you have are the same disks that you used when you
selected "Update" from the dselect menu and that they are a "matched pair",
then they are defective.
During the "Update" step the multi-CD access method reads the
Packages.cd.gz files on your CD, which contain entries for each
package saying which CD they are on; dselect looks at the file
.disk/info on each CD to find out its name. The message you received
indicates that the name on the CD you are using
("Debian GNU/Linux Slink (2.1) 1/4 main binary-i386 section 1 SAM19990706")
is different to the name that dselect found in Packages.cd.gz
("Debian GNU/Linux Slink (2.1) 1/4 main binary-i386 section 1 SAM19990306")
If you have disks from two different pressings (i.e., disk 1 and disk 2 came
from different sources, or different master sets from the same source) try
installing a basic system using only disk 1 (repeat the "Update" step using
only CD 1), and then after installation use apt to access the CDs (run
apt-cdrom add for each disk, then use apt-get or dselect's apt method to
install your software).
If you get the same problem when using CD1 alone, then the disk really is
badly mastered and you should look for a replacement, although you should
still be able to mount the CD by hand and use the "apt" or "mounted" dselect
methods, and then use apt-cdrom as above to access packages from both CDs.
> Also, I get the following error with dselect on occasion right before my NEW
> 40x CDROM makes clicking sounds:
>
> hdb: irq timeout: status = 0xd0
> hdb: ATAPI reset complete
>
> This error is not always the same, the part in bold varys from time to time.
> When this error happens three times in a row, I get another error something
> like "I/O error in Sector xxxxx."
>
Could be marginal hardware, a marginal CD or dodgy cabling. Some older
CDROMs have trouble with some CDRs, and some CDROMs seem to have a way of
falling apart on or shortly after their birthday.
John P.
--
[EMAIL PROTECTED]
[EMAIL PROTECTED]
"Oh - I - you know - my job is to fear everything." - Bill Gates in Denmark
