Adding Drives to a RAID 5

I have a XSERVE RAID with 4 250GB drives configured as a RAID 5. We're starting to get low on space so I'd like to expand the capacity by adding some drives.
Is there a specific number of drives I need to add or can I add 1, 2 or 3 drives as long as they're on the same controller?
Mac OS X (10.4.6)

This is incorrect.
The Xserve RAID does not ship with any file system on it whatsoever. It is just disks, set up in a RAID configuration that you specify.
You can format the RAID volume as HFS+ if you connect it to a Mac. You can format it with NTFS if you connect it to a Windows machine. Or ZFS on a Solaris box, etc.
What you CANNOT easily do is grow a volume. Period.
Buy the RAID with 7 drives, or with 14 drives. If you buy a "2 TB" one (what is this -- 4x500 GB drives? Recall that is about 1.3 TB of usable space in RAID 5)... plan on reformatting if you add 3 drives later. Plan on it. I mean it: plan on it. Growing the RAID is complicated and unless you want to set up a concatenated RAID set, it's what you MUST do to grow the volume.
Again, my advice could not be clearer (search back as well, I've stated this many, many times): Buy the RAID with 7 drives, or with 14, and NEVER plan on growing the RAID by adding drives WITHOUT reformatting. Period.

Similar Messages

Adding Drive to Concatenated RAID in Disk Utility

Hello,
I'm having a spot of trouble with Disk Utility. 24 hours ago I added a new drive to a Concatenated Raid through Disk Utility, and clicked Update to set the process going.
Now it's not responding. It just claims to be updating. I struggle to believe that it takes this long though!
I didn't format the disk before adding it to the RAID. Is this what's causing the upset?
When I try to cancel it tells me I risk losing data on the disk. I'm not sure if it means the new disk or all disks on the array - which is a terrifying prospect. If I quit Disk Utility, will my existing data on the array be safe?
Thanks in advance for the help,
Ben

The drives are in Sonnet P500 enclosures and connected to the MacPro via a Sonnet SATA card.
On purhcase I was told this could be done, as it's a Concatenated JBOD setup. For a better description of what I mean by that, this wiki article describes it well http://en.wikipedia.org/wiki/StandardRAIDlevels.
Does this provide any further clues?
Currently there are 7x 1TB drives in 2 enclosures. I've now added 2 more 1TB drives. I can currently see and continue to use the data on the existing 7 drives. My worry though is that if I quit the disk utility I may lose the data on the 7 original drives.

Adding Drives to an Existing RAID 0 Stripe Set

I have 4 HDDs (250x1 and 320x3). While the OS is installed on the 250gb disk the rest of the three disks are striped.
I want to share files that are on my RAID Set. As OSX supports sharing of files only in the HOME directory, I now want to reinstall OSX on my stripe set.
My questions!?
1. Can OSX be installed on a striped set?
2. Can a fresh (identical) HDD be added to an existing RAID 0 set (configured using the Disk Utility)?
3. Is it possible to install OSX 10.4.x Tiger on a MAC Pro with 4 HDDs all configured as RAID 0 OR as RAID 1 (2HDDs) / RAID 0 (2 HDDs) Combination?
4. Can the default Home Directory location be changed to another volume, other than the startup volume?
Thanks in advance!

1) Yes.
2) Yes although the data on the current RAID set will be deleted.
3) Yes.
4) Yes.

Hard Drive stuck in RAID limbo

I formatted a 186.3 GB and 279.5 GB drive into an MS-DOS Concatenated RAID. I did this because I had read that you can add on new drives without reformatting the whole RAID set.
http://discussions.apple.com/thread.jspa?messageID=664639&#664639
http://discussions.apple.com/thread.jspa?messageID=594757&#594757
Even Disk Utility's Help files says that it's possible.
http://docs.info.apple.com/article.html?path=DiskUtility/10.5/en/duh1948.html
Well, I added another 186.3 GB drive, but the new space doesn't appear. I read that on +HFS setups adding drives may not work but I'm using a FAT32 setup. I don't understand where I went wrong.
Right now the drive is just sitting here. The RAID won't mount without it but it's space isn't being recognized so it's just stuck in limbo. Can anybody tell me how I can allow the space to be accessed or how to separate the drive? Anything is better than it just doing nothing.
The drives are located externally through a firewire Coolgear CGS-213FB brideboard with an Inito 2430L chip. The board allows for 4 drives.

Pannn-
Greetings and welcome to the Apple boards.
Have you seen this hard drive replacement manual? It does mention something about using a flat head screwdriver to pry apart hinges when you meet resistance.
Luck-
-DaddyPaycheck

I had a power mac g4 into which i put 3, 320 gb PATA hard drives in a raid slice config so that it worked as one drive needless to sat that i lost the g4 to a surge but the drives are good. now i have an imac, how can i recover the info off those drives

i had a power mac g4 into which i put 3, 320 gb PATA hard drives in a raid slice config so that it worked as one drive needless to sat that i lost the g4 to a surge but the drives are good. now i have an imac, how can i recover the info off those drives. can i put the drives in external cases and plug them all in, will the imac see them as a raid slice then help please

Before you have another accident:
Buy a UPS of good quality and sufficient to your needs.
I would have to assume that the drives were connected to a PCI PATA card, hopefully. Otherwise, well RAID and having drives on the same bus (master and slave).
And no backup, none at all...
Get your hands on a G4.
Data Rescue 3 from Prosoft maybe.
If they were SATA and running on PCI SATA controller, very popular and common really in G4s, more options would be open.

BIOS setup for SSB boot drive and 2 RAID 0 data drives

I'm trying to setup my new rig. I was able to get Win 7 to see all drives when plugged into the white SATA connectors. This with no BIOS RAID. If I change the BIOS from AHCI to RAID, Windows fails to boot completely.
After some research, I tried plugging the SSD boot drive into the JMicron controlled blue SATA 7 connector. It works. The 2 WD 640's are in the South Bridge controlled SATA 1-6 connectors (3 & 4). Windows sees the drives with On-Chip ATA Devices set to AHCI. I can setup the 640's with On-Chip ATA Devices set to RAID and the BIOS sees them during boot up, but Windows can't. I did install the RAID drivers as specified in the manual Appendix B.
My system specs are in my sig. I don't see them in preview, so I hope the show up.
So, what did I miss? Thanks if advance for any assistance!
Scott

I did this from the manual appendix B:
Installing the RAID Driver Under Windows
(for Non-bootable RAID Array)
1. Insert the MSI DVD into the DVD-ROM drive.
2. The DVD will auto-run and the setup screen will appear.
3. Under the Driver tab, click on AMD chipset drivers by your need. The AMD chipset
drivers includes RAID Driver.
4. The driver will be automatically installed.
Plus, I installed the JMB36x drive under the RAID button on the MSI CD.

Where to buy new drives for Xserve RAID

I have been looking all over to buy NEW drives for my RAID. Can anyone direct me where to go to buy new drives with the slot attachment? 500GB or 750GB
Forgive my lack of specific/correct terminology - I am a newbie when it comes to the RAID.
Thanks in advance!
Brian

I think the fine print says DVD Player support requires 10.3 or higher. But you can still play DVDs in the original drive you have, and are looking to add a drive in the empty bay, right?
Also, Patchburn is available for 10.2 to add native burning support, or you can maybe find an old version of Toast (5 ?) for 10.2 that should allow you to burn to the drive.
http://patchburn.de/download.html
I agree with the suggestion to upgrade to 10.3 or 10.4, if you can, but you should be able to make this drive work in 10.2 (and still use the original for OS 9 and DVD Player) and decide to do the other upgrades later on if you want.
http://eshop.macsales.com/item/Pioneer/DVR112/

How to identify physical drives in software RAID?

I've got 6 G-Tech 2TB drives in a RAID 10 configration hanging off of an older Mac Mini. A couple of the slices have started to act up leading me to believe one day soon I might need to replace a drive in the event the automatic rebuild fails. The trouble is I do not know how to associate the slice name (disk'n's2) with the actual physical device. Any ideas on how to do this?

How are they connected & what OSX version?
If SATA, in System Profiler>More Info>Hardware>Serial-ATA, once I highlight the manufactures name it shows the Serial#, at least in 10.5.8

How to setup x2 sata W/D Raptor drives not using raid

Hi all,
I am new to this forum so please be kind.
I have just got myself this NE02 board along with 2 W/D Raptor SATA Hard Drives.
I have seem many instructions in these groups about how to configure sata drives using a raid configuration.
What I am looking to do is basically install 2 Raptor SATA drives not using raid,
And also have 2 ide cdrom drives.
Can someone please come back with a nice simple if that can be done! configuration on how i can best achive this.
Many thanks for all your help.
Silent2004

In bios under Integrated Peripherals, On Chip ATA Operating Mode set
Native Mode
ATA Configuration - SATA only
SATA Keep enabled - yes
PATA Keep enabled - yes
PATA channel selection - both
Configure SATA as Raid - no
Read the raid thread at the top anyway, as you may want to install the drivers during the XP install in case you change your mind later.
Also, during your Windows installation, just connect a single SATA drive untill you are up and running.
Read P4 Neo Unofficial Guide for more information.

0xc0000135 while adding driver packages to boot image

Hi, I am currently having issues adding driver packages to the boot image.
Currently running Server 2008 R2 and have MDT 2013 installed.
Tried searching for the error but no luck. No matter if I choose the specific driver I want to add or if I just start from the beginning it just constantly fails. Does anybody have any clue as to what could be causing it to not accept either from the boot image
created from MDT Deployment Share or even using a generic boot image?

Hi,
First make sure you are using the correct version of DISM
Secondly look at this http://social.technet.microsoft.com/Forums/en-US/ff8509ec-0ddd-4ad8-9e53-ecf527a80919/dismexe-is-failing-to-add-drivers-to-a-mounted-image-file?forum=w7itproinstall

Proper procedure for replacing drive in Xserve RAID RAID5 set

I've got a five-drive RAID-5 set (with a sixth hot spare) in an Xserve RAID running the 1.5/1.50f firmware. One of the drives in the RAID-5 set has an amber/orange status light on and has been getting occasional errors like to following:
Timestamp: 11/10/10 10:34:53 AM
Priority: Warning
Controller: Upper Controller
Type: 112
Event ID: 1000
Event: Disk 5 Reported An Error. COMMAND:0x35 ERROR:0x10 STATUS:0x51 LBA:0x19B80
Description: The drive reported an ATA error. This is a failure in the communication from the RAID Controller to the drive.
I have double checked the drives in RAID Admin and, as the drive is only in a warning state, the hot spare has not been pulled into the RAID set yet. As this is an old drive, I'd like to replace that particular drive first. I have a current, full backup of the data, but want to make sure I understand the process correctly.
I understand the "Installing or Replacing an Apple Drive Module" section of http://manuals.info.apple.com/en/XserveRAID_UserGuide.PDF, but it and RAID Admin's built-in help don't describe what will happen when replacing a drive in a RAID set that has a hot spare. When I pull out the drive and replace it, will it correctly use the newly inserted drive or will it use the hot spare? If it uses the hot spare, will the hot spare revert back to a hot spare once the new drive is inserted or will it permanently become a member of the RAID set and need to be moved to the original drive's slot? Or, should I just pull out the hot spare, pull out the failing drive, and pop the hot spare into the failing drive's slot?

Hello, makkintosshu, and welcome to the AppleBoards,
If you pull out the drive the RAID should/will immediately start rebuilding using the hot spare. The hot spare will become a new permanent member of the RAID and the new replacement drive will become the new hot spare. The physical slot locations of the drives don't matter you can build a RAID from any combination of drives as long as they are on the same side.
If you pull the hot spare and then the failing drive the RAID will wait for a new drive before taking action. I find it hard to recommend this course of action unless there is a really good reason for you not wanting the hot spare to become part of the RAID. Rebuilding is going to take a good long while and you want it to start as soon as possible - as long as the RAID is not rebuilt your data is at risk. Letting the RAID rebuild hang as you physically swap out the failed the drive strikes me as bad idea that needs a really good justification.
HTH,
=Tod

[SOLVED] Possibly dead hard drive or bad raid setup...

I have a 4 drive raid5 running. Just recently one of the drives kept removing itself from the array. I have re / formated / partitioned the drive multiple times, but either mdadm doesn't accept the drive, or it accepts, resyncs, and when i try to access the raid it fails again.
I eventually pulled the drive out and plugged it into my desktop machine. That machine recognized the partition fine. However after putting the drive back into the raid i receive these sort of errors on startup:
Jun 8 17:04:41 localhost kernel: [ 213.942913] ata3.00: failed command: READ DMA
Jun 8 17:04:41 localhost kernel: [ 213.942922] ata3.00: cmd c8/00:08:40:10:00/00:00:00:00:00/e0 tag 0 dma 4096 in
Jun 8 17:04:41 localhost kernel: [ 213.942924] res 51/40:00:40:10:00/00:00:00:00:00/e0 Emask 0x9 (media error)
Jun 8 17:04:41 localhost kernel: [ 213.942928] ata3.00: status: { DRDY ERR }
Jun 8 17:04:41 localhost kernel: [ 213.942931] ata3.00: error: { UNC }
Jun 8 17:04:41 localhost kernel: [ 213.979780] ata3.00: configured for UDMA/133
Jun 8 17:04:41 localhost kernel: [ 213.979794] ata3: EH complete
Jun 8 17:04:44 localhost kernel: [ 216.508311] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Jun 8 17:04:44 localhost kernel: [ 216.508316] ata3.00: BMDMA stat 0x24
Jun 8 17:04:44 localhost kernel: [ 216.508321] ata3.00: failed command: READ DMA
Jun 8 17:04:44 localhost kernel: [ 216.508330] ata3.00: cmd c8/00:08:40:10:00/00:00:00:00:00/e0 tag 0 dma 4096 in
Jun 8 17:04:44 localhost kernel: [ 216.508332] res 51/40:00:40:10:00/00:00:00:00:00/e0 Emask 0x9 (media error)
Jun 8 17:04:44 localhost kernel: [ 216.508336] ata3.00: status: { DRDY ERR }
Jun 8 17:04:44 localhost kernel: [ 216.508339] ata3.00: error: { UNC }
Jun 8 17:04:44 localhost kernel: [ 216.538146] ata3.00: configured for UDMA/133
Jun 8 17:04:44 localhost kernel: [ 216.538160] ata3: EH complete
Jun 8 17:04:47 localhost kernel: [ 219.073696] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Jun 8 17:04:47 localhost kernel: [ 219.073701] ata3.00: BMDMA stat 0x24
Jun 8 17:04:47 localhost kernel: [ 219.073705] ata3.00: failed command: READ DMA
Jun 8 17:04:47 localhost kernel: [ 219.073714] ata3.00: cmd c8/00:08:40:10:00/00:00:00:00:00/e0 tag 0 dma 4096 in
Jun 8 17:04:47 localhost kernel: [ 219.073716] res 51/40:00:40:10:00/00:00:00:00:00/e0 Emask 0x9 (media error)
Jun 8 17:04:47 localhost kernel: [ 219.073720] ata3.00: status: { DRDY ERR }
Jun 8 17:04:47 localhost kernel: [ 219.073723] ata3.00: error: { UNC }
Jun 8 17:04:52 localhost kernel: [ 224.093967] ata3.00: qc timeout (cmd 0x27)
Jun 8 17:04:52 localhost kernel: [ 224.093972] ata3.00: failed to read native max address (err_mask=0x4)
Jun 8 17:04:52 localhost kernel: [ 224.093976] ata3.00: HPA support seems broken, skipping HPA handling
Jun 8 17:04:52 localhost kernel: [ 224.093980] ata3.00: revalidation failed (errno=-5)
Jun 8 17:04:52 localhost kernel: [ 224.093989] ata3: hard resetting link
Jun 8 17:04:52 localhost kernel: [ 224.567030] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Jun 8 17:04:52 localhost kernel: [ 224.587154] ata3.00: configured for UDMA/133
Jun 8 17:04:52 localhost kernel: [ 224.587174] sd 2:0:0:0: [sde] Unhandled sense code
Jun 8 17:04:52 localhost kernel: [ 224.587177] sd 2:0:0:0: [sde] Result: hostbyte=0x00 driverbyte=0x08
Jun 8 17:04:52 localhost kernel: [ 224.587182] sd 2:0:0:0: [sde] Sense Key : 0x3 [current] [descriptor]
Jun 8 17:04:52 localhost kernel: [ 224.587187] Descriptor sense data with sense descriptors (in hex):
Jun 8 17:04:52 localhost kernel: [ 224.587190] 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
Jun 8 17:04:52 localhost kernel: [ 224.587202] 00 00 10 40
Jun 8 17:04:52 localhost kernel: [ 224.587207] sd 2:0:0:0: [sde] ASC=0x11 ASCQ=0x4
Jun 8 17:04:52 localhost kernel: [ 224.587212] sd 2:0:0:0: [sde] CDB: cdb[0]=0x28: 28 00 00 00 10 40 00 00 08 00
Jun 8 17:04:52 localhost kernel: [ 224.587223] end_request: I/O error, dev sde, sector 4160
Jun 8 17:04:52 localhost kernel: [ 224.587228] Buffer I/O error on device sde1, logical block 512
I have tried using SMART to test the drives, however all the drives seem to fail with some sort of error. I believe this is a false positive as I have read elsewhere that the 1TB Green Western Digitals (WD10EARS) seem to have problems with SMART.
Is this drive dead? Its only a year old... and unfortunately just out of warranty.
Last edited by passbe (2011-06-24 08:52:16)

Ok so i zero filled /dev/sde, and re-added it back to the array. It synced (for 2 days), and then my RAID5 completely failed. I can't bring it back up at all now. My BIOS says one of the hard drives is dead (SMART error). Fair enough drive is dead. But now i cant get the 3 drives back up and running in the RAID.
I have attempted the following:
sudo mdadm --assemble -vv /dev/md127 /dev/sdb1 /dev/sdc1 /dev/sdd1
mdadm: looking for devices for /dev/md127
mdadm: cannot open device /dev/sdb1: Device or resource busy
mdadm: /dev/sdb1 has no superblock - assembly aborted
It complains that every device does not have a superblock?
A mdadm --examine on each drive:
/dev/sdb1
Magic : a92b4efc
Version : 1.2
Feature Map : 0x0
Array UUID : e3da6078:d4699e2d:c1da42cc:d58a42bf
Name : myhost:0
Creation Time : Sun Feb 27 09:27:39 2011
Raid Level : raid5
Raid Devices : 4
Avail Dev Size : 1953517954 (931.51 GiB 1000.20 GB)
Array Size : 5860552704 (2794.53 GiB 3000.60 GB)
Used Dev Size : 1953517568 (931.51 GiB 1000.20 GB)
Data Offset : 2048 sectors
Super Offset : 8 sectors
State : clean
Device UUID : 95618add:2d0b86be:d06cc198:1a5e101f
Update Time : Tue Jun 14 20:44:51 2011
Checksum : 51b4a80f - correct
Events : 4808
Layout : left-symmetric
Chunk Size : 512K
Device Role : Active device 0
Array State : A.A. ('A' == active, '.' == missing)
/dev/sdc1
Magic : a92b4efc
Version : 1.2
Feature Map : 0x0
Array UUID : e3da6078:d4699e2d:c1da42cc:d58a42bf
Name : myhost:0
Creation Time : Sun Feb 27 09:27:39 2011
Raid Level : raid5
Raid Devices : 4
Avail Dev Size : 1953517954 (931.51 GiB 1000.20 GB)
Array Size : 5860552704 (2794.53 GiB 3000.60 GB)
Used Dev Size : 1953517568 (931.51 GiB 1000.20 GB)
Data Offset : 2048 sectors
Super Offset : 8 sectors
State : clean
Device UUID : 3056502e:51e004d0:4380f027:fe2d9ebc
Update Time : Tue Jun 14 20:44:51 2011
Checksum : e0b65526 - correct
Events : 4808
Layout : left-symmetric
Chunk Size : 512K
Device Role : Active device 2
Array State : A.A. ('A' == active, '.' == missing)
/dev/sdd1
Magic : a92b4efc
Version : 1.2
Feature Map : 0x0
Array UUID : e3da6078:d4699e2d:c1da42cc:d58a42bf
Name : myhost:0
Creation Time : Sun Feb 27 09:27:39 2011
Raid Level : raid5
Raid Devices : 4
Avail Dev Size : 1953517954 (931.51 GiB 1000.20 GB)
Array Size : 5860552704 (2794.53 GiB 3000.60 GB)
Used Dev Size : 1953517568 (931.51 GiB 1000.20 GB)
Data Offset : 2048 sectors
Super Offset : 8 sectors
State : clean
Device UUID : 3b7ea2c8:9fd80575:94fbe3a0:cde69026
Update Time : Tue Jun 14 20:34:16 2011
Checksum : 2f1a716 - correct
Events : 4791
Layout : left-symmetric
Chunk Size : 512K
Device Role : Active device 1
Array State : AAAA ('A' == active, '.' == missing)
/dev/sde1 (This is the bad drive)
Magic : a92b4efc
Version : 1.2
Feature Map : 0x0
Array UUID : e3da6078:d4699e2d:c1da42cc:d58a42bf
Name : myhost:0
Creation Time : Sun Feb 27 09:27:39 2011
Raid Level : raid5
Raid Devices : 4
Avail Dev Size : 1953523057 (931.51 GiB 1000.20 GB)
Array Size : 5860552704 (2794.53 GiB 3000.60 GB)
Used Dev Size : 1953517568 (931.51 GiB 1000.20 GB)
Data Offset : 2048 sectors
Super Offset : 8 sectors
State : clean
Device UUID : bad3c5fd:3e439065:957ca15a:412339dc
Update Time : Tue Jun 14 20:44:51 2011
Checksum : 98033b24 - correct
Events : 4808
Layout : left-symmetric
Chunk Size : 512K
Device Role : spare
Array State : A.A. ('A' == active, '.' == missing)
The only difference being that /dev/sdd1 thinks that the RAID has all four devices? Where do i go from here, I'm completely stuck and about to loose 50% of my data. Help!?!

Hard drive setup on raid with XP

Ok, My motherboard is the kt3 ultra aru. I have just added a third hard drive onto ide # 3. Raid is set to on in the bios. The machine dual boots with win98 and xp.
Everything is working fine with win98 and the drive shows up and has a drive letter assigned.
In xp, when it comes to new hardware found and it asks for the raid driver it also says it needs a file from online and when I connect it pauses for a while then continues to ask for the driver, which it installs from the floppy.
I then get the message that the installation has failed and the drive doesnt show up.
Device manager shows a yellow question mark.
Anyone had this happen ??
Any ideas ?
cheers bluedog

Yes I have read that post and understand it.
As I said, the installation into win 98 went without a hitch. But the problem arises when trying to install the promise driver for win xp and it asks to go to the windows update.microsoft.com and get a file.
I have tried to find an updated promise driver with no joy, they dont list one on the promise site.
i'm stuck ;(

Can I config. a SSD with two SATA drives on a RAID pro card?

Hello,
I'm planning to order the new Mac Pro (hexa 3.33) and want to run OS X and my main applications off of it for speed. I was planning to get two SATA drives and connect them with a RAID pro card. Is this set up compatible (i.e. running an SSD with a RAID pro card installed in the system)?
The reason why I'm asking is that on the APPLE build your MAC site there is a note about the RAID pro card:
"Note: Solid-state drives are not compatible with the Mac Pro RAID Card in either RAID or Enhanced JBOD mode. To add a solid-state drive to your Mac Pro in any drive bay, you must deselect the Mac Pro RAID Card."
Thanks for your help guys (and gals)

Thanks. I have the Apple RAID card in my Early 2008 Mac Pro and it's served me reasonably well. I use it for RAID-5 and I don't care about booting Windows so that's not an issue for me (though I confess that I hadn't even considered the implications for Windows).
I bought the system with one Apple drive (a 1TB Hitachi) and added three additional Seagate 1TB drives and have had no problems beyond the need to replace a failed drive, and in that case the array was rebuilt and the system is behaving well again.
Ah, so you're talking about third-party SATA controllers that go in a PCI Express slot, to which one would connect a third-party RAID enclosure via eSATA, is that correct?
Concerning the additional SATA ports on the Mac Pro motherboard: I don't know about the just-announced models, but MacSales was/is selling a SATA cable for the prior model--apparently that model has one additional SATA port (not two) on the motherboard.
By the way: I had a question in another thread (http://discussions.apple.com/thread.jspa?threadID=2545031) about whether it's possible to upgrade my Apple-card-managed RAID-5 array in place. If you (or anyone else with expertise) could take a quick look, I'd appreciate it.

Missing a hard drive in a RAID

I noticed today that /proc/mdstat isn't quite as it should be, namely:
Personalities : [raid6] [raid5] [raid4] [raid1]
md2 : active raid1 sda2[0] sdc2[2] sdb2[1]
2000000 blocks [3/3] [UUU]
md1 : active raid1 sda1[0] sdb1[1]
192640 blocks [3/2] [UU_]
md0 : active raid5 sda3[0] sdb3[1]
972382080 blocks level 5, 64k chunk, algorithm 2 [3/2] [UU_]
unused devices: <none>
This is md2 has all three drives, but md0 and md1 do not and are hence degraded. Not sure how long it has been like this. The program 'mdadm' reports that:
Number Major Minor RaidDevice State
0 8 3 0 active sync /dev/sda3
1 8 19 1 active sync /dev/sdb3
2 0 0 2 removed
I assume this is different to failed somehow (espeically since md2 is fine). Has anyone got some tips on how to debug this further? Thanks.

I am having the same problem with a 2 disk raid 1 array. I tried readding the missing disk and got an error.
Personalities : [raid1]
md0 : active raid1 sdc1[0]
732571904 blocks [2/1] [U_]
Personalities : [raid1]
md0 : active raid1 sdc1[0]
732571904 blocks [2/1] [U_]
unused devices: <none>
[root@will bill]# mdadm
Usage: mdadm --help
for help
[root@will bill]# cat /proc/mdstat
Personalities : [raid1]
md0 : active raid1 sdc1[0]
732571904 blocks [2/1] [U_]
unused devices: <none>
mdadm: /dev/sdd1 does not appear to be an md device
relevant info from blkid
/dev/md0: LABEL="DATA" UUID="7943ec50-8669-47ab-b6e2-ff931c3d1f6b" TYPE="ext4"
/dev/sdc1: UUID="ca184520-f9f6-4d38-8ec5-336832aadbe8" TYPE="linux_raid_member"
/dev/sdd1: UUID="ca184520-f9f6-4d38-8ec5-336832aadbe8" TYPE="linux_raid_member"
Is the next step to reformat that drive and try adding it again even though smartctl and fdisk -l both seem to indicate that it is fine and formatted as linux raid autodetect?

Adding Drives to a RAID 5

Similar Messages

Maybe you are looking for