Skip to main content

ubuntu - RAID 1+0 vs RAID 0+1




I went with some advice I was given from someone I know to go with a RAID setup for this server I ordered. The specs are below. I plan on using this server to host multiple sites in a PHP/MySQL environment and an SVN repository in Ubuntu Server. I'd like to have a setup where the primary drive is mirrored so that in the event of failure on a drive the server could just use the other pair of drives.



I'm reading on wikipedia about raid setups and I see RAID 0-5, but don't see a 10 listed on wikipedia. Perhaps I'm just not sure what I'm looking for, to be honest I've never used anything RAID.



On-Board Intel ESB2 RAID controller - 0,1,5,10 SATA RAID



Manufacturer: SuperMicro
Model / Part Number: 6015P-TR
Processor(s): Dual (2x) Intel Xeon 2GHz 5130 Dual Core 64-Bit Processors - 4MB Cache, 1333MHz FSB
Memory: 4GB RAM (4x 1GB PC2-5300) - 8 slots on motherboard

Hard Drive(s): Four (4) Hitachi 500GB 7200RPM SATA Hard Drives
Optical Drive: DVD-ROM
Floppy Drive: Included
Network Interface: Dual 10/100/1000 Gigabit Ethernet
RAID: On-Board Intel ESB2 RAID controller - 0,1,5,10 SATA RAID
Power Supplies: 2 (Redundant) - 700W each
Form Factor: Rack Mount - 1U


I'm not sure the best route to take with RAID for what I'm looking for as I'm totally new to it.







update



At this point, when I select RAID10 from the raid controller and go into Ubuntu server installation it shows 2 separate 500GB drives instead of a single 1 TB drive. Ubuntu is not giving me any RAID options duration installation.



I'm thinking I'm just going to install everything on one of those 500 GB drives for the server, then have all my site's data on the other drive.



I need to get moving on this server, I can't spend weeks working out RAID issues.



Answer



The idea of most RAID levels is to provide better reliability or speed for arrays of disks using a combination of the below methods:




  • striping - splits data speed-efficiently across two or more disks +speed

  • mirroring - copies the data onto two or more disks -capacity +reliability

  • parity - a separate disk(s) to verify the data on the other disks is correct +reliability



You have to decide what's most important for you, capacity, reliability, or speed.




Raid 1+0



The official name for RAID 10 is RAID 1+0. Raid 1+0 is a good compromise between speed and reliability as it combines striping and mirroring. Using Raid 1+0, you will have 1TB of space.



How a RAID 1+0 hardware controller works:



+-----------------------------------------------------+
| | :
| 500GB 500GB 500GB 500GB | :

| | | | | | :
| +-500GB-MIRROR-+ +-500GB-MIRROR-+ | : RAID Controller
| | | | :
| +---------1TB-STRIPE--------+ | :
| | | :
+-------------------------|---------------------------+
|
+-------------------------|---------------------------+
| | | :
| OPERATING SYSTEM | :

| | | : Software
| APPLICATION | :
| | :
+-----------------------------------------------------+


It is important to understand that, with a RAID controller, the operating system knows nothing about RAID or multiple disks, it will merely see a plain, single hard drive. All hardware-controlled RAID configuration must be done through the BIOS.



Redundancy: RAID 1+0 vs RAID 0+1




RAID 0+1 is effectively the same thing as RAID 1+0, just the other way round:



                 RAID 1+0              ¡             RAID 0+1              
|
[#] [#] [#] [#] | [#] [#] [#] [#]
| | | | | | | | |
+-MIRROR-+ +-MIRROR-+ | +-STRIPE-+ +-STRIPE-+
| | | | |
+----STRIPE----+ | +----MIRROR----+
| ! |



RAID 1+0 is far more commonly used, however, because it has better redundancy (smaller chance of array failure because of multiple drive failures). The probability of array failure for each RAID level is:




  • RAID 1+0: 1 drive fails: 0 (0%), 2 drives fail: ⅓ (33%), 3 drives fail: 1 (100%)

  • RAID 0+1: 1 drive fails: 0 (0%), 2 drives fail: ⅔ (66%), 3 drives fail: 1 (100%)


Comments

Popular posts from this blog

linux - iDRAC6 Virtual Media native library cannot be loaded

When attempting to mount Virtual Media on a iDRAC6 IP KVM session I get the following error: I'm using Ubuntu 9.04 and: $ javaws -version Java(TM) Web Start 1.6.0_16 $ uname -a Linux aud22419-linux 2.6.28-15-generic #51-Ubuntu SMP Mon Aug 31 13:39:06 UTC 2009 x86_64 GNU/Linux $ firefox -version Mozilla Firefox 3.0.14, Copyright (c) 1998 - 2009 mozilla.org On Windows + IE it (unsurprisingly) works. I've just gotten off the phone with the Dell tech support and I was told it is known to work on Linux + Firefox, albeit Ubuntu is not supported (by Dell, that is). Has anyone out there managed to mount virtual media in the same scenario?

hp proliant - Smart Array P822 with HBA Mode?

We get an HP DL360 G8 with an Smart Array P822 controller. On that controller will come a HP StorageWorks D2700 . Does anybody know, that it is possible to run the Smart Array P822 in HBA mode? I found only information about the P410i, who can run HBA. If this is not supported, what you think about the LSI 9207-8e controller? Will this fit good in that setup? The Hardware we get is used but all original from HP. The StorageWorks has 25 x 900 GB SAS 10K disks. Because the disks are not new I would like to use only 22 for raid6, and the rest for spare (I need to see if the disk count is optimal or not for zfs). It would be nice if I'm not stick to SAS in future. As OS I would like to install debian stretch with zfs 0.71 as file system and software raid. I have see that hp has an page for debian to. I would like to use hba mode because it is recommend, that zfs know at most as possible about the disk, and I'm independent from the raid controller. For us zfs have many benefits,

apache 2.2 - Server Potentially Compromised -- c99madshell

So, low and behold, a legacy site we've been hosting for a client had a version of FCKEditor that allowed someone to upload the dreaded c99madshell exploit onto our web host. I'm not a big security buff -- frankly I'm just a dev currently responsible for S/A duties due to a loss of personnel. Accordingly, I'd love any help you server-faulters could provide in assessing the damage from the exploit. To give you a bit of information: The file was uploaded into a directory within the webroot, "/_img/fck_uploads/File/". The Apache user and group are restricted such that they can't log in and don't have permissions outside of the directory from which we serve sites. All the files had 770 permissions (user rwx, group rwx, other none) -- something I wanted to fix but was told to hold off on as it wasn't "high priority" (hopefully this changes that). So it seems the hackers could've easily executed the script. Now I wasn't able