On Wed, 29 Dec 1999, Matthew Jacob wrote:

> 
> 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 think it may be a combination of bad disklabel and weirdness with the
IDE DMA. It's a cheap Western Digital Spartan drive so it may be doing
funky things. Checking the message log I see: 

Dec 29 11:40:18 team5 /netbsd: pciide0:0:0: lost interrupt
Dec 29 11:40:22 team5 /netbsd:  type: ata
Dec 29 11:40:22 team5 /netbsd:  c_bcount: 1024
Dec 29 11:40:23 team5 /netbsd:  c_skip: 0
Dec 29 11:40:23 team5 /netbsd: pciide0:0:0: Bus-Master DMA error: missing
interrupt, status=0x60
Dec 29 11:40:23 team5 /netbsd: wd0d: DMA error writing fsbn 1838610 of
1838610-1838611 (wd0 bn 2866770; cn 2844 tn 0 sn 18), retrying
Dec 29 11:40:23 team5 /netbsd: wd0: soft error (corrected)

I may just reinstall again and pay more attention to the
partitioning of the disk.

> 
> 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
> 
 
I have an ITI-6100N SCSI card but the AlphaPC 164 doesn't recognize the
card. I would much rather have that working than the WD drive. 

Thanks,
Joe