[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#49517: Potato i386 "problem with file" error on base2_2.tgz

Package: boot-floppies
Version: 2.2.1-1999-10-22

I'll apologise up front for the lack of information here.
Unfortunately, the machine I was using is now unavailable, so I'll
have to work from memory....

When installing potato from scratch, the "Install Base System" option
fails with an error to the effect of "problem with file" on
base2_2.tgz.  (The error message appears on tty1 nicely formated in
the block graphics.)  I couldn't find anything to indicate what the
problem might be.  The install then jumps to the "Make boot floppy"
option, jumping over the "Configure Base System" stage.

Here are a few pieces of potentially useful information.....

	1) I tried using the base14-*.bin 12-floppy set instead of
		base2_2.tgz via NFS.  The same problem existed, and
		the base2_2.tgz file extracted from the floppies
		was identical (I checked) to the one in

		This is probably no surprise given the automated
		process obviously involved :^)

	2) I checked with the ftp.debian.org archives and the files
		are identical, suggesting there's not a problem with
		my mirror.

	3) tar and gunzip seemed happy with the files.

	4) Forcing the install through "Configure Base System" 
		will get you through the reboot, but numerous
		things fail to start correctly, and the system
		seems pretty badly screwed up.  None of the
		errors seemed terribly enlightening (in the
		wee small hours of the morning).

All of the above occurred while trying to install on a Toshiba Tecra
8000 laptop, over PCMCIA (see Bug#49126) via NFS and, subsequently,
via floppies.  However, there was nothing obvious to indicate this
platform or the PCMCIA bugs had anything to do with it.

I'm trying to track down some alternative hardware in order to 
repeat the installation and obtain additional info.  However, this
could take a while, so hopefully the scant info above will give
someone else an idea of where to look.

Reply to: