Welcome to our community

Be a part of something great, join today!

Log in
  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

New Workstation Build - i7 X99, Titan X, Overclocking...

I'd love some feedback on my system and if anyone thinks that a TitanX would be worth the cost/performance gains for me from a GTX 680. Recently with the Dragon upgrade my computer could definitely use a bit of help wherever it can.

I've tried maxing out my system, currently running at 4.4ghz on the old 3930K and 64gb DDR3 memory.

I'm tempted to order the superclocked Titan X or wondering if I should hold off with my system having bottlenecks being a few years old now.

Any advice would be appreciated.

nQoknCZ.jpg


JqgQYh3.jpg
 
Last edited:
A Titan X card would be a good upgrade since you can move it to a new system or upgraded system later if you upgrade to the X99 platform. The current system you have wont push the Titan X card completely but it will help considerably.
 
@Jeff @Eric

My Promise Pegasus2 R6 keeps unmounting itself when I'm not writing on it, then I have to the reboot full system. So basically I can use the drive for 5-10min after reboot and then it unmounts if I'm only reading or not using it. Do you have any ideas why it'd do that?
 
Yes turn off the drive power management and see if the volume still unmounts. Also make sure the firmware is up to date for the storage unit.
 
Eric Bowen said:
Yes turn off the drive power management and see if the volume still unmounts. Also make sure the firmware is up to date for the storage unit.
Click to expand...

Same problem with drive power management off and latest firmware on the storage unit. It looks like a Thunderbolt issue because the drive also disappear from Connected Thunderbolt devices panel. I never had this issue with my MBP.
 
Ok that sounds like you have a raid volume issue. I would suggest you get the data off the raid volume and redo the raid config. Make sure you run a full initialization when you configure the raid. Also what systemboard do you have in this system ie model number?
 
Eric Bowen said:
Ok that sounds like you have a raid volume issue. I would suggest you get the data off the raid volume and redo the raid config. Make sure you run a full initialization when you configure the raid. Also what systemboard do you have in this system ie model number?
Click to expand...

Ok I see, I never had this issue with my MBP though, I ordered my RAID card and Seagate drives for the X99 so I can move the data and do a full initialization. My Pegasus is formatted in HFS+, do you think it can be an issue? I'm using Paragon HFS+ on Windows. Here are my settings:

pegasus2-r6-settings.png
 
Yes the HFS+ adds another layer to the translation of block data to partition data for the OS. The Volume could be unmounting from that. However I have not had anyone call using the Paragon HFS+ software with that issue. Do you have a OSX system that you can move the unit to and run Disk utility to verify and repair the volume. You want to backup the data though before you run this in case there are raid volume issues. Raid Volume corruption could cause Disk Utility to collapse the volume if it's already compromised. Do you not have standard external storage to move the data to ie a backup option somewhere?
 
Eric Bowen said:
Yes the HFS+ adds another layer to the translation of block data to partition data for the OS. The Volume could be unmounting from that. However I have not had anyone call using the Paragon HFS+ software with that issue. Do you have a OSX system that you can move the unit to and run Disk utility to verify and repair the volume. You want to backup the data though before you run this in case there are raid volume issues. Raid Volume corruption could cause Disk Utility to collapse the volume if it's already compromised. Do you not have standard external storage to move the data to ie a backup option somewhere?
Click to expand...

I just ran a verify from my MBP and everything is fine.
 
What systemboard are you running with Thunderbolt ie model for the windows system? Have you run a parity verification or integrity scan on raid volume anytime recently or in the past? What Intel Thunderbolt driver do you have installed btw?
 
Eric Bowen said:
What systemboard are you running with Thunderbolt ie model for the windows system? Have you run a parity verification or integrity scan on raid volume anytime recently or in the past? What Intel Thunderbolt driver do you have installed btw?
Click to expand...

I have an Asus Rampage V Extreme motherboard with ThunderboltEX II Dual pcie card. I never ran any verification or integrity scan on raid volume in the past. I have the Intel Thunderbolt Driver V1.5.1.1 installed (from Asus website): https://www.asus.com/us/Motherboards/ThunderboltEX_IIDUAL/HelpDesk_Download/
 
Well I know the Dual card did not work in the past though the latest bios updates were suppose to fix it. This may be a resource issue with the Dual card still or AIC support issue. Go into the bios and select F7 to go to advanced mode. Go to the advanced tab at the top. Then go to the Intel Thunderbolt. Go to AIC support and turn it off. Then go down to TBT device i/o resource support and turn that on. Once that is on a new menu item appears Resource I/O per PHY slot. Change that from 4 to 8. Hit f10 and select save changes and reset. See how the Thunderbolt storage acts then. BTW you need to run the Parity verification on a regular basis as maintenance on Raid 5 or 6. That is the only way to catch parity corruption before it compromises the raid volume. A raid 5 volume will collapse at some point if the parity data corruption becomes to significant and HFS+ is not very robust versus corruption. NTFS is very robust versus corruption while the performance is less than HFS+. That is the trade off.
 
Eric Bowen said:
Well I know the Dual card did not work in the past though the latest bios updates were suppose to fix it. This may be a resource issue with the Dual card still or AIC support issue. Go into the bios and select F7 to go to advanced mode. Go to the advanced tab at the top. Then go to the Intel Thunderbolt. Go to AIC support and turn it off. Then go down to TBT device i/o resource support and turn that on. Once that is on a new menu item appears Resource I/O per PHY slot. Change that from 4 to 8. Hit f10 and select save changes and reset. See how the Thunderbolt storage acts then. BTW you need to run the Parity verification on a regular basis as maintenance on Raid 5 or 6. That is the only way to catch parity corruption before it compromises the raid volume. A raid 5 volume will collapse at some point if the parity data corruption becomes to significant and HFS+ is not very robust versus corruption. NTFS is very robust versus corruption while the performance is less than HFS+. That is the trade off.
Click to expand...

I turned on TBT device i/o resource support on with Resource I/O per PHY slot to 8 and it seems to be working great for an hour now! Thank you very much Eric for your time and patience! I'll do some Parity verification on the volume as soon as I have it fully backed up. What do you use to do that?

Other question unrelated: In Resolve 12, I can play/work on my r3d 6k footages seamlessly but it's impossible to play/work on H264 4k footages. I have some footages from the DJI Phantom 3 and it's so slow not even a frame per second. Is there any alternative than having to transcode everything to dpx...
 
The storage unit should have a management utility that allows you to configure the raid volumes and run maintenance. Each management is different in what they call the parity verification. Areca for example calls it a Raid Consistency Check. Intel and LSI call it Consistency Check. So it depends on what SAS controller is used in the unit. H264 was not really designed ie optimized for 4K. The highest H264 level or profile included 4K but it does not perform nearly as well as other codecs with realtime playback. XAVC and H265 were designed for 4K so they perform far better. I would suggest converting the H264 4K to Cineform or DNxHR though since either will not lower quality and also have far better realtime playback performance.
 
Last edited:
Eric Bowen said:
The storage unit should have a management utility that allows you to configure the raid volumes and run maintenance. Each management is different in what they call the parity verification. Areca for example calls it a Raid Consistency Check. Intel and LSI call it Consistency Check. So it depends on what SAS controller is used in the unit. H264 was not really designed ie optimized for 4K. The highest H264 level or profile included 4K but it does not perform nearly as well as other codecs with realtime playback. XAVC and H265 were designed for 4K so they perform far better. I would suggest converting the H264 4K to Cineform or DNxHR though since either will now lower quality and also have far better realtime playback performance.
Click to expand...

Awesome thanks again for all those info! What would you use on Windows to quickly convert to DNxHR or Cineform? Sorry for all those Windows newbie question, I owe you some drinks after that!
 
You must log in or register to reply here.
Back
Top