RE: Disk Corruption with ide hpt-366 controller software raid5

1999-09-14 Thread Andre Hedrick
On Tue, 14 Sep 1999, Tom Livingston wrote: note that actual PCI setup is: AGP Slot: Trident 975 (IRQ disabled) PCI 1PDC20246: IDE controller on PCI bus 00 dev 78 hdm/n/o/p PCI 2PDC20246: IDE controller on PCI bus 00 dev 68 hdi/j/k/l PCI 3PDC20246: IDE

SMP MegaRAID 428

1999-09-14 Thread Chad Schmutzer
Hello, I'm sorry if this is a known issue, but I have been having problems which I cannot find an answer for. The system in question is a Dell PowerEdge 6300 with 4 processors. I have the Dell OEM AMI MegaRAID 428 controller configured for RAID 5. When I boot with any 2.2.x SMP kernel and run

Autodetection of Raid Array

1999-09-14 Thread root
Hello, I'm having a problem with Linux RedHat 6.0 autodetecting my 3 disk Raid5 array and was hoping you could look at the error message. Here's the info: Kernel = 2.2.5-15 Raidtool package = version 0.90 3-IDE 6.1GB Harddrives /dev/hdb /dev/hdc /dev/hdd I've set the partition types for the

RE: Disk Corruption with ide hpt-366 controller software raid5

1999-09-14 Thread Tom Livingston
Rogier Wolff wrote: If you're seeing THIS kind of errors, it SURE looks like a hardware issue. If the software is making errors, I'd expect a random byte inserted somewhere. A block of data shifted one byte. A whole block corrupted (delivered to the wrong address in memory). Things like

Re: Disk Corruption with ide hpt-366 controller software raid5

1999-09-14 Thread Rogier Wolff
Someone whose name I snipped wrote... dd if=/dev/md0 count=50 2 /dev/null | md5sum done 08d3b2b34dfc667ca96c549f8a8a3c15 - cee7aa5dd1ee81ff63a93bba3830ca31 - a577d2d50f9ebc535b9e49905c29631c - f8c6aea89094543aaf2982ef6504285d - 596f99e3047d18eef9798634a091670b -

Re: Disk Corruption with ide hpt-366 controller software raid5

1999-09-14 Thread Andrea Arcangeli
On Tue, 14 Sep 1999, Rogier Wolff wrote: If you're seeing THIS kind of errors, it SURE looks like a hardware issue. If the software is making errors, I'd expect a random byte Don't understimate the RAM. Some month ago reports like this got solved by replacing the only RAM in the system. Andrea