<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:st1="urn:schemas-microsoft-com:office:smarttags" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="PersonName" /><!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]--><style>
<!--
/* Font Definitions */
@font-face
{font-family:"Arial Unicode MS";
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"\@Arial Unicode MS";
panose-1:2 11 6 4 2 2 2 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:blue;
text-decoration:underline;}
p
{mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman";}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:Arial;
color:navy;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
{page:Section1;}
-->
</style>
</head>
<body lang="EN-US" link="blue" vlink="blue">
<div class="Section1">
<p class="MsoNormal"><font size="2" color="navy" face="Arial"><span style="font-size:
10.0pt;font-family:Arial;color:navy">That might have been the old Adaptec OEM PERC. I never used those PERC2 controllers and the fact they existed caused me much confusion
some time back when I was trying to troubleshoot an LSI OEM PERC2. I’ve not seen this with any of the LSI OEM stuff which is everything from some of the PERC2 and above (they’re up to PERC6 at least nowadays).<o:p></o:p></span></font></p>
<p class="MsoNormal"><font size="2" color="navy" face="Arial"><span style="font-size:
10.0pt;font-family:Arial;color:navy"><o:p> </o:p></span></font></p>
<p class="MsoNormal"><font size="2" color="navy" face="Arial"><span style="font-size:
10.0pt;font-family:Arial;color:navy">Judging computer technology by what it did 10 years ago hardly seems reasonable to me. I’ve been using the PERC stuff for over 7 years
now and haven’t seen any irrecoverable failures for supported equipment.<o:p></o:p></span></font></p>
<p class="MsoNormal"><font size="2" color="navy" face="Arial"><span style="font-size:
10.0pt;font-family:Arial;color:navy"><o:p> </o:p></span></font></p>
<div>
<div class="MsoNormal" align="center" style="text-align:center"><font size="3" face="Times New Roman"><span style="font-size:12.0pt">
<hr size="2" width="100%" align="center" tabindex="-1">
</span></font></div>
<p class="MsoNormal"><b><font size="2" face="Tahoma"><span style="font-size:10.0pt;
font-family:Tahoma;font-weight:bold">From:</span></font></b><font size="2" face="Tahoma"><span style="font-size:10.0pt;font-family:Tahoma"> ale-bounces@ale.org [mailto:ale-bounces@ale.org]
<b><span style="font-weight:
bold">On Behalf Of </span></b>Jim Kinney<br>
<b><span style="font-weight:bold">Sent:</span></b> Thursday, November 17, 2011 11:37 AM<br>
<b><span style="font-weight:bold">To:</span></b> <st1:PersonName w:st="on">Atlanta Linux Enthusiasts</st1:PersonName><br>
<b><span style="font-weight:bold">Subject:</span></b> Re: [ale] Onboard RAID</span></font><o:p></o:p></p>
</div>
<p class="MsoNormal"><font size="3" face="Times New Roman"><span style="font-size:
12.0pt"><o:p> </o:p></span></font></p>
<p><font size="3" face="Times New Roman"><span style="font-size:12.0pt">-2 on perc<br>
Multiple perc failures on a wide array of systems all with same root process: at the point in the battery exercise cycle where it was fully discharged, it would drop a drive from the array and all disks were dirty because the exercise cycle opened a block on
each drive on the array to store a timestamp.<br>
Granted these were all old scsi systems but they were the "the high class item" at the time (2001-2002).<o:p></o:p></span></font></p>
<div>
<p class="MsoNormal"><font size="3" face="Times New Roman"><span style="font-size:
12.0pt">On Nov 17, 2011 9:17 AM, "Lightner, Jeff" <<a href="mailto:JLightner@water.com">JLightner@water.com</a>> wrote:<o:p></o:p></span></font></p>
<p class="MsoNormal"><font size="3" face="Times New Roman"><span style="font-size:
12.0pt">+1 on PERC<br>
<br>
We've been using the PERC controllers here for years in all PC based systems (Windows, Linux, FreeBSD) and haven't had an extended downtime due to using (real) hardware RAID. Note that the PERC stuff is OEMed from LSI so even if you're not using Dell PowerEdge
you can get one. However, it sounds like you don't have any money so you should probably go with Software RAID. We ran some systems without PERC on Software RAID for several years with no major issues.<br>
<br>
I agree that Fake RAID doesn't save you anything over doing software RAID and the downside of using it likely outweighs any touted benefits.<br>
<br>
<br>
<br>
<br>
<br>
-----Original Message-----<br>
From: <a href="mailto:ale-bounces@ale.org">ale-bounces@ale.org</a> [mailto:<a href="mailto:ale-bounces@ale.org">ale-bounces@ale.org</a>] On Behalf Of Brian Mathis<br>
Sent: Wednesday, November 16, 2011 4:12 PM<br>
To: <st1:PersonName w:st="on">Atlanta Linux Enthusiasts</st1:PersonName><br>
Subject: Re: [ale] Onboard RAID<br>
<br>
There is a world of difference between "hardware" BIOS RAID and a real<br>
RAID card like a PERC H700. Please do not throw both of those things<br>
in the same category. Given the choice between software RAID and BIOS<br>
RAID, software RAID is the only real choice. However, a real RAID<br>
card will almost always be the best option, if you have one available.<br>
<br>
I haven't used Windows software RAID recently, but I think it will be<br>
difficult to get a RAID10 working since the drivers required for<br>
accessing the striped data are themselves striped across the disks,<br>
rendering them unreadable to the system as it boots. Windows may use<br>
a separate boot partition that is not striped to get around this<br>
issue, but you will have to research that (and I'm not sure a Linux<br>
user group mailing list is the place to find the best answer). I'm<br>
sure you could test it out in a VM.<br>
<br>
As for Windows being completely, horribly sucky sucky, please cut it<br>
out. A very large portion of the world uses Windows for rather large<br>
file storage on a daily basis, and they don't all constantly crash and<br>
burn. It may not be your preference, so leave it at that. Linux has<br>
its own share of problems.<br>
<br>
Finally, why do they include BIOS RAID on systems? Mainly to have a<br>
feature to list on the package. Incidentally, I don't think I would<br>
buy a board for enterprise usage that has such a feature. Those are<br>
typically aimed at the enthusiast market.<br>
<br>
<br>
P.S. Please pay attention to whether the replies you receive are top<br>
or bottom posted and use the same method to continue the conversation.<br>
I'm not one to care, as long as you are consistent within the same<br>
thread.<br>
<br>
<br>
</span></font><font face="Arial Unicode MS"><span style="font-family:"Arial Unicode MS"">❧</span></font> Brian Mathis<br>
<br>
<br>
<br>
On Wed, Nov 16, 2011 at 2:53 PM, Greg Clifton <<a href="mailto:gccfof5@gmail.com">gccfof5@gmail.com</a>> wrote:<br>
> Well, we have a contract for this system and got hit by the recent hard<br>
> drive price increase, so we don't have any more $ to spend on an additional<br>
> box (and it wasn't my sale or I might have pitched a FreeNAS box). Plus we<br>
> have mucho surplus redundant power in this box. Surely RAID support under<br>
> Server 2008 is way better than running a [I think] non raided NT drive that<br>
> has been running for years now?<br>
> Now as I understand it, all the BIOS options are "fake RAID" and I fully<br>
> appreciate the potential for problems with a [bootable] hardware RAID. I<br>
> always recommend that my customers have a separate mirrored boot drive and<br>
> NOT boot from the storage array. I suppose the same sort of problem could<br>
> result from booting from the fake RAID. The next question is, if it is so<br>
> bad/unreliable, WHY do the BIOSes support the fake RAID in the first place?<br>
> Especially now that we have 3TB and soon will have 4TB hard drives--that<br>
> pretty much does away with the need for RAID for capacity needs for most<br>
> folks, though there is still a demand for striping for faster data access.<br>
><br>
> On Wed, Nov 16, 2011 at 2:28 PM, Michael B. Trausch <<a href="mailto:mike@trausch.us">mike@trausch.us</a>> wrote:<br>
>><br>
>> On 11/16/2011 02:12 PM, Greg Clifton wrote:<br>
>> > More details this is a new server (Single Proc Xeon X3440) with only 10<br>
>> > users, so it won't be heavily taxed. Moving the storage to a different<br>
>> > Linux box really isn't an option either. We're replacing an OLD server<br>
>> > running NT with the 2008 server.<br>
>><br>
>> Depending on the reason why it "isn't an option", it might be worth<br>
>> pushing back on. The whole point of separating it out is because<br>
>> Windows server sucks, even with only 10 users on it. The way it<br>
>> operates sucks, the way it treats things on the disks sucks, the overall<br>
>> speed of data access sucks. Keep a single disk in the Windows server<br>
>> (maybe mirrored) that is the system disk, and put everything else<br>
>> somewhere else. Don't want a Linux box, then get a RAID array box that<br>
>> hooks up to the Windows box with a single eSATA connection and call it a<br>
>> day. That is better than having Windows sort it out.<br>
>><br>
>> > What you are saying is that SOFTWARE is "more better" in all cases than<br>
>> > the BIOS based RAID configuration. OK, but does Server 2008 support RAID<br>
>> > 10? If not, we must rely on the BIOS RAID.<br>
>><br>
>> And you do NOT want to rely on BIOS RAID. At all, period, never. Bad<br>
>> idea, bad call. I have seen *many* BIOS RAID setups fail for a wide<br>
>> variety of reasons, but most of the time it seems to me that it is<br>
>> because some component of the implementation of them is buggy. It<br>
>> happens frequently enough that I wouldn't trust hourly snapshotted data<br>
>> on such a storage mechanism, I'll say that much.<br>
>><br>
>> > If we must do that then the question falls back to which is the better<br>
>> > RAID option [under Windows].<br>
>> > I saw something on some RAID forum that said the Adaptec was for Linux<br>
>> > OS and the Intel for MS OS. Since Adaptec drivers are built into Linux,<br>
>> > that at least makes some sense.<br>
>><br>
>> Adaptec has drivers for Windows as well.<br>
>><br>
>> The thing is that with hardware RAID it doesn't matter: you cannot<br>
>> upgrade, you are not portable. It is a dangerous option.<br>
>><br>
>> Consider this: what happens if your disk controller fails? If that<br>
>> disk controller does RAID, and it has been discontinued, you may be<br>
>> looking at a whole RAID rebuild instead of just a hardware swap-out. In<br>
>> other words, with hardware RAID, it's far more likely that an outage is<br>
>> going to last forever because you'll have to start over and rebuild the<br>
>> array, restoring data to it.<br>
>><br>
>> If the thing that fails is a box running Linux with four disks in it,<br>
>> you replace the box and move the disks over and you're done. If you<br>
>> have a spare box on hand, you can be up in ten minutes.<br>
>><br>
>> If you *are* going to go the hardware RAID route, make sure you have a<br>
>> spare, identical controller in stock in case of failure. I've seen it<br>
>> happen where RAID controllers were incompatible after seemingly minor<br>
>> changes (device F00e vs. F00f might be two completely different things,<br>
>> same for F00e and F00e+) to the model number.<br>
>><br>
>> And just don't use fakeraid (that is, BIOS provided RAID). It is simply<br>
>> not a viable option if you like uptime and robustness.<br>
>><br>
>> --- Mike<br>
<br>
_______________________________________________<br>
Ale mailing list<br>
<a href="mailto:Ale@ale.org">Ale@ale.org</a><br>
<a href="http://mail.ale.org/mailman/listinfo/ale" target="_blank">http://mail.ale.org/mailman/listinfo/ale</a><br>
See JOBS, ANNOUNCE and SCHOOLS lists at<br>
<a href="http://mail.ale.org/mailman/listinfo" target="_blank">http://mail.ale.org/mailman/listinfo</a><br>
<br>
<br>
<br>
<br>
Athena®, Created for the Cause™<br>
Making a Difference in the Fight Against Breast Cancer<br>
<br>
---------------------------------<br>
CONFIDENTIALITY NOTICE: This e-mail may contain privileged or confidential information and is for the sole use of the intended recipient(s). If you are not the intended recipient, any disclosure, copying, distribution, or use of the contents of this information
is prohibited and may be unlawful. If you have received this electronic transmission in error, please reply immediately to the sender that you have received the message in error, and delete it. Thank you.<br>
----------------------------------<br>
<br>
<br>
_______________________________________________<br>
Ale mailing list<br>
<a href="mailto:Ale@ale.org">Ale@ale.org</a><br>
<a href="http://mail.ale.org/mailman/listinfo/ale" target="_blank">http://mail.ale.org/mailman/listinfo/ale</a><br>
See JOBS, ANNOUNCE and SCHOOLS lists at<br>
<a href="http://mail.ale.org/mailman/listinfo" target="_blank">http://mail.ale.org/mailman/listinfo</a><o:p></o:p></p>
</div>
</div>
</body>
</html>