![]() ![]() ![]() 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. Know Your Systemįirst, it is important to understand that Silverstack does not communicate directly with your hardware but through the operating system. MacOS is the conductor in the orchestra of software components (e.g., drivers, firmware, virtual file systems) playing together over your hardware. Any piece of software or hardware in the chain (e.g., hubs, cables, reader) can be faulty and the potential cause of errors. 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. If a simple retry does not help, you need to try to track down the reoccurring errors yourself. That’s possible if you investigate when and where the error happens and try to see a pattern. ![]() To be able to do that, you need to know what is happening during an offload in Silverstack. 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. If the (file-)system or Silverstack’s metadata scanner notices any error related to this process, the wizard will show it: A scanning error got flagged up in the offload wizardĮven if the wizard indicates no error, you should check the file list for completeness as it is the reference for the offload job: what Silverstack did not find at this point, it won’t copy later. This is even more important when offloading from shared or virtual volumes as those might change their contents (e.g., during initialization) without your awareness. Once the “Offload” button is clicked, Silverstack adds a new offload job to its queue and reliably keeps track of its progress, even when terminating the application, or the system crashes. Per default settings, file after file is read on the source and written to the destination(s). The files will appear on the destinations with the extension “.pfncopy” for as long as the copy is incomplete and until Silverstack has read them again to ensure they are identical to the respective source files – this process is called verification.ĭepending on the configuration in the offload wizard, the verification will either be performed after a single file is copied and before copying the next one (default: “Included in Copy Job”) or as a separate job after all files are copied (option: “Separate”). Verification behavior configuration in the offload wizardĪdditionally, there is the option of “Source Verification”. This refers to the process of also rereading the source after the copy’s completion. This makes sure that the source files did not change in the meantime and can detect if the source volume is unreliable concerning read consistency. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |