That's the wrong thing to do-there's just no other way to put it. We hear all the time that people are using images to "make more efficient use of space".
GLOBALSAN HIGH SIERRA DRIVER
Don't format it as a foreign file system (like NTFS) and use a special driver to access it. Don't write to an image stored on that drive. That's going to be your most reliable, bootable solution. This: you should write directly to a local drive. This should be obvious, but is often ignored in the search for convenience (or expedience): the fewer layers there are between your computer and the storage device, the more reliable your backups are going to be. So let's take a moment to talk about "best practices" for backup devices and methods. But if you implement a successful backup plan, you can protect your data, even in the face of this sort of adversity. Whether the problem is a bug in the OS or a hardware error, failure is inevitable. Failure is Inevitable, Success Requires Planning
GLOBALSAN HIGH SIERRA FULL
This looks to be another manifestation of a problem we've known about for years (and documented in the User's Guide back in 2006): when an image can't grow, whether due to disk full errors, or because the host volume doesn't support large files (eg FAT32/EXT2), writes to that image can fail catastrophically. Worse still, double-checking the data seems to indicate it's OK-even a checksum succeeds-until you eject, at which point the data is lost. We've been getting a lot of questions lately about the APFS image bug ( recently documented by Mike Bombich, author of CCC) where, when an image container can't grow, APFS doesn't reliably indicate an error, which can silently lose data.
0 kommentar(er)
