If you move on to edit/view another photo *before* the windmill stops and clears, the file has not completed its update and will be corrupted. Chg_canon is correct: check your workflow.
If you do a search for "instant jpg from raw" there is a free program that will help extract the jpg.
DWU2
Loc: Phoenix Arizona area
Does the issue happen with both the CF card and the SD card? In the past, I had some issues with a bent pin on the camera which impacted the CF card.
Fat32 is used by Linux bases systems and is more problematic than other file systems on Linux. I use Linux as my primary machine with a large Windows 10 virtual machine to do my edits. Fat32 used to be needed to copy files between Linux and Windows but no more. Most people now use ext4 for Linux.
I have a QNAP NAS and have not had any issues with corruption from my CR2 and CR3.
It is possible that there is a bad block on the drive. Are you setup in a Raid configuration? Some people like Raid 0 which is just a copy, but I typically use Raid 5 or 6 with parity. If a file becomes corrupt, it can be rebuilt using the parity bit.
TriX
Loc: Raleigh, NC
gouldopfl wrote:
Fat32 is used by Linux bases systems and is more problematic than other file systems on Linux. I use Linux as my primary machine with a large Windows 10 virtual machine to do my edits. Fat32 used to be needed to copy files between Linux and Windows but no more. Most people now use ext4 for Linux.
I have a QNAP NAS and have not had any issues with corruption from my CR2 and CR3.
It is possible that there is a bad block on the drive. Are you setup in a Raid configuration? Some people like Raid 0 which is just a copy, but I typically use Raid 5 or 6 with parity. If a file becomes corrupt, it can be rebuilt using the parity bit.
Fat32 is used by Linux bases systems and is more p... (
show quote)
RAID 1 is mirroring - RAID 0 is striping for speed. The rotating parity of RAID 5 (or 6) is designed to protect against missing data from a drive failure, it’s not designed to repair a corrupted file.
I used to do mirroring but my NAS has 4 10 tb drives and 5 4tb sides. I use Raid 6. I have had corrupt files rarely but I have been able to fix everyone buy rebuilding the partition.
Unfortunately, yes. Also, the corruption rarely occurs on successive images.
TriX wrote:
RAID 1 is mirroring - RAID 0 is striping for speed. The rotating parity of RAID 5 (or 6) is designed to protect against missing data from a drive failure, it’s not designed to repair a corrupted file.
Drobo uses a proprietary RAID approach.
gouldopfl wrote:
Fat32 is used by Linux bases systems and is more problematic than other file systems on Linux. I use Linux as my primary machine with a large Windows 10 virtual machine to do my edits. Fat32 used to be needed to copy files between Linux and Windows but no more. Most people now use ext4 for Linux.
I have a QNAP NAS and have not had any issues with corruption from my CR2 and CR3.
It is possible that there is a bad block on the drive. Are you setup in a Raid configuration? Some people like Raid 0 which is just a copy, but I typically use Raid 5 or 6 with parity. If a file becomes corrupt, it can be rebuilt using the parity bit.
Fat32 is used by Linux bases systems and is more p... (
show quote)
Drobo uses proprietary RAID. I'll contact them and see if they can recover singe images. Thanks for taking the time.
TriX
Loc: Raleigh, NC
pfazio wrote:
Drobo uses a proprietary RAID approach.
Have you red the white paper on their “beyond RAID” implementation? The net-net is they use RAID 1 (simple mirroring) with 2 drives, RAID 5 with 3 or more and RAID 6 (dual parity RAID 5) with 4 or more drives. Again, none of these RAID implementations are designed to protect against corrupted files or file systems - they are designed to protect against the loss of a drive or to increase speed. RAID 5 was actually designed/optimized to allow multiple users to access small files simultaneously - it’s a compromise for a single user with large (image) files. It essentially writes a block of data to one drive, and rotates the parity information across the remaining drives. Once you’ve eliminated simple HW explanations for your problem (corrupted files from the camera cards, bad reader, bad USB cable, etc), the most likely cause is a file system issue or RAID controller issue.
To isolate the cause. Write the same image to both the computer internal HD and the RAID, and then look at each. If only the one stored on the RAID is bad, you have a bad cable, a bad RAID controller card, a failing drive, or a corrupted file system. If both are bad, then look upstream at your camera, card, reader (if used) and cable.
If you want to reply, then
register here. Registration is free and your account is created instantly, so you can post right away.