WD RED 2TB - Partitioning + Burn-in. What Do YOU Do?

[icanhascpu2]

So I got a WD RED coming next week. I'd like some input on what you guys would normally do when getting a new hard drive of this size.

I dont have a NAS setup, but this will be on near 24/7 in a desktop system as a general use behind my 64GB SSD.

So, how would YOU partition the drive. Not at all? I'm considering partitioning the first 10% or so for things I access a lot that I dont want to clog my SSD with. Is there a better plan maybe?

Also, I want to be able to test it fully to sort out bad sectors and whatnot so I can do that within the RMA threshold if needed. What are some good tools for that?

Thanks!

 

[BFG10K]

Partition it based on how your arrange your data. I personally put games at the edge of the platter and my "dumb" data on inner partitions.

I don't bother with burn in, but you could run a low-level format/chkdsk/HD Tune test before you start using it.

 

[bryanl]

HDDscan

 

[icanhascpu2]

Partition it based on how your arrange your data. I personally put games at the edge of the platter and my "dumb" data on inner partitions.

I don't bother with burn in, but you could run a low-level format/chkdsk/HD Tune test before you start using it.

Yeah thats what I was thinking of doing. Main game on SSD, other games on 128-256GB partition.

Thanks guys

 

[Emulex]

get it nice and warm, full format, and several fills with teracopy for about 1 week straight - verify of course. That will bring out any bugs quickly!

 

[Charlie98]

I just got a 2TB Red for my HTPC... I just stuck it in, formatted it up and let it roll.

 

[icanhascpu2]

Thanks. If this were a HTPC Id probably do that as well. But its a semi powerful desktop system, so I thought Id put a bit more thought into it as it will be partitioned however way I end up doing probably its entire life.

Emu, wow one week lol Well I think I could for several full read/write verification but a week might be too long for my patience Terrcopy looks like just a copy tool rather than really aimed at this one solution isnt it? Clearly I can just do basic full formats to it, but what Im concerned about is if their are special things that arnt accounted for with simple methods like that that a utility aimed at this would be more likely to address in a HDD burn-in. So I dont get surprised later because a terracopy/full format didnt expose a vulnerability. I thank you for the suggestion regardless!

Anyone understand what I mean?


Now that I think of it, I wonder if si-soft sandra has something like this built in.

 

[Tsavo]

No real point to multiple partitions on a non-OS drive.

Also, no real point to 'burn-in testing'. I used to do all that hocus-pocus, but then I stopped. My drives don't last any longer or die any sooner because of it.

I had a Red as 2ndary drive to my SSD, but stopped using it for that. It's too slow for anything other than light work.

 

[Charlie98]

Thanks. If this were a HTPC Id probably do that as well. But its a semi powerful desktop system, so I thought Id put a bit more thought into it as it will be partitioned however way I end up doing probably its entire life.

Actually, my HTPC is a semi powerful desktop and the media I have stored on the 2x 2TB drives (1 Seagate, 1 WD Red) is no less critical. I sure didn't do any burn-in or testing of the other 11 HDD's I've installed in the past 2 years.

Also, no real point to 'burn-in testing'. I used to do all that hocus-pocus, but then I stopped. My drives don't last any longer or die any sooner because of it.

That's kind of my thoughts... Install and go... and BACKUP!

 

[icanhascpu2]

No real point to multiple partitions on a non-OS drive.

Also, no real point to 'burn-in testing'. I used to do all that hocus-pocus, but then I stopped. My drives don't last any longer or die any sooner because of it.

I had a Red as 2ndary drive to my SSD, but stopped using it for that. It's too slow for anything other than light work.

Actually, my HTPC is a semi powerful desktop and the media I have stored on the 2x 2TB drives (1 Seagate, 1 WD Red) is no less critical. I sure didn't do any burn-in or testing of the other 11 HDD's I've installed in the past 2 years.



That's kind of my thoughts... Install and go... and BACKUP!

The point of partitioning the Red or not is to have a small slice of the best-performance-on-drive dedicated to certain higher demand but large things (when SSD comes down to 10c/GB, Ill say goodbye to all this), and the rest for data that is not as speed sensative, something Tsavo might have want to considered before regarding the drive as 'too slow' ಠ_ಠ http://www.anandtech.com/Gallery/Album/2223#1. Meaning you were pulling data from all over the drive, likely from the slower parts rendering you with low access time average *ontop* of low throughput across the board (sequential, random etc). Guess what helps stop that? As the PC is my main game machine, its going to serve more than videos and surf the web. Thus considering sliding the drives plates outer section into a partition for large hungry games to improve access time is relevant.

The point of burn in isnt to make the drives last longer, it is to find any weaknesses in the drive sooner (before RMA limit) rather than later (have to deal with warranty and risk losing important data). So it not 'hocus-pocus', its responsible computing.

I use to "install and go", but then I got some bad drives and bad performance over the last 15 years, and wised up to be more mindful of such things and be preemptive in their care. The Russian roulette method isn't the best, and you may want to consider out of your 11 hard drives, you have not filled them all, and the errors may lay in a sections you've yet to fill in two years, something I will be sure about rather than risk my data, as I'm guessing you don't burn-in your backups either. A very bad and risky method for data longevity.

I can certainly understand not wanting to bother, but don't pawn it off as a good reason NOT to do it. I'm simply asking if anyone knows of a good utility for it.

 

[dma0991]

Burn-in can only detect factory flaws within the first few months. Have bought two WD Green 3TB recently and haven't filled it with important data just yet, as a precaution.

Its about a month old and I've run WD Data Lifeguard's Extended Test about twice. Other than that, I just let it run in my PC normally to verify that it isn't a DOA unit. Occasionally, I check CrystalDiskInfo to see any anomalies in this duration.

Its merely a precaution and not a guarantee that you will have a more reliable HDD or longer lasting. I've had a friend whom I recommended to do the same routine. He didn't and it died 2-3 months after purchase, taking his data along with it.

 

[icanhascpu2]

Burn-in can only detect factory flaws within the first few months. Have bought two WD Green 3TB recently and haven't filled it with important data just yet, as a precaution.

Its about a month old and I've run WD Data Lifeguard's Extended Test about twice. Other than that, I just let it run in my PC normally to verify that it isn't a DOA unit. Occasionally, I check CrystalDiskInfo to see any anomalies in this duration.

Its merely a precaution and not a guarantee that you will have a more reliable HDD or longer lasting. I've had a friend whom I recommended to do the same routine. He didn't and it died 2-3 months after purchase, taking his data along with it.

Yes, Im not under the impression that burn-in utilities can travel though space and time to fix errors that will only be present a year from now (id buy that). Their only goal is to find existing flaws. A lot can happen between sitting on a warehouse shelf for months and being shipped across states to my door. I want to rule that out as being an issue that will show itself months from now when I try and write over a damaged sector that was present from the time i got it, and instead general wear and tear and old age can take my drive from me instead. *single tear*

Checking SMART status as youre doing is an additional and wise step, but not a replacement as some seem to think.