raid0 failure within a month- WD 6tb

[Todd Perchert]

Anand – sounds like you want to make sure that you won’t have a similar problem even with RAID-1. It sounds like you have 3 x 2TB & 2 x 6TB & a system drive??? I would check to make sure you have good power. You need a pretty good power supply to run all that. I’ve seen issues where a PC was so close to the edge of the power output of the PSU, that it worked fine for a short time, then at some point it would lose a drive and cause havoc on the RAID that was internal. This could be the case here. I’m just throwing that out there as something to check on.
Good Luck!
TC

[Anand Kamal]

Thank you Sorin and Todd.. it was informative….

I use cooler master 1000w power supply… there may seldom be voltage fluctuations. Yes, I now decided to unplug all the hard disks internal and external except the raid which i will be working on..

[Neil Sadwelkar]

Where did you come across a data rate of 150 Mbps for Magic Lantern Raw? I checked and it appears to be in the 60-80 Mbps range. Mind that this is megabits/sec.
So, even 150 Mbps is just under 19 Megabytes/sec MB/sec while 60-90 Mbps is 7.5-11.25 MB/sec.
None of these need RAID0 with two SATA drives. Even a single drive with a mirror for safety will do just fine.

Ideally you should put one drive inside your machine and use a good drive like a GTech as the mirror and keep it outside the PC connected by USB3. And use a cloning software to keep them in sync. This way you have a redundant drive and an offsite backup too.

———————————–
Neil Sadwelkar
neilsadwelkar.blogspot.com
twitter: fcpguru
FCP Editor, Edit systems consultant
Mumbai India

[Anand Kamal]

thanks Neil… Sorry I meant 150 MB/s…Mine is full HD cinema DNG files. One frame is almost 4MB in size and 4 X 23.976seconds = 96 MB/sec… Also i practically faced difficulty in reading those cdng files in premiere.

I initially planned for a resolve-premiere roundtrip. Now i plan to edit in premiere directly. But it takes time to read. So I was told I can get the read speed and space via Raid. Now that I can edit in premiere directly, i can save spaces by not producing proxies. So raid 1, despite halving my space, lends me the read speed (double, like raid0). My footage is 3TB, no proxies, direct output to DCP (theatrical purpose) drive. As my writing speed is going to be normal anyways, I can write it to external drives too.

I was not aware of the mirroring technique. However, it could be useful for h264 dslr files i presume.

Trivia: I am a more of a screenwriter frm bio-background than a computer-guy. This being an indie feature, I’m doing it all myself.. Sorry if i m not good with computer-jargon 🙂

[Neil Sadwelkar]

Oh all right. CinemaDNG files, that explains the data rate.

However, I still feel that even if Premiere Pro CC supports native files, its ‘healthier’ for the system if you work on down-converted files like ProRes LT or even ProRes Proxy. Everything will move more fluidly in the timeline with this workflow.

About space taken by converted files, that shouldn’t be much. Let’s say you have 20 hrs of CinemaDNG at the stated 4 MB/frame. It will take up 6.91 TB. When converted to ProResLT the same 20 hrs will occupy just 687 GB. And it will play and render very fluidly.

Since you’re on Windows you may have trouble converting to ProRes. You can select another codec, like DNxHD or any compressed codec delivering about 100 Mbps data rate and get very good looking pictures and saving space.

If you happen to be in India (totally guessing from your name), let me know, I’m in Mumbai and can help you with this workflow.

———————————–
Neil Sadwelkar
neilsadwelkar.blogspot.com
twitter: fcpguru
FCP Editor, Edit systems consultant
Mumbai India

[Anand Kamal]

So nice of you to think about helping me sir. I am in Chennai.

I was exactly doing the process of creating proxies that you mentioned. Of late, I faced troubles with the roundtrip as I cannot sync the xml from premiere to resolve (may be because of the converter I use to extract cdng files from raw).. not sure. Also I will have to check for cuts and transitions and audio sync. Only because the xml did not re-sync the videos in resolve for master coloring, I decided to edit cdngs in premiere directly. I found I had realtime playback, but some effects slowed it down. I render some group of files in timeline and carry on with edit in such cases.

My raw footage is almost 3TB, my extracted cdngs would be around 3.5Tb. Good thing is that I viewed all my raw footage even before extracting cdngs and I have selected the clips that will be imported to NLE. Based on the size that i noted (3TB), I think the total running hours would be around Eight.

I am following you in twitter and glad to have your help in case of doubts 🙂

[Anand Kamal]

friends, after the above suggestions from you all I have been using raid1 controlled by my asus z87pro motherboard, with two 6TB WD red turned to raid1.

The Intel Rapid Storage Technology software showed “raid1 degraded” and “port missing, unknown,” when I restart, it started auto-rebuilding (i think it switched the mirror disk) the raid and worked properly for a day.

After a day again, it showed the same problem. I deleted the raid volume and I am using the disks as non-raid members but still in Raid mode (not AHCI mode). Even after i delete the raid volume, i still have data (same, mirrored while raid formation) in both my 6TB hard disks. As non-raid disks, I continued to work in premiere pro. HD tune pro software did a health check up for both of my 6TB hard disks and they were perfect. I carried on with my edit but yesterday, Intel Rapid Storage Technology popped up a message “sata disk removed.” I just restarted the system and is now fine.

Two times, it was port 0 that was shown missing and yesterday, it was port 4 missing. I never switched the port of the two drives but once ensured if it is connected well with enough power supplies.

Is this a connectivity problem? or what should I do to avoid this problem.. Is something failing while accessing the data in the two disks? Everytime, the problem occurred while I work in premiere pro.

thanks,
anand