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 PROTE
[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 s
On Fri, 8 Oct 2004 [EMAIL PROTECTED] wrote:
> The discussion concerning this thread tells me that my own
> understanding of the issues at play is far below that of certain other
> posters. However, I will humbly wonder aloud if the IDE cable is firmly
> seated in the connectors at both
On Thu, Oct 07, 2004 at 07:57:05AM -0700, [EMAIL PROTECTED] wrote:
>
> Whether or not this is related to debian is not clear, but it's possible.
>
> 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 e
Alvin Oga wrote:
So this problem has a history. I had previously been seeing
corruption in the /dev directory and only the /dev directory.
get a clean /dev from a clean system ..
retoring /dev from a suspect corrupt system will only make things worst
1. the /dev directory seems to be somewhat d
hi ya brian
On Thu, 7 Oct 2004 [EMAIL PROTECTED] wrote:
> I have 1 IDE cable with nothing but 1 HD and 1 CDROM on it. I keep
> things simple to avoid exactly such problems.
take off the cdrom .. and i bet your problems will disappear
and new disk does not imply it's a gooouuudd drive..
you
> "Andrea" == Andrea Vettorello <[EMAIL PROTECTED]> writes:
Andrea> On Thu, 7 Oct 2004 09:43:36 -0700, [EMAIL PROTECTED]
Andrea> <[EMAIL PROTECTED]> wrote:
>> well that was silly. the fs is just ext2 2.6.8 kernel
>>
>> I haven't tried smartmontools. I will :-)
>>
Andrea> I'
On Thu, Oct 07, 2004 at 07:57:05AM -0700, [EMAIL PROTECTED] wrote:
> Whether or not this is related to debian is not clear, but it's possible.
>
> 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 erro
> "Henrique" == Henrique de Moraes Holschuh <[EMAIL PROTECTED]> writes:
Henrique> On Thu, 07 Oct 2004, [EMAIL PROTECTED] wrote:
>> I've currently set fsck to run pretty much on every other boot.
Henrique> Install the memtest86+ package, activate it in lilo/grub,
Henrique> reboot.
H
On Thu, 7 Oct 2004 09:43:36 -0700, [EMAIL PROTECTED]
<[EMAIL PROTECTED]> wrote:
>
> well that was silly.
> the fs is just ext2
> 2.6.8 kernel
>
> I haven't tried smartmontools. I will :-)
>
I've read at least two different claims of fs corruption with kernel
2.6.8-1 and reiserfs (i'm running b
> "Alvin" == Alvin Oga <[EMAIL PROTECTED]> writes:
Alvin> On Thu, 7 Oct 2004 [EMAIL PROTECTED] wrote:
>> I've currently set fsck to run pretty much on every other boot.
Alvin> why
because it likes to fail, so I figure something must be wrong, so I'm
running it more often.
Alvin> it
well that was silly.
the fs is just ext2
2.6.8 kernel
I haven't tried smartmontools. I will :-)
Brian
> "Andrea" == Andrea Vettorello <[EMAIL PROTECTED]> writes:
Andrea> On Thu, 7 Oct 2004 07:57:05 -0700, [EMAIL PROTECTED]
Andrea> <[EMAIL PROTECTED]> wrote:
>> Whether or not this
On Thu, 07 Oct 2004, [EMAIL PROTECTED] wrote:
> I've currently set fsck to run pretty much on every other boot.
Install the memtest86+ package, activate it in lilo/grub, reboot.
Let it test your main memory for at least 12h.
> 3. Could this be a bug in fsck ? Why doesn't fsck actually tell me
On Thu, 7 Oct 2004 [EMAIL PROTECTED] wrote:
> I've currently set fsck to run pretty much on every other boot.
why
it will figure it out for itself
> And just about every time it runs , it informs me that it fixed file
> system errors and reboots the system.
how do you shutdown ? ( exactly wh
On Thu, 7 Oct 2004 07:57:05 -0700, [EMAIL PROTECTED]
<[EMAIL PROTECTED]> wrote:
>
> Whether or not this is related to debian is not clear, but it's possible.
>
> 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 fi
Whether or not this is related to debian is not clear, but it's possible.
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.
However all other indicators of disk operation are
16 matches
Mail list logo
