snip
Almost every RAID system out there handles the sudden removal
of a disk from the system pretty well. Why? Because it's EASY
to create that failure mode. Problem is, in 25 years in this
business, I don't recall having seen a hard disk fall out of a
computer as a mode of actual failure
Hi Nick,
I highly appreciate your detailed report about your experiences
with RAID systems. That was cool. Surely I don't expect any
miracles from RAID anymore.
The current plan is to move to a ramdisk based system to get rid
of disk access afap, and to use carp to setup a fallback host.
Stuart Henderson wrote:
With IDE (Integrated Drive Electronics), the controller is *on the
drive*. A failing drive/controller can do all sorts of nasty things
to the host system.
So you mean I should not use IDE disks (PATA or SATA), because
Raidframe cannot support a failsafe operation
Harald Dunkel wrote:
Stuart Henderson wrote:
With IDE (Integrated Drive Electronics), the controller is *on the
drive*. A failing drive/controller can do all sorts of nasty things
to the host system.
So you mean I should not use IDE disks (PATA or SATA), because
Raidframe cannot
On Thu, Aug 07, 2008 at 12:33:40PM +0200, [EMAIL PROTECTED] wrote:
Seems we have some misunderstanding here. I am talking about
future events. Of course I don't know in advance which disk
fails when. If a disk dies, then its the job of raidframe to
detect this event, to mark the disk as bad,
On 2008-08-08, Olivier Cherrier [EMAIL PROTECTED] wrote:
Couldn't it be related to the IDE bus? What for noise can a deffective
disk on an IDE controller generate when it is failling.
With IDE (Integrated Drive Electronics), the controller is *on the
drive*. A failing drive/controller can do
Hi folks,
I've got a configuration issue with Raidframe: Our
gateway/firewall runs a raid1 for the system disk.
No swap partition.
Recently one of the raid disks (wd0) showed some
problem:
Aug 2 17:22:35 fw01 /bsd: wd0(pciide0:0:0): timeout
Aug 2 17:53:52 fw01 /bsd: type: ata
Aug 2
On Thu, Aug 07, 2008 at 09:27:24AM +0200, Harald Dunkel wrote:
I've got a configuration issue with Raidframe: Our
gateway/firewall runs a raid1 for the system disk.
No swap partition.
Recently one of the raid disks (wd0) showed some
problem:
Aug 2 17:22:35 fw01 /bsd: wd0(pciide0:0:0):
Ariane van der Steldt wrote:
Your best bet is to replace the disk. 30 minutes wait time seems a bit
odd though. I have a similar situation where one disk is having
problems, requiring the disk to restart, but that only takes approx. a
minute. You can mark the disk as bad and replace it before
On Thu, Aug 07, 2008 at 11:41:59AM +0200, Harald Dunkel wrote:
Ariane van der Steldt wrote:
Your best bet is to replace the disk. 30 minutes wait time seems a bit
odd though. I have a similar situation where one disk is having
problems, requiring the disk to restart, but that only takes
Harald Dunkel wrote:
Ariane van der Steldt wrote:
Your best bet is to replace the disk. 30 minutes wait time seems a bit
odd though. I have a similar situation where one disk is having
problems, requiring the disk to restart, but that only takes approx. a
minute. You can mark the disk as bad
nothingness wrote:
Presumably this was after a reboot? If so, the trick is to move the
'raidctl -P all' line from /etc/rc to /etc/rc.local and add a '' so it
runs as a background process.
There was no reboot involved. Before this event the machine was
running for weeks, and it is still
Ariane van der Steldt wrote:
On Thu, Aug 07, 2008 at 11:41:59AM +0200, Harald Dunkel wrote:
Ariane van der Steldt wrote:
Your best bet is to replace the disk. 30 minutes wait time seems a bit
odd though. I have a similar situation where one disk is having
problems, requiring the disk to
13 matches
Mail list logo
