<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Raid Recovery Tips &#187; pci scsi raid controller</title>
	<atom:link href="http://www.raidrecoverytips.org/tag/pci-scsi-raid-controller/feed" rel="self" type="application/rss+xml" />
	<link>http://www.raidrecoverytips.org</link>
	<description>Tips about Raid 0, Raid 1, Raid 5, Raid 6, Raid Software, Raid Controller, Linux Raid...</description>
	<lastBuildDate>Tue, 01 Dec 2009 01:25:48 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>I have a PCI SCSI RAID controller and the drives go offline during heavy loads</title>
		<link>http://www.raidrecoverytips.org/i-have-a-pci-scsi-raid-controller-and-the-drives-go-offline-during-heavy-loads.html</link>
		<comments>http://www.raidrecoverytips.org/i-have-a-pci-scsi-raid-controller-and-the-drives-go-offline-during-heavy-loads.html#comments</comments>
		<pubDate>Wed, 05 Aug 2009 06:31:39 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Raid Configuration]]></category>
		<category><![CDATA[drive offline]]></category>
		<category><![CDATA[pci scsi raid controller]]></category>

		<guid isPermaLink="false">http://www.raidrecoverytips.org/i-have-a-pci-scsi-raid-controller-and-the-drives-go-offline-during-heavy-loads.html</guid>
		<description><![CDATA[<p>The most common reason for <strong>drives being marked offline</strong> is <strong>cabling/termination issues</strong>. Make sure the cabling is of the highest quality (twisted pair or Teflon ribbon) that&#8217;s within SCSI specifications as to maximum bus length, impedance matching, and maximum allowed devices.     <br />For best results, use a system level SCSI terminator (LVD/SE) on the end of the cable, instead of using the last drive for termination. Make sure the hard drives are set to provide SCSI Termination Power, if supported. Rarely is drive firmware an issue more often a SCSI controller BIOS or ASPI driver update. </p>
<p>Try the following troubleshooting steps:</p>
<ol>
<li>Check all&#8230;</li></ol>]]></description>
			<content:encoded><![CDATA[<p>The most common reason for <strong>drives being marked offline</strong> is <strong>cabling/termination issues</strong>. Make sure the cabling is of the highest quality (twisted pair or Teflon ribbon) that&#8217;s within SCSI specifications as to maximum bus length, impedance matching, and maximum allowed devices.     <br />For best results, use a system level SCSI terminator (LVD/SE) on the end of the cable, instead of using the last drive for termination. Make sure the hard drives are set to provide SCSI Termination Power, if supported. Rarely is drive firmware an issue more often a SCSI controller BIOS or ASPI driver update. </p>
<p>Try the following troubleshooting steps:</p>
<ol>
<li>Check all cable connections. Test the data cable by trying a different cable or try the cable on a known working drive.</li>
<li>Confirm the jumper settings.</li>
<li>Check termination.</li>
<li>Check the host adapter card. Test the card by either trying a known good card or a known working drive.</li>
<li>Check host adapter settings. Set to asynchronous negotiation and the transfer rate to 10MB/s. (or the slowest setting).</li>
<li>Make the offending drive the only SCSI device in the system and re-test.</li>
<li>Run the low-level format routine provided by the host adapter manufacturer.</li>
<li>Try the drive in a different system.</li>
</ol>
]]></content:encoded>
			<wfw:commentRss>http://www.raidrecoverytips.org/i-have-a-pci-scsi-raid-controller-and-the-drives-go-offline-during-heavy-loads.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
