[Reinis Traidas]

This indeed seems to be the case.

I sent all diangnostic logs to ATTO and their reply was that the drive may be faulty.

I have kept the chassis door open since the last time the group got degraded – and guess what – it’s still up and running fine.

So currently it appears that the TRX8 is suffering from heat related issues with the lowest drive trays – 7 and 8. Keeping the door open and/or aiding ventilation from the front of the unit seems to help/solve this issue.

[Reinis Traidas]

Thanks for that note, I will keep observing my TR8 unit to see if heat becomes an issue. So far it has been running well.

[Reinis Traidas]

Yes, the rebuilt went fine, all drives are OK now, flashed the controller to the latest FW, updated the BIOS on the HP Z820 and all seems well now. We’ll see how long the RED drives last.

Performance is good, averaging 740-820MB/s on the desktop.

[Reinis Traidas]

Hello there,

I did a rebuild of the group and it is now back to normal. I also updated my computers BIOS to the latest, as well as flashed the R680 to the latest FW. I will see how the RAID performs and if I get further parity errors or not.

I do want to point out, though, to whoever might google and stumble upon this is – my experience with the Atto R680 in the HP Z820. After installing the card, all my fans in the Z820 went nuts and kept running at very high (and loud) speeds right after turning the thing on. They just wouldn’t slow down. I couldn’t find any info on this, but after updating the BIOS to J63 v03.65 and after flashing the R680 to the latest, the fans went quieter. I don’t know if this is the R680 that is just running hot or the fan daemon on the card itself (I read that some Mac Pro’s have had heat/fan issues with it).

Anyway, I am happy with the performance of the R680 with the Sans Digital enclosure and WD RED drives. It’s giving 680-780MB/s easily and greatly decreasing render times for .tiff sequences. Before, rendering 15 minutes of Prores 444 footage to XYZ Tiffs would take about 50 minutes if done on a single internal SATA drive. With the RAID6 group, that time went down to about 15 minutes, so practically real time, which is great.

I’m probaby getting a “hot spare” HDD just to keep on the shelf incase any of the drives fail.

[Reinis Traidas]

I’ve initiated a rebuilt on the “degraded drive”, will see if that makes the error dissapear.

[Reinis Traidas]

Davinci Resolve wouldn’t accept XDCAM wrapped in .mp4, so I rewrapped them to .mov using FFmpeg. That worked fine on a Mac, but the Quicktime decoder for Windows doesn’t support XDCAM and therefore, neither does Adobe CC.

So re-wrapping to .mov is not recommended if you travel between PC/Mac on projects. I guess the only simple thing to do is to ingest via Adobe Prelude (a great tool, btw) and transcode to DNxHD Quicktimes which are supported everywhere. If an edit has been started, then you need to relink all to the newly transcoded files. A hassle, but there is no other way to get PC, Mac, Adobe and Resolve to play nice together with XDCAM.