Something like this should very definitely not happen on a fresh lightly
loaded system that has been correctly started, etc..

What's your disklabel setup? I would suspect, in the following order of
likelihood

	Bad disklabel (overlapping partitions)
	Bad fstab (missing entries to cause fsck to be run)
	Improper shutdown that somehow missed the 'clean' bit
	Possible wierdness with IDE DMA
	'Other' 1.4.X bugs

I'd approach this from the point of:

	Check the files/labels/etc.
	Install the latest snapshot, or at least a kernel from same
	If you have a SCSI controller/disk that's bootable, try that

		

On Wed, 29 Dec 1999, Joe wrote:

> I just made a fresh install and while extracting pkgsrc.tar.gz I get the
> following panic:
> 
> mode = 010064, inum = 1349143, fs = /usr
> panic: ffs_valloc: dup alloc
> Stopped in tar at	Debugger+0x4:	ret	zero,(ra)
> db>
> 
> Would anybody happen to know what kind of problem I am dealing with? I
> attached dmesg to show what kind of system it is. Prior to the panic I
> was getting soft errors pci-ide bus-master device ( going to fast for me
> to pick up exact message). I would appreciate any info or help. 
> 
> Thanks, 
> Joe
>