On 27/10/05, Horms <[EMAIL PROTECTED]> wrote:
>
> Ok, that does sound like fair resoning, though I should
> say that almost always these kind of errors show up faulty hardware.
> In this case, its probably a bug.
Don't get me wrong, I think may well be faulty hardware, but a general
fault rather t
Is there any chance that #336103 is related to this?
http:://bugs.debian.org/336103
--
Horms
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On 01/11/05, Horms <[EMAIL PROTECTED]> wrote:
> Is there any chance that #336103 is related to this?
>
> http://bugs.debian.org/336103
Hmm, don't think so. In my case I had no trouble turning DMA on (in
fact, I disabled it yesterday with hdparm just to see if it would make
any difference - it will
P.S. I could try unloading the ide-generic module etc. if you think
that's a good idea.
On Tue, Nov 01, 2005 at 09:24:16AM +, George B. wrote:
> P.S. I could try unloading the ide-generic module etc. if you think
> that's a good idea.
I think its certainly worth a try, though its probably not going
to make much difference.
--
Horms
--
To UNSUBSCRIBE, email to [EMAIL PROTECTE
I think I finally fixed the problem by installing the apmd package. :-\
The problem was, I am guessing, that the hard drive went to sleep at
some random time (despite it being explicitly told not to in the BIOS)
and regardless of the disk activity (so even my 15 min dd cronjob did
not fix it) and
Package: kernel-image-2.6.8-2-386
Version: 2.6.8-16
Severity: important
Hello,
I've been having the same problem on 3 firewall boxes: after a certain
amount of time (days, weeks) the hard drives will either go into read
only mode or lock up for good (until a reboot) with I/O error messages.
I wi
On Mon, Oct 24, 2005 at 03:37:52PM +0100, George B. wrote:
> Package: kernel-image-2.6.8-2-386
> Version: 2.6.8-16
> Severity: important
>
> Hello,
>
> I've been having the same problem on 3 firewall boxes: after a certain
> amount of time (days, weeks) the hard drives will either go into read
>
>
> Your disks are failing, get new ones if you value your data.
I'm afraid I will have to disagree with you on this one. All of the
disks were brand new and the problem started showing up after a few
days/weeks after assembly.
Also, one of the firewalls had a different (3.5") drive in it before,
On Wed, Oct 26, 2005 at 10:42:46PM +0100, George B. wrote:
> >
> > Your disks are failing, get new ones if you value your data.
>
> I'm afraid I will have to disagree with you on this one. All of the
> disks were brand new and the problem started showing up after a few
> days/weeks after assembly.
On 04/09/06, Eito Tamura <[EMAIL PROTECTED]> wrote:
Hi George,
I am having the same problem as you did. So installing ampd package didn't
fix the problem?
Just those crappy HDD problem? Upgrading kernel might fix this problem?
Hello,
The problem is still there, although it does not occur ver
Just to let you know that the 'fix' did not work. :-(
The hard drives will still randomly go to sleep and not wake up.
What's more, even a sysrq forced reboot does not wake the drive up -
only a cold boot works!
The end result is that we are gradually replacing these crappy disks
in our firewalls
12 matches
Mail list logo
