Incompatible RAID controller?

"Eric Gisin" <ericg.DeleteThis@10.11.12.13> wrote in message
news:bok1fq0b0h@enews2.newsguy.com...
 > I have never heard of that particular message, it is not part of the MBR
or
 > Win 2K/XP loaders. Since you got it from Intel RAID but not Adaptec, it is
 > very likely a message from their RAID ROM.

Funny that, I wondered the same thing. I couldn't determine if it was an
O.S. error, BIOS or RAID ROM error. I suspect you are correct, it's from
the RAID ROM, yet Intel told me they have no knowledge of such an error.

If you search for "disk read error" on Google, I noticed some other people
experience the same thing, but with different hardware configurations.

@drian.<!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: Incompatible RAID controller? 

On Sun, 09 Nov 2003 02:45:31 GMT, "@drian" <nospam.RemoveThis@nospam.com>
scribbled:

 >"Eric Gisin" <ericg.RemoveThis@10.11.12.13> wrote in message
 >news:bok1fq0b0h@enews2.newsguy.com...
  >> I have never heard of that particular message, it is not part of the MBR
 >or
  >> Win 2K/XP loaders. Since you got it from Intel RAID but not Adaptec, it is
  >> very likely a message from their RAID ROM.
 >
 >Funny that, I wondered the same thing. I couldn't determine if it was an
 >O.S. error, BIOS or RAID ROM error. I suspect you are correct, it's from
 >the RAID ROM, yet Intel told me they have no knowledge of such an error.
 >
 >If you search for "disk read error" on Google, I noticed some other people
 >experience the same thing, but with different hardware configurations.
 >
 >@drian.

I had it happen briefly on a Promise 20276 (Onboard "MBFastTrak133
Lite") controller that was running two 120GB Seagates in RAID 0,
though unfortunately I have no idea what I did to correct it, since I
was in the midst of wrestling with several system problems at that
particular time. Same message, about the read error. Wish I could
help, but at least I can say that people aren't going insane - it
really does exist.

-Slash
--
"Ebert Victorious"
-The Onion<!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: Incompatible RAID controller? 

I did some searching on "disk read error ...". There is only one MS KB article
that seems to apply:
http://support.microsoft.com/default.aspx?scid=kb;en-us;240672

Google groups has a few messages related to this setup problem on Win 2K/XP,
with no clues.

It does seem to be a logical problem, not physical read error. I suspect the
disk geometry is getting mangled. Try deleting all partitions in DOS, then
"fdisk /mbr".

Running setup from CD with no HD partitions is always a good idea. If you
still get the error, dump the partition table from DOS and post it.

There could be a bad sector in the first hundred of your RAID array, but I
would think they should be reallocated when setup writes them.

"@drian" <nospam.DeleteThis@nospam.com> wrote in message
news:Eofrb.220099$0v4.16667058@bgtnsc04-news.ops.worldnet.att.net...
| Recently as some may have read, I have been having trouble getting XP to
| boot onto a RAID 0 array, using the onboard RAID controller on my Intel
| D875PBZ motherboard (ICH5-R). I have two SATA Western Digital (WD) Raptor
| 36GB drives, hooked up to the Serial ATA ports of my motherboard.
|
| I created the array from the Intel RAID BIOS then booted from the Windows XP
| CD. Pressed F6 to install the Intel RAID floppy drivers, XP would see the
| array (67GB; 2 x 33.5GB), prompt me for partitioning information then copy
| its files, at the end of which it would reboot.
|
| The PC would reboot then show a "A Disk Read Error Occurred, Press
| Ctrl+Alt+Del to Restart" message. I could never get past it. I *could*
| install XP in a non-RAID single drive situation (even with the Intel RAID
| controller enabled but without an array setup), but not in RAID. Migrating
| to RAID from a single drive would produce the same results.
|
 >> Stay informed about: Incompatible RAID controller? 

"@drian" <nospam RemoveThis @nospam.com> wrote in message
news:Eofrb.220099$0v4.16667058@bgtnsc04-news.ops.worldnet.att.net...
 > Recently as some may have read, I have been having trouble getting XP to
 > boot onto a RAID 0 array, using the onboard RAID controller on my Intel
 > D875PBZ motherboard (ICH5-R). I have two SATA Western Digital (WD) Raptor
 > 36GB drives, hooked up to the Serial ATA ports of my motherboard.
 >
 > I created the array from the Intel RAID BIOS then booted from the Windows
XP
 > CD. Pressed F6 to install the Intel RAID floppy drivers, XP would see the
 > array (67GB; 2 x 33.5GB), prompt me for partitioning information then copy
 > its files, at the end of which it would reboot.
 >
 > (FYI: The boot order in the BIOS is set to the RAID array as the first
boot
 > device, followed by the CD drive I am booting from, with no other boot
 > devices specified after that.)
 >
 > The PC would reboot then show a "A Disk Read Error Occurred, Press
 > Ctrl+Alt+Del to Restart" message. I could never get past it. I *could*
 > install XP in a non-RAID single drive situation (even with the Intel RAID
 > controller enabled but without an array setup), but not in RAID.
Migrating
 > to RAID from a single drive would produce the same results.
 >
 > As a last ditch effort, I bought an Adaptec 1210SA SATA RAID PCI
controller.
 > Hooked up the HDDs to the PCI card, disabled the Intel RAID controller,
 > created a RAID 0 array with the Adaptec card and followed the same path to
 > install XP as I did before.
 >
 > This time, XP booted! It actually booted using the Adaptec PCI card, then
 > continued its install process. Yet, using the exact same procedure for
the
 > Intel RAID controller, XP refused to boot after the first part of the XP
 > installation.
 >
 > My question is, has anyone ever heard of a RAID controller being
 > incompatible with certain make/model of HDDs? This is obviously the case,
 > otherwise the drives would fail under the Adaptec card. Yet, the Intel
RAID
 > controller worked fine with a pair of Seagate 120GB SATA drives I used to
 > have.
 >
 > @drian.

I setup a RAID 1 array instead, something I hadn't tried. So naturally I
had a 33.5GB disk after creating the array. I went through the process of
installing XP, the first part. After booting (the point where the BIOS
would give me the Disk Read Error message), I seen this on the Intel RAID
information:

ID: 0
Name: RaptorRAID
Level: RAID1(mirror)
Strip: N/A
Size: 33.5GB
Status: Degraded
Bootable: N/A

(the following two blocks are sub-entries from the above line block)

ID: N/A
Name: WDC WD360GD-75GH
Level: 634 (partial serial number of drive)
Strip: Port 0
Size: 33.5GB
Status: Error Occurrd
Bootable: N/A

ID: N/A
Name: WDC WD360GD-75GH
Level: 560 (serial number of drive)
Strip: Port 1
Size: 33.5GB
Status: Normal
Bootable: N/A

Ah ha! All I did was run through the first part of the XP install. So,
maybe SATA Port 0 of the M/B is faulty with regard to RAID. So I downed the
PC, switched the cables going into each port. If the hard-drive is faulty,
then the "Error Occurrd" would move.

After switching cables, then installing the first part of XP, I got this:

ID: 0
Name: RaptorRAID
Level: RAID1(mirror)
Strip: N/A
Size: 33.5GB
Status: Degraded
Bootable: N/A

(the following two blocks are sub-entries from the above line block)

ID: N/A
Name: WDC WD360GD-75GH
Level: 560 (partial serial number of drive)
Strip: Port 0
Size: 33.5GB
Status: Error Occurrd
Bootable: N/A

ID: N/A
Name: WDC WD360GD-75GH
Level: 634 (serial number of drive)
Strip: Port 1
Size: 33.5GB
Status: Normal
Bootable: N/A

Note the serial number of the drive has changed, but the "Error Occurrd" has
not moved with the drive serial number, meaning the drives are OK. I assume
that RAID functionality on SATA Port 0 is defunct, no longer works
correctly. I'm not sure what the actual meaning of "Error Occurrd" is, I'd
like to see more detail.

Anyway, this gets me a step closer.

@drian.<!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: Incompatible RAID controller? 

"Slash" <slash3.TakeThisOut@geocities.com> wrote in message
news:pforqvoshss6n6gpmm2eb9dbkid2c0id9u@4ax.com...
 > I had it happen briefly on a Promise 20276 (Onboard "MBFastTrak133
 > Lite") controller that was running two 120GB Seagates in RAID 0,
 > though unfortunately I have no idea what I did to correct it, since I
 > was in the midst of wrestling with several system problems at that
 > particular time. Same message, about the read error. Wish I could
 > help, but at least I can say that people aren't going insane - it
 > really does exist.

LOL! Oh yes. If you search for "disk read error" on the newsgroups, you'll
see a few people with the same problem.

@drian.<!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: Incompatible RAID controller? 

"Eric Gisin" <ericg.TakeThisOut@10.11.12.13> wrote in message
news:bon0u4020kp@enews4.newsguy.com...
 > I did some searching on "disk read error ...". There is only one MS KB
article
 > that seems to apply:
<font color=purple> > <a style='text-decoration: underline;' href="http://support.microsoft.com/default.aspx?scid=kb;en-us;240672</font" target="_blank">http://support.microsoft.com/default.aspx?scid=kb;en-us;240672</font</a>>

Yes, I read that one too.

 > Google groups has a few messages related to this setup problem on Win
2K/XP,
 > with no clues.

Same here. I even e-mailed a few people with the problem, I didn't really
guage any clues from them.

 > It does seem to be a logical problem, not physical read error. I suspect
the
 > disk geometry is getting mangled. Try deleting all partitions in DOS, then
 > "fdisk /mbr".
 >
 > Running setup from CD with no HD partitions is always a good idea. If you
 > still get the error, dump the partition table from DOS and post it.
 >
 > There could be a bad sector in the first hundred of your RAID array, but I
 > would think they should be reallocated when setup writes them.

Well, I suspect the motherboard. As when I setup a RAID 1 array, I get
"Error Occurrd" on Port 0. Even when I switch cables going into the ports
on the M/B, the error stays on the same line.

Last night was the topper, I enabled RAID in the BIOS, booted and the RAID
BIOS screen never showed! It flat refused to even come up, so I couldn't
create an array. It sounds like the M/B is slowly going faulty.

All this is made evident by the fact the Adaptec RAID controller works
flawlessly, in both RAID 0 and RAID 1.

I called Intel and they want the board first, and will send a new one out
two b/days later. Of course, I forgot to ask them, is the board they send a
new one or repaired? Anyway, I'll find out.

@drian.<!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: Incompatible RAID controller?