Failure
One of the WD SATA 120Gig JB's in my array just died a very horrid death.
I've spent the better part of today trying to save it thinking that I'd just got fubar'ed data on the drive from my follies with the old bios but I'm begining to think that half the trouble I was having in oc'ing with the old bios was the fact that the drive was failing.
After I get the new drive from RMA I'm not sure if I'll transfer all the info on this drive over to a spare 40gig I've got laying around and ghost that back onto a new array or just go with 2 separate 120Gig drives.
Any suggestions?
I've spent the better part of today trying to save it thinking that I'd just got fubar'ed data on the drive from my follies with the old bios but I'm begining to think that half the trouble I was having in oc'ing with the old bios was the fact that the drive was failing.
After I get the new drive from RMA I'm not sure if I'll transfer all the info on this drive over to a spare 40gig I've got laying around and ghost that back onto a new array or just go with 2 separate 120Gig drives.
Any suggestions?
0
Comments
Except for servers of DB intense work, I would not bother with a volume-brdiging array with a physical HD size of 120 each even these days. Either seperate and use one HD as a Ghost target at need, or sperate with second HD HALF as ghost target, or as a full mirror for array on a non-server box, once you grok bridges (other good reason to do volume bridging is to LEARN about it, but if no needs critically, learn only and log it for later reference, then use mirroring until you need it.).
Your decison, NEEDS based. Which is good depends on your data needs, and data needs only typically treble or quadruple over two-three years, not sextuple in size under normal use in that time frame UNLESS normal use for you is video or DB work that needs LOTS of HD acerage.
John.
I need the acreage because I save all my pic.s, music and games to my drive.
Consider this; I filled up 68.3gigs since I built this machine in August of this year.
I like running a stripe to allow higher speed transfers for faster load times in the games I play.
I'd be thrilled normally but 1.) this was half of an array stripe so I won't be able to rebuild my array without having 40gigs hidden from use.
2.) I'm kind of wondering if maybe this is an indicator that WD found that this drive has problems and their idea of damage control is to just stop making them.
If that's the case I wouldn't want to build another array with the 120 and the 160 striped anyways because if the 120 I still have died I'd end up in the same boat I'm in now.
To give myself a bit of mental ease I'm planning on ghosting everything from ther 120 to the 160 and formating the 120 to use as storage for files that I can afford to lose and just have my games and OS on the 160.
I'm actually kinda hoping the 120 takes a dump so I can get a second 160 and go back to running an array.
I speak in redundancies I know but it's just so frustrating.
I think I would mirror array the thing, hide 40 GIG on the 160, and GHOST core stuff to that with target hidden....
John.
I don't think that's necessarily true with the Western Digitals. They've had special edition 120 Gigers (IDE) for at least 1.5 years. I bought my first one over a year ago and my other one a couple of months ago. I think the Special Edition is just to differentiate the 8mb cache versus the 2mb. Although WD now sells 8mb cache non Special Edition drives. They are in fact the same and in most cases still hold the 3 year MFR Warranty that the SE does.
I would keep an eye out for good deals on the 160 gigs. That way you could setup your array and still have the 120 handy. There have been some crazy deals as of late.
I just wonder about the fitness of the 120 SATA drives as I've read in here where someone else had one half of their array built upon the same drive do the same thing.
Oddly enough I think I've seen it in Max PC as well.
Oh well, if this one dies I'll tell them that they owe me another 160gig drive, it's still got another 2.5 years left on the warranty.