Mitchell Laks wrote:
Hi,
I have a production server in place at a remote site.
I have a single system drive that is an ide drive
and two data drives that are on a via SATA controller in a raid1
configuration.
I am monitoring the /var/log/messages and I get messages every few days
Mar 22
Mar 29 23:33:26 A1 kernel: ata6: status=0x51 { DriveReady SeekComplete Error
}
Mar 29 23:33:26 A1 kernel: ata6: error=0x84 { DriveStatusError BadCRC }
BadCRC is unambiguous: the packet was corrupted. that could happen several
ways, the most common of which is bogus cables (remember, PATA is
On Friday 31 March 2006 03:57, David Greaves wrote:
Yes. There is a *definite* chance that there is a hardware fault and you
need to try hard to confirm that it's not.
I ended up spending over $100 on a new (unneeded) PSU - just in case...
You mean that it may (possibly) simply be a hardware
Hi,
I have a production server in place at a remote site.
I have a single system drive that is an ide drive
and two data drives that are on a via SATA controller in a raid1
configuration.
I am monitoring the /var/log/messages and I get messages every few days
Mar 22 23:31:36 A1 kernel: ata6:
Party line: It's a faulty cable (on both drives? triggered by rsync?
Doesn't show up under 'badblocks'? hah!)
Check out the linux-ide archive for my (and others) reports.
I've had lots of issues like this - spurious and IMHO incorrect error
messages. Only certain types of disk access cause them
THANK YOU! :)
it appears this might be related to some of the errors a friend of mine got
(ref: Re: recovering data on a failed raid-0 installation).
after a bit more research, it does appears that a kernel bug in combination
with some fast and loose protocol usage on a laptop IDE interface
David Greaves david at dgreaves.com writes:
Check out the linux-ide archive for my (and others) reports.
I just read them and weeped.
I've had lots of issues like this - spurious and IMHO incorrect error
messages. Only certain types of disk access cause them - xfs_repair and
rsync seem
