From: "Ralf Müller" <ralf@bj-ig.de>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Daily crashes, incorrect RAID behaviour
Date: Tue, 15 Aug 2006 15:45:49 +0200 [thread overview]
Message-ID: <200608151545.49345@bj-ig.de> (raw)
In-Reply-To: <13e988610608150436y6812f623p9919b2d5b1989427@mail.gmail.com>
On Tuesday 15 August 2006 13:36, you wrote:
> My problems continue, even with a new and good power supply.
> 1) The system loses a disk about every week, only a hard reboot
> solves that 2) In the last three nights the system lost all disk
> access and trashed the file systems
>
> Regarding 1)
> The system works normally and suddenly one disk does not respond.
> After a soft reboot the BIOS does not recognize the disk, here a hard
> reboot helps. Whenever I start my normal system in this situation, my
> file systems get trashed. I think the software raid thinks the failed
> disks (which lost several hours of write accesses) is OK and then
> merges the data. When I delete the disk (or create another raid on
> the partitions) I can add the disk without problems. This might be a
> bug, at least it is _very_ annoying.
> 4x Maxtor 300GB (Sata2)
I have a similar problem with maybe the same type of disk. My analysis
of the problem is still not that complete so I did not asked on the
kernel mailing list yet.
The disk type we use here in a ten disk RAID6 is:
Maxtor 7V300F0 300GB Sata2
on Promise Sata 300 TX4 controllers
Once in a week or two a random disk is not responding anymore and needs
a complete power off/on cycle to recover. After power cycle the disk
works without problems, doesn't report any SMART problems ...
I'm quite sure it is no problem with power supply, motherboard,
backplane or controllers. Still open are cabling and disks. Nearly the
same setup of hardware - just with different disks - is running smooth
since about 8 month in a different system.
If this is the same disk type we maybe should return the disks to our
hardware vendors as it may be a disk problem.
The only messages I get are like that:
Aug 13 17:25:10 backup-core kernel: ata7: command timeout
Aug 13 17:25:10 backup-core kernel: ata7: translated ATA stat/err
0xff/00 to SCSI SK/ASC/ASCQ 0xb/47/00
Aug 13 17:25:10 backup-core kernel: ata7: status=0xff { Busy }
Aug 13 17:25:42 backup-core kernel: ata7: command timeout
Aug 13 17:25:42 backup-core kernel: ata7: translated ATA stat/err
0xff/00 to SCSI SK/ASC/ASCQ 0xb/47/00
Aug 13 17:25:42 backup-core kernel: ata7: status=0xff { Busy }
Aug 13 17:26:43 backup-core kernel: ata7: command timeout
Aug 13 17:26:43 backup-core kernel: ata7: translated ATA stat/err
0xff/00 to SCSI SK/ASC/ASCQ 0xb/47/00
Aug 13 17:26:43 backup-core kernel: ata7: status=0xff { Busy }
Aug 13 17:26:43 backup-core kernel: end_request: I/O error, dev sdg,
sector 2104383
Regards
Ralf
--
Van Roy's Law: -------------------------------------------------------
An unbreakable toy is useful for breaking other toys.
next prev parent reply other threads:[~2006-08-15 13:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-15 11:36 Daily crashes, incorrect RAID behaviour Carsten Otto
2006-08-15 12:33 ` Michael Tokarev
2006-08-15 12:57 ` Alan Cox
2006-08-15 12:42 ` Carsten Otto
2006-08-15 13:08 ` Jan Engelhardt
2006-08-15 13:45 ` Ralf Müller [this message]
2006-08-19 11:37 ` Andrew Baker
2006-08-19 11:47 ` Justin Piszcz
2006-08-19 18:53 ` Andrew Baker
2006-08-15 15:31 ` Carsten Otto
2006-08-15 18:28 ` Mike Dresser
2006-08-15 19:27 ` Alistair John Strachan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200608151545.49345@bj-ig.de \
--to=ralf@bj-ig.de \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.