What happens if a disk fails in jbod

Sign up using Facebook. Sign up using Email and Password. Post as a guest Name. Email Required, but never shown. The Overflow Blog. Podcast Explaining the semiconductor shortage, and how it might end.

Does ES6 make JavaScript frameworks obsolete? Featured on Meta. Now live: A fully responsive profile. Related 1. Hot Network Questions. Question feed. Super User works best with JavaScript enabled.

Accept all cookies Customize settings. Hopefully that 4th disk is in fact a Seagate so I'll be able to identify the bad one easily. During the first run, I won't select the option that says "Fix Bad Sectors" or whatever; I'll just run it to find out if and how many bad sectors there are.

I realize that if there's a lot, it will take forever for Windows to correct them, so I'll wait to do that only if you recommend it. If there's some other step I should be doing first, please let me know.

Also, what if the drive won't be recognized by Windows and Device Manager at all when I attach it separately? Is there anything I can do at that point, other than chuck it in the garbage? Thanks again for your continued help! Well a Disk Check will not help up here. That is only meant for partitions. When you find the bad drive which is probably the drive you are talking about since there are in fact 3 1TB WD's in there from the screenshot then yes you are correct in trying to use a SATA to USB adapter or something similar.

If we can read it great! If it still doesn't come up even after that I'd also try a different SATA port as well But if it doesn't come up then the drive just might be dead. Might only make it worse.

But if we can't get a PC to see the drive then there isn't much more i could help you with. You would have to send it in to a Pro with all 4 Drives and see what they could do. Thanks for the knowledge! I'm going to take the bad drive out and attach it separately this afternoon, so I should have some answers for you soon. That's interesting what you mentioned about swapping out the PCB board if the drives are, in fact, identical.

I suppose there's a chance that 4th drive is another one of those WD's I have two of. I'll find out when I crack open my case. I'll be back shortly with whatever results I find. Sorry it took me so long to reply, drtweak. It was easy to determine which drive was bad, and it turned out it was a Seagate Barracuda When I connected it to my PC and powered it on, it made the sound that a normally-functioning HDD makes when first turned on it "wound" up. However, after winding up for about 5 seconds, it made a clicking sound, followed by "sliding" sound sort of a "click-wooosh, click-woosh".

It did this times before the drive "wound" down and stopped making any noise, as though is was shutting itself off. Nothing on my PC to indicate it was recognized no driver loading message, nothing showed up in Device Manager so obviously there's a major problem. When I powered it off, there was no sound at all, as if it had already shut itself off after the set of "click-wooshes. Now for the hopefully good news: I have an exact duplicate of this Seagate drive that's fully functional, so perhaps your idea of swapping the PCB would work, and allow the bad drive to power on normally.

Is it literally just a matter of unscrewing the PCB off the good drive and screwing it onto the bad one? If you need me to post pics of the two, identical drives, I certainly can if you need to compare the identifying information on each drive to confirm that they're, in fact, identical.

They literally have the same firmware and date code, so I'm hopeful the PCB-swap idea is one we can pursue in this case. If there's anything else I need to know prior to attempting this, please let me know. I'll await your reply before venturing into this. Thanks again for your attentiveness to this on-going saga! Not as easy I thought it would be.

They're like the smallest heads I've ever seen, and they're sort of star-shaped, like an asterisk. I don't have anything that small to unscrew those with, and I've got one of those multi-tools with the flip out rods that you'd think would cover every screw head possible!

Any insights as to what I need to get those screws off? But yea they are Torx screws. Probably like a T6 size screw. Again be careful and do this at your own risk. The thing is because its a clicking sound it may not be the PCB it could be the heads and may just not work. So again if you swap them and screw up everything even worst then yea don't blame me lol.

I have have in the past successfully swapped PCB's before and have them work. No sweat, drtweak. I did a lot of reading last night and discovered just how bad these It all seemed to point to two issues that seem to happen to a lot of them, but they're firmware issues, and from what I read, the 11 clicking noises which is what mine does indicates something wrong with the head.

I tried the PCB swap to no avail. It's hard to know what to do now. I couldn't find exactly what you're supposed to do when this issue arises. I saw a few videos that showed you how to supposedly correct a stuck head, but they involved opening up the drive and exposing the platters, which I'm not really prepared to do without a cleanroom and the right tools.

The thing that sucks is when this issue occurs, the data is usually fine in most cases, at least from what I could find. OT: the risk you're always running at least is losing the data on the drive that fails, as you would with any hard drive. Not sure how it handles drive failures, although I wouldn't expect it to be too difficult to recover data from the good drives. Wouldn't plan on it personally though. If you have the JBOD appear as, say, 9 different drive letters or mount points, then one disk failure will take out one drive letter.

The controllers should be interchangeable, of course, it could go down in flames in such a way that it destroys everything, but that's life. However, that all depends on the controller and how it writes data to the disks.

If you have two 20GB disks in a JBOD config with only 5GB of info on it it's possible one drive could die and the other drive could have nothing on it. For your situation JBOD might be a good fit, though, at least temporarily. BTW, how big are the drives in your system? No striping, no spanning, nothing. End of story. They're saying that taking two or more hard drives and spanning them into a single volume is called JBOD?!

JBOD is just a bunch of disks. Nothing more. No spanning or mirroring. Get this: "Disc Spanning. That makes complete sense. Spanning stores data on to a drive until it is full, then proceeds to store files onto the next drive in the array. There are no additional performance or fault tolerance array features in this array. When any disk member fails, the failure affects the entire array. There are no performance or fault-tolerance features.

When a disk fails, all data on the disk is lost. Other disks are unaffected. OP: Want the real poop? Call Promise. It's on your nickel, but they generally will give you a straight answer. If you haven't already, go to MS Technet and read up on the features of NTFS and dynamic disks not that dynamic disks are required to mount drives to folders, but dd offers other options for volume manangement. Note that the original raid advisory board only defined 1 through 5, and then later added 6, which no company has implemented yet to my knowledge.

Given this faint praise, why would you consider using JBOD architecture? In a MSExchange.