When opening the offload wizard for a folder or volume (source), Silverstack scans its content, tries to identify the recording device, and reads-out first metadata to give you a condensed overview of what’s actually there.
To be able to do that, you need to know what is happening during an offload in Silverstack. That’s possible if you investigate when and where the error happens and try to see a pattern. If a simple retry does not help, you need to try to track down the reoccurring errors yourself. In most of those cases, macOS has only limited information available: While it informs Silverstack reliably that a specific error happened (e.g., “Can’t access file”), it only rarely adds the obviously interesting information, why an error happened.
#SILVERSTACK CANCEL JOBS SOFTWARE#
Any piece of software or hardware in the chain (e.g., hubs, cables, reader) can be faulty and the potential cause of errors. MacOS is the conductor in the orchestra of software components (e.g., drivers, firmware, virtual file systems) playing together over your hardware. Know Your Systemįirst, it is important to understand that Silverstack does not communicate directly with your hardware but through the operating system.
#SILVERSTACK CANCEL JOBS VERIFICATION#
But what is to do if Silverstack indicates that your offload or verification job fails? In this article, we’re diving into error messages and strategies to deal with them.
Most of the time, everything just runs smoothly but to detect the rare but critical cases where something goes wrong, you are using Silverstack: It has elaborate mechanisms to track this process, double-check for integrity and alert you in case something is not as it should be. However, surprisingly, many things can go wrong when reading a file from one device and creating a copy on one or multiple others. When offloading a camera mag, you want to be absolutely sure that all files are copied correctly.
0 kommentar(er)
