Martin Husemann wrote:
> On Tue, May 10, 2005 at 10:59:11AM +0200, Jukka Salmi wrote:
> > Did you newfs / format the FAT file system after seeing the corruption
>> with NetBSD and before not seeing it with Linux?

Yes. May be a good point. Would it be possible that a corrupted FAT had 
inodes (or whatever it is called on that FS) pointing to *another* 
partition? I find this unbelievable, but you never know...

 >> In case you see corruption again, try restarting the system without
>> reformatting the file system in question. If the corruption is gone after
>> reboot, this is probably definitely bad hardware.

In both cases, the boot error was reproductible so, if I understand well 
your point, this may not be a RAM issue.

>>All things considered, this sound like bad hardware (RAM?) to me. Did you
>>already run memory tests?
> 
> That was my first thought too.

Thanks. I'll try this.

> Another possibilty is that you got your partitions wrong and windows
> overwrites parts of your NetBSD install.

That was my first idea. But I'm sure that it was not the case for my
second installation, and somewhat dubious about the first one: as I
wrote, the NT partition stands *between* the FAT and the NetBSD ones.
I assume that if it was something with the partitions, the NT one
should have been impacted too.

Thank you for your answers,

sL