![Why Are My Files Missing a SHA-1?]({"bg": "//theme.zdassets.com/theme_assets/34506/e106cc8a79a6a41c781c71d999cffaa33b481de7.jpg"})
![Why Are My Files Missing a SHA-1?]({"bg": "//theme.zdassets.com/theme_assets/34506/d38d9cc5a4fcb160800cb7a8f0e0cb60aaa36d2e.jpg"})
When large files are uploaded to the B2 servers they are broken up into smaller parts (using the b2 upload_part call), each part of the file is assigned a SHA-1 checksum. The entire large file itself is not assigned a SHA-1 automatically. This is why you are not seeing SHA-1's for certain files.
If you do know the SHA-1 for the entire large file being uploaded, we do recommend specifying the SHA1 in the fileInfo during the call to b2_start_large_file call.
Inside the fileInfo header for the b2_start_large_file call, specify one of the keys as large_file_sha1 and for the value use a 40 byte hex string representing the SHA1.
Articles in this section
- Not Receiving SMS on Indian Phone Number
- Does B2 have CORS headers support?
- How to Gather Logs for Hyper Backup or CloudSync on Synology NAS
- Why am I receiving a 'Not Allowed' alert for Odrive?
- Why Are My Files Missing a SHA-1?
- Why Do I Receive an 'Unauthorized' Error When Downloading Files?
- Why am I Reaching Class C Transaction Caps with Synology?
- Support or Feedback for MSP360 (formerly CloudBerry)
- Support or Feedback for Synology Cloud Sync
- Limitations to the B2 Web UI