This happend to me, and the problem was faulty memory. Use memtest86+ to check your memory, or as other users suggested before, was to check for bad cabling by doing dd of your harddisk partition into /dev/null
On Mon, 22 Nov 2004 12:48:09 -0500, Daniel B. <[EMAIL PROTECTED]> wrote: > [EMAIL PROTECTED] wrote: > > > ... > > I've currently set fsck to run pretty much on every other boot. > > > > And just about every time it runs , it informs me that it fixed file > > system errors and reboots the system. > > Is it an IDE disk? Are you running with DMA enabled? > > Some versions of the kernel have a bug with some IDE controllers > that leads to severe disk corruption. > > If it's an IDE disk you probably want to turn off IDE DMA as > early as possible in the boot process (I think it's "ide=nodma" > in the kernel boot command line). > > Daniel > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
