One drive cannot be added to raid 0

[X1XNobleX1X]

Hello guys,

I recently purchased three hard drives to put into raid 0. When I go to disc manager two out the three drives allow me to create a stripped volume. the last one that has a portion of it being system reserved, for some reason will only allow me to do a new simple volume.

How do I fix this?

Thanks

[X1XNobleX1X]

Anyone?

[alpenwasser]

Hello guys,

I recently purchased three hard drives to put into raid 0. When I go to disc manager two out the three drives allow me to create a stripped volume. the last one that has a portion of it being system reserved, for some reason will only allow me to do a new simple volume.

How do I fix this?

Thanks

 

 

Anyone?

While I probably won't be able to help you I can mention two things: The forums

are usually not too active at this time of day (at least I get almost no notifications

during the current few hours), and secondly if anyone is going to help you they will

most likely require more info, such as

• your OS
• your controller/disk managing software
• HDD model , maybe

Good night, and good luck. :)

[X1XNobleX1X]

Hmmm now I'm getting an error : an unexpected I/o error has occured

[LapX]

 

 

While I probably won't be able to help you I can mention two things: The forums

are usually not too active at this time of day (at least I get almost no notifications

during the current few hours), and secondly if anyone is going to help you they will

most likely require more info, such as

• your OS
• your controller/disk managing software
• HDD model , maybe

Good night, and good luck. :)

 

Like he said we need those informations to help you. But why a RAID 0 ? Can you back it up with an external hard drive or a nas ? It's risky if you have important data.

[IdeaStormer]

Well first off where those drives used for anything else prior to you trying to setup the raid array? If so you may need to reset those drives as non-raid or non what ever they were used for, deleting the format should be good enough via the Storage manager of a Window 7/Vista system.

 

If you still cannot add all three to the raid array the drive maybe bad, run the drives manufacture test software on it.

[IdeaStormer]

Like he said we need those informations to help you. But why a RAID 0 ? Can you back it up with an external hard drive or a nas ? It's risky if you have important data.

 

If you are using one drive you should also backup. Don't see the point of pointing a finger to RAID 0, when single drive systems are in the same boat.

[LapX]

If you are using one drive you should also backup. Don't see the point of pointing a finger to RAID 0, when single drive systems are in the same boat.

There's 3x more chance of failure am I right ? (3 drives)

[IdeaStormer]

There's 3x more chance of failure am I right ? (3 drives)

 

Yes, 3x more yet every workstation I build uses RAID 0 and guess what, the non-RAID systems die at the same rate as the RAID 0 systems, could it be that a hard drive fails on either the whole thing fails, regardless of RAID? This is the 21st Century man, its not like the hard drives die at the drop of a hat like in the old days. Ugh... at least tell me a sob story where you lost data in a RAID 0 setup you had.

[LapX]

Yes, 3x more yet every workstation I build uses RAID 0 and guess what, the non-RAID systems die at the same rate as the RAID 0 systems, could it be that a hard drive fails on either the whole thing fails, regardless of RAID? This is the 21st Century man, its not like the hard drives die at the drop of a hat like in the old days. Ugh... at least tell me a sob story where you lost data in a RAID 0 setup you had.

No sorry I never used RAID 0, I'm just repeating what I heard Linus say. I should have stayed out of this, I don't really know what I'm talking about. Sorry.

[X1XNobleX1X]

It seems the drive I took out of my other computer seems to be the problem. Once I had disconnected that drive it worked perfectly. What is the solution to getting the last drive to work?

Just an FYI the error I'm getting when the older drive is plugged in is

error : an unexpected I/o error has occured

your OS: windows 7

HDD model WD velociraptor

[IdeaStormer]

Download the Western Digital Drive Tester and see if its bad and what the bad is.

 

http://support.wdc.com/product/download.asp?groupid=612&sid=3〈=en

[X1XNobleX1X]

I ran the tests and it didn't spit out any errors. But now the drive cannot be found. Not in the bios or windows.

[IdeaStormer]

I ran the tests and it didn't spit out any errors. But now the drive cannot be found. Not in the bios or windows.

 

Have you tried using the port/cable of the working drives and placing the other drive in the supposed bad drives port/cable?

[alpenwasser]

There's 3x more chance of failure am I right ? (3 drives)

The chance of one HDD failing are physically the same, but the chance of losing all

your data in that RAID0 configuration is indeed significantly higher than the probability

of losing all your data on 3 independent disks.

I think this is often overlooked. Most people just say "chance is 3x as high" when

comparing RAID0 vs. JBOD. But it's not exactly that simple. In a JBOD arrangement (no

backups assumed), your data depends on x disks (let's assume 3) for 100% completeness

and integrity. The chances of one drive failing within a certain amount of time have

a certain value. If one drive fails you do not lose all your data, but you do lose

a third of it.

If you take a 3 disk RAID0 arrangement, the chances of one HDD failing within those

3 disks is exactly the same as in a JBOD arrangement. However, in case of failure you

lose all your data. So, the chances of losing all your data in RAID0 are the

same as the chances of losing a third of your data in JBOD (I think).

TBH I'm a tad rusty when it comes to probability calculations, so I'm not exactly

sure how much sense this makes and if we have a probability expert around here somewhere

feel free to correct any mistakes I've made and/or explain this better. Probability

can be quite un-intuitive, so I'm a bit unsure of my train of thought to be frank. ;)

Yes, 3x more yet every workstation I build uses RAID 0 and guess what, the non-RAID systems die at the same rate as the RAID 0 systems, could it be that a hard drive fails on either the whole thing fails, regardless of RAID? This is the 21st Century man, its not like the hard drives die at the drop of a hat like in the old days. Ugh... at least tell me a sob story where you lost data in a RAID 0 setup you had.

You wouldn't happen to have any proper sources on this, would you? Not trying to troll

you or start a flame war, but if there's been done some large-scale studies on this I'd

be seriously interested in them. And as said above the statistics and probabilities in

cases like this can become rather complex, so any serious data on this would be much

appreciated.

Hmmm now I'm getting an error : an unexpected I/o error has occured

Whenever I have encountered this error (been a few times now) the cause was either

one of two things: I hadn't connected the drive properly or it was broken.

I ran the tests and it didn't spit out any errors. But now the drive cannot be found. Not in the bios or windows.

I think your drive might be defective.

[X1XNobleX1X]

But I had just pulled it out of my old computer which it was working in .

[alpenwasser]

But I had just pulled it out of my old computer which it was working in .

Do you still have another machine available to test the drive? If it still works it

might also be your controller.

[LapX]

The chance of one HDD failing are physically the same, but the chance of losing all

your data in that RAID0 configuration is indeed significantly higher than the probability

of losing all your data on 3 independent disks.

 

I meant the chances to lose the data 3x higher, thanks for clarifying it.

[IdeaStormer]

You wouldn't happen to have any proper sources on this, would you? Not trying to troll

you or start a flame war, but if there's been done some large-scale studies on this I'd

be seriously interested in them. And as said above the statistics and probabilities in

cases like this can become rather complex, so any serious data on this would be much

appreciated.

 

I haven't done the actual stats but I'm talking about my experience with the workstations/servers I deploy and maintain. Of 26 Workstations so far the older ~'09 systems have had hard drive failures (non-RAID setups) and of the Raid-ed systems none have failed drives yet, some are ~'10 and up to ~'13 in age, so newer but still 100% unless we lose power which so far has been only once for a day or so. Have lost a motherboard as well on the older systems, and 3 of the 6 older systems have had a drive fail. Wait one of the '10 systems did have a bad drive but I caught it before it failed, still have it and use it to run tests, just bad sectors and was in a RAID 10 array so didn't kill that.

 

I guess I could make a spread sheet to log it all but I'm just going off of what I am seeing day to day. Sure RAID 0 can be risky but its also faster which tends to make users happier in day to day use. Those users also have all their data NFS mounted so if a machine dies they just log on to another and well don't miss a beat, except maybe their chair. Data planning or backup is key before you start I do agree, but saying RAID 0 is dangerous of risky is well not true at all, its performance with some risk I do agree but its well worth it and why its used and offered on almost all motherboards these days. Why would a company offer you a feature it thought would be bad for you? Assuming you know what you're doing of course. A single drive systems is equally as dangerous as a RAID 0 system, and no single drive person has proven or provided any data or story on how they have proven that to be true, other than printed stats, which are not reality.

[alpenwasser]

I'll take that, 26 machines isn't too bad :)

I do agree that, as long as one knows about the risks and plans accordingly, RAID0

is perfectly OK. It's the same as with every other tool/technology: You need to know

for what purpose it is intended to be used under what sort of conditions and deploy it

accordingly, and then all will be hunky dory (unless of course Finagle's Law decides to

start playing with you and everything fails everywhere :lol: ).

[IdeaStormer]

But I had just pulled it out of my old computer which it was working in .

 

Well it could of died? I have seen cases where a drive decides its not going to work on another system but most likely due to a mis-configured SATA Port. Is the port set to ON or Hot Swap? Is it recognized in BIOS? If not have you placed the drive in a SATA slot of a working drive?