Re: Unusual filesystem/memory corruption

2001-08-12 Thread Mike Brownlow
John Toon wrote: > On 11 Aug 2001 21:06:52 -0500, Mike Brownlow wrote: > > VIA. It's a KT133 chipset on a Asus A7V. The drives are on the ATA100 > > promise controller. > > That's very similar to mine (Abit KA7-100, with a VIA chipset, Highpoint > hard disk controller). > > If you build a correct

Re: Unusual filesystem/memory corruption

2001-08-12 Thread Mike Brownlow
Robert Waldner wrote: > >> > On 11 Aug 2001 16:37:58 -0500, Mike Brownlow wrote: > >> > > I suspect hardware failure caused it, but there are still a few > >> > > software > >> > > unknowns. I'm starting to lean on corruption due to using -m16 for > >> > > hdparm. Any other suggestions appreciated

Re: Unusual filesystem/memory corruption

2001-08-12 Thread Robert Waldner
>> > On 11 Aug 2001 16:37:58 -0500, Mike Brownlow wrote: >> > >> > > I suspect hardware failure caused it, but there are still a few software >> > > unknowns. I'm starting to lean on corruption due to using -m16 for >> > > hdparm. Any other suggestions appreciated... Just for good measure, I wou

Re: Unusual filesystem/memory corruption

2001-08-12 Thread John Toon
On 11 Aug 2001 21:06:52 -0500, Mike Brownlow wrote: > VIA. It's a KT133 chipset on a Asus A7V. The drives are on the ATA100 > promise controller. That's very similar to mine (Abit KA7-100, with a VIA chipset, Highpoint hard disk controller). If you build a correctly configured 2.4.[3-8] kernel

Re: Unusual filesystem/memory corruption

2001-08-11 Thread Mike Brownlow
Michael Perry wrote: > Quoting John Toon on Sun, Aug 12, 2001 at 12:04:20AM +0100: > > On 11 Aug 2001 16:37:58 -0500, Mike Brownlow wrote: > > > > > * hdparm options: -m16 -d1 > > > * Machine is behind firewall, and has few services for external > > >access > > > > > > I suspect hardware fa

Re: Unusual filesystem/memory corruption

2001-08-11 Thread Mike Brownlow
John Toon wrote: > On 11 Aug 2001 16:37:58 -0500, Mike Brownlow wrote: > > > * hdparm options: -m16 -d1 > > * Machine is behind firewall, and has few services for external > >access > > > > I suspect hardware failure caused it, but there are still a few software > > unknowns. I'm starting t

Re: Unusual filesystem/memory corruption

2001-08-11 Thread Michael Perry
Quoting John Toon on Sun, Aug 12, 2001 at 12:04:20AM +0100: > On 11 Aug 2001 16:37:58 -0500, Mike Brownlow wrote: > > > * hdparm options: -m16 -d1 > > * Machine is behind firewall, and has few services for external > >access > > > > I suspect hardware failure caused it, but there are still

Re: Unusual filesystem/memory corruption

2001-08-11 Thread John Toon
On 11 Aug 2001 16:37:58 -0500, Mike Brownlow wrote: > * hdparm options: -m16 -d1 > * Machine is behind firewall, and has few services for external >access > > I suspect hardware failure caused it, but there are still a few software > unknowns. I'm starting to lean on corruption due to using

Unusual filesystem/memory corruption

2001-08-11 Thread Mike Brownlow
I run debian/unstable and I know the risks involved with that. Woke up and I found my computer to seem to be operating normally. The screensaver was on and running. I clicked the mouse to turn it off and my normal apps were still running. I used xmms open->dir to pop in some mp3s, and the filesys